All Activity
- Today
-
My guess would be performance. Mafia was already kind of pushing the hardware of it's time to the limits, so they've probably tried to make it more accessible for people with weaker rigs. Yup, the race is easy if you're actually paying attention and learn the handling. Digital re-releases of this game isn't the most graceful one. I'd suggest buying old games from GOG, since those releases are usually better.
-
contact5156 reacted to a post in a topic:
Add the "See the engine page for more details." for unreal engine 3 to Template:Video
-
Markie reacted to a post in a topic:
Add the "See the engine page for more details." for unreal engine 3 to Template:Video
-
polariss69 joined the community
-
Is there a reason as to why eye animations and car scratches were remove from version 1.2 ? Also on the side note I did beat the race mission on version 1.0 during my test run, I do remember my older brother beat it on version 1.0 back in the day, when I played it on gog version, there's already been choice of diffcult options, but to be fair I didn't find any diffrents between 1.0 and 1.2 that much, the race isn't arduous per say, it's just matter of not going too fast at curves. P.S. Strange how Steam forgot to add A7.dta - Records for Czech Dub, since that's the reason for broken lipsync.
-
linciyik joined the community
-
passs joined the community
-
- 3 comments
- Yesterday
-
jacobi joined the community
-
matiko13 started following Need For Speed: Porsche Unleashed Combined Patch
-
Need For Speed: Porsche Unleashed Combined Patch
matiko13 commented on radishface's file in Unofficial patches
-
matiko13 joined the community
-
Call of Duty: World at War - Custom Patch
LuKeStorm commented on LuKeStorm's file in Unofficial patches
-
dexter_desantino joined the community
- Last week
-
Mystyle48 started following Adventures of Nyangi - Full Version and Darkened Skye - Demo
-
-
-
ismajooj joined the community
-
AlphaYellow started following World's Greatest Coasters 3D - Widescreen & FOV Fix
-
Version 1.0
2 downloads
Comes with a RAR file, which includes an ASI plugin intended to fix the resolution, aspect ratio and field of view in the rollercoaster building game "World's Greatest Coasters 3D" (2002), since the game runs at limited 4:3 resolutions by default. Source code available here: https://github.com/alphayellow1/AlphaYellowWidescreenFixes/blob/main/source/fixes/WorldsGreatestCoasters3DWidescreenFix Instructions: 1. Extract all files to the game folder. 2. Download ThirteenAG's Ultimate ASI Loader (32-bit version of dinput8.dll), and also extract it to the game folder. 3. Set the desired resolution and FOV factor in WorldsGreatestCoasters3DWidescreenFix.ini. 4. Once in-game, alt+tab to the desktop and back to the game (this is to fix a viewport-related issue). -
uroshuchiha started following Soul Reaver 2 trailer , Legacy of Kain: Blood Omen - Verok's GL Wrapper & Patch and SRHook
-
jcopas joined the community
-
Hi, I installed v2.8.3 and now the game stutters a lot when fading out. It seems to drop to 5 FPS for some reason and it's really jarring. I've tried messing with my Nvidia GPU settings, the FPS settings in the ini, the core processes in the ini, and nothing seems to fix it. I'm fairly certain it was not like this until the most recent update. Any ideas? Processor: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz Graphics Card: GeForce GTX 750 Ti Windows: Windows 10 desktop Edit - Just needed to restart my PC, sorry for the false report
-
Version 1.0.0
2 downloads
Description: XP-compatible ASI build of the original X: Beyond the Frontier - FOV Fix. This version is intended for legacy Windows XP setups and fixes Vert- style image cropping/stretching on widescreen resolutions by correcting the in-game FOV behavior. Mini installation guide: 1. Copy dinput.dll (Universal Windows XP ASI Loader) into the game folder (next to X.exe). 2. Copy X-Beyond-The-Frontier-FOV-Fix-WinXPEdition.asi into the same folder. 3. Copy X-Beyond-The-Frontier-FOV-Fix-WinXPEdition.ini into the same folder. 4. Configure resolution in the INI: Width = 0 and Height = 0 = auto-detect desktop resolution or set manual values (for example 1920 / 1080) 5. Start the game. Testet with X-BtF Version 2.2 (July 2010) Known Bugs: Use Turbo of X-Ship resets Fov to wrong value. Press F12 and click cancel in the Menu, to fix this. Credits: Original fix and concept: AlphaYellow Original PCGW release: https://community.pcgamingwiki.com/files/file/3934-x-beyond-the-frontier-fov-fix/ Original source code: https://github.com/alphayellow1/AlphaYellowWidescreenFixes/blob/main/source/fixes/XBeyondTheFrontierFOVFix/dllmain.cpp Windows XP adaptation/build: based on the original patch above. Universal Windows XP ASI Loader builded by my self. -
neocromicon joined the community
-
fujispeed06 joined the community
-
-
SubSonix reacted to a comment on a file:
Disco Elysium - 60hz/60fps Camera Stutter Fix
-
Disco Elysium - 60hz/60fps Camera Stutter Fix
fourtytwo commented on LoafyX's file in Unofficial patches
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 🙂 -
13 downloads
Important notes: - It includes controller HUDs for Xbox 360 and PS3, as well as low resolution ones for PS2, Gamecube, and OG Xbox. - It requires Rayman Control Panel. - It's recommended to install Better Rayman 3 and (for the high resolution HUDs) HD textures first. - This mod is for the main menu only, as the controller buttons will not show up in the dialogue boxes. - It's important to mention that since each HUDs are directly extracted from the assets of each Rayman 3 port, there are elements of this mod that are unrefined, such as the "mnu_fix.png" files, which are why alternative files (aka. "mnu_fix (alt).png") are included in each folder, The original "mnu_fix.png" files (as well as the PS2, GameCube and OG Xbox HUDs) are still included in case someone planned to fix them one day. --------------------------------------------- How to download and install the mod: 1. Download the .zip archive for Better Rayman 3 HD. 2. Extract the archive. 3. Open Rayman Control Panel. 4. Select "Rayman 3", and find the "Archive Explorer" section. Select "Open". 5. Go to the folder "tex32_1.cnt" and then go to "menu", and then right click the file "mnu_fix" and select "Import and convert". 6. Go to your extracted archive, and go to "hi res/low res > (your preferred controller) > tex32_1.cnt and tex32_2.cnt > menu" and select either "mnu_fix.png" or "mnu_fix (alt).png". 7. Now go to the folder "menupc" and right click "mnu_gen select "Import and convert". 8. Go to your extracted archive, and go to "hi res/low res > (your preferred controller) > tex32_1.cnt and tex32_2.cnt > menupc" and select "mnu_gen.png". 9. After the files are imported, select "Save Archive". 10. Repeat steps 5-9 for "tex32_2.cnt". -
Version 1.0
5 downloads
Comes with a RAR file, which includes an ASI plugin intended to fix the aspect ratio and field of view in the action flight combat game "Rebel Raiders: Operation Nighthawk" (2005), since the game stretches the view at resolutions with an aspect ratio wider than 4:3. Source code available here: https://github.com/alphayellow1/AlphaYellowWidescreenFixes/blob/main/source/fixes/RebelRaidersOperationNighthawkWidescreenFix Instructions: 1. Extract all files to the game folder. 2. Download ThirteenAG's Ultimate ASI Loader (32-bit version of dinput8.dll), and also extract it to the game folder. 3. Set the desired resolution to fix the stretching and FOV factor in RebelRaidersOperationNighthawkFOVFix.ini. -
I'm hoping someone here has run into this before. The game previously launched and ran correctly, but after changing some display / resolution settings it now refuses to start properly. Current behavior: • Launch game from Steam • Safe Mode prompt appears • If I choose Yes, the game still behaves the same • The game logo appears briefly • Screen flickers black for a moment (looks like it's attempting to switch video mode) • Game immediately exits back to Steam with no error message No crash dialog, no Windows error, nothing in Steam. Important context: Originally the game kept launching on my secondary monitor instead of my laptop display. I was experimenting with resolution / display mode settings trying to correct that. After doing so, the game began exhibiting the behavior described above. So the issue started immediately after changing resolution/display settings. System: Windows 11 Lenovo laptop NVIDIA RTX GPU Dual-monitor setup (laptop display + external Dell monitor) Game installed via Steam Troubleshooting attempted so far: • Launching in Safe Mode • Verifying game files in Steam • Updating NVIDIA drivers • Switching Windows display to single-monitor mode • Disconnecting the secondary monitor • Various launch attempts after restarting None of these changed the behavior. One thing I noticed is that the folder: Documents → Call of Duty Modern Warfare Remastered exists but appears empty. I'm wondering if the game is failing when it tries to load or create its video configuration. If anyone knows how to manually reset the renderer / display configuration, or has seen this exact launch behavior before, I'd really appreciate the help.
-
I have a GamesSir Nova Lite controller and the game wont even start IF I have the controller connected to the PC (Dongle or USB), starting the game and connecting the controller later make the game not recognize the controller. Using the files on this topic I was able to open the game with the controller plugged on the PC and to select the controller on the game Control Options, but no input in the controller affects the game. Also lots of throtlling. It is already an improvement, so thank you. This solved the issue for me. Game start, no trothttling and controller working. Thank you very much.
- 19 comments
-
- controller
- assassins creed
- (and 5 more)
-
- 1 comment
-
- widescreen
- widescreen fix
-
(and 1 more)
Tagged with: