The latest amazing new version of DOOM BFA is now available.
WARNING: The game dll support is nearly complete but
there are still bugs while using them.
[classicdoom]
- Improve rumble effect
- Improve Stability
- Fixed issue loading wild files
- Add Classic DOOM Freelook limiter (cl_freelookclamp defaut 550 max 4000)
- Fixed issue with loading an empty EXPINFO (DOOM 2 Game boot crash bug)
- the frame rate is now indepedent from DOOM 3
but enabling Interpolation (FPSI) you can edit DOOM 3's framerate as Classic DOOM's Refresh rate
- Re adjust ThirdPerson View constants
- Made more keys remappable (namely the Function Keys)
[DOOM3BFG]
- Vastly improve SWF Ui
- Improve Text intro skiping
- Improve Controller support
- Fixed weapon circling not working under random circustances
- Reworked Frame Rate/ Refresh Rate on all games,
on DOOM 3 the frame rate will have only the available resfresh rates of your monitor
- Add additional translation strings including Zoom key binding title and advaced options
- On the first run retrieve the monitor's resolution and resfresh rate and use them to setup the fullscreen
- Update Open Platform to Version 0.4.7
- Fixed issue when trying to revert fullscreen resolution
I'm having some strange issues where soft shadows appear heavily pixelated/boxed-out when a light is shining on a shadow. seems to be related to LOD setting but testing has produced strangely inconsistent results.
Yep, if I am not wrong the Soft Shadow LOD is mainly for the shadow details, the higher it is the more sharp the shadow details will look, the reason why in my port is quite low (while on RBDOOM is maxed out) is due to performance.
Is there no way to dither the samples? it's quite jarring when it happens, as the banding is quite intense and causes the texture underneath to appear striped.
Also, if soft shadows are disabled, it disables all shadows.
To be honest I really don't know, sorry.
Chaingun normal fire rate is tied with the 120 fps cap and fires way slower under that, I have a 75hz monitor and I tried to force the cap with "set com_engineHz "144" on a autoexec but it didn't work. Any way to force the frame rate to that value?
Nope, sorry. The framerate is tied to your monitor refresh rate.
P.S.: Try to lower it on 60 FPS, or try a multiplayer map and see how it goes.
P.S. 2: I also have a 75hz monitor but I haven't notice any issue with the chaingun so far
Multiplayer fires normally regardless of the option. Oddly, after switching options multiple times, the chaingun now fires a little bit more faster at 75, and slower at 60.
I really don't know how it works exactly on single player (and I should start investigating it at some point) but for the Multiplayer it uses fix framerate, 60 or 120 FPS
Someone on Steam forums, mentions that is a script that causes this. I can't post links, but is called "no 144hz option?" on Discussions
Maybe you should make an account on ModDB
I found an odd issue after updating to the latest version (including following instructions for deleting old files in the readme). When I try to disable HDR, it does so for a split second then turns it right back on. Attempting to manually disable it through the config file also forcibly reenables it upon relaunching the game. As my monitor doesn't support HDR, this makes the whole game look as gaudy as Borderlands.
Try to open the classic DOOM games (they will force it to close).
It turns the feature off but it flips right back on the instant I quit the classic games back to the menu.
I found a fix! If this happens to anyone else, turn off soft shadows then turn off HDR. It'll stay off when you turn soft shadows back on.
I recently bought the retail version of Doom 3 BFG Edition. It runs normally on its own, but whenever I try to run it with BFA, I get a "_default material not found" error. How do I fix this?
What folders does it have inside the game folder ?
Only the ones that it came with-Base,directx, and msvc210.
does the base folder have _common.resources file ?
Also try the Classic Edition (as a standalone game) and see if that play the shareware (like in BFG it also uses it's own _common.resources inside the base folder).
Sorry for all that but I still trying to figure out the source of your problem.
Yes, the base folder does have a _common.resources file.