Back to the Vavoom Forum Archives


Forum

[Closed] Help /w Debug.txt

Sat, 03 Aug 2002 11:29:17

roy5050

I have just ULed debug.txt--<br>Beta 114 crashes when<br>attempting to load a level.<br><br>It ran fine before.<br><br>The problems started when I attepted<br>to upgrade the VaVoomC (vc) files<br><br>Please help me.<br><br>Thanks.
Sat, 03 Aug 2002 11:54:59

roy5050

The error message I get when trying to run<br>VaVoom is:<br><br>Segmentation Violation<br><br>Stack Trace: (.TranslateThing) <- TProgs::ExecuteFunction <- (TranslateLevel)<br><- LoadLevel <- SV_SpawnServer <- COMMAND Map <br><- HostFrame<br><br>Trying to start the game displays this error message & then dumps the game back to Windows.
Sat, 03 Aug 2002 12:12:32

roy5050

I ran<br>glvis -f doom2.wad<br>& now everything runs fine<br>& I can play my TC again.<br><br>Sorry for the premature posting.
Tue, 06 Aug 2002 03:52:29

Janis Legzdinsh

A little bit strange it solved this way. <!-- s;) --><img src="{SMILIES_PATH}/icon_wink.gif" alt=";)" title="Wink" /><!-- s;) -->
Thu, 08 Aug 2002 02:39:21

Hodapp87

Building the GWA or vis data with separate tools seemed to fix some of my problems with crashing in DOS... it just takes awhile to build BSP\vis for larger WADs on my Pentium 120 - along the lines of 3 hours for TNT\Evilution. I was not using fast mode though because that appeared to be what Vavoom was using normally when I would get crashing. I still get crashes, but much less frequently.
Thu, 08 Aug 2002 03:53:24

Janis Legzdinsh

Yes, by default plugin in the Vavoom builds vis data in fast mode, but utility defaults to the full one.

Back to the Vavoom Forum Archives