Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 12/11/2025 in all areas

  1. AlphaYellow

    Version 1.1

    41 downloads

    Comes with a RAR file, which includes an ASI plugin intended to fix the resolution and aspect ratio in the survival horror first-person shooter game "Nosferatu: The Wrath of Malachi" (2003), since the game only supports limited 4:3 resolutions (800x600, 1024x768 and 1280x960). This fix, unlike jackfuste's one, allows both resolution and FOV to be fully customized. Source code available here: https://github.com/alphayellow1/AlphaYellowWidescreenFixes/blob/main/source/fixes/NosferatuTheWrathOfMalachiWidescreenFix Instructions: 1. Extract all files to the game folder. 2. Download ThirteenAG's Ultimate ASI Loader (32-bit version of winmm.dll), and also extract it to the game folder. 3. Set the desired resolution and FOV factor in NosferatuTheWrathOfMalachiWidescreenFix.ini.
    2 points
  2. Steam006
    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.
    2 points
  3. carter

    20 downloads

    Need for Speed: Underground had a total of 4 patches. If you install the last patch 4, it misses certain files, which were changed in patch 1-3. Since patch 1-3 were not released as an .exe and can not easily be installed anymore, I gathered the changed files, which can be copy-pasted into the game folder. This works for any region. Instruction: Install NFSU patch 4 extract missing patch files into your game folder
    1 point
  4. Blackbird
    I already handled it, don't worry. Just wanted to make sure you are aware.
    1 point
  5. xnastyx
    BMT.EXE Here you go thanks for your work!
    1 point
  6. Patrxgt

    Better Rayman 3+

    Orzełek reacted to Patrxgt for a file

    21 downloads

    Updated version of the Better Rayman 3 mod for Rayman 3: Hoodlum Havoc that uses more modern wrappers and tools to provide pain-free experience on the modern machines. Installation: Follow instructions enclosed in the "ReadMe.txt" file. Credits: RibShark - Original Better Rayman 3 doitsujin - DXVK samuelgr - Xidi ThirteenAG - Ultimate ASI Loader ICUP321 - Classic button layout for controllers Me - Putting it all togheter, creating batch scripts, configurations, modern button layout for controllers, playtesting, etc.
    1 point
  7. AlphaYellow

    Version 1.0

    7 downloads

    Comes with a RAR file, which includes an ASI plugin intended to fix the resolution, aspect ratio and HUD in the third-person action-adventure game "Over the Hedge" (2006), since the game only runs at limited 4:3/5:4 resolutions by default. Source code available here: https://github.com/alphayellow1/AlphaYellowWidescreenFixes/blob/main/source/fixes/OverTheHedgeWidescreenFix Instructions: 1. Extract all files to the game folder. 2. Download ThirteenAG's Ultimate ASI Loader (32-bit version of winmm.dll), and also extract it to the game folder. 3. Set the desired resolution and FOV factor in OverTheHedgeWidescreenFix.ini.
    1 point
  8. Dgrdsv
    What's the reasoning behind showing both DLSS FG and MFG as separate options in the Frame Generation field of Video section? DLSS MFG is a superset of DLSS FG, which means that if a game supports DLSS MFG then it also supports DLSS FG by definition (i.e. MFG 2x mode). The way it is now just creates a lot of visual noise where you have something like this in the field: I'd suggest on either hiding FG if MFG is also set in this field - and maybe adding a note on this to the editing guide? That you don't need to specify DLSS FG is you are specifying DLSS MFG. Or tuning the template to combine these into one label, for example: "DLSS Multi- & Frame Generation", although this seems excessive to me for reasons explained above. Another suggestion I have is to abbreviate the "Frame Generation" labels there to just "FG". We have the field name on the left and the labels are linking to Glossary pages, should be obvious what it means. So above would shorten to just this: And would look a lot closer to the High-fidelity upscaling field above.
    1 point
  9. AlphaYellow
    No problem. Also, happy new year too 🙂 For the HUD size, you can actually run the game at a smaller 16:9 resolution (set it in the fix's INI), and force your native one on dgVoodoo2, makes the HUD way bigger and like it should.
    1 point
  10. uprighthorse3
    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 )
    1 point
  11. AlphaYellow
    Thanks, I updated the fix now.
    1 point
  12. miller11568
    Can you help me hex edit pun.exe to skip the copyright screen every time The Punisher (2005) starts? I skipped intro videos using ThirteenAG's widescreen fix but I have not tried that trick yet. Thanks in advance.
    1 point
  13. jackbow
    UPDATE. It's Solved. Just had to run the game as administrator. Aspen.cfg showed up on the game's folder. Give administrator status to the both Aspen files and saved it.
    1 point
  14. jackbow
    Hi! Here is a screenshot of my Aspen.cfg, I had to edit it in other folder, because I am not allowed to save the edited file in the Gmae folder, so I copy and paste it to other folder, edited it there and then paste it on Game folder. The widescreen is not working for me. Any help please? Thanks!
    1 point
  15. jackbow
    @AlphaYellowI tried everything, I can't fix the aspect ratio. I'm disappointed.
    1 point
  16. taxakla
    This was unexpected. Thank you very much!
    1 point
  17. Aemony
    So to summarize: Steam client == the digital distribution client used to download and install games. This client alone is not regarded as DRM from the perspective of PCGW nor have been since around 2017-2019. This corresponds to the Source column of PCGW's availability table. Steam DRM == the actual DRM component provided by Valve to game developers, and which are embedded as part of the game executable and applies various forms of piracy and tamper protection to the executable. This is tracked as "Steam" within the DRM column of PCGW's availability table. Steamworks API == the "Steam API" used by games to communicate/interface with the Steam client to unlock achievements and such. This is technically not DRM per se (it doesn't inherently have a dependency on the Steam client) but common misuse of it by game developers can result in it acting as DRM (not allowing the game to be launched without the Steam client running). This is tracked as "Steam" within the DRM column of PCGW's availability table when it acts as such despite using a steam_appid.txt file to provide it with the App ID of the game. DRM-free == A Steam game is DRM-free if it fulfills both of these requirements: the game does not have the Steam DRM wrapper embedded in the game executable and the game does not have the Steamworks API act in a DRM-like capability when provided with an appropriate steam_appid.txt file. If a Steam game fulfills both of these requirements, meaning they can properly be launched separately without the Steam client installed or running on the system, it's marked as DRM-free within the DRM column of the availability table Our main issue isn't with the way the templates are treating this -- it's with people filling out the fields without improper testing (which only education and training can resolve) and legacy data provided and inserted from PCGW's younger years before we separated the client/launcher from the DRM tracking (which can only be resolved by someone going back and retesting all of the games).
    1 point
  18. Aemony
    There is no need to split anything as the way it’s being tracked is already fine enough. The issue isn’t with how PCGW handles it — it’s with how users, and typically in the past, filled out the information and that issue would remain regardless of what change was implemented. Steam DRM refers to the DRM component of the game. It doesn’t refer to the Steam client (the launcher) at all. And regardless of its efficiency, it’s still DRM and treated as such by PCGW. As I mentioned, we don’t care about the efficiency of a DRM solution. If it’s DRM it’s DRM, regardless of how reverse engineered and easy to remove it eventually becomes. And to clarify PCGW does not consider the Steam client as DRM, nor have we done that since around 2017-2019.
    1 point
  19. Aemony
    The Steam DRM wrapper is DRM -- there's no question about that. It's however not a proper full-blown anti-piracy solution because of the basic and standardized protection measures it employs. As Valve themselves says, it protects against extremely casual piracy (and tampering) and wouldn't prevent a motivated actor. But that's all besides the point for PCGW -- the site doesn't make a distinction between a "successful" DRM and a "so well documented and reverse engineered it's functionally useless" DRM. They're both equally treated as DRM on PCGW. That thread is insanely out of date and harkens back to the very early design and guidelines the site had over a decade ago. The modern approach and coverage of DRMs and stores (where Steam/Epic/etc games can be flagged as DRM-free) were introduced later sometimes around 2017-2019 or so. As I said in an earlier post, there's not a lot PCGW can do about this to improve it further as we've already built and implemented everything that's required to flag DRM-free titles on Steam/Epic/etc as such since years ago. Your issue, at its core, is with older unmaintained game pages and potentially incorrect DRM tracking within them and there's nothing the PCGW staff can really do about. Those pages and DRM claims needs to be gone through by an owner of said games, and then verified and updated/corrected where possible. And it is pretty much all of the game pages that would need to be gone through as most of them almost certainly lack an actual reliable reference to the DRM claim being made. And when it comes to that kind of job, PCGW is a community project where literally anyone can edit the game pages so anyone would be able to take on that kind of project upon themselves and go through and do it. The staff itself, however, will pretty much never have the time to do anything like that since their focus is on other areas.
    1 point
  20. Mastan
    All that info is already provided via icons and text, any specifics are mentioned in notes. Examples: Activation limit: https://www.pcgamingwiki.com/wiki/Mirror's_Edge Constant Internet connection: https://www.pcgamingwiki.com/wiki/Battlefield_2042 Description of all DRM types: https://www.pcgamingwiki.com/wiki/Digital_rights_management_(DRM) Custom Executable Generation seems to be obsolete btw: https://www.pcgamingwiki.com/wiki/Digital_rights_management_(DRM)#Custom_Executable_Generation
    1 point
  21. Aemony
    Hi, PCGW already makes that distinction where possible, however the incorrect DRM tracking stems from editors assuming that a specific store-provided DRM option is used for a game at the time the article was created, which is often months or years before the release of the game. The intention is for editors to always follow up and validate the claim upon release, if possible. The ”store DRMs” that we supports refers to those store-provided DRM options, e.g. Steam DRM for Steam, EOS/EGS based DRM for Epic Games Store, EA’s DRM for EA App, etc. So they do not technically refer to the storefronts themselves, but the clients/underlying platform used to enforce said DRM. This is also why PCGW support flagging a DRM such as ”DRM-free*” (with a star/wildcard), in scenario where digital distribution releases (e.g. Steam games) requires a few manual steps to ”access” its actual DRM-free nature (e.g. steam_appid.txt for some Steam games). PCGW also note the ”default store DRM” assumption discrepancy over on the DRM-free lists: https://www.pcgamingwiki.com/wiki/List_of_DRM-free_games Basically, there’s not a lot PCGW can do in this regard than what we already do. P.S.: That Reddit thread is inaccurate and only concerns games that uses the Steamworks API but does not use Steam DRM to protect the game. Such games don’t have a dependency on the Steamworks API client — they only have a dependency on knowing the Steam App ID which the embedded Steamworks API should engage in. These are supported and tracked on PCGW as ”DRM-free*” (star/wildcard) due to the manual methods involved. For games actually protected by Steam DRM, the method will have no effect at all.
    1 point
  22. miller11568
    Will Tom Clancy's Splinter Cell: Chaos Theory be available on GOG.com? Only the first game in the series is available on GOG.com.
    1 point
  23. saber-nyan
    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
    1 point
  24. c4nvas
    Thank you so much for your support.
    1 point
  25. Methanhydrat

    FEAR 2 Mouse Fix

    gottwald reacted to Methanhydrat for a file

    Version 0.3

    16,493 downloads

    What is this? This fix makes FEAR2 use raw mouse input and removes the game's deadzone and sensitivity problems. It is easy to install and use and does not require any external configuration. Overview Description While the mouse controls are pretty responsive, FEAR2 suffers from a deadzone for small movements, as well as an unusual high sensitivity, even on the lowest settings. This fix removes these problems by acquiring raw mouse input and injecting it directly into the game's input function. Features Raw mouse input No additional smoothing or positive/negative mouse acceleration Configuration via the ingame settings as usual Simple installation and usage without any external configuration Instructions Supported Versions This fix relies on the latest, fully patched executables of the supported versions. Older versions or ones that otherwise have been tempered with might not work. Steam/Retail GOG Install The fix does not make any permanent changes to the game or the system and can easily be removed (see below). Extract the file X3DAudio1_5.dll to your main game folder. For example: "C:\Program Files (x86)\Steam\steamapps\common\FEAR2\" Start the game like you would normally, for example directly through Steam or Origin Uninstall Remove or rename the X3DAudio1_5.dll from the folder of the game. How To Use After the installation the fix does not require any additional treatment. Just launch and configure the game as usual. Additional Information What You Should Know This fix is essentially a hack and relies on the layout of the specific executable. There may be crashes or unexpected issues. Feel free to provide feedback so that the problems can get fixed. Since the fix consists of an executable DLL-File, I could have put any harmful shenanigans in there. You just have to trust me that the file is clean. If you don't -- and why should you -- feel free to use a meta online virus scanner like VirusTotal to verify the file. Be aware however, that because the fix uses "hacking techniques" such as injection and hooking, it could trigger anti-virus software without being harmful. Known Issues The mouse controls of the mech are currently unaffected by the fix and might use a higher sensitivity than the rest of the game. This should not be a big issue, since those sections are quite short and comparatively easy. Contact And Support If you like this mod and want to support the development or show your appreciation, you can find more information on my website. There you can also find out more about other fixes that I have done and means to contact me if you have a question, want to provide feedback, bug reports or suggestions.
    1 point
  26. Mastan

    Creative Alchemy

    Orzełek reacted to Mastan for a file

    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.
    1 point
×
×
  • Create New...