You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certainly a big ask to make, but I'd like to see Woof able to run with even greater performance, allowing for higher resolution, higher framerate, lower frametime, smoother experience on any WAD's maps of basically any size and complexity. I will understand if the devs deem this out of scope for Woof, but I believe it would be of great value to have great performance without sacrificing the vanilla renderer tricks and the tools and behaviors that were built on top of it, for example, any custom Boom TRANMAP tricks are (and correct me if I'm wrong) effectively useless in truecolor and hardware renderers.
Yes, we have plans for a multi-threaded renderer, similar to the KEX port or Rum and Raisin Doom.
smoother experience on any WAD's maps of basically any size and complexity.
Multi-threaded renderer improves performance at high resolutions. If WAD is slow at 100% resolution scale (320x200), it won't improve. Just to keep expectations in check.
Multi-threaded renderer improves performance at high resolutions. If WAD is slow at 100% resolution scale (320x200), it won't improve. Just to keep expectations in check.
Certainly a big ask to make, but I'd like to see Woof able to run with even greater performance, allowing for higher resolution, higher framerate, lower frametime, smoother experience on any WAD's maps of basically any size and complexity. I will understand if the devs deem this out of scope for Woof, but I believe it would be of great value to have great performance without sacrificing the vanilla renderer tricks and the tools and behaviors that were built on top of it, for example, any custom Boom TRANMAP tricks are (and correct me if I'm wrong) effectively useless in truecolor and hardware renderers.
https://doomwiki.org/wiki/Multithreaded_renderer
The text was updated successfully, but these errors were encountered: