Technical support > Bugs in stable version (2.5)
Infrared glasses don't work !!!
anonymissimus:
All right.
I have just managed to get them working in 2.5 for the first time, perhaps because I used a debug build (which means building with debugging symbols I suppose/hope ?)
Previously to that, I checked out the 2.4 branch, in the resulting self-built binary they didn't work for me, albeit in the 2.4 version I got from the repository they always worked.
Thus I now think that undefined behavior of some sort must be involved, which leads to them randomly working or not working. This also quickly explains why they happen to work for MonkeyHead and why none reported it yet.
Is it supposed to depend somehow on the build configuration such as whether uforadiant is build ? it doesn't make sense to me, but just in case. That's one of the things I changed during my trials.
EDIT
Yes, I can toggle in 2.5 between not working and working by using ./configure --enable-release or just ./configure (then it builds with debug). Clearly UB.
DarkRain:
Yes, I can confirm, furthermore: As they're implemented IR Googles shouldn't work, but the trace function returns incorrect values in *both* release and dev builds, but only in dev builds that makes the ir googles work purely by accident
Unfortunately I'm not very (read: 'at all') familiar with the tracing code...
Duke:
DarkRain, which trace (src, line) do you mean in particular ?
Thought it was a rendering issue.
Mattn:
can you define the accident a little bit more?
DarkRain:
I'm talking about the call to G_Trace in g_combat.cpp:927, I put some more details in the tracker...
Anyway, upon further investigation it seems that the tracing code isn't at fault, but the start and end vectors get mangled before they are passed to G_Trace haven't had the chance to look more into it
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version