Zdoom fullbright issue

Post by **Graf Zahl** » Sun Oct 15, 2006 1:59 pm

No, it won't. But what does it matter? A file is a file, regardless of extension.

Dancso · Post by **Dancso** » Mon Oct 16, 2006 9:17 am

Log started: Mon Oct 16 17:25:43 2006

 adding D:/Games/Doom/Zdoom/Newest/zdoom.pk3
 adding ./doom2.wad (2920 lumps)
CPU Speed: 2405.497074 MHz
CPU Vendor ID: GenuineIntel
  Name: Intel(R) Celeron(R) CPU 2.40GHzn(R) CPU 2.40GHz
  Family 15, Model 2, Stepping 9
  Features: MMX SSE SSE2
I_InitSound: Initializing FMOD
  Setting DirectSound output succeeded
  Setting driver 0 succeeded
  Initialization succeeded
Resolution: 1152 x 864
Init DOOM refresh subsystem.
Init miscellaneous info.
Init Playloop state.
Setting up sound.
S_Init
Checking network game status.
player 1 of 1 (1 nodes)



MAP01 - entryway

Here's the log.

Risen · Post by **Risen** » Mon Oct 16, 2006 10:50 am

Your DOOM2.WAD file may be altered. A quick forum search turns up that most people have 2919 lumps in their doom2.wad, and my personal copy does as well. Yours is showing an extra one at 2920.

I don't know what the lump count should be for different WADS, but since most people have upgraded to recent, this seems suspect to me.

Restore the WAD from your original copy and see if that helps.

Edit: Confirmed that my own DOOM2.WAD also has 2919 lumps.

HotWax · Post by **HotWax** » Mon Oct 16, 2006 10:53 am

Except that he said other ports work just fine with that same IWAD. Could there be anything in there that ZDoom would handle differently from other source ports?

Risen · Post by **Risen** » Mon Oct 16, 2006 10:56 am

ZDoom does have different handling of palettes, lighting and color translations than other ports do. I don't know if that handling can cause this sort of error, but if the WAD is altered then it's certainly the first place I would look for errors.

DoomRater · Post by **DoomRater** » Mon Oct 16, 2006 12:49 pm

This is exactly why I waited for Graf to post on it. We're just sitting around speculating about what's going on instead of getting the answer.

Post by **Graf Zahl** » Mon Oct 16, 2006 1:55 pm

There is no answer. My guess would be some kind of data corruption. I'm almost certain it's not ZDoom's fault.

Post by **Nash** » Mon Oct 16, 2006 2:15 pm

I'm almost certain it's because his DOOM2.WAD is modified because mine has 2919 lumps, too.

Post by **edward850** » Mon Oct 16, 2006 8:37 pm

I have heard of a vires that affect games, could affect doom or doom2.wad if it wanted to

HotWax · Post by **HotWax** » Tue Oct 17, 2006 12:30 am

The dreaded FULLBRIGHT.WORM2 no doubt.

Post by **edward850** » Tue Oct 17, 2006 12:34 am

hell, it can even affect HL2, srb2 and even quake2

Ultraviolet · Post by **Ultraviolet** » Tue Oct 17, 2006 2:25 am

That's somewhat of a [censored word] suggestion.

Post by **edward850** » Tue Oct 17, 2006 2:36 am

i know, but i read it somewhere

Dancso · Post by **Dancso** » Tue Oct 17, 2006 7:02 am

It can't be the wad's fault. All my wads do this. but only in zdoom. I tried in doomsday, and it was fine!!

Post by **TheDarkArchon** » Tue Oct 17, 2006 7:06 am

edward850 wrote:i know, but i read it somewhere

you can read all sorts of crap on the internet. Fail.