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

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

Done, added support for the Russian version.

It was a mistake in my code, it's fixed now.

It's possible to force the game to use windowed mode but it has some issues. Set these values in dgVoodoo.conf FullScreenMode=false AppControlledScreenMode=false DisableAltEnterToToggleScreenMode=false

Try now. Make sure you delete the old one and don't try to change the FOV from the config.cfg.

You're welcome, glad it works now.

It does work, both in retail and Steam versions. Could you send a screenshot of the fix's log file?

Hello everyone! Today I bought the game and encountered the same issue. Searching for solutions, including disabling GSync, changing the monitor refresh rate, and toggling all other relevant settings in the game, in the Nvidia Control Panel, and in Windows yielded nothing. I can confirm that the only working solution is the one discussed in this thread. Since the patches are long outdated, I spent some time examining GameAssembly.dll and want to share a working method to manually fix the stuttering issue in the current and potentially any future version of the game. We already know that the issue arises from the static update timer setting of the Unity engine, and editing GameAssembly.dll is required to synchronize the engine timer (specifically, the fixedDeltaTime function) with the FPS you are playing at. I will try to describe everything as detailed as possible so it is helpful for players without any IT background. I am almost certain that in-game graphics settings do not affect the problem, nor do the relevant parameters in the Nvidia Control Panel. I haven't tested all possible combinations, but in my case, it is set up and working as described below. Game settings: Build 21464562 from 23 January 2026 (https://steamdb.info/patchnotes/21464562), Steam version, all settings on maximum, fullscreen mode. Nvidia Control Panel settings (global for all games): VSync depends on the application (i.e., enabled since the game has no VSync setting and it's enabled by default), GSync is enabled in fullscreen and windowed modes, 118 FPS cap (for reliable GSync operation), Low Latency Mode is set to Ultra. System: Win 11 Pro 25H2, RTX 5090, Nvidia Display Driver 591.86, 120Hz monitor. Now let's edit GameAssembly.dll. I didn't arrive at this method immediately; at first, I tried to find the necessary offset using Il2CppDumper and analyzing Assembly-CSharp.dll via dnSpy, but came to the conclusion that the easiest way is to... test the 3 offsets in GameAssembly.dll one by one 🙂 Yes, it turned out to be that simple. The library contained exactly 3 occurrences of the value 0.02 (the fraction of a second that passes between two logical engine updates), which is the engine timer for 50 updates per second. So let's begin. Method for build 21464562: Find a HEX editor of your choice. I use the classic HxD, but in this tutorial, we will use https://web.imhex.werwolv.net for simplicity. Locate the GameAssembly.dll file, it is in the game's root directory. Right-click the game in Steam -> Manage -> Browse local files. Make a backup of the file! Open the file in the HEX editor via File -> Open File or by dragging and dropping. Perform a search via View -> Find. In the Find panel that opens, select the Numeric Value mode, enter 0.02 in the Value field, select the float type from the dropdown list, and click the magnifying glass icon. It should find 3 offsets: 0x01F983D8, 0x022972B8, 0x0234A9B5, but there might be more, fewer, or different offset values depending on when you are reading this tutorial and how many updates have been released. If your offsets do not match the tutorial, proceed to the method of testing values one by one below. We need the second offset 0x022972B8. Double-click it in the search results panel, and in the editor panel, you will jump to this offset. Copy the required FLOAT (not HEX and not FPS) value (without spaces, just the value) from the list below corresponding to your configuration or target FPS. Return to the HEX editor. To the right of the editor panel is the Data Inspector panel; find the float field there, make sure it says 0.02. If it is not 0.02, start over, you are doing something wrong. Double-click the float field and paste the copied FLOAT value into it, then press Enter to save the changes. Save the file via File -> Save As... It will download as file.bin, rename it to GameAssembly.dll, and replace the original GameAssembly.dll in the game folder. Launch the game and test it. If something went wrong, restore the file from your backup or verify the game files in Steam and start over. Method for any build: If your build is not 21464562, if more or fewer than 3 offsets are found, or if the offsets do not match 0x01F983D8, 0x022972B8, 0x0234A9B5, then the easiest option is to test the offsets one by one, thankfully there are only 3 of them. You need to do the exact same things described above but with all found offsets in a row. Follow steps 1-4, find a certain number of offsets. If there are three offsets, the second one is most likely the correct one. Edit it as described in steps 5-9, and launch the game. If it didn't work, restore the GameAssembly.dll file from the backup or by verifying files in Steam, try with another offset, and repeat until successful. If none of the offsets worked, it means the developers changed the engine update timer and it is no longer equal to 0.02. Here you will need to find a new value, but that's a completely different story 🙂 List of values for different FPS with and without GSync: These Float values are calculated with maximum machine precision (little-endian float), so the engine physics will work without losing synchronization, provided that your target FPS matches. FPS - FLOAT - HEX 58 - 0.01724138 - CB 3D 8D 3C 60 - 0.01666667 - 89 88 88 3C 73 - 0.01369863 - 38 70 60 3C 75 - 0.01333333 - 0E 74 5A 3C 98 - 0.01020408 - 05 2F 27 3C 100 - 0.01000000 - 0A D7 23 3C 118 - 0.00847458 - F3 D8 0A 3C 120 - 0.00833333 - 89 88 08 3C 142 - 0.00704225 - B4 C2 E6 3B 144 - 0.00694444 - 39 8E E3 3B 163 - 0.00613497 - DA 07 C9 3B 165 - 0.00606061 - 0C 98 C6 3B I hope I helped someone deal with this issue. I highly doubt I will return to this forum after beating the game, but I will monitor questions for a while if there are any left. Good luck with your playthrough everyone 🙂

