Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


File Comments posted by Aemony

  1. Hi,


    PCGW is generally against bypassing DRM and such, see the wiki policy.

    I noticed that the developers were still semi-active on the Steam forums for another one of their titles, and this game is still being sold on Steam. Have you tried reaching out to them on admin@dreamssoftgames.com about the issue? I imagine they might be able to fix the issue properly on their end or, possibly, upload a copy without this issue.



  2. @asabarabi, sadly it seems the forum software can't handle the name of the file you uploaded. Can you remove any special characters etc and ensure the file name is only named using regular Latin characters such as A-z, 0-9, and dots/underscores/dashes, etc ? Then re-upload the file again by using "File Actions ->  Upload a new version".


  3. 21 hours ago, linkolead said:

    Windows 10 is recognizing the file as a  virus and not allowing it to run at all.

    "operation did not complete successfully because the file contain a virus or potentially unwanted software"

    Probably a false positive, though you've to decide yourself whether to 'trust' the file or not. PCGW in general does not guarantee  the safety of files, and due to the numbers of false positives occurring in gaming related files -- particularly those created using e.g. Cheat Engine -- we usually don't remove uploaded files either due to "virus detections".

    See the "Virus detected in PCGamingWiki file" section for a bit of context.

  4. 39 minutes ago, cbk@csolutions.no said:

    This is A virus, Trojan. Do not use!

    Reports as Trojan:Win32/Glupteba!ml

    Astroneer FOV - Steam.exe



    The last part of the recognized virus definition “!ml” suggests the definition was created through machine learning. Basically there is an extremely high chance of it being a false positive.

    @Rose is otherwise a well-known and recognized ultrawidescreen modder whose patches occasionally runs into AV’s false positives.

    @cbk@csolutions.no, at the end of the day you yourself have to determine if you put your trust in a stranger online, but for what it’s worth, I personally highly suspect this is a false positive. Of course I can’t say for certain, but then nobody really can unless they created the executable themselves.

  5. 6 hours ago, patrxgt said:

    Launcher has been cut from the official edition of the game purchased in Poland, which was published here by Cenega, so it cannot contain viruses.

    Of course I can publish the password version, but what is this for? It will only make the process of installing the Polish language more difficult.

    It isn't about whether the file is actually malicious or not -- it's intended to protect PCGamingWiki from automatic flagging by third-party internet safety scanners like for example Google's Safe Browsing filter.

    You can read more about it in the files section of the editing guide: https://www.pcgamingwiki.com/wiki/PCGamingWiki:Editing_guide/Files#Password_protection_policy

  6. Hi,

    Can you upload a password protected version of the archive? The launcher packaged in this archive triggers AVs.

    Click on File Actions -> Upload a new version at the bottom of the "About This File" section to upload a new version of the file.


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

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

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

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

  • Create New...