Widescreen Gaming Forum

Unfortunately, multimonitor is still not working after March 2018 update. Flawless widescreen needs an updated DOOM.lua to address different hex values.

Any word on a update for Flawless Widescreen? I'd really like to replay this again.

Yeah 32:9 on this Samsung panel at first I thought was working, but there is definitely some stretch going on in the rendering. Would love a fix but for now I guess I'll just get used to the stretching. It looks so nice on this ultra-ultra-wide monitor.

I just went up to a Samsung panel recently as well and was going to give this a go but that stretch with my res at 3840x1080 is just so bad. Hopefully there will be a fix soon.

Since the last update was in March and we are well into July, I'm starting to think we're not going to see a fix for this.
Thanks Bethesda......

I was stoked to re-play doom in ultrawide now that I've built a system that can drive the FPS

Maybe I should learn how these things are done and tinker with it.

tet5uo wrote:I was stoked to re-play doom in ultrawide now that I've built a system that can drive the FPS

Maybe I should learn how these things are done and tinker with it.

Would be nice. It could just be that some values that are changed in the exe have just shifted. In that case the fix could be relatively simple (I have no idea how and what though, have changed some values in .exe's for other games, thats about it, the fix for DOOM and the weapon view model is way over my head). But if it was easy, it would probably have already been fixed.. Ah well, what do I know. I will just wait, hoping for an update. Even though DOOM is such a technical achievement, that these things are not natively supported is quite a pity. Luckily we have people that fix these things in their spare time, but we cant expect from them to keep on top of every single game that breaks Flawless Widescreen's fixes.

Any idea when you can fix the aspect ratio and FOV issues as per the latest patch which rendered the tool inert? I have donated before and would do so again.
https://steamcommunity.com/id/rama333/s ... 6884340712

DSR999 wrote:Any idea when you can fix the aspect ratio and FOV issues as per the latest patch which rendered the tool inert? I have donated before and would do so again.
https://steamcommunity.com/id/rama333/s ... 6884340712

I hate to say it but since we are well into July and the last update was in what March? I doubt were going to see an update anytime soon if ever. I've donated a few times over the years also.

I send a support request to Bethesda and they didn't help worth sh**.

Thank you for contacting the Bethesda Customer Support Team about the problems with the display over 3 monitors.

I appreciate you getting back to us on this issue. At this time, DOOM does not support the resolution 5760 x 1080 or similar which is the stretch between 3 monitors.

As the game updates, it may not run across 3 monitor correctly since we do not support the resolution, however, we are always open to feedback for the game and things we can support more in the future and bring back the display we may have had in the past! Feel free to leave us feedback for the game on our forums here: https://bethesda.net/community/category/50/pc

If there is anything we can assist with, please let us know! Thank you for your continued interest and support!

Warm Regards,
Bethesda Customer Support

Had a not so fruitful interaction with support as well regarding this (https://imgur.com/a/JQmDyIq). Hopefully if enough people submit a ticket regarding this issue they will do something with it. Again, it doesnt look like it involves that much work for a developer if a third-party added it easily, and the engine supports it anyway (see Wolfenstein II, weapon FOV scales wonderfully. Dont know about multiple screens support though for that game).

Is there anyone that knows what the fix by HaYDeN actually did, and how it worked? Is there something we ourselves can do, if necessary with cheat engine or something?

Garwinski wrote:Had a not so fruitful interaction with support as well regarding this (https://imgur.com/a/JQmDyIq). Hopefully if enough people submit a ticket regarding this issue they will do something with it. Again, it doesnt look like it involves that much work for a developer if a third-party added it easily, and the engine supports it anyway (see Wolfenstein II, weapon FOV scales wonderfully. Dont know about multiple screens support though for that game).

Is there anyone that knows what the fix by HaYDeN actually did, and how it worked? Is there something we ourselves can do, if necessary with cheat engine or something?

I wish I knew what HaYDeN did. Someone here must know or have an idea.
I have submitted a bug report on the pinned item "Submitting a bug report" like a week ago, nothing yet.
Should be called Bethesda Suckport.
I'm sorry but this problem is really making me mad. I bought a product and it doesn't work, wish i could get my money back.

I opened the Lua file of doom, where the memory addresses are mentioned. They are wrong right now, no idea what to change. I opened the memory register for doom with cheatengine, but I have no clue.

Garwinski wrote:I opened the Lua file of doom, where the memory addresses are mentioned. They are wrong right now, no idea what to change. I opened the memory register for doom with cheatengine, but I have no clue.

I wish you luck Garwinski. Please update us if you find anything.

The problem is that at this moment, the memory addresses in the .lua file are wrong as Flawless Widescreen reports that it can not find those adresses, so the memory adresses in the running .exe of DOOM have changed to different adresses. The problem is, that I have no idea where to begin to find the new adresses where the fix should be 'injected' in the memory of the running .exe to make the fixes work on this new version of DOOM. Maybe if I had an old .exe of a DOOM version that worked I could crosscheck those memory adresses, but I dont have an old DOOM.exe atm.

EDIT: Decided to follow these steps:

https://steamcommunity.com/sharedfiles/ ... 1086279994

I only redownloaded the executable from August 24, 2017 from the Windows Executable-depot, placed them in my DOOM map, overwriting the files there, and I was good to go again.

Garwinski wrote:The problem is that at this moment, the memory addresses in the .lua file are wrong as Flawless Widescreen reports that it can not find those adresses, so the memory adresses in the running .exe of DOOM have changed to different adresses. The problem is, that I have no idea where to begin to find the new adresses where the fix should be 'injected' in the memory of the running .exe to make the fixes work on this new version of DOOM. Maybe if I had an old .exe of a DOOM version that worked I could crosscheck those memory adresses, but I dont have an old DOOM.exe atm.

EDIT: Decided to follow these steps:

https://steamcommunity.com/sharedfiles/ ... 1086279994

I only redownloaded the executable from August 24, 2017 from the Windows Executable-depot, placed them in my DOOM map, overwriting the files there, and I was good to go again.

I tried to do that too but got lost and wasn't sure what package to download.
Could you maybe setup a mega link for the older exe?

jc0123 wrote:

Garwinski wrote:The problem is that at this moment, the memory addresses in the .lua file are wrong as Flawless Widescreen reports that it can not find those adresses, so the memory adresses in the running .exe of DOOM have changed to different adresses. The problem is, that I have no idea where to begin to find the new adresses where the fix should be 'injected' in the memory of the running .exe to make the fixes work on this new version of DOOM. Maybe if I had an old .exe of a DOOM version that worked I could crosscheck those memory adresses, but I dont have an old DOOM.exe atm.

EDIT: Decided to follow these steps:

https://steamcommunity.com/sharedfiles/ ... 1086279994

I only redownloaded the executable from August 24, 2017 from the Windows Executable-depot, placed them in my DOOM map, overwriting the files there, and I was good to go again.

I tried to do that too but got lost and wasn't sure what package to download.
Could you maybe setup a mega link for the older exe?

I am not sure if that is allowed, and even then, I am also not quite sure as to what extent those files generated by this method are machine or steam id dependent, so it would be better to do it yourself.
__________________________________________________________________________________________
https://steamcommunity.com/sharedfiles/ ... 1086279994

1.Follow step 1 of the guide to open the steam console. (fast way, follow this link, open with Steam client bootstrapper: steam://open/console)

2.Then, skip to step 7 of the guide.The app id is 379720, depot ID is 379721, and manifest ID for the files I used is 907965064786099828. So, in the steam console you type (or paste):

download_depot 379720 379721 907965064786099828

And press enter. Steam will now start to download.

3."If you successfully downloaded the package, it will be on your [path to Steam folder]/Steam/steamapps/content folder".
Be aware, this is where you have steam installed, so you wont find them on the drive where you installed DOOM per se. So, if you installed DOOM on your D: drive but steam on your C: drive, you will find the files in the steam path on the C: drive.

4.Copy the files which you downloaded and have found in the previous step into your DOOM directory and overwrite the files. Voila!
__________________________________________________________________________________________
There is a step in the guide to prevent the game from updating, but the values the guide indicates you should change where already what the guide told me to set them at, and DOOM has not overwritten those files with newer once as of yet for me. In my experience anyways steam wont do this unless you manually verify game files, or the game receives an update. I keep the new files acquired through this method in a separate map in my steam directory, just in case they do get upgraded to the newer versions, so I can overwrite them again without much hassle.

(You probably wont be able to play the multiplayer with the older files, but I figure most people dont play that anyways.)

Garwinski wrote:

jc0123 wrote:

Garwinski wrote:The problem is that at this moment, the memory addresses in the .lua file are wrong as Flawless Widescreen reports that it can not find those adresses, so the memory adresses in the running .exe of DOOM have changed to different adresses. The problem is, that I have no idea where to begin to find the new adresses where the fix should be 'injected' in the memory of the running .exe to make the fixes work on this new version of DOOM. Maybe if I had an old .exe of a DOOM version that worked I could crosscheck those memory adresses, but I dont have an old DOOM.exe atm.

EDIT: Decided to follow these steps:

https://steamcommunity.com/sharedfiles/ ... 1086279994

I only redownloaded the executable from August 24, 2017 from the Windows Executable-depot, placed them in my DOOM map, overwriting the files there, and I was good to go again.

I tried to do that too but got lost and wasn't sure what package to download.
Could you maybe setup a mega link for the older exe?

I am not sure if that is allowed, and even then, I am also not quite sure as to what extent those files generated by this method are machine or steam id dependent, so it would be better to do it yourself.

https://steamcommunity.com/sharedfiles/ ... 1086279994

1.Follow step 1 of the guide to open the steam console. (fast way, follow this link, open with Steam client bootstrapper: steam://open/console)

2.Then, skip to step 7 of the guide.The app id is 379720, depot ID is 379721, and manifest ID for the files I used is 907965064786099828. So, in the steam console you type (or paste):

download_depot 379720 379721 907965064786099828

And press enter. Steam will now start to download.

3.

"If you successfully downloaded the package, it will be on your [path to Steam folder]/Steam/steamapps/content folder".

Be aware, this is where you have steam installed, so you wont find them on the drive where you installed DOOM per se. So, if you installed DOOM on your D: drive but steam on your C: drive, you will find the files in the steam path on the C: drive.

4.Copy the files which you downloaded and have found in the previous step into your DOOM directory and overwrite the files. Voila!


There is a step in the guide to prevent the game from updating, but the values the guide indicates you should change where already what the guide told me to set them at, and DOOM has not overwritten those files with newer once as of yet for me. In my experience anyways steam wont do this unless you manually verify game files, or the game receives an update. I keep the new files acquired through this method in a separate map in my steam directory, just in case they do get upgraded to the newer versions, so I can overwrite them again without much hassle.

(You probably wont be able to play the multiplayer with the older files, but I figure most people dont play that anyways.)

Made an account to say thanks. This worked perfect for me!

Garwinski wrote:

jc0123 wrote:

Garwinski wrote:The problem is that at this moment, the memory addresses in the .lua file are wrong as Flawless Widescreen reports that it can not find those adresses, so the memory adresses in the running .exe of DOOM have changed to different adresses. The problem is, that I have no idea where to begin to find the new adresses where the fix should be 'injected' in the memory of the running .exe to make the fixes work on this new version of DOOM. Maybe if I had an old .exe of a DOOM version that worked I could crosscheck those memory adresses, but I dont have an old DOOM.exe atm.

EDIT: Decided to follow these steps:

https://steamcommunity.com/sharedfiles/ ... 1086279994

I only redownloaded the executable from August 24, 2017 from the Windows Executable-depot, placed them in my DOOM map, overwriting the files there, and I was good to go again.

I tried to do that too but got lost and wasn't sure what package to download.
Could you maybe setup a mega link for the older exe?

I am not sure if that is allowed, and even then, I am also not quite sure as to what extent those files generated by this method are machine or steam id dependent, so it would be better to do it yourself.
__________________________________________________________________________________________
https://steamcommunity.com/sharedfiles/ ... 1086279994

1.Follow step 1 of the guide to open the steam console. (fast way, follow this link, open with Steam client bootstrapper: steam://open/console)

2.Then, skip to step 7 of the guide.The app id is 379720, depot ID is 379721, and manifest ID for the files I used is 907965064786099828. So, in the steam console you type (or paste):

download_depot 379720 379721 907965064786099828

And press enter. Steam will now start to download.

3."If you successfully downloaded the package, it will be on your [path to Steam folder]/Steam/steamapps/content folder".
Be aware, this is where you have steam installed, so you wont find them on the drive where you installed DOOM per se. So, if you installed DOOM on your D: drive but steam on your C: drive, you will find the files in the steam path on the C: drive.

4.Copy the files which you downloaded and have found in the previous step into your DOOM directory and overwrite the files. Voila!
__________________________________________________________________________________________
There is a step in the guide to prevent the game from updating, but the values the guide indicates you should change where already what the guide told me to set them at, and DOOM has not overwritten those files with newer once as of yet for me. In my experience anyways steam wont do this unless you manually verify game files, or the game receives an update. I keep the new files acquired through this method in a separate map in my steam directory, just in case they do get upgraded to the newer versions, so I can overwrite them again without much hassle.

(You probably wont be able to play the multiplayer with the older files, but I figure most people dont play that anyways.)

Thank you so much works like a charm.

it works for me!!! thank you!