Leaderboard

Binary diffed old version of DLL, done some IDA Pro research, got some patches for 2024-11-27 version! 60 FPS: Disco Elysium 2024-11-27 60FPS.xdelta 90 FPS: Disco Elysium 2024-11-27 90FPS.xdelta 200 FPS: Disco Elysium 2024-11-27 200FPS.xdelta

OMG thankyou!.. 8160x1600 perfectly!

Hello All (Especially those wanting Eyefinity / Surround) , This Patch worked great!!! I use Triple Monitor 7680 x 1440 and had to do the following: Launch Game (without Flawless Widescreen running) as normal Once inside game got to setting ("K" key for quick access) Inside setting go to the video tab Under Display Menu, go to first field "Window Mode" and select "Borderless Window" from the options (Fullscreen / Windowed) Apply Changes ("F" key for quick access) and Exit Game Now Start "Flawless Widescreen" and have program running as Helifax instructed Start Doom Eternal Enjoy the game in 7680 x 1440 🥂 First Photo @ 7680 x 1440 w/out Helifax patch Second photo @ 7680 x 1440 with Helifax patch -Mad Hatter 🍭

https://github.com/dolphin-emu/dolphin/pull/11850 https://github.com/Filoppi/PumboAutoHDR https://www.nexusmods.com/starfield/mods/588

Development of the mod is finished. My intent was the implement HDR, the rest was extra. I can't keep implementing every new technology from nvidia, I have other projects now. Regarding this mod being officially published, I can't comment on that, but it's not been ruled out.

I have a new version in the works that will improve the dlss ability to denoise ray tracing.

PCGW stores our files on DigitalOcean's Spaces service, specifically in their SFO2 datacenter primarily (San Francisco). We also use their CDN to cache files on their various CDN servers around the world. Currently DigitalOcean has ongoing network connectivity issues in the APAC region, so it's possible that users with connections that goes through that region can experience issues as a result.

Using gog version the savegame directory changes from "%USERPROFILE%\Documents\My Games\Control" to "%LOCALAPPDATA%\Remedy\Control\Default-Generic-User\", the structure and file names change too and need a whole bunch of manual renaming to adapt. HDR mode displays artifacting i can only describe as fireflies, they are not single pixels but slightly larger white blocks flashing randomly (not present in SDR, rx 7900xt with 23.1.1 drivers). Edit: The AMD fix does remove this issue entirely. Those things aside the HDR looks very impressive, miles ahead of AutoHDR, i can also confirm that FSR2 injection appears to work just fine.

Had the same problem as well. It's really unfortunate. Until some workaround is created, I'll have to play the game windowed in 1280x1024 for that extra viewing distance.

@camm I made a generic patcher for Alchemy a while back, only posted it on one forum though so it was probably pretty easy to miss... Reposted here: https://www.mediafire.com/file/387vesqfe7o91f4/GenericALchemyDerestrictor-1.0.zip/file Only tested with the 1.45.20 version, but it uses signature searching rather than offsets so should work with other versions too. (hopefully this is fine to post here, seeing as the Glossary:Sound_card page links to similar patches too)

this is a pic from the steam release, works perfectly fine 🙂

Thank you Rose. I found an easier and more reliable way to do this trick. You have to go to your "\Documents\Rockstar Games\Red Dead Redemption 2\Settings" folder. There, you'll see several files with .bin extension. One of these files contains the horizontal HUD location. Mine was named "400042567_19054853.bin". I don't know if the name may vary from computer to another. All of these files are in fact xml files and easy to edit with any notepad. I found the following key to contain the horizontal HUD location. <Item key="7014661855" type="rage__fwuiValueFloat"> <value value="0.328000" /> </Item> All you have to do is to modify the value to whatever you desire then set this file to be read only. Last step is important because it prevents the game from modifying this value. Once this value is modified never go back in game to the HUD location setting or it may reset the value in memory and it will revert the HUD location. This works really well for me.