Very strange indeed. I honestly am not sure how to help you. You might try removing those d3d dlls and play in native DX8 mode. Also, check if antivirus haven't blocked any files in the game's folder.

Same here. What fixed it for me was: Download the latest DxWrapper. Extract dxwrapper.dll, dxwrapper.ini into the game's main directory. Extract ddraw.dll and Stub.ini from the "Stub" folder into the game's main directory. Rename Stub.ini to ddraw.ini. Extract the AlphaYellow's widescreen fix into the scripts folder (if it doesn't exist, create it) and configure it's .ini file. If you wish to use it with dgVoodoo2 or want bigger UI, look up those guides: https://www.pcgamingwiki.com/wiki/Hitman:_Codename_47#Combining_the_Widescreen_Fix_with_dgVoodoo_2 https://www.pcgamingwiki.com/wiki/Hitman:_Codename_47#Too_small_UI_elements_at_higher_resolutions

IT WORKED!!!!!!!! Finally I can play this game. I'm taking a new education and this game is such a sweet guilty pleasure in breaks. Thank you so much! Other than the uninstall which I described above I did the following and nothing else: Installed the game on steam Installed OpenAL Installed WaterVaporGoggerMTFix(placed in the game folder) Placed OpenAL32.dll, dxvk.conf and d3d9.dll in the folder Checked dxvk.conf to see if the refresh rate was correct In my case I think there were files or registry entries left over after the steam uninstall that made things impossible.

@AtotehZ DXVK addon consists on 2 files, one dll file and one conf file. Like this capture: If you only get the conf file, your antivirus might be doing naugthy things. And maybe the GridMTFix is not applying correctly. Check your config. Also, If none works, be sure to check if you have the UTF-8 Support bug of Windows. Check as stated on the PCGW : To fix the UTF-8 issue: Open the Windows Control Panel. Go to Region. Click the Administrative tab. Click Change system locale.... Remove the checkmark next to "Beta: Use Unicode UTF-8 for worldwide language support". Click OK and restart your computer.

