D4D - Announcement in 1st post (Jan 4th 2017)

[EddieMann]

So I used the latest devbuild and I got this error;
https://anonmgur.com/up/312e97bc747bbb3 ... 6bc0f1.png

Because that's not the latest devbuild - yours is about 2 months older than the latest and the latest has a lot of new features that this mod uses quite a lot.

SIlly me, thank you! I get crashes whenever I try to upgrade my weapons, though.

[Major Cooke]

That crashing bug was just fixed. Please allow zdoom to update on the drdteam website (should only take 10 and a half hours from the time of posting, roughly, so that's 3 AM my time).

[OscarGuy]

I can run it perfectly with gzdoom with vidrender values to 0 and with last zdoom devbuild. Everything is fine... with exception of the upgrade menu. Everytime I enter it and want to press on a weapon to buy upgrades, the engine crash and send me to desktop, anyway to fix this?

[mutator]

I can run it perfectly with gzdoom with vidrender values to 0 and with last zdoom devbuild. Everything is fine... with exception of the upgrade menu. Everytime I enter it and want to press on a weapon to buy upgrades, the engine crash and send me to desktop, anyway to fix this?

You have to go d4d options, go to display and turn off voxel

[Devianteist]

I can run it perfectly with gzdoom with vidrender values to 0 and with last zdoom devbuild. Everything is fine... with exception of the upgrade menu. Everytime I enter it and want to press on a weapon to buy upgrades, the engine crash and send me to desktop, anyway to fix this?

Turn off voxels.

EDIT: Got ninja'd.

[Major Cooke]

GZDOOM WARNING. (Zdoomers, for once, you can ignore this message.)

Only update your GZDoom versions with EXTREME CAUTION. Your safest bets are July 29th, maybe 30th builds.

They are implementing Bloom, Multisampling, ToneMap, the ability to toggle render buffers and patch shader support.

...

If you get this termination bug (glCheckFramebufferStatus failed: GL_FRAMEBUFFER_INCOMPLETE_MULTISAMPLE):

1. Open the .ini file used with your GZDoom (this doesn't affect zdoom for once... You guys are safe.)
2. Find gl_multisample
3. Set whatever number it is to ONE. NOT ZERO.
4. Save it and start it again, it should be gone.

This is just-in-case when the new build comes out and some people have this issue, you'll know what to do. I build my own builds so I'm way ahead of you guys.

[mutator]

I can now play this mod but I wish I could play it with gzdoom features.. When I try it on gzdoom, I can't see half of the screen.... I'm not able to get the best experience from the mod

[Major Cooke]

Then that's something you'll want to report and screenshot for gzdoom bugs. Not us.

[mutator]

Then that's something you'll want to report and screenshot for gzdoom bugs. Not us.

I don't know if it's bug though.. This mod works perfectly in gzdoom features for others

[OscarGuy]

Thanks people, unfourtanelly I had to turn off the voxels. But is not that of a great thing for not enjoying the mod. Is awesome

[JimpArgon]

Just letting you guys know that you should probably make a post on this dumbass's thread and ask him to take this down. Its more then likely outdated and will just confuse people. He should not have even uploaded it in the first place.

http://www.moddb.com/games/doom-ii/addo ... for-doom-2

[Major Cooke]

Well at least he gave some credit.

[Jeimuzu73]

Icarus has made a new episode featuring your mod:

I'd say congrats, but I'll save the applause until your mod gets nominated for the Cacowards.

[JimpArgon]

Icarus has made a new episode featuring your mod

I already posted that on page 52.

[Jeimuzu73]

Oh, my bad. Just shift it to the bumps thread then.