[4.1.1] Crash with Eviternity

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: [4.1.1] Crash with Eviternity

Re: [4.1.1] Crash with Eviternity

by Graf Zahl » Sun May 12, 2019 1:20 am

Fixed. This was accessing a global variable that only gets set after the first frame is rendered.

Re: [4.1.1] Crash with Eviternity

by Xaser » Sun May 12, 2019 12:25 am

Huh, weird -- this happens to me too, so it's not just a one-off. Here's a crashlog:
CrashReport.zip
(55.1 KiB) Downloaded 27 times
[EDIT] In case it helps, if you start an episode with the GL renderer on and change it back to software in-game, things work fine (even starting new episodes). Some sort of first-time-init borkiness, presumably.

[4.1.1] Crash with Eviternity

by drfrag » Sat May 11, 2019 8:18 am

Just start a new game with the Carmack renderer to reproduce the crash.
Someone mentioned it @doomworld:
I just tried playing Eviternity with GZdoom 4.0 and it played flawlessly when using Hardware renderer. However, using software renderer resulted in a crash.
https://www.doomworld.com/idgames/level ... eviternity

Top