I have remade this patch using the clean, DRM-free GOG version executables, if anyone wishes to play at higher frame-rates without DRM data, here is the patch: http://www.mediafire.com/file/9307hi3nkyhrdke/FPS_Fixes.7z/file Also, to the uploader, if you could update your upload with these files it would be very appreciated to me.

You need to either run the game as admin or move the game to some other location on your drive. The game can't write the save file where it is currently.

Thank you. I do not have any donation going on, this is pure love for the game, free and for anyone that wants to give it a try. Enjoy and have a nice time!

This version of the widescreen fix is outdated (dated 2016). There was a newer version made in 2019 that can still be downloaded by opening up his site in Wayback machine then copying the download link and removing the web archive part from the link (original MEGA download link so it still works) dunno if pcgw allows links but here: https://mega (dot) nz/ #!q8hWVKyI!eyDyd92xUXX-y2z5oCmC4egTHlGJth0h47mnYScg1yY

The patch works perfectly, you can see the reviews on the forum https://www.reddit.com/r/macgaming/

ATTENTION LINUX (STEAM) USERS If you are having difficulties using this mod, you may find the following helpful. I was having difficulties getting the mod to work (as you may have seen above), not because I couldn't open the application, but because the F9 enable button did not work. It is hypothesized this was because the application was not able to see the game was open, potentially because of a mismatch of opening the application in one Wine prefix, and the game opening in another. How I got this to work was to use Steam Tinker Launch. This package "is a versatile Linux wrapper tool for use with the Steam client which allows for easy graphical configuration of game tools". By using this tool I could configure the ultrawide mod exe to open at the same time with DBH through Steam. My system is running Arch and the GNOME desktop environment. I do not believe the Proton version, Wine version, or Steam version matters. - Installation - This will of course depend on your OS, but for arch with YAY it was as easy as: yay -S steamtinkerlaunch If you're unfamiliar with how to install on your system, check out the Steam Tinker Launch guide above. Before continuing, make sure Steam is closed. In a terminal, run the following command. This will add Steam Tinker Launch as a compatibility option in Steam: steamtinkerlaunch compat add The terminal will output something about creating a new symlink and pointing it to the appropriate location. - Configuration - Open Steam, go to your library, find Detroit: Become Human in the list. Right-click > Properties > Compatibility. Tick 'Force the use of a specific Steam Play compatibility tool', then select 'Steam Tinker Launch' from the list. If you don't see Steam Tinker Launch, close and reopen Steam, restart your computer, and/or re-run the 'steamtinkerlaunch compat add' command from above. Close the properties window down, and click 'play' to start the game. When the game begins to load, you will be greeted by a new Steam Tinker Launch window, which will only stay active for a few seconds. If you don't click anything it will launch the game, but to stop this from happening, click 'Main Menu' at the bottom-right of the window before it disappears. Another window will appear, with some DBH information at the top. You can ignore most of the buttons here, and select 'GAME MENU' from the list of buttons along the bottom of the window. Yet another window will appear. Here you will want to select (buttons found near the top): - Use custom command - Fork custom command Between 'Use custom command' and 'Fork custom command' there is 'Custom command'. By default this will contain the game's main exe file (DetroitBecomeHuman.exe). Click that and select @Rose's mod exe (in my screenshots below I renamed it to dbh.exe, but by default this will be 'Detroit Become Human ultrawide 0.9.9.exe'). Click 'SAVE AND PLAY' at the bottom. - Finalising - That is everything. Now the game will launch, but it will also launch the ultrawide mod exe. When the game is up and running you can alt-tab or super-key out of the game, and use F9 to enable the tool. You will get an indication it is working by the text changing green. Now you can use the tool as expected! Thanks to @Rosefor pointing me in the right direction. I can't take much credit for these instructions here, as I took them from this Reddit thread here.

