This wiki provides lots of info on patches, fixes and ways to tune the game to work on pc. But as someone who plays kb+m, it's difficult to find ways to tell if a ported game managed to convert controller prompts to kb+m equivalents.
Any chance we could add this information to wiki's for games ported to pc?
I've had the idea that the infoboxes should somewhere contain information about a game's save system, since there are a lot of different ways games handle it:
- Roguelikes (dying completely resets you, but you retain certain benefits)
- Hardcore-modes where dying deletes your savegame, e.g. "Trial of Iron" mode in Pillars of Eternity 2
- Only at the start of each level, e.g. Freespace 2
- Only checkpoint / autosave, e.g. most modern shooters
- Checkpoints that can be manually activated several times, e.g. Resident Evil typewriters or sleeping in Kingdom Come: Deliverance
- Bonfire-system, e.g. Dark Souls (like above, but respawns all enemies)
- Free, manual saving (and whether it also allows in combat + how many available save slots)
- "Free" saving that still resets you to checkpoints, e.g. Tomb Raider: Legend
- Manual saving, but at a cost, e.g. Kingdom Come: Deliverance (consumes alcohol)
- Special savegame shenanigans (e.g. message if you save too often in Metal Gear Solid 1, deleting your savegames if you die too often in Hellblade: Senua's Sacrifice, voluntary savegame deletion in Nier and Nier: Automata...)
- Whether it allows to select individual chapters to replay, e.g. Syndicate (2012) and Condemned: Criminal Origins
What do you think about this feature? For me personally, not being able to save freely is almost disqualifying for a game, so I always want to know such information. And it often changes even inside a franchise (e.g. FEAR 1 has manual saving, 2 and 3 only have checkpoints; Splinter Cell 1-4 allow manual saves and quicksaves, 5 and 6 only have checkpoints; Call of Juarez 1+2 has quicksaves, 3+4 only has checkpoints; etc.), so even if you like the previous installment you can't be sure if the next game works the same when you want to buy it.
This information could be included in the infobox below the "save game location" info. It could just be simplified into a simple checkbox whether the game allows manual saves or not, and a "Notes" field with additional information (e.g. the things I listed above, how many save slots etc.). This way it wouldn't be cluttered, you just have a simple "Manual Saves?" checkbox next to the save location, and if there is any additional custom information, it can be written into the Notes field. What do you think about that?
This is follow on from my post on the Special K Steam Discussions, but expanded to include other third party tools such as Re:shade.
Link to Steam Discussion thread: https://steamcommunity.com/app/1157970/discussions/0/2650881941771332222/
Reply from: @Aemony
Today more than ever, (fast) storage space is expensive. One thing that always makes me mad is the insane amount of unused Localizations, game modes (often dead/closed multiplayer modes) that are installed by default - this is literally dead content. Wasted storage. Wasted money.
Now back in ye old days, it used to be a gigabyte at best. Not the end of the world, and not exactly worth the time investment. But old habits die hard, and I'm still doing it today.
With games becoming larger and larger, storage has become an issue that can thankfully be alleviated.
I'm going to list a few interesting examples, then propose a solution and finally suggest a way to integrate it to PCGW's structure. I'll also list a couple of issues with my proposal, potential flaws and uses cases etc. If you have a better idea or any suggestion to make this a thing, you're more than welcome.
Please note that all the numbers given are taken from Steam, but GoG, Uplay, EGS & Origin are guilty of the very same thing. Uplay's even worse, as always.
Any constructive feedback would be much appreciated - I never suggested a feature before, but this one has been on the back of my mind for at least a year. I feel like it could be very useful to many folks out there.
So, let's get to it. Those are easy ones to "clean-up" (more on that later):
Batman Arkham Origins. Had a multiplayer mode, servers are down. Delete one folder and the install size goes from 27.06Gb to 18.1Gb. 9Gb (33%) saved Final Fantasy XIII. Well documented, check the PCGW entry for it, you can remove ~20Gb if you don't want the Japanese audio. 57.6Gb to 37.7Gb. 19.9Gb (52%) saved (!!!) Doom 2016. Do you really play the MP or Snapmap modes? That's ~15Gb (11Gb if you only delete the MP) saved. From 69.68Gb to 54.68Gb. 15Gb (21.5%) saved Here's the problem. I can manually delete all localizations, "deluxe edition content", Readme/Support and redists safely from most MT_Framework, UE3 and Ubi games just fine because they use the same naming conventions. All I have to do is search in the root folder for any file with the _ita. suffix for instance and delete it - but that's because I know what I'm doing and I'm willing to take the time to locate and delete those files.
Listing that would massively bloat any page of course, and not many users would do it anyways.
The best way I can think of to implement a reliable and simple method to delete files that we're absolutely sure are safe to delete goes something like this:
Add a "debloatable" boolean to the Other Information infobox, If True, how much can be shaved-off at best. Users like myself could build a database of games we know we can "shave" (much like SK/ReShade compat, with a dedicated page) The end user would download a batch file, hosted here and verified by members based on a template which would include one option for each localization, and a "clean-up" option (remove Readme, Deluxe content, redists if safe) So for instance, I can flag all the localization for Resident Evil 6 and write them down in the dedicated page. I don't have any experience making modular batch files like that however, so someone else would have to make a template. I can then edit that batch to point it to all the files we want to delete. The end user launches the batch file, delete all locales but the one he's/she's using and boom. That's money saved right there.
I know there are programs that are much better than Win Explorer's Search feature - if we can feed such a program with a config file it should do the trick too. We'd still need to build a database though.
I do realize that I make it sound much easier than it may be, or that it may sound overkill if we're talking about a Gb at best. But for extreme cases like Doom 2016, Far Cry 3/4, FF XIII, the Arkham series, The Evil Within - huge games basically, it would be very helpful and hey, I'm already doing it anyways so might as well share it. There's also games like Battlefront 2 (2005) where you can cut the install size in half. It's about 5Gb (vanilla) if memory serves, about 2-3Gb when cleaned.
With that said, if anything I hope that this thread at least brings more attention to this issue.
Last but not least, to everyone: Happy holidays! I hope you're all doing well, and ready for more PCGW grunt work for this year to come.
"Keep on keeping on".
This seems like an important setting, especially with the prominence of high-PPI UHD monitors.
True: Has option to change scaling settings. May or may not automatically scale based on selected resolution. Example: SWTOR
Always on: Is automatically scaled based on resolution, but has no manual setting. Example: Lego Star Wars: The Complete Saga
Limited: Only scales certain elements (ex: graphics but not text), or cannot be scaled beyond a certain percentage of the base resolution. Example: Half-Life 2
False: Is not scaled and does not have an option to scale. Can't think of an example off the top of my head.
Hackable: Hackable. Example: Quake
This could go in the video settings table, or it could go in a potential accessibility table. I think probably wait until a dedicated accessibility table is made and put any info in 4K for now.
Who's Online 2 Members, 0 Anonymous, 537 Guests (See full list)
Recently Browsing 0 members
No registered users viewing this page.