Stuttering from Load Custom Textures

[ThaHalcyonX]

actually it loads them into ram when needed and drops them when they're not, the issue might be that custom textures isnt using the gpu

[JMC47]

It has to decode them before putting them into ram.

[Zexaron]

Major Update:

This performance issue was indeed due to the way custom textures were loaded and uncompressed and has been fixed by developing support for native compressed texture loading, which also fixes prefetching as well.

Simultaneously, RAM & VRAM requirements were greately reduced. It should be possible now to load the full Hypatia's HD Pack for Zelda WW without having to reduce it's size, with many GBs of RAM to spare.

It should apply for all games not just Zelda.

At this moment it is not yet part of nightly, but should definitely be a non-issue for any versions post 5.0-stable (for those that reading this in future)

[JosJuice]

(04-23-2017, 09:15 PM)Renazor Wrote: but should definitely be a non-issue for any versions post 5.0-stable (for those that reading this in future)

No, not for any version post 5.0. There have already been many development builds released that don't contain the change. You can't even know for sure that it'll be in the next stable release - the PR isn't even merged yet! (It is likely that it will get merged, though.)

[Zexaron]

(04-23-2017, 09:21 PM)JosJuice Wrote: No, not for any version post 5.0. There have already been many development builds released that don't contain the change. You can't even know for sure that it'll be in the next stable release - the PR isn't even merged yet! (It is likely that it will get merged, though.)

There are 2.5 years between 4.0.2 and 5.0 - How many chances are there that even if the next stable after 5.0 comes half or 3 times the less time and that this still wouldn't be included in it?

Secondly the error I mentioned happened with or without loading any custom textures, and Stenzek confirmed to me he already fixed it, I tested Zelda WW for many hours yesterday on his build, haven't seen absolutely any problems.

This is a substantial feature which I think should block the next stable until it's been thoroughly, set deadlines are not something that happens in the natural world, they are artificial corporate constructs.

People and humans make programs, programs don't know themselfs if they're correct or what should or shouldn't be more or less important.

Obviously anyone has the full freedom to protest these conclusions.