Jump to content

Welcome to the upgraded PCGamingWiki forums and files page. The current Wiki and Forum bridge is not functioning at the moment, therefore your Forum account currently has no password set. Please reset your Forum password via email check to generate a new password. If you have any issues please message Andytizer on Discord.

Aemony

Moderator
  • Content Count

    30
  • Joined

  • Last visited

  • Days Won

    7

Aemony last won the day on May 18

Aemony had the most liked content!

About Aemony

  • Rank
    Supporter

Profile Information

  • Gender
    Undisclosed

Recent Profile Visitors

291 profile views
  1. Aemony

    Overhaul of the editing guide?

    If so, the icon for the "always on" locked state should probably be changed to blue, to be more neutral. In the eye of the beholder, and all that. Having it "green" suggests that whatever it is that's locked "always on" is positive, which typically isn't the case, such as with these: - Mouse acceleration/smoothing being locked to always on. - Anti-aliasing being locked to always on. - Subtitles/Closed captions being locked to always on. etc. Hmm... "features that can't be configured at all would be set to false as usual" vs."while the proposed "always on" state would be used for any features that are active but cannot be configured." This is correct, and was what I was going for. There's not a lot of games with native multi-monitor support, but they exist and typically allows the use of the secondary monitors in some special way. For example some of the Battlefield games allows the use of a second monitor to show the minimap of the game, and some racing games have allows for native extended view across multiple monitors without involving AMD/Nvidia specific features. The current multi-monitor parameter could almost entirely be worked into the existing ultra-widescreen parameter with the minor difference (if one exists) noted in the Notes field. In my opinion, the multi-monitor parameter should be an highly obscured parameter, hidden by default, that properly categorizes games that allows the use of one or more secondary monitors for unique features independent of GPU features. Not be used as an "additional-ultra-widescreen" parameter.
  2. Aemony

    Overhaul of the editing guide?

    The fact that the methods does the heavy lifting and sets up a virtual display is the reason why its current use is wasted. The parameter is basically relegated right now to a “wider-than-ultra-widescreen” field, a ”hyper-widescreen”. I believe we looked it up a few weeks ago and found that in most instances that the parameter mirrors the ultra-widescreen parameter, since it’s effectively just a subparameter of that. Meanwhile we’re losing out on tracking actual games with native multi-monitor support, since those are basically combined with every other title that can “spoof support” through Eyefinity or Surround. I love the idea with a lock though, although it introduces the question of what warrants a green or red lock.
  3. Aemony

    Overhaul of the editing guide?

    Overhauling the editing guide sounds too encompassing 🙂 What I think is needed is that we simply go into more detail about the various parameters that allows true/limited/hackable/false values, with the focus being on Video and Input sections primarily, with the Audio section secondarily. A few example discussion points: 4K parameter seems heavily tied to 16:9 at the moment. Should preferably not be tied to any particular aspect ratio and more in general deal with whether a game can run at the 4K resolution of whatever aspect ratio the game is designed for (3840x2160 for 16:9-designed games, 3840x2400 for 16:10-designed games, 3840x2880 for 4:3-designed games). Repurpose multi-monitor parameter somehow, since right now it tends to mean "wider aspect ratio than ultra-widescreen". The "main element" of multi-monitor gaming today is AMD Eyefinity and Nvidia Surround, which isn't really relevant to the game itself, as all of that logic is separate from the game. Possibly repurpose to real multi-monitor support? As in games that allows the use of a secondary monitor for minimaps, view etc? Real native multi-monitor support, that is, without involving AMD Eyefinity or Nvidia Surround? Generally make it clearer whether a parameter means that a game have an option for toggling something vs. supports something. Right now the difference isn't always clear, which can cause new editors to interpret some parameters incorrect (e.g. should "mouse acceleration" be set to true or false if mouse acceleration is used, but no option is available to adjust it?) New parameter(s) in Audio settings detailing spatial audio support and possible tech required to enable it. Either replacing the existing EAX support field, or supplementing it somehow. The above is just a few examples that can be discussed. Past that, we should add abbreviations (hover explanations) to all of the parameters in the tables with a short and concise description of what the parameter tracks to make it easier editing without having to visit the Editing Guide. Some parameters already have this, and it simply needs to be extended to the rest after the discussions about what the parameters should actually mean have finalized.
  4. Aemony

    What's up with all the broken images ?

    1600 images are corrupt, or experience other issues (e.g. being too large for the wiki to handle) based on this list: https://pastebin.com/8yQ2xDSj There's also some 300 images entirely missing: https://files.aemony.se/pcgw/images_missing.txt Note that this list isn't updated, so a few of the images have already been solved.
  5. Version 1.0.0

    94 downloads

    The retail copy of Borderlands (2009) uses SecuROM DFA to perform an automatic online-based release date check to prevent pre-release access to the game. The online servers this service relies upon, however, is non-working as of 2019, and this manual tool is required instead. Instructions: These instructions must be performed before the installation of the game is started from the retail disc. 1. Download and run Borderland-ManualReleaseDateCheck.exe from this page. 2. The tool should automatically start up at the "Generate Request File" step and prompt you to save a "ActivationRequest.dfa" file. 3. Click on "Select..." and pick an appropriate location. 4. Click on "Next". The tool should save the activation request file on the desired location and move unto the next step called "Activate License File". Leave this window open for now. 5. Now open SecuROM's official DFA Manual Activation page in a web browser. 6. Click on "Browse..." on the website and select the "ActivationRequest.dfa" file you saved using the tool. 7. Leave the "Serial Number" field empty if your retail copy of Borderlands (2009) didn't come with a serial number (only GOTY-versions did, I believe, and only for the DLCs). 8. Type in the security code, and click on "Submit Query". 9. You should be taken on a new web page that says "Your 'ActivationResponse.lic'-file has been created sucessfully" and give you a link do download said license file. Click on the link to download it. 10. Now go back to the SecuROM tool you left at the "Activate License File" step. 11. Click on "Open..." and select the "ActivationResponse.lic" file that was downloaded from the SecuROM webpage. 12. Click on "Activate". You should get a message about the activation process being successful. Click on "Next" to close down the tool. 13. Finally, proceed with the installation of the retail disc copy of Borderlands from the disc. Sources: * https://support.securom.com/borderlandsdfa/ (non-working upload form, use the generic DFA Manual Activation page linked above instead) * Official download link of the manual release date check tool: http://download.securom.com/support/2k/BorderlandsManualReleaseDateCheck.zip (obtained from https://web.archive.org/web/20140714091342/https://support.securom.com/pop_borderlands.html)
  6. Version 1.4.1

    6 downloads

    This is the final and last update that was released to the retail version of Borderlands (2009) before the transition over to Steamworks for multiplayer and as such the update is only applicable to retail copies and installs. Note that this update includes a SecuROM v7.42.0004 protected executable for the game.
  7. Writing in support of the proposal, although I also will have to re-read the replies as I basically just skimmed them now.
  8. Aemony

    Proposal: Genres and Modes

    "First person shooter", "Third person shooter", "3D", "2D" are primarily all just different forms of perspective from which the gameplay is available. "Genres" typically deal with content matter, as in "Adventure", "Action", "Racing", etc. The way Valve currently handles this subject is to basically don't even bother. They define all of the above examples as "tags", and then allows developers to set which tag they prefer to have the game listed primarily as being under, and whatnot. So the question is rather to what extent PCGW should start to categorizing games, and whether stuff like content matter of games is the purpose or just technical details such as 2D/3D and first or third person view.
  9. Played around a bit in Firefox's inspector tool. If we solely plan to keep this limited to "alternative sources" of obtaining access to games right now, then I can whip up an extension to the Availability template, and add notes to boot. Example mockup: Base source code, so I don't forget it 😅 <tr class="template-infotable-head"> <th scope="col" style="width: 230px;">Alternative sources</th> <th scope="col" style="width: 50px;"> </th> <th style="width: 540px;" scope="col" colspan="3">Notes</th> </tr><tr class="template-infotable-body"> <th scope="row"><abbr title="asdsad">Xbox Play Anywhere</abbr></th> <td><div title="Native support" class="svg-icon svg-25 tickcross-true"></div> </td> <td colspan="3">Does not apply to the 2016 re-release.</td> </tr><tr class="template-infotable-body"> <th scope="row"><abbr title="asdsad">Xbox Game Pass</abbr></th><td><div title="Native support" class="svg-icon svg-25 tickcross-true"></div> </td> <td colspan="3">Comes pre-packaged with cosmetics DLCs.</td> </tr><tr class="template-infotable-body"> <th scope="row"><abbr title="asdsad">Origin Access Basic</abbr></th> <td><div title="Native support" class="svg-icon svg-25 tickcross-false"></div> </td> <td colspan="3">Limited to 10-hour trial.</td> </tr><tr class="template-infotable-body"> <th scope="row"><abbr title="asdsad">Origin Access Premier</abbr></th> <td><div title="Native support" class="svg-icon svg-25 tickcross-true"></div> </td> <td colspan="3">Deluxe Edition</td> </tr>
  10. The existence of this template and the attempt to now track Game Pass titles (a subscription service that adds and removes games in its catalog every now and then) have made me question whether we shouldn't opt for a more generic template instead that's designed to be extended for whatever supplementary feature might come up. Something like this basically: {{Store features | microsoft store game pass = true | microsoft store play anywhere = true | origin access = | origin access premier = true }} which would then create a list like this: {{ii}} Included in Xbox Game Pass subscription service. {{ii}} Xbox Play Anywhere title; purchase it on either Microsoft Store on Windows 10 or Xbox, and receive copies for both platforms. {{ii}} Included in Origin Access Premier subscription service. If this was then used below the availability row, you'd have an easy placement where the list could grow naturally as features was determined as necessary to add to the template. Edit: The obvious negative downside of this is that it wouldn't allow us to include it in the Availability table unless we redesigned that entirely and added new parameters to it.
  11. Because we don't currently have a good way to handle these sorts of supplementary features, I opted to create a new template that allows setting these properties and embeds the results in a {{ii}} bullet point, with the intention of the template being used just below the availability table. The reason why I opted for this and not the Notes section of the availability table was because I believe the field can otherwise become quite lengthy in text if there's other notes that needs to be mentioned there. That said, all that needs to be changed for the template to be compatible and used directly in the Notes field is the removal of the {{ii}} bullet point, and nothing else. Preview: Properties: Property:Microsoft Store Game Pass Property:Microsoft Store Play Anywhere Templates: Template:Microsoft Store features Template:Microsoft Store features/Documentation
  12. Aemony

    Is it allowed to add a DX12 games list to the wiki?

    References should go in the "direct3d notes" field, and not the "direct3d versions" field, of the API template. The "direct3d notes" field is limited to only supported values, as anything else will screw up the backend connections. Only remove listings if you've actually confirmed that they do not support DirectX 12 on your own, or you find a concrete source mentioning that it doesn't. PCGW generally assumes that edits are accurate despite a lack of reference, so to remove ones that are "suspicious" you'll have to find a concrete source confirming the suspicions. Feel free to add {{cn}} in the notes field to flag that a citation is needed, though.
  13. Aemony

    Sound and Windows 10

    I don't think this is really the case any longer, based on my testing with my Hi-Res Audio certified DAC and headset. That DAC have a visual indicator that showcases what sample rate and bit depth, and in shared mode it will _always_ output as the selected format according to what I've selected in the Advanced tab of the output device (24 bit, 96 000 Hz). In exclusive mode through WASAPI it'll output whatever format is configured in the player, regardless of the source itself (tested and verified using Foobar2k and the foo_out_wasapi plugin.
  14. Version 1.27b

    33 downloads

    Mirror of the 1.27b standalone Mac patches released for Warcraft 3: Reign of Chaos and Warcraft 3: The Frozen Throne, as obtained from Blizzard's official FTP server. Click on Download this file to the right to get the list of PCGW mirrors for the patches. Official FTP download links Reign of Chaos only: http://ftp.blizzard.com/pub/war3x/patches/Mac/War3ROC_127b_Castellano.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3ROC_127b_Cesky.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3ROC_127b_Chinese_Simp.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3ROC_127b_Chinese_Trad.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3ROC_127b_Deutsch.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3ROC_127b_English.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3ROC_127b_Francais.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3ROC_127b_Italiano.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3ROC_127b_Japanese.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3ROC_127b_Korean.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3ROC_127b_Polski.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3ROC_127b_Russian.zip With The Frozen Throne expansion: http://ftp.blizzard.com/pub/war3x/patches/Mac/War3TFT_127b_Castellano.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3TFT_127b_Cesky.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3TFT_127b_Chinese_Simp.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3TFT_127b_Chinese_Trad.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3TFT_127b_Deutsch.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3TFT_127b_English.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3TFT_127b_Francais.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3TFT_127b_Italiano.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3TFT_127b_Japanese.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3TFT_127b_Korean.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3TFT_127b_Polski.zip http://ftp.blizzard.com/pub/war3x/patches/Mac/War3TFT_127b_Russian.zip For Windows patches, see the file below:
  15. Version 1.0.0

    130 downloads

    libEGL.dll retrieved from Next Up Hero, from NextUpHero\GameGuide\Streamer\bin\32bit\libEGL.dll, on the 2018-12-15. Extract to the same folder as Chrono Trigger.exe, so to Steam\steamapps\common\Chrono Trigger.
×