Jump to content

ThatOneReaper

Member
  • Content Count

    303
  • Joined

  • Last visited

  • Days Won

    25

Reputation Activity

  1. Like
    ThatOneReaper got a reaction from Blackbird in Editing guide   
    "Hackable" means that a feature or option can be enabled through either unofficial means (patches, mods, etc.) or built-in engine commands/options that are not explicitly made available through the in-game options menus (command line arguments, modifying official config files, etc.)
     
    In your particular case, if the feature can be enabled through the in-game options menu (abit in an awkward and roundabout fashion), it would still be considered native support.
  2. Like
    ThatOneReaper got a reaction from Blackbird in Editing guide   
    I should backtrack a bit.
     
    If you want to add in a note about lost OS/hardware support just from an archival prospective, go ahead. I'm just highlighting that it wouldn't serve any purpose beyond that.
     
    As for mentioning unofficial OS/hardware support lower than what the minimum specs are, my reasoning is that it would complicate troubleshooting issues if we do. When a developer states minimum system requirements, they are saying "This is the general configuration we found that allows you to play the game at the bare minimum with no issues. We cannot guarantee stability with older configurations".
     
    Of course, you can try to run the game on older configurations. It might even work just fine, abit with heavy compromise in graphics. But any issues that do arise under such configurations would be difficult to nail down. Is it the person's configuration that's causing the issue or the game itself?
     
    The only reasonable fix I could give in such a situation is "Upgrade your hardware/software".
     
    I am advocating "dev says so, you must comply", but for good reason. Our fixes assume that at the very least the system the person is using is equal to or newer than the minimum specs. I don't want someone to look at our statements on such support, run the game on the "supported" OS/hardware, and come back to us reporting bizarre issues that may or may not be due to the configuration.
     
    Unofficial OS/hardware support equal to or newer than the minimum specs (but older than the recommended specs) is a different matter. If a particular OS/hardware works, but is not officially supported (and not specifically mentioned as an unsupported configuration), it can be listed. It would need some notice along the lines of "X OS/hardware works with the game, but is not officially supported. Stability is not guaranteed".
  3. Like
    ThatOneReaper got a reaction from Blackbird in Editing guide   
    Marioysikax has the right idea. Games that use digital distribution need to have the newest system requirements listed as games can drop support for outdated OSes and hardware (see Space Engineers).
     
    I don't think we should put a note regarding lost OS/hardware support because it wouldn't really matter for the latest build. Unless there is a way to use older builds of a game legally, there is no point in adding it to the page beyond historical purposes.
     
    Mentioning unofficial hardware/OS support also doesn't make sense. Even if a game still does work, there might have been a good reason why that hardware/software configuration was not listed (assuming hardware/OS is below minimum specs). Bringing it up may cause users to run the game on unsupported specs and find issues that are not present in officially supported specs.
  4. Like
    ThatOneReaper got a reaction from Mirh in Editing guide   
    Marioysikax has the right idea. Games that use digital distribution need to have the newest system requirements listed as games can drop support for outdated OSes and hardware (see Space Engineers).
     
    I don't think we should put a note regarding lost OS/hardware support because it wouldn't really matter for the latest build. Unless there is a way to use older builds of a game legally, there is no point in adding it to the page beyond historical purposes.
     
    Mentioning unofficial hardware/OS support also doesn't make sense. Even if a game still does work, there might have been a good reason why that hardware/software configuration was not listed (assuming hardware/OS is below minimum specs). Bringing it up may cause users to run the game on unsupported specs and find issues that are not present in officially supported specs.
  5. Like
    ThatOneReaper got a reaction from Hawaii Beach in Are discrete soundcards worth buying for modern games?   
    Unless you're an audiophile or someone who does a bunch of audio-related projects, there's no reason to buy a sound card for modern games. As you have already mentioned, the sound cards integrated in most modern motherboards are high enough quality to render the discrete options obsolete.
     
    To get the best audio quality nowadays, just buy a pair of decent headphones. They do give a distinct advantage over most players in multiplayer games.
  6. Like
    ThatOneReaper got a reaction from Marioysikax in Are discrete soundcards worth buying for modern games?   
    Unless you're an audiophile or someone who does a bunch of audio-related projects, there's no reason to buy a sound card for modern games. As you have already mentioned, the sound cards integrated in most modern motherboards are high enough quality to render the discrete options obsolete.
     
    To get the best audio quality nowadays, just buy a pair of decent headphones. They do give a distinct advantage over most players in multiplayer games.
  7. Like
    ThatOneReaper got a reaction from Blackbird in Are discrete soundcards worth buying for modern games?   
    Unless you're an audiophile or someone who does a bunch of audio-related projects, there's no reason to buy a sound card for modern games. As you have already mentioned, the sound cards integrated in most modern motherboards are high enough quality to render the discrete options obsolete.
     
    To get the best audio quality nowadays, just buy a pair of decent headphones. They do give a distinct advantage over most players in multiplayer games.
  8. Like
    ThatOneReaper got a reaction from Mirh in AA, AF, Vsync and forcing through GPU   
    The only way I would see that working is if the Video Settings table had a dedicated field to enable showing generic instructions ("show_generic"). If the field is set to "true", then add a blurb to the relevant video settings along the lines of:
     
    "Generic instructions for forcing <VIDEO SETTING> can be found in <LINK TO GLOSSARY SECTION>"
     
    Even then, I don't like the idea of having a dedicated element in game articles for general fixes like that. I want to remove general solutions, not highlight them.
     
    I already mentioned the best approach to this: Add one set of generic instructions to the glossary pages (Anisotropic filtering, Anti-aliasing, Vertical sync) and remove said instructions from specific game pages. All tables are already linked to these glossary pages. If someone absolutely wants to force a specific video setting for a game, they can look there.
  9. Like
    ThatOneReaper got a reaction from Marioysikax in AA, AF, Vsync and forcing through GPU   
    I'm going to weigh in on this issue as I've been thinking of adding something to the Editing guide to address this.
     
    Video settings that can be forced through a video card's drivers can be considered general fixes that are application-agnostic. It's the type of solution that can be applied to practically every 3D game the wiki covers.
     
    Based on that knowledge, I think we should not consider forcible video settings to be "hackable" in the context of any specific game. An article should be dedicated to game-exclusive fixes only. Allowing very general solutions tends to make an option field always "hackable", which I personally think does not add anything of value to the page.
     
    The only exception where adding a general fix would make sense is if in-game support for the setting is fundamentally broken with no other possible workaround (ex. game has broken V-sync support). Otherwise, I would add general steps to the relevant video setting glossary pages on how to force each setting.
  10. Like
    ThatOneReaper got a reaction from Mars icecream in Spec Ops: The Line - lot of goodies in 'SREngine.ini'   
    Done. If you want to share huge chunks of text temporarily next time, use Pastebin.
     
    As for adding the tweaks to the article, I would recommend either using instructions to modify the required lines (assuming it's just a few) or upload to the Files section the modified config file.
     
    In any case, I'm looking forward to the full list of tweaks that come out of this.
  11. Like
    ThatOneReaper got a reaction from Marioysikax in What are the wiki screenshots used for? What uses do they have?   
    Screenshots serve a couple of purposes:
    They complement the tables in the articles by giving a visual reference to most of the options covered by the wiki. Like you said, articles tend to be very dry without them. They give readers an idea where to find all the options in-game without having to dive into the actual menus themselves. They "flatten out" the menu hierarchy.Ex. The subtitles toggle might be under "General", rather than "Audio". They also show all the possible settings a user can modify (including features not covered by the wiki).
  12. Like
    ThatOneReaper got a reaction from Expack3 in Editing guide   
    The guide already talks about how to handle this sort of thing:
     
    So in your case the file caption format will be "In-game keyboard settings (#/3)"
     
    On a related note, for screenshots of remapping menus, just one picture for each input device is enough. The full list of remappable commands is not relevant for the wiki.
  13. Like
    ThatOneReaper got a reaction from Blackbird in Editing guide   
    The guide already talks about how to handle this sort of thing:
     
    So in your case the file caption format will be "In-game keyboard settings (#/3)"
     
    On a related note, for screenshots of remapping menus, just one picture for each input device is enough. The full list of remappable commands is not relevant for the wiki.
  14. Like
    ThatOneReaper got a reaction from Marioysikax in Editing guide   
    The guide already talks about how to handle this sort of thing:
     
    So in your case the file caption format will be "In-game keyboard settings (#/3)"
     
    On a related note, for screenshots of remapping menus, just one picture for each input device is enough. The full list of remappable commands is not relevant for the wiki.
  15. Like
    ThatOneReaper got a reaction from Expack3 in Editing guide   
    Thank you very much for pointing out these inconsistencies. I've fixed most of them. When I can find the time, I'll fix the more complicated ones.
     
    Note that the Creative Senz3D problem is beyond my skillset right now. One of the admins will need to fix that.
     
    The Files article guide is very much in need of updating. I'll make that my next project.
     
     
    The sole reason the Editing guide and the Sample guide exist is so that you don't "decide what to do on your own for the most part anyway". It is the standard by which all edits on the wiki are held against. Everyone from new contributors to admins must follow both documents. There should be absolutely no reason why we should be telling people to disregard the guide.
     
    If there is an issue regarding clarity in a particular section, just post it here. The guide is fairly malleable if given good reason to do so.
     
    As for the expansion naming, the reasoning behind it is that retail expansions are complete, separate products that just so happen to require the base game to function. Digital DLC are more along the lines of plugins for games (the best description I can give on this). The naming is to distinguish between both types of expansions.
  16. Like
    ThatOneReaper reacted to Faalagorn in Editing guide   
    When I started following the editing guide creating a new page and saw some inconsistencies between the sample article and editing guide, I saw some differences between the two and made a thread about it in sample article's page.
     
    However, I started seeing more differences and inaccuracies between the two, so I thought a forum may be a better place to discuss it.
     
    I'm going to list what caught my eye, but I'll also list the things that should be fixed in both of those places, since both of them are for view only:
    "wikipedia" and "winehq" places are swapped in infobox; it's in different order in sample article's cheat sheet than it is in editing guide "steam appid side" parameter is missing in the sample article's cheat sheet square enix cloud syncying option is missing in save game cloud syncing table in sample article's cheat sheet API and middleware tables are missing in the sample article's cheat sheet, seems it was already mentioned before, but not answered AFAIK. They are in the base article body though and editing guide does not say anything about the tables being optional Sample article's cheat sheet for series pages uses {{SUBST:PAGENAME}} while the editing guide do not use it Sample page's "genre information" links to the now-dead Style Policy page links in "General information" in sample article does not match what the editing guide recommends (i.e. GOG links should be over Steam links). Editing guide does not mention nothing about the point: "If still relevant, state where bugs can be reported." A small discrepancy in availability type, in example GOG.com is written as Gog.com (no uppercase) The "Which is the 'best' version of the game to get?" under availability point is not present or explained in editing guide I'm a bit puzzled about the patches section in essential improvements. Editing guide is really vague about it, only saying to place "Patches (both official and unofficial)", while sample article says [only?] "Include If There is a benefit in using an older patch". For example Brigade E5 is patched to latest 1.13 version on Steam, but my retail version is not. Following what the sample article says, I should not upload a link to patch 1.13? Or should I anyway? I'm confused x.x Intro skip methods section is missing in sample article entirely The order of utilities and modifications is swapped between sample article and editing guide (patches-utilities-mods in sample article vs patches-intro skip-mods-utilities in editing guide) Configuration file(s) location table is missing in sample article body (not cheat sheet), and while we're at it, cheat sheet (and editing guide) says "Save game data location" while body simply "Save game location" Some of the newly added table options are missing the appropriate "See <something>" section and matching headers. While we're at it, should we always use "See <something>" instead of just fill the notes, or only for really long explanations? Nor sample article or editing guide explains it Sample article does not use the new way of treating fan translations for Spanish example Creative Senz3D table features "class="generic-table-notes-cell" colspan="2"|" "Other information" guidelines differ in sample article vs editing guide P.S. There are other minor differences between the two, especially when it comes to the formatting of missing data in cheat sheet - for example sample page's cheat sheet fills steam id with "000000" while they are blank in editing guide. Those are less of an issue, as they will get replaced anyway and will not reflect the final page's look in any way.
  17. Like
    ThatOneReaper got a reaction from Expack3 in Alternatives to FRAPS?   
    The Editing guide has a small list of recommended screen capture utilities. I personally use Bandicam due to its simplicity.
     
    ShareX is also not a bad choice.
  18. Like
    ThatOneReaper got a reaction from Nicereddy in Uploading fullscreen images instead of cropping them   
    For screenshots, they can only be cropped in the following cases:
    The options menu is displayed as an in-game window, rather than a separate screen.  Especially need to be done if said window is small compared to the rest of the screen. There is personal profile information that cannot be changed to an appropriate throwaway profile. All the settings for a menu do not fit in a single screenshot and must be stitched together. The screenshot is of an external menu/application. In these cases, it helps cut down on the clutter both on-screen and in the game article. Otherwise, provide a fullscreen screenshot.
     
    It should also be noted that when cropping, do not leave any unnecessary space outside of the in-game window.
     
    Good examples of properly cropped images can be found on any Company of Heroes page, Half-Life 2, and Splinter Cell: Blacklist.
  19. Like
    ThatOneReaper reacted to Marioysikax in Uploading fullscreen images instead of cropping them   
    Few problems. 
     
    First: games with settings menu seperated into many parts. 
    Best example I can think out of my head is Osu!. Graphics settings would've taken three screenshots alone and would've included my personal game information and other settings in other settings screenshots. Would've been total mess without cropping and combining. Screenshots in Metal Gear Rising: Revengeance were replaced (png with png, and replaced, not updated original file like it should be done, my files are still there and aren't even tagged for deletion) and now audio and input settings basically containg 99% of the same settings and can't be viewed directly from game article. 
     
    Second: games with tiny setting screens. 
    There can be games which have 90% of space which doesn't containg anything useful, but is there to increase image size SIGNIFICANTLY. This means you can't see anything from pages thumbnail and opening up the image will take ages. 
    One good example I can think of this is Mitsurugi Kamui Hikae. 
     
    You can compare yourself, cropped image found in article (37 KB) vs uncropped image (2.52 MB). 
    Now that whole main menu would repeat with all the images and glutter whole damn page! 
     
    So basically, I'm againts posting uncropped settings images if it's simply stupid, especially if only counterargument is "Cropped images look really ugly". Cropped images are usually directly viewable without opening in articles, they are much smaller to open if necessary and they focus on only the thing that's important. Especially when many games have super stylized options menus these days. And we have only talked about cropping and combining, there's no mention of altering content of the images, so even if images are cropped on pages, they should contain everything that settings menu have to offer.
     
    I will say though that some form of cropping does definitely look ugly, thus I have tried to maintain astetic beauty and possibly some visible thing to show that everything is shown in the screenshot when cropping (e.g. including settings menu borders, showing right side scroll bar, etc.). One good example is Transistor, Here's soebs original screenshot vs my screenshot when I updated all the screens in the article. They are pretty visible on article, all I did was remove complete black space around it and kept vertical resolution same so they look consistant when viewing article. Soebs screenshots did do their job of course, but must admit they looked really ugly for such beautiful game. 
     
    Of course when it comes to configuration tools, it's usually better to have whole thing, because it's in theory already cropped without anything extra and having window border does tell everything is there. And for something like Hyperdimension Neptunia Re;Birth 2: Sisters Generation where cropping would save vertical space only and not by much, of course it's not smart to crop it and whole screenshots are better. 
  20. Like
    ThatOneReaper got a reaction from Blackbird in List of shady game developers?   
    We don't have such a list.
     
    The wiki is meant as a neutral database for PC games. Having a list that shames specific developers would go against our base ideology.
     
    There's also the issue of what can be considered "shady". Not every potential case is clear cut.
  21. Like
    ThatOneReaper got a reaction from Suicide machine in List of shady game developers?   
    We don't have such a list.
     
    The wiki is meant as a neutral database for PC games. Having a list that shames specific developers would go against our base ideology.
     
    There's also the issue of what can be considered "shady". Not every potential case is clear cut.
  22. Like
    ThatOneReaper got a reaction from Mirh in List of shady game developers?   
    We don't have such a list.
     
    The wiki is meant as a neutral database for PC games. Having a list that shames specific developers would go against our base ideology.
     
    There's also the issue of what can be considered "shady". Not every potential case is clear cut.
  23. Like
    ThatOneReaper got a reaction from Nicereddy in List of shady game developers?   
    We don't have such a list.
     
    The wiki is meant as a neutral database for PC games. Having a list that shames specific developers would go against our base ideology.
     
    There's also the issue of what can be considered "shady". Not every potential case is clear cut.
  24. Like
    ThatOneReaper got a reaction from Nicereddy in Editing guide   
    After nearly a full year working on it, the PCGamingWiki Editing guide is now officially done!
     
    It is currently in the process of being ported over to the redesigned site. No further changes to the guide will be made until after the relaunch (excluding spelling/grammar edits).
     
    I want to thank everyone that helped contribute to the project. Your input was of great help for me and all future editors that will use the guide.
  25. Like
    ThatOneReaper got a reaction from Expack3 in Editing guide   
    Editing: Regardless of if a browser has good crash recovery or not, it wouldn't serve any purpose to mention it. Some people will end up relying upon that functionality too heavily, rather than backup changes properly.
     
    References: I've added an exception for posts made by development team members or representatives if that helps.
     
    Fixboxes:
    It's always a good idea to mention backing up critical game files before they get modified. Even the best of computer users forget from time to time. I only mention the warning in fixes if the file is a DLL, EXE, or multi-line CFG/INI modification. Yes, we need to add launching the game as a step. A fix covers everything right up to the start of the game. If you want to create a page with a list of recommended programs to use, feel free. I wouldn't have the time to write such a thing up. I keep going to a specific file path and opening a file separate for a reason. The first step ("go to <path>") establishes the context of all future steps in the fix in a clean manner. I might need to do more than just modify a file afterwards. Merging the two will make the steps look "sloppy".​ What the wiki does not cover: Putting in pornographic games on the list is due to good business sense and decency, not "good old American dissonance towards nudity and sex". No console manufacturer or major retail store carries AO-rated games (most porn games fall under this rating) because they are very bad for their image. The same logic goes here.
     
    Regardless, porn games are seedy by nature and would cheapen the wiki if we started to allow them. They ultimately have no place here.
     
    Finally, I've already stated that the definitions are subjective in nature. Questionable games can be run by the mods/admins if there is confusion.
     
    Availability: I'm not dealing with that argument again. Like you said, the editor will need to make that determination.
     
    Video settings:
    The Widescreen and Windowed notes have been added. 4K: That is such a bizarre edge case, even if it is hypothetical. I have yet to encounter a 4K-ready game that does not support widescreen. It stays as is. Input settings:
    Trying to come up with methods to disable acceleration for every game is nigh impossible. Not every game have an INI file that can be modified. I've linked the toolkit in the table. If controller support is false, we leave it as is. Adding the notice to every page would look messy. Anyways, the Glossary page already handles that. The XInput preference is because most major controllers and modern games are designed with XInput in mind. I don't want editors to try testing for full controller support with non-standard controllers. Audio settings: I've added the note.
     
    Template documentation: That's not my responsibility. You're better off asking Soeb or Garrett.
     
    Anyways, I believe the guide is finished and ready for a full release. I have to start porting it over to the redesigned site at some point this week.
×
×
  • Create New...