Quote:
Originally Posted by Edward Edgemenace
If anything, it makes client-side rendering slower (two groups of textures have to be loaded and reloaded and re-rendered now.) But since 90% of the "lag" issues that people notice and complain about are server-side lag issues, I'm more confused than ever, about this particular "enhancement."
|
I don't think it's a bad idea at all. If you're farther away, you don't need to see the details. Having a higher detailed texture loaded when you can't even appreciate the details is a waste. Regarding reloading the textures over and over, the textures are already in memory. This enhancement is meant for people with a lower-end system configuration and perhaps not as much video memory. Now if there's an issue with the lower-end textures up-close, then there's probably a problem with graphic settings on the client.
Quote:
|
Originally Posted by Edward Edgemenace
Meanwhile, client-side memory management is still non-existent. Scene changes still don't relinquish memory, but now the "loading screen" error can even happen when launching (which never happened before - only when dinghy-boarding someone else's ship, in the past.)
|
Non-existent you say? No doubt about it. ToonTown has had a memory leak since its inception and I wouldn't doubt that PotCO is the same way. Disney isn't really known for its memory conservative programmers. I wouldn't expect memory management to be on their top 10 list of things to fix. Disney's
solution so far is to restart the client.