Jump to content

Aemony

Administrator
  • Content Count

    227
  • Joined

  • Last visited

  • Days Won

    34

File Comments posted by Aemony


  1. Hi!

    Am I correct in assuming this acts as a crack and effectively disables Steam API related features as well as the ownership check of the Steam copy?

    PCGW attempts to distance itself from cracks, so the use of steam_api64.dll as the DLL injection point makes it currently questionable whether we should approve the upload or not.

    If possible, then I highly recommend using some other DLL as the injection point such as D3D12.dll or DXGI.dll.


  2. This CheatEngine FOV table is dated 2017-02-08 and so predates the fourth patch for the game that was released in 2018 and updated the game engine to Unreal Engine 4.18. As such it is incompatible with an updated copy of the game.


  3. 5 hours ago, mrpenguinb said:

    Are there any differences in terms of functionality between the x86 and x64 versions of the driver?

    Do some games require specifically one version of the driver?

    No, it's solely based on the architecture of your operating system. x64 versions of Windows require the 64-bit driver, and vice versa.


  4. 1 hour ago, Mirh said:

    I don't want to be that guy, but I thought we had dismissed this solution already with XInput Plus, due to the bugs and problems it caused here and there?

    No idea -- never heard of Xinput Plus before today.

    I used to use this driver to enable force feedback in old DirectInput based games on my Xbox Controller and don't remember having run into any noticeable issues with it, so feel free to elaborate on what potential issues you mean.

    Looking up XInput Plus, that tool allows rebinding what Xbox Controller buttons the virtual DirectInput controller maps to, which is sorta another use case entirely -- primarily to solve issues between games expecting different controller layouts. Sure, that tool might encompass more, feature-wise, but I see no reason as to why that would prevent the inclusion of this tool. If I only care about a couple of DirectInput games which all expects the same controller button layout then I'd personally prefer this install-it-and-forget-it driver as opposed to messing with a separate tool and whatnot.


  5. Thanks for uploading these! They're one of the most critical tools for players of older games.

    I did a minor change and added "DirectInput" to the title and description though, as these drivers basically add support for force feedback in DirectInput games for XInput-based controllers.

    The original title is most likely a translation issue or unfamiliarity with English.


  6. 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.


  7. A new recompiled version of the script have been uploaded by @Suicide machine to clear the false positives of the file.

    If it where to trigger false positives in the future yet again (which I sorta expect, seeing how it's using AutoHotKey to monitor the system for key presses to enable its functionality), users can follow the instructions in the Modification section of the file description to recompile the executable file themselves, which might clear the false positives.


  8. @Brownd There's no need to password protect the archives if the installers doesn't trigger many AVs on VirusTotal, which these installers don't seem to do. If you want to, you're free to upload them without archiving them or password protect the archive.

×
×
  • Create New...