Rendering: what the first response contains
Many cam platforms are built as JavaScript apps. The server sends a nearly empty page, then scripts fill in the performer grid, often from a live feed. Google can run JavaScript, and Google's Martin Splitt has said that most pages now render within minutes of being crawled. But the process still has a queue, it has timeouts, and search engines do not click buttons or wait for a websocket to deliver the next batch of performers.
The practical rule: for every page type you want indexed, the first HTML response should already contain the main text, the performer names and the links to other pages. Server-side rendering, or pre-rendering those templates, is usually the cleanest way to get there. Live elements can still update in the browser on top of that.
URLs matter too. Addresses built with a # fragment, such as /#/model/name, are not treated as separate pages. Each model and category needs its own real path.