Ok, cool, thanks for the feedback.
I think I will explain why all this:
Basically, the only way that I am not accounting for is keybinds to "quit/exit" or "open" (personally idk why would someone have one, I had "open" keybinds to test NW3 in specific maps and they were particularly annoying when I mistyped them in an online game...(good old FUUUUUUUUUUU moments)
I can account for those too, but the solution would force me to write to the User.ini, and personally I don't want to do that and if 99% of people don't have such keybinds, I won't even worry about it.
Anything else, from going to the menu, typing in either consoles and such, are all ensured (even sudden GPFs that force the game exit, although for this one you would have to run NW3 again for it to auto-fix).
The problem itself is the following: most custom renderers have a property called ZRangeHack, and which is True by default.
This property basically fixes the Redeemer overlapping the HUD, and the FlakCannon as well in the case of 16:9 screens, and in some *really old* video cards the problem of decal flickering on some medium to big distances.
However, this messes up something else: the rendering of those "glow/light" effects in a few of my weapons in first person view. It's not serious, but it's annoying enough to me.
When setting ZRangeHack to false, everything is good, but then the Redeemer overlaps the HUD :\
So, I came up with a simple solution: when rendering a NW3 weapon, set ZRangeHack to false, for everything else to True (as long ZRangeHack was True by default initially, if not, nothing is done).
This however, makes the ZRangeHack to be saved in the ini each time it's changed, thus I have to ensure that either you: exit the game, leave a server, open another map through console, etc, the ZRangeHack is reset to its original value, so you don't have any problems when playing something else.
The only situations where the ZRangeHack may not be reset right now are:
- quit/exit/open through keybinds (through console there's no problem for me)
- sudden exit for whatever reason, and once you enter you go to a non-NW3 server or practice session
In either situations, NW3 auto-fixes this once you run it again, but still.... :\
So I wanted to know what most people do so if someone has a problem, it will be 1 in each 100 or so (and which I can always put in a FAQ).