Loading...
  OR  Zero-K Name:    Password:   

To bloom or not to bloom

6 posts, 324 views
Post comment
Filter:    Player:  
sort
4 years ago
There is a widget (distributed with the game, so gadget?) that can enable bloom. This is not about that widget.

In the game settings under Graphics (no, not my video card's) there is experimental HDR and bloom support. When enabling bloom, controls disappear. Minor issue, and I can't say that my configuration is not at fault, but this is the only setting that behaves that way.

Pictures and infolog (which I will keep there for a few days) are here:

http://rndt.rf.gd/zk.php

The page also describes some other problems that I encountered.
+1 / -0


4 years ago
The bloom is done with a widget. The widget crashes when you enable it. The widget does not seem to crash for anyone else. Weirdly, it checks whether the texture that is being created exists and should say if creation has failed.

[f=-000001] [SpringApp::MainEventHandler][SDL_WINDOWEVENT_SHOWN][2]

[f=-000001] [cawidgets.lua] Error: Error in DrawScreenEffects(): [string "LuaUI/Widgets/gfx_deferred_rendering.lua"]:546: bad argument #1 to 'glRenderToTexture' (string expected, got nil)
[f=-000001] [cawidgets.lua] Error: Removed widget: Deferred rendering
+0 / -0
Does this mean that Bloom() is somehow called before ViewResize()?

E: And only on my machine?
+0 / -0


4 years ago
ViewResize() is called manually at the end of InitilizeShader, which should be called as soon as an option changes its value. You could test it by copying the widget and putting Spring.Echo at various points to check the order.
+0 / -0
Hm. OK. I'll try that. Never tried to override vfs widgets, do I need to disable the "old" one and change info in the copied one for it to work, or can I just use it like any other widget that I made myself and it will replace the default one?

E: Never mind, got the widget and it behaves just like the old one, so here's a necessary step for STR: Must start with HDR enabled and Bloom unchecked, else the bug does not occur. Also, a way to bring back the controls is to toggle the widget on and off. I'll investigate the reason it does this probably later this week.

E2: Quick fix is now available (same link as above, the infolog is now gone). Feel free to use or not to use it, or to revert my changes in GetInfo. Hopefully, I didn't cause a massive slowdown with my edit... but I really don't feel like doing any more work on this minor bug. Enjoy.
+0 / -0


4 years ago
Thanks. It seems to work.
+0 / -0