Comments - THEV00D00

Nice work as always. I suggest creating a simple red dot. Thats the most common crosshair people like to use. ;)

You could make a shortcut or a *.bat batch file as mentioned in the readme to start the mod and add any parameter you want:
RBDoom3BFG.exe +set fs_resourceLoadPriority 0 +set fs_game @UltimateHD +set r_fullscreen 0

But I recommend giving the latest version of the Classic Doom / Doom BFA Edition executable from MadDeCoDeR/MoDFaNGuy a try to run the mod. It's way more up to date than RBDoom3BFG. Moddb.com

Of course you would have to make a new shortcut/Batchfile to start the mod with it. This is mine right now: DoomBFA.exe +set fs_resourceLoadPriority 0 +set fs_game @UltimateHD +set com_skipIntroVideos 1 +set com_allowconsole 1

yes, but it might cause a desync with the linked reload soundfile in some cases. That would take more time to fix.

modifying the speed of the monster is quite simple: you have to edit the *.md5anim files with any text editor located at @UltimateHD\models\md5\monsters\<nameofmonster>\

for exaple if you like to slow down the imp walk speed open @UltimateHD\models\md5\monsters\imp\walk1.md5anim and faster_walk.md5anim with notepad and change the value behind the entry "frameRate". Higher values will increase , lower values will decrease the speed. You might have to edit a lot of those *.md5anim files regarding to the animation you want to alter in speed.

not a bug... but the gog installation works a bit different.
to fix this open the autoexec.cfg file and add the line:
set sys_lang "english" // valid options are "english" / "french" / "german" / "Italian" / "spanish" / "japanese"

Thanks! :)

"pm_cursor" ist the new cvar for the crosshair if i get it right?

I would really love to see an option to turn off/on the reticle in Doom3 (cvar or bindable key) without turning off the whole hud.

go check the autoexec.cfg

set g_armorProtection "0.3" // value of damage protection by armor

For the Flashlight...
Open the autoexec.cfg located at ..\DOOM 3 BFG Edition\@UltimateHD\ with any texteditor and check the "FLASHLIGHT SETTINGS" section.
Edit the values to your likings. I wrote a detailed description next to the values.

no, most modifications are complex interlocked

What app are you using to extract the package? Try 7-Zip if that's not already the case (http://www.7-zip.org/)

For smaller download reason i uploaded the alternative file for Win7 users... Moddb.com

I'm unable to compile the exe for win7 in vs2017 running on win10. As workaround you can use the latest RBDOOM3BFG.EXE from the latest Hi Def patches => www.moddb.com/mods/doom-3-bfg-hi-def.. It's the most similar one to the one i compiled.
Anyway, there are few differences between them.
I further increased the decal limit and removed the blueish tint from filmicpostprocess shader

Sorry not sure about this, could be an engine or cvar problem. If it doesn't happen with Hi Def you could replace the RBDoom3BFG.exe with the one in his mod (the newest one should be in one of his patches). I also had a lot of shadow glitches without HDR but those glitches changed their behaviour with every new gfx driver release. ;)

If you mean this issue: Github.com , then update your gfx driver.

Thanks for feedback, seems like VS2017 on Win10 can't compile for previous windows versions O_o

yes, should be the same as in 2.0.3 if you didn't change it with the cvar g_armorProtection.
However, i wanted an easy accessible option to change the armor behavior. So if you prefer more armor protection, you can change it in the config file at ..\@UltimateHD\autoexec.cfg
Those settings will always be forced at startup.

run "_remove generated files.bat" in @UltimateHD, i guess it's a collision data error in the generated files. Don't know why this never happens to me, i ran the whole campaign without any errors :-/

for unknown reason the default armor protection in the base game was 0.2 => 20%.
The cvar game defaults should be 0.3 => 30%
The 50% in the changelog was a mistake (i tied around with 50% but it was a bit to high for my likings so i decided to change it back to 0.3 for ultimate)
Anyway, you can set your prefered amount in the autoexec.cfg in @UltimateHD
I corrected the changelog now.

Hi, Noe.
Thanks for the feedback, i already re-balanced some things in v2.1.0, You might give it a try :)

Hmm, XInput seems to be an OS API for the XBox Controller. I would guess that this is an system issue but otherwise you mentioned that 2.0.3 worked fine. I dont have Win7 anymore so i can't check it (at least it runs fine on Win10 x64). For testing purpose please start the RBDOOM3BFG.EXE without any parameter and check if you get the same error.

If you still have the v2.0.3 7z Package you can also extract the old RBDOOM3BFG.EXE and replace the v2.1.0 one as workaround. ATM you're the only one reporting this problem.

Hmm, der Konsolenabschnitt zeigt leider keine aufschlussreiche Fehlermeldung. Ich kenne das Phänomen eigentlich nur wenn man versucht einen inkompatiblen Spielstand zu laden. Passiert das selbe, wenn du versuchst über den DEV Menüpunkt die Mission Erebus 1 (unter -DOOM 3 Expansion- ) zu starten? Ansonsten bin ich mit meinem Latein am Ende und muss mal abwarten ob noch mehr Leute dieses Problem melden. Auf meinem System ist das Problem leider nicht reproduzierbar.

Du kannst die screenshots auf imgur.com hochladen und hier verlinken.
Vielleicht liegt auch ein Problem mit alten Einstellungen vor. Diese findest du unter %userprofile%\Gespeicherte Spiele\id Software\RBDOOM 3 BFG\@UltimateHD. Lösche darin erstmal alles, damit diese neu erstellt werden.

No, the 7z package is unencrypted and doesn't need a password at all. I would suggest to use 7-Zip to extract it (www.7-zip.org) and try again.

Kannst du mir folgende paar Infos zu dem Problem geben:
-) Hattest du eine Vorversion von UltimateHD die du zuvor entfernt hast?
-) Hast du zuerst die Hauptkampagne gespielt, oder sofort mit der Erweiterung gestartet?
-) Verwendest du modifizierte base Datein (z.B. durch die Hi Def Mod)
-) Kannst du in der console etwas nach oben scrollen und einen screenshot der eher letzteren Fehlermeldungen zur verfügung stellen?

Zu guter letzt kannst du die Datei "_remove generated files.bat" im @UltimateHD Ordner ausführen, die hoffentlich das Problem behebt. Alternative kannst du auch den Ordner "generated" selbst löschen und das Spiel danach neu starten und testen.

Remember to remove any old UltimateHD installation before installing this version!

FYI: Softshadow issue got fixed with Geforce v382.53 - But might reappear with a future version ;)

Update: Softshadow issue got fixed with Geforce v382.53

Well the problem is, and i'm pretty sure about that, they don't know that there is a problem with an unofficial release of Doom3 BFG. And even if the would know about it, i doubt they would put effort in it to fix it, when this is the only game that has this problem. If RB doesn't find a solution to fix it in RBDoom3BFG, nvidia will only fix it by accident ;)

@egold: i already answered it in the HiDef comments but for integrity here again: if you have a huge dark square, starting from the lower left corner, covering more than 1/3 of your whole screen and using a nvidia card, the latest driver is causing this. If you roll back to v378.78 it's gone. The only way to get rid of this issue with the actual geforce driver (v381.65) is to turn of softshadows. r_useShadowMapping 0
This issue appears with any rbdoom3bfg release.

In UltimateHD you can edit the cfg\*.cfg file that is loaded via autoexec.cfg to take permanently effect.