This file corrects the startup error that occurs when BRUTAL DOOM v20b is started using "GZDoom 3.0.0".
The content of the game is the same as "BRUTAL DOOM v20b".
** Bugs fixed information
(BrutalDoomv20b_R.zip)
- Fixed a bug in Blood.txt so that you can start Brutal DOOM using the latest GZDOOM.
(BrutalDoomv20b_R2.zip)
-Fixed the funny BUG that the attacked tree slipped and flew.
In the latest GZDOOM, it was BUG which occurred because the upper limit value of "Mass" was set.
(BrutalDoomv20b_R3.zip) -- NEW
-Fixed a minor BUG that When Chaingun guy died by explosion, may not drop Minigun.
********
Latest GZDoom - Download
Gzdoom.drdteam.org
The original "BRUTAL DOOM v 20 b" is here.
Moddb.com
Thanks!
Awesome trailer!
Still, doesn't work on GZDoom g3.0.1 - SDL version
*** Error in `gzdoom': free(): invalid next size (fast): 0x0000000000ef53c0 ***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x722ab)[0x7ff30fd262ab]
/usr/lib/libc.so.6(+0x7890e)[0x7ff30fd2c90e]
/usr/lib/libc.so.6(+0x7911e)[0x7ff30fd2d11e]
gzdoom(_ZN18FFunctionBuildList5BuildEv+0x551)[0xaa4951]
gzdoom(_Z10LoadActorsv+0xac)[0xa69a2c]
gzdoom(_ZN11PClassActor10StaticInitEv+0x1d5)[0x7beb75]
gzdoom(_Z10D_DoomMainv+0x1139)[0x760009]
gzdoom(main+0x15c)[0x520f0c]
/usr/lib/libc.so.6(__libc_start_main+0xf1)[0x7ff30fcd4511]
gzdoom(_start+0x2a)[0x53446a]
======= Memory map: ========
00400000-00ce3000 r-xp 00000000 09:00 752929 /usr/bin/gzdoom
00ee3000-00ee4000 r--p 008e3000 09:00 752929 /usr/bin/gzdoom
00ee4000-00ef6000 rw-p 008e4000 09:00 752929 /usr/bin/gzdoom
00ef6000-0154e000 rw-p 00000000 00:00 0
02da3000-09a87000 rw-p 00000000 00:00 0 [heap]
7ff2fc000000-7ff2fc021000 rw-p 00000000 00:00 0
7ff2fc021000-7ff300000000 ---p 00000000 00:00 0
7ff304000000-7ff304021000 rw-p 00000000 00:00 0
7ff304021000-7ff308000000 ---p 00000000 00:00 0
7ff309cd0000-7ff30a0d1000 rw-p 00000000 00:00 0
7ff30a0d1000-7ff30a26c000 rw-p 00000000 00:00 0
7ff30a680000-7ff30a681000 ---p 00000000 00:00 0
7ff30a681000-7ff30b699000 rw-p 00000000 00:00 0
7ff30b699000-7ff30b69a000 ---p 00000000 00:00 0
7ff30b69a000-7ff30b79a000 rw-p 00000000 00:00 0
7ff30b79a000-7ff30b8a0000 r-xp 00000000 09:00 701036 /usr/lib/libasound.so.2.0.0
Wow. It is an error I have not seen at all.
I confirm the operation with "GZDOOM 3.0.1 (Windows 64-bit)".
What is "SDL version"?
Linux, altough I didn't expected that it can be so much platform-specific...
I've launched it without any additional WADs, with DooM2 wad and your pk3.
Too bad that 3.0.X breaks so many things =/
On the other hand - Brutal DooM 64 works like a charm. I have no idea what's going on. Probably an upstream issue...
P.S.
SDL is 2.0.5
P.S.S.
Trailer - indeed - cool ;)
latest drd gzdoom (gzdoom-x64-g3.0pre-202-gbb1e927)ran with this and a few small addons with ZDL launcher.
One thing i can't seem to place correctly is health kits of every kind. So you know, they kind of float.
I Wait the v21 looks awesome
Just tested it with 3.0.0 and it does work. Thanks for the update.
There are still few minor bugs in this package. When loading GZDoom it showed errors for:
ImpShield.txt - DeadImp1 does not exist. Change to DeadImp
Nazis.txt - there is a 'Goto Crouch', also does not exist. Change it to 'Stop'.
Imps.txt - ImpTorso and DeadImp have 'Goto See', should be 'Stop'.
I have fixed these errors. You can download the fixed R4 package here (and reupload it here for everyone, because this link will expire in 30 days):
Filedropper.com
Meanwhile, in the zzbrutalxcod_bcoding_b3V85c.wad, in the D_INFO at line 170, there is an "actor Reloading : Inventory", this already exists in BrutalDoom, so it makes a conflict. It can be safely commented out or removed from the mod.
All the above fixes together make the entire CoD and Brutal Doom load with no errors and load much faster!
when i played it it just played normal doom 2 but i could look around
This comment is currently awaiting admin approval, join now to view.
I have a problem in Brutal Doom that I really need help. When I first open Brutal Doom it has the classic aim that you can't "aim" up and down. I enabled it on the mouse settings. It worked, however when I look up and down the floor and ceiling is slightly zoomed. I really need help how to fix it, please help me.
Fixed the problem.
This comment is currently awaiting admin approval, join now to view.
I think I've found a bug. On certain maps that require all Mancubi to be slain before certain sectors open up (map 07 of several wads including Doom2.wad Dead Simple), killing them doesn't register even when I use the "kill" or "remove" commands via console, so I have to noclip to get into certain areas that should open up (using gzdoom btw). I also noticed that barrels detonating over water cause a massive fps drop to the single digits (high particle count maybe?) when my gaming rig can otherwise run BD smoothly.
This comment is currently awaiting admin approval, join now to view.
This comment is currently awaiting admin approval, join now to view.
This comment is currently awaiting admin approval, join now to view.
This comment is currently awaiting admin approval, join now to view.
This comment is currently awaiting admin approval, join now to view.
This comment is currently awaiting admin approval, join now to view.
Hey guys, using this with the latest version of gzdoom (3.1) the brutal doom options are not available in the menu, so cannot change blood options or janitor and such, any ideas or help?
Download Dropbox.com
Add file MENUDEF.TXT to the archive "brutalv20b_R.pk3" (open "brutalv20b_R.pk3" with WinRAR or 7-zip and drag'n'drop file MENUDEF.TXT, confirm replace) or add like addon
This comment is currently awaiting admin approval, join now to view.
This comment is currently awaiting admin approval, join now to view.
This comment is currently awaiting admin approval, join now to view.
This comment is currently awaiting admin approval, join now to view.
Can this work for gzdoom 2.3
This comment is currently awaiting admin approval, join now to view.