HUDCaching slows down TC wand focus/goggles lens selection menus
Evan555alpha opened this issue ยท 11 comments
Your GTNH Discord Username
Evan555alpha
Mod Version
1.0.0-alpha33
Java Version
Java 8
Graphics Card Vendor
NVidia
Bug Report
Title, pretty much. When HUDCaching is enabled, the funny purple circle that appears when going to select a wand focus / goggles of revealing lens, slows to a relative crawl, as though its speed is tied to its framerate. Not unusable, but very noticeable. Toggling off HUDCaching solves the issue.
Mod List or GTNH Pack Version
GTNH Pack 2.5.1
Hodgepodge 2.4.34
CodeChickenCore/Lib 1.2.0
UniMixins 0.1.16
GTNHLib 0.2.10
Final Checklist
- I have searched the issues and haven't found a similar issue.
- I have read the known incompatibilities and this is not related to one of those.
- I am running an officially released version. (Or, if I've compiled it myself I plan to fix the issue)
- This issue is not related to a feature that is disabed by default - Shaders, MCPF, etc. [They'll be enabled when they're ready for testing]
as though its speed is tied to its framerate
It actually is after reaching the thaumcraft code
It actually is after reaching the thaumcraft code
Indeed it is, and is always why I unlock my framerate when messing with TC, it's... unpleasant otherwise...
(someone really needs to mixin fix that... hodgepodge maybe? Who do we need to ping to get a fix into hodgepodge or whatever? A configurable speed (based on ticks, unbound by fps) would even be far superior, I want to double/triple its speed even when I'm getting 200fps)
Maybe @Alastors can help :P
Indeed it is, and is always why I unlock my framerate when messing with TC
I'm assuming this is implying higher fps = faster menu?
I have my framerate unlocked, 200 fps and my focus menu is still slow. (with angelica)
Without Angelica, the menu behaves normally.
Angelica caches the rendering calls so it doesn't update as rapidly as it would otherwise, which is much better for rendering performance, but bad when a mod does something stupid like lock functionality to re-render times, lol.
Maybe @Alastors can help :P
I mean I can look into it, but my knowledge in rendering as a whole is limited
hud cache probably needs to be updated to have its own framerate setting, and generally other caches improved so the framerate by default can be higher to prevent edge cases like this, but yeah the issue is TC being framerate dependent here instead of animating using deltas
I'll close this for now then. If it turns out to still be a problem someone can reopen
Was this fixed with #562?