News:

One Minute Game Review by The Happy Friar: https://ugetube.com/@OneMinteGameReviews
Also on Rumble: https://rumble.com/c/c-1115371

idTech 4 (aka Doom 3 tech) Discord Server! https://discord.gg/9wtCGHa

Main Menu

fhDOOM (modernized idTech4)

Started by eXistence, April 10, 2016, 12:35:13 PM

Previous topic - Next topic

0 Members and 5 Guests are viewing this topic.

originalxboxrulez

Quote from: The Happy Friar on April 06, 2019, 03:38:04 PM
if it's like stock D3,
r_customheight, r_customwidth, for the monitor height/width respectively, r_mode -1 for custom resolution, r_customaspect for the aspect ratio of your monitor.

Ya it set that in the config file and it just errors out starting the game ''Doom3 has stopped working'' lol and of course i cant enter that into the console because game wont start :P

Here's what it says

Problem signature:
  Problem Event Name:   BEX
  Application Name:   fhDOOM.exe
  Application Version:   1.0.0.1
  Application Timestamp:   5994adcf
  Fault Module Name:   StackHash_0a9e
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   00000000
  Exception Offset:   00000000
  Exception Code:   c0000005
  Exception Data:   00000008
  OS Version:   6.1.7601.2.1.0.768.3
  Locale ID:   1033
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789


The Happy Friar

delete the config file & put your custom res in the autoexec.cfg file (you may need to make one, same folder as the config file).
That will eliminate something conflicting in the config.

originalxboxrulez

Quote from: The Happy Friar on April 07, 2019, 04:58:16 PM
delete the config file & put your custom res in the autoexec.cfg file (you may need to make one, same folder as the config file).
That will eliminate something conflicting in the config.

Didnt work :(

revelator

BEX is a buffer overflow error, can be in the code itself, in a driver or even in the OS.
Most likely its a bug in the GFX driver, AMD has had a few of those, but report it upstream anyway.