That's just because the actual game resolution is smaller, and the nGlide wrapper just forces the 3D part to run at native resolution and it makes the 2D parts bigger (not sharper), you can achieve the same with dgVoodoo2 in Direct3D. Just run the game at a smaller resolution that matches the same aspect ratio (the lowest 16:9 equivalent that's close to 4:3's 640x480 which keeps the exact same aspect ratio is 864x486, just create a custom resolution in Nvidia Control Panel or AMD's equivalent), and force 2560x1440 in dgVoodoo2's DirectX tab. Also I recommend using the updated D3D.exe and fixer that comes with this patch, because the previous version of my fix used the 1.3 version's D3D.exe as base, and 1.3 has some bugs that might make the game unfinishable, so I based the fix on the 1.2 version instead, which is more stable overall and doesn't have those bugs.

I got like 15$ donations since the mod was first uploaded, so i doubt you'll manage to put together enough to buy a 4090 😁, but if I just found an RTX 4090 at my door, I couldn't really say no to implementing DLSS 3.5. But until then, I don't really have much more to say. Thanks for showing interest!

Oh well, I guess crowd funding a 4090 for you to implement Nvidia's DLSS3.5 AKA ray reconstruction, Would be a waste of time then 😉

I mean the Ray Reconstruction that should improve and fix the noise Issue of Ray Traced Effects literally works on all RTX cards from every generation. Only Frame Generation is 40 Series exclusive. I mean Nvidia and news outlets are probably to blame for the confusion that people think if DLSS 3.0's biggest feature was 40 Series exclusive that the latest DLSS 3.5 features would be as well, which they aren't. I am still using a 2080Super that I bought used earlier this year because I don't have the money for buying the latest GPU or donating for someone else's hardware. So while you getting donations for a 4090 is justified alone for keeping this game updated with the latest technological features, hope that you will look into adding support for Ray Reconstruction even without owning a 4090. And again thank you for your amazing work on this game!

If you crowdfund a 4090, I might do it 😁

There's no further development planned.

Could you add Skip Intro and Fix2D from Widescreen Fix please? Thanks.

The No DRM version is not the epic store version without DRM (none of them actually have DRM afaik), but it's also not the GOG version. I am unable to release that at the time, so please either start a new save or don't use the mod. I don't know about how the GOG save files work, but they are likely the same and conversion shouldn't bring bugs, but I can't confirm that.

I apologize for the disparaging comment on the mod, I have been told that the GOG version of the game is just prone to corrupting save files exactly like mine. It was just a coincidence that it only happened one hour after installing the mod, and the mod happened to involve non-standard access to save files. Here's a couple of .bat files I wrote to make things a little easier. This one will automatically copy the GOG saves over to the Epic save folder, provided it exists, provided the save you want to copy is slot 00, and provided you copied over your preferences file as well already. First step copies the files, second step adds ".chunk" to the end of the filenames, third step removes "savegame-slot-00_" from the beginning of the filenames. xcopy %UserProfile%\Documents\"My Games"\Control\Saves\savegame-slot-00_* %LOCALAPPDATA%\Remedy\Control\Default-Generic-User\savegame-slot-00\*.chunk @echo off setlocal enabledelayedexpansion set sourceFolder="%UserProfile%\Documents\"My Games"\Control\Saves\" set backupFolder="%LOCALAPPDATA%\Remedy\Control\Default-Generic-User\savegame-slot-00\" for %%I in (%sourceFolder%\savegame-slot-00_*) do ( set filename=%%I set newFilename=!filename:savegame-slot-00_=! set newFilename=!newFilename!.chunk go copy "%%I" "%backupFolder%\!newFilename!" ) Setlocal enabledelayedexpansion Set "Pattern=savegame-slot-00_" Set "Replace=" For %%# in ("%LOCALAPPDATA%\Remedy\Control\Default-Generic-User\savegame-slot-00\*.chunk") Do ( Set "File=%%~nx#" Ren "%%#" "!File:%Pattern%=%Replace%!" ) Pause&Exit Just save that to a .bat file and run it and it will copy your GOG saves over to the Epic location so you can run this mod. Again provided your saves are in slot 00, and the Epic saves directory exists, and you've already copied your preferences file to the other directory. This little guy is for me and anyone else running the GOG version, it will make a backup of all your saves to c:\_temp\savesbackup (or whatever you edit this to) every 30 minutes while it is running. Leave it running while you play the game, and if you encounter any game-breaking bugs like I did (which are NOT the fault of this mod) then you will have a save game to return to: @echo off :loop xcopy /s /e /y %UserProfile%\Documents\"My Games"\Control\Saves\*.* C:\_temp\savesbackup timeout 1800 goto loop

I have a similar problem. After installing the DRM-free version of the mod the game started using a different save folder and save format than the GOG version normally does, as described earlier in this thread. I followed the instructions previously linked here and converted the save files to the .chunk type in order to continue my playthrough using the mod. I encountered weird glitches like having to cleanse control points after fast traveling to them and being able to pick up collectibles I already had, but it was playable. Until after playing a couple of hours and fast traveling to a location that had previously had a scripted fight around the control point - this time I was unable to re-cleanse the control point and became stuck. I don't know why the mod changes the save location and format but it 100% does. And unfortunately this makes it unplayable on the GOG version, unless someone figures out a completely bug free method of converting the save files. Great mod though, if you're not using the GOG version.

savegame GONE - what the actual f*** !!!!! I've been playing this game for about 150 hours in total and decided to try this update... now my savegame has gone! I'm running the GOG version of the game.... can I get my savegame back?.... if so, how ?

there are some minor issues with this mod when replacing DLSS with FSR 2.1 from CyberFSR. some shaders clip in SDR and the sharpening causes massive overshoot on shiny edges in HDR (I saw 90000 nits at some point). to fix those edit the nvngx.ini and change the following settings: AutoExposure=true HDR=true

Yes I will return to SH4 soon.

Not anymore it's been replaced by d3d8.dll.

There is going to be an update comming out soon. You will be able to play at 32x9 with the update.

File is infected as fuck, avoid at all costs! Author has been informed. VirusTotal report: https://www.virustotal.com/gui/file/76295a621b8c9c408aa4434fba3207a9a29a0787ab527bff0ab7bfc89698a307

@jacobThere isn't a FH5_RT_WIN_v6.CT yet, we apologize for the confusion from the typo in @cevian 's original message. @cevianand I haven't needed to create a v6 version yet since the v5 version should still work just fine at this time. If we find that an update for the mod is necessary later on, we will be uploading the newer version to this forum page.

See if unpacking the file with Steamless helps. Adapt the first steps of this guide.

Crashing here too, even after enabling post the 'Press any button' screen. Not during loading, not during start up, just randomly while playing the mission 😟

Can confirm the crashes, seems quite random during gameplay. I've been enabling the tool when at camp. Really helpful tool shame the new update causes issues. 🤔

Warning! There is a virus in this file called "Contebrew.A!ml"

Open \patches\main.patch in a text editor and change the hotkeys #bind [PRESSED:VK_F5] → #bind [PRESSED:VK_F1] #bind [PRESSED:VK_F6] → #bind [PRESSED:VK_F2] #bind [PRESSED:VK_F7] → #bind [PRESSED:VK_F3]

That would suggest the issue stems from modifications made to the file by you though, not the trainer. It makes no changes to the game files and restores the original code in the memory when you press F8 again. For some display modes or other variables, it may also require pressing alt+enter twice to have the game read from its original code again.

Look up reverse engineering software on YouTube to get started 😁 Contrary to the popular belief, it usually takes many hours of disassembling, and few games are properly fixed by searching for the well-known aspect ratio or Unreal Engine 4 FOV-related bytes. If they are, the solutions are usually available on day one because every advanced ultrawide user knows them by now. From the developer standpoint, it's easier than it is from mine because they already have all their functions defined and documented as classes and such, while to me every game is a black box with many lines of pure assembly code to dig through. String references can be of value in 1% of the cases but the rest is discovery, trial and error. I actually think the community can be too harsh on the developers, because although on their end enabling ultrawide may be as simple as two checkboxes and a number of FOV values to convert from horizontal to vertical, expanding the field of view means there is a lot more space to fill with assets, as previously explained by me here. Shooting a film, two constructed walls in a warehouse can be enough to create the illusion of being inside a house with four walls and a roof. Imagine expanding the field of view to the point of the warehouse being visible and zooming out for the viewer to see the construction. It's usually not as bad in games but even a small out-of-place item or a pop-in can be seen as a significant problem capable of ruining the immersion and causing outrage. As ultrawide users, we are used to those and we can tolerate them and often forgive them when using an unofficial mod. Moreover, as a modder I have no responsibility if something goes horribly wrong, as my livelihood does not depend on it. With that said, I think it's fine to put some pressure on developers and show them that there is a demand for wider resolutions. No posts about it would never push them to improve or care, and there are quite a few cases of developers - like those of Terminator: Resistance or Disco Elysium - listening and shipping ultrawide support in post-release updates.

for me, it doesn't work, now my Windows 10 even says that there is a virus or unwanted file in the dllinjector.exe. Without these files, SH3 load fine, so the problem is not with the game or my system

It seems that you are not selecting the updated version. I downloaded this today and it worked perfectly fine, but on the flawless widescreen app there are two GTA plugins, you have to select the one with "(updated)" at the end. The author of the new one is Rose, you are using the original from HaYDeN.

Thanks for the continued feedback and offering to help. A while ago I had a user share their config file with me but it completely matched mine, so I had no idea what was wrong. I had another look at the game today and it turned out that it was indeed a global issue and I either didn't notice it earlier or it didn't occur for some reason. I updated the mod to hopefully put this particular issue to rest - tested at all the listed resolutions again. There are still a couple of unrelated imperfections I'm aware of and I might try to fix them in the future as well.

Already updated!

You're a treasure Rose. Thank you for this!

For anyone with concerns about this tool I have made an open source one at https://github.com/cecton/patch-ultrawide-the-outer-worlds

As the off-topic discussion have served its purpose and deteriorated past its relevance I've cleaned out the thread and locked it from further comments. The never-ending race between malware creators and anti-malware suites means that general-purpose legitimate tools and utilities that might enable nefarious purposes can and will eventually be used as such, which will understandably trigger a response from anti-malware suites. While some AVs might just flag an individual known file as malicious, others use more general-purpose detection patterns that gets triggered on all files based on that pattern, whether they're used for malicious purposes or not. To further complicate the matter, the last decade have also seen protection suites expand outside of their original intended use-case and started to flag other files that might be seen as inappropriate or unwanted, even if they might not be malicious to the end user per se. This can be from everything that might install ad software that runs in the background (often categories as "Potentially Unwanted Applications") or tools or utilities that allows the patching of another application (prime example being CheatEngine) as these might be in some cases used to allow the unauthorized or unlicensed use of an application. The recent events that resulted in the retirement of the dedicated Widescreen Gaming Forum (a community dedicated to improving widescreen gaming experience in games) is a clear example of how volatile and uncertain the situation have become. As a result PCGW can't ensure or guarantee the safety of community contributed files, and users downloading and making use of files does so at their own risk, per our disclaimer. As content on PCGW are community-created, what options are available (such as an easy-to-use tool or manual patching instructions) are up to community creators, and we welcome contributions from new as well as old community members. If anyone feels that they would rather make use of another method that's currently not documented, feel free to add it to the article for the game. Edit 2019-11-04: Comments have opened again as more than a week have passed.

This version is out of date. A up to date version can be found here.