So, given the number of stupidly misplaced things in every other map, how far off are we from a 2.0.6? Five months?
犬夜叉;672467 said:Do me a favor and try Alam's Mingw build of 2.0.5 and tell me if the lag is still there.
If it isn't... well, that gives us a perfectly valid reason to FINALLY start using GCC.
(I wouldn't vouch for this being compatible with the released 2.0.5 EXE due to floating point math differences, like before, so you might want to rename this EXE instead of just replacing the normal one.)
The problem is, most of the faults in this version seem to stem from the IWAD, which is harder to update than the executable. Unless we have some sort of diff-based patching system working which I don't know about.Wasn't 2.0 super buggy when it came out? Most of these "bigger" patches end up buggy at first, 'till another (usually quicker to produce) patch goes and fixes them.
Are you not keeping up with developments? Check tables.c for FIXEDPOINTCONV. When #define'd, it prevents these math issues. Also, it's only VC6 that handled floating point math differently - VC9 wouldn't have this issue even if FIXEDPOINTCONV wasn't #define'd.
OpenGL shouldn't have been enabled in the build. Oh well. Another issue to fix!
犬夜叉;672467 said:Do me a favor and try Alam's Mingw build of 2.0.5 and tell me if the lag is still there.
If it isn't... well, that gives us a perfectly valid reason to FINALLY start using GCC.
(I wouldn't vouch for this being compatible with the released 2.0.5 EXE due to floating point math differences, like before, so you might want to rename this EXE instead of just replacing the normal one.)
Please don't make us go through that again. X_X犬夜叉;672719 said:1.09.3.x.
(10char)
You can still use the OpenGL EXE...Dont please!I love OpenGL!!
You can still use the OpenGL EXE...