I've been testing and looking for such things for a while, it's part of my job after all. It was never a problem, not in Raze anyway, but since the gameplay is inherited from the parent ports I have reason to believe it didn't occur in EDuke32 either.
Phredreeke wrote:lowskill: during my last playthrough I used crouch toggle, after switching to regular crouch what you're saying is correct. This option will later be made available on the startup popup as soon as possible. For modern content that requires EDuke32's features use +duke_compatibility_15 0 to reset it. The setting is persistent and will be remembered on later starts. For such classic content I recommend starting Raze with +duke compatibility_15 1. This frontend is a lot closer to original Duke Nukem 1.5 and should exhibit considerably less errors with classic maps.Ĭonsidering this, effectively immediately I will no longer investigate any bug in Duke Nukem that originates from EDuke32 and hasn't been fixed there. I spent some time today to make the RedNukem-based Redneck frontend capable of running Duke and its offspring games NAM and WW2GI. I cannot deny that trying to fix these may end up a losing proposition. Anybody reading the bugs forum for Raze may have noticed that there have been several bug reports for Duke Nukem that were inherited directly from EDuke32.
