Report this content
We want the Dreams coMmunity to be a safe, diverse and tolerant place for everyone, no matter their age, gender, race, sexual orientation or otherwise. If you believe this content to contradict these principles, you can file a report for our coMmunity teams to investigate.
Note that misuse of the reporting tool will not be tolerated.Item being reported:
Something to understand is that not rendering something doesn't mean it takes 0 thermo. Dreams still has to know where it is and its shape and how it looks to figure out all the stuff you described: if it would be on-screen, or occluded (hidden behind other stuff), or close enough to the camera to be worth rendering, or what level of detail ("LOD") it should be rendered at.
And if you were thinking it could load new sculpts into memory (thermo) when they come into view, and go out of memory (lowering thermo) when they can't be seen any more... The problem is that it takes time to turn the sculpt data into an actual sculpt (I'll say it's "decompressing" it, but it's more involved than that) which takes time, especially if the sculpt is high-detail and complex. So you'd see frame stutters when new things are being put into memory, which isn't great.
As for performance gains by not rendering that stuff, or rendering it at a lower detail... Dreams does all of those things automatically for us, which is pretty great :D
If you'd like to talk more about your ideas, and explain what it would give us on top of what Dreams already does, that's great! I just wanted to make sure we're all on the same page regarding how awesomely Dreams already handles this kind of thing ;P