Metal_Gear_Rising_Revengeance_PCFix.dll = the asi (asi files are essentially just renamed dll's) ------------- @Steam006: I noticed that the game doesn't automatically default to a user's dedicated GPU in multi-gpu environments (ie laptops with both an integrated intel chip & a nvidia gpu) In case you want to fix that bug too, just add this block anywhere in your mod; extern "C" { __declspec(dllexport) DWORD NvOptimusEnablement = 0x00000001; __declspec(dllexport) int AmdPowerXpressRequestHighPerformance = 1; } e.g.; https://github.com/Lyall/MGSHDFix/blob/master/src/fixes/fix_default_gpu.cpp (These exports just tell graphics drivers to automatically use the dedicated GPU instead of whatever's enumerated first in Windows's device list when d3d inits.)

update: found a way to run this on proton via steamtinkerlaunch (https://github.com/sonic2kk/steamtinkerlaunch) on game files: select a custom command and put this mod's exe on it, then click on fork custom command, that will make the ultrawide mod and yakuza run both on the same wine / proton prefix, making them communicate with each other.

!!THIS FILE CONTAINS SEVERAL VIRUSES. DO NOT DOWNLOAD. malware warning!!!!

I already handled it, don't worry. Just wanted to make sure you are aware.

Looks like it's working all correct for me now, thank you so much! I also appreciate how quick you were to respond after I left you a comment and wanted to resolve this small issue, it's very cool of you. Also on the topic of improving this mod I think it would be really neat if your widescreen script could also handle the HUD/UI scaling if that's even possible in this game. AND ALSO HAPPY NEW YEAR!!! ✨🎉 ( I will be doing my yearly replay of this game tonight )

This was unexpected. Thank you very much!

Thank you, AlphaYellow, for your great work on the FOV modification for From Dusk Till Dawn. Your expertise and effort made a real difference, and the result is perfect. I truly appreciate your time and skill. Keep up the amazing work!

Hello Himanshu, it's really a great help you've provided to the old players of Recoil game. Could you please provide me with your Telegram or whatsapp id....

Microsoft has released the October 28 KB5067036 Preview Windows 11 update which has fixed movie playback.

Thank you! Just decided to replay it after Village, and stretched 2D is awfully looking. It's a must-have one! 🤝

It puts a limit on the speed of animations.

Heads up, for some reason using "XInput Plus" with the "ReplaceMoviePlayer" shows a black screen instead of the FMV, to fix it do the same steps as the fix for the Audio Enhancement Pack crashes, by going into XInputPlus.ini and set UseInitBeep=FALSE edit: although it seems the blackscreen still happens in some fmv? the lisa fmv in the hospital played correctly but afterwards it was just a blackscreen but could still walk and interact with menus, just that everything was black, switching to ReplaceMoviePlayer to 0 and then saving fixed the issue for now

Thanks. renaming asi loader to winmm helps me.

I know some games like Chaos Legion on PC that have effects like depth of field tied to resolution; at 1080p it's muted to the point it's invisible but at 480p-dgvoodoo'd to 1080p the depth of field effect is low-res and pixelated. However, for Contracts I don't recall any type of resolution-dependant effects in use, I last played the game a few months ago and nothing in particular caught my eye unless I'm wrong as the only other system I've played it on is the PS3 HD edition. Didn't take as many screenshots when I played but here you can see the bloom is intact and not pixelated as it is usually a resolution-tied effect in some games

I've been waiting for this for a while thank you! did you know that the game had its source code released by the way? https://github.com/dizzy2003/MuckyFoot-UrbanChaos

I didn't know that, thanks a lot.

Actually, the latest compatible version is 2.81.3. I can't find any working link but I've attached my local copy to help. dgVoodoo2_81_3.zip

Well, I left the navigator computer view as Vert- to allow the text to be seen, try the new version I just posted, might work for you this time.

@psxmichacorrect, private message sent.

Update 20250811 - Added: Alternative dbghelp dll proxy In case winmm dll doesn't work, there is now an alternative. Let me know if the alternative also doesn't work @psxmicha and others

@psxmicha dsound.dll: Thanks for the very useful feedback, Now I know why it doesn't work with winmm on some systems. (I will add further options) v1.2 mp or sp ? (mp v1.2 not supported) with custom patch? what you mean by "version"?

can confirm this does allow achievements to pop, just 100%ed it 🙂

@zerocool22 Private message sent

Mr. Xator I just wanna say thank you for truly keeping this game alive and your dedication to helping others. Cheers my friend and if you happen to have a discord/donation page I will gladly contribute. For others who see this, simply patching the exe file fixed all the issues I encountered with the GOG version of the game on a Lenovo Legion GO. Portable Grid never felt so good.

Weird, but I can give you some pointers: Since you have a laptop, be sure to be launching the game with the NVidia card. You can do that adding the EXE file to the nvidia control panel, NVIDIA Control Panel > Manage 3D Settings > Preferred graphics processor setting, and select your 3050Ti from there. Also, GOG release comes without OpenAL for the sound. Be sure to install it from here: https://openal.org/downloads/ Finally, if all of the above fails, please check if the game is launching correctly: go to %userprofile%\Documents\Codemasters\GRID\hardwaresettings and share both files here, for me to check the values.

You were right about tweaking it. This is what worked for me with the Windows 10 taskbar on the bottom of the screen and not on autohide: if(o0.x > 0.465){o0.x += 0.535;}else{ if(o0.x < -0.465){o0.x -= 0.535;} Thanks for the advice! It's nearly perfect. The only thing I notice now is that there is pop in textures and text that is not usually rendered is blurred. Do you know if any of the settings in the ShaderFixes file increase the render distance? Would love to have my cake and eat it too. :)

I was surprised to see it on the next day actually) Thank you for fixes and their updates!

Oh yeah, there is another widescreen fix, honestly at this point I'd outright ignore it, it just fixes the resolution and nothing else.

I´m sorry, i just noticed i modified the exe File from an older Widescreen Fix and that prevented your Fix to work. All is working now.

Okay, wow. Never expected a Widescreen Fix for that Game.

hey, since you don't seem to have the time to update the mod, could you please release the source code at least? like maybe I can at least do the same thing with cheat engine or something like that. surely the general method hasn't changed between the versions, just the offset?

I uploaded that file to the /r/BackyardBaseball Discord server.

There is a typo in PecanEngine.ini on line 626- bAllowDistributedShaderCompile=Ture (should be True). There may be more mistakes like this but this is the only one I've happened to come across so far.

I just now saw this, Sorry. I tried that just now and It didn't work, but I didn't stop there. I did some research and it is actually the valve_addon folder and Allow custom addon content must be checked in the settings. I will be updating the instructions as well as compile the latest revision and provide a version that works with Retail Half-Life also when I get the chance.

Latest version available directly is Creative Alchemy v1.45.19 https://support.creative.com/downloads/DriverDetails.aspx?driverID=100239 Judging by changelog, 1.45.20 is integrated into Sound Blaster AE-7 and Sound Blaster AE-9 driver packages. P.S. I've just installed their driver packages AECMDMasterInstaller_3.4.72.00.exe and surely C:\Program Files (x86)\Creative\ALchemy folder appeared and dsound.dll there has version 2.4.2.18, like that changelog above says. P.P.S. If that link https://support.creative.com/downloads/DriverDetails.aspx?driverID=100239 doesn't work for you and shows error page instead, switch country on that page to United Kingdom in low right corner and click link again, it should work then.