Jump to content

Generic Troubleshooting Page


Recommended Posts

  • Replies 35
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Games using PhysX typically fail with no feedback (game exits or crashes with no error message), so I'd lean towards covering it on that basis. There is also the issue of legacy PhysX--games bundling

I have made a WIP version: User:Garrett/Troubleshooting. Feel free to edit/expand/etc. Main page has no styling for now (navigation layout would probably be something clear like the editing guide). L

I have redesigned the introduction and navigation. Basic troubleshooting has been merged into the introduction page, and the first steps for each page are presented more prominently.   Pages for Win

That would depend on the complexity. Disabling processing methods like f.lux would be under basic since it's all about eliminating third-party interference. Other stuttering causes will be more about determining bottlenecks or choosing between driver versions, so that would be more of an advanced thing.

Link to post
Share on other sites
  • 6 months later...

I have redesigned the introduction and navigation. Basic troubleshooting has been merged into the introduction page, and the first steps for each page are presented more prominently.

 

Pages for Windows Vista and Windows 8 are no longer included due to support ending for these versions (extended support ended last year for Windows 8 and will end for Windows Vista on April 11, 2017).

 

Anyway, see what you think.

Link to post
Share on other sites

Wtf? Since when were we caring for official damns? :s

If any, the only criteria I'd see to hide something is popularity. But this only if space was really all that constraint.

 

For the remainder, wow, pretty nicely of a good page.

Do we have statistic for most searched fixes btw? xD

In hindsight, it's smart to already present there some.. flesh, I mean especially basic troubleshooting (which in your connotation is what I was imagining as "good practices")

And I was also going to critcizie you for duplication "install directx"... But yeah, you are totally right instead: unless they see the "error window" buzzword, some people will never really get it.

 

but aren't sound/controller/graphics pages a bit too much hidden?

Link to post
Share on other sites
  • 2 weeks later...

I have rebuilt the example as the Troubleshooting Hub. This separates issues by category instead of OS. The starting page includes some example problems to help guide the reader.

 

but aren't sound/controller/graphics pages a bit too much hidden?

Troubleshooting information from the glossary pages would be moved to the troubleshooting pages.

Link to post
Share on other sites
×
×
  • Create New...