Jump to content

PCGamingWiki will soon migrate to a Single Sign On (SSO) system to bridge Wiki and Forum accounts, please read our FAQ.


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Garrett

  1. This game starts after a couple of fixes:

    • Download ogg-winmm.
    • Extract everything to the installation folder.
    • Download dgVoodoo 2.
    • Extract the contents of the MS folder into the installation folder.
    • The game should now start.
    • If you want to disable the watermark you can change this in dgVoodooCpl.exe.
    EDIT: As noted on Discord, CD music seems to be broken even after these fixes (no music, music slider can't be adjusted in-game) despite following the ogg-winmm steps for ripping the music in OGG format.

  2. You may be able to get the space campaign to start by doing the following:

    1. Download the latest version of dgVoodoo 2.
    2. Extract the contents of the MS folder into the game's installation folder.
    3. Run the game normally.

    I have no idea whether this works reliably at this point. Each language was sold separately (so there may be some differences there) and I also had some behavior differences between the versions of Windows I tested it on.


    Based on my testing this does not fix the temporary color corruption on the main menu and it may also cause videos to show no picture (you can play the videos on the CD outside the game if you want to see what you've missed).


    If this works on your end do let me know what language your game CD is and what version of Windows you're playing on.

  3. You can use DevCon to disable devices (further details here). This is the equivalent of disabling a device through the Device Manager. You could make a set of batch files that run DevCon with the commands needed to get just the controller you need.


    x360ce only works for games that use the XInput API since it overrides the DLL. You might need to use a different DLL name (the x360ce documentation lists some known DLL names to try). If a game uses other methods (such as DirectInput or raw input) you'll need to use a different program.

  4. 5000 pages is MediaWiki's limit for the Special:Export category feature (details). This limit does not apply to page names entered manually. If you don't want to use the API a quick way to grab a full list is to click and drag over the names on Category:Games and copy-paste that into the Special:Export box, repeating for each additional page of results in the category, then start the export once you have the full list.


    Do you have a particular use in mind? If your interest is in the settings information you can query this through Special:Ask (or the API) using one or more properties to find and display the information you're wanting to see (Semantic MediaWiki has extensive documentation for this). You could also use this to make a reduced list of relevant pages for Special:Export etc.


    If you have any further questions feel free to ask. You can also usually find some of us in the Discord server.


    (For reference, PCGamingWiki content is available under the terms of the Creative Commons Attribution Non-Commercial Share Alike license.)

  5. The Semantic Result Formats extension should be installed. This would enable use of the DataTables display format (example). The search box applies a full or partial match for the keyword(s) to all result data for that query, even data that is currently off the page--note how the "Show # entries" and "Previous/Next" controls directly update the display instead of loading a different page.


    As an example with this wiki's data, you could put the operating system name in the search box (on its own or together with other keywords) to show only games for that system, etc.


    (For reference, the Cargo extension also supports the DataTables display format, so this sort of searching would still be available if the wiki switched to that extension).

  6. Most games can have AA/AF/Vsync forced successfully, so it is more useful to note the cases where this capability does not work as expected. Last month I updated Template:Video settings to show default notes when AA/AF/Vsync is set to false without a note specified, so cases where support has been set to false without further explanation suggest a likely solution.


    Working methods specific to a game (INI edit, mod, Nvidia flag, etc.) should be set to hackable as always.

  7. I have made an initial version of the form interface for editing game pages. See Development:Forms for some sample pages to experiment with.


    This is an initial version to demonstrate the viability of this approach. Let me know of any errors in the settings, e.g. dropdowns missing values that should be supported (or vice versa) or multi-instance templates not having the correct minimum/maximum use limit. The form layout is done with standard wiki tables, so any spacing issues etc. can be adjusted as needed.


    The biggest change is that form editing works around all form content being contained within templates. Any text not used in a template parameter gets relocated to the bottom of the page (shown in the "debugging area" when editing with the form). The updated templates have notes sections etc. so information can be added in the usual places while now actually residing within the associated templates.


    Another change is that pages edited with the form have empty template parameters and template whitespace removed (there is no option to disable this), so manual editing is not as easy to read as it was before.


    This form introduces some new templates such as Patchbox. These templates provide a layout specific to that type of information and supply additional semantic data for the wiki. In the case of Patchbox, the Issues fixed/unresolved sections would link to the Patches section when it exists (this is implemented already but isn't visible in the examples due to using the development namespace).


    Template features that rely on property checks (GOG.com and Steam Cloud rows, WSGF infobox icon, etc.) don't work in this namespace after a page has been saved.


    Unfortunately, due to the way forms work each template can only be used in one place on the form (but multiple times in that place). This form uses redirects for several templates to get around this limitation (listed in the "Redirected templates" section).


    This form currently has an issue where some page sections are shown when empty. This would be resolved with some template adjustments (most of which are already present). EDIT: form editing from section links on the page isn't present yet.


    Anyway, let me know what you think.


    EDIT: I have moved the sample pages to my user space (I didn't realise the Development: namespace had restricted editing). Feel free to tinker with the pages.

  8. I have added Steam Controller support for prompts. This is currently represented by the pad symbol because the regular ABXY buttons are the same as an Xbox controller. Feel free to suggest improvements or alternatives to more clearly represent this type of controller.


    I have also added simultaneous input to all the examples (this was initially excluded because I had considered rewording it).

  • Create New...