I apologize for the large amount of changes, the page overall was very well-done. However, some of the instructions were things that may not be clear to the majority of users who don't have as much experience in changing config files, etc. I just wanted to make sure the fixes were usable by the layman, so I expanded the instructions to be easier to use for "the noobs".
Talk:SWAT 3: Close Quarters Battle
Regarding the changes I made
I second Mirh's sentiment regarding the edits. I'm not quite sure what page weight has to do with things, though (other than loading times and site bandwidth), but I'm sure I'll pick it up eventually...
i was referring to visual weight, not others
for example, this - "Use the
-windowed launch parameter" OR "Launch the game with
-windowed switch" would be much more elegant in comparison to the (2) big fixbox(es) below
they seem good
but i was starting to think that we should make something for all those "launch the game with XXX parameter" things
i mean.. i understand they should be the most noob friendly possible, but they weight so much the page
I would definitely approve of a page for these common fixes. It'd look like your suggestion but with "-windowed" including a link to a page which goes more in-depth on it.
Preferably the page would have the two common ways of adding launch parameters, through Steam or through the file itself.
exactly what i thought!
there, we could also include all the overused tips like:
- If the not-run-as-admin game you are looking the savegames for, writes them in its %program files% folder (thus write protected) they will instead be in the
- Make sure you have the most updated driver for your graphics card
- Make sure you are running the latest DirectX, VC++, .NET, punkbuster, silverlight, flash player, game version
- Please, make sure you are not transcoding any video in the background before starting BF4
- Please, make sure you are not sharing any torrents before complaining about online lag
That page that was linked previously - it had such descriptions (Command Line Arguments). I was wondering whatever it should be describe it fully step by step, like we have it now, but I've seen (I think) Garrett writing "Pass -x command line argument" for some game once or twice, so I just copied that. A full description seems to be better - especially for "noobs".
What I think, we should do - if only possible - is to make fixboxes collapsible, especially that some fixboxes can be really, really, really long (see: Freelancer#Widescreen_resolution).