[Fixed] OMG!! A bug!!

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: [Fixed] OMG!! A bug!!

by Ty Halderman » Tue Jan 06, 2004 11:27 pm

randy wrote:
Ty Halderman wrote:somewhere around a function called PopulateEnvList in eaxedit.obj.
Actually, the crash is in FBaseStatusBar::BlendView, which starts at address 004A5850. PopulateEnvList is at 0048CF70.
Oh, poo. Right when I thought I had this figured out too :oops:

My map file shows:

Code: Select all

 0001:000c0a70       ?BlendView@FBaseStatusBar@@UAEXQAM@Z 004c1a70 f   shared_sbar.obj
so obviously I didn't compile the same 2.0.60 you did... I knew this would be harder than I had hoped for. But no wonder I can't figure out any of these dumps.

/goes back to add 0x0001C220 to everything :P

by randi » Tue Jan 06, 2004 5:25 pm

Ty Halderman wrote:somewhere around a function called PopulateEnvList in eaxedit.obj.
Actually, the crash is in FBaseStatusBar::BlendView, which starts at address 004A5850. PopulateEnvList is at 0048CF70.

Assuming you used spynext/spyprev to spy on player 2 and then player 2 left, this bug is fixed.

by Hirogen2 » Wed Dec 31, 2003 3:40 pm

I like to type
subst X: C:\ra2\...
for that.

by HotWax » Tue Dec 30, 2003 6:16 pm

He didn't like Doom because "it crashed your computer"... and he wouldn't let you buy other computer games for the same reason. *sigh*

Stupid people suck.

by cccp_leha » Tue Dec 30, 2003 6:14 pm

Hahaha, you're gonna laugh but I have pretty much the same story. My ZDoom path is "c:\ra2\gam\westwood\doom2". Although my father is a much bigger computer wiz than me, he still never found it...

by Tai » Tue Dec 30, 2003 5:57 pm

giest118 wrote:
C:\Halflife\doom2\zdoom.exe
Why do you keep ZDOOM in your Half-Life folder?
1. Does it really matter? No.

2. If you have to know, it USED to be to hide the folder from my Dad. He used to not like Doom on the computer because it crashed on my old one... I did that with the doom folder in my old computer....but then again he won't let me buy anymore PC games because he thinks they will crash like Doom did(Did I mention this isnt my computer?), so maybe I wasn't keeping my doom files safe after all. Anyhow, he doesn't really care that much anymore. I don't even have Halflife (this is not ANYMORE either, I simply have never had it). :(

Ty Halderman: Not sure if it matters, but this is the first time that Zdoom has crashed for me in Coop. Like I said, I don't know if whether playing coop or single would increase the chances of this crash happening. It has happened very rarely in Single player, but it's happened. (maybe like 3 times or so..) So the answer your above question, I'd say this is a one-time experience.

by Giest118 » Tue Dec 30, 2003 2:13 pm

C:\Halflife\doom2\zdoom.exe
Why do you keep ZDOOM in your Half-Life folder?

by Ty Halderman » Tue Dec 30, 2003 2:11 pm

I don't see "Yes, I have the most recent drivers for my sound card" anywhere in there, or whether it was a repeatable error or a one-time experience.

by Tai » Tue Dec 30, 2003 11:05 am

1. I used Doom Connector. Everything on the "command line" was set up there. I don't set up Coop games with shitty command line *gets shot*.

2. Everything else is on console. Alwaysapplydmflags 1 is an example.

3. This was a coop game

4. The command line is defective...>_>

5. I don't know how cchest.wad was loaded 3 times in the command line.

6. Hopefully it won't happen again. :-)

7. It crashed on Map05.

by HotWax » Mon Dec 29, 2003 7:39 pm

+dmflags isn't a CLP. :P If you add "+dmflags 65536" to the command line, it's the exact same as typing "dmflags 65536" in the console, which sets dmflags to 65536.

Anyhow, if you were to type "-dmflags" at the command line, ZDoom would laugh at you, and so would I.

by Biff » Mon Dec 29, 2003 6:09 pm

I'm pretty sure that + does not exclude something from being a CLP. Isn't +dmflags a typical instance? It's always worked for me.

by HotWax » Mon Dec 29, 2003 6:06 pm

Yes, but technically speaking that's not a CLP either. Any argument with a + before it means to execute the following command in the console. So you could do +map mymap, or +fullscreen 0, or +set alwaysapplydmflags 1, etc.

by Biff » Mon Dec 29, 2003 6:01 pm

HotWax wrote:Not to mention that -alwaysapplydmflags is not a valid command-line argument. :roll:
What is the correct one, maybe +alwaysapplydmflags 1 ??

by HotWax » Mon Dec 29, 2003 5:57 pm

Not to mention that -alwaysapplydmflags is not a valid command-line argument. :roll:

by Ty Halderman » Mon Dec 29, 2003 5:55 pm

"This bull" :roll: means that your game crashed, somewhere around a function called PopulateEnvList in eaxedit.obj. (EAX in this case is sound-related, not a reference to a CPU register.)

Does it happen repeatedly after rebooting in the same situation? Do you have most current sound drivers? Does it ever happen when just playing the game, or only in a network situation?

And why on earth do you load c:\halflife\doom2\cchest.wad three times on the same command line? If I were ZDoom, I'd crash just on general principles :P

[edit]beaten 3 times by the time I could type this. Bah ;)[/edit]

Top