Help talk:Troubleshooting
Y'know, this should probably go under "srb2", and not "navigation". -Shadow Hog 19:36, 20 April 2008 (PDT)
err
For the Character WAD thing, shouldn't it talk about the lowercase lump name problem? Kitsune 02:51, 9 January 2009 (UTC)
This needs reworked.
Seriously, I think this needs reworked. Rather than having one page for each step, we need to have several on each page. We need to find some generic troubleshooting steps for each issue. For example, SIGSEGV needs as many reasonable troubleshooting steps as possible, like this:
| Troubleshooting Question | Explanation |
|---|---|
| 1. Have you run an error test on your level? | Running an error test in SRB2DB can find a lot of possible illegal sector configurations. |
Can't think of anymore for generic troubleshooting of that step, but that's a start, you know? Discuss. –SonicMaster 21:57, 6 August 2009 (UTC)
Honestly, the whole thing needs some help. It needs to have far fewer amounts of pages. One possible format could be like "Click here for crashing issues," "click here for specials not working," "click here for map editor issues," "click here for lump editor issues (XWE/SLumpEd)" and then put it in the format listed above. I want your input on this, because this massive amount of pages for try-steps-one-through-ten thing I have recently found is not really efficient. –SonicMaster 02:40, 26 October 2009 (UTC)
Well, I'm gonna start a little test here of the new format and leave what's currently there, there for right now. –SonicMaster 02:43, 26 October 2009 (UTC)
OK. I've pretty much noticed that the dichotomous-style troubleshooting is just really too complex to maintain, create, and get help through. Let's use the new test troubleshooting instead and simply put a lot of generic steps that will resolve a lot of random issues. It's much simpler. The Knowledge Center on us.playstation.com uses a format similar to this, and I think we should go with that. I might decide to compile what we have in the other one, delete the mess and put it in the nice one-page troubleshooting. –SonicMaster 01:41, 15 December 2009 (UTC)
Node builder did not build the requiered structers
Sorry I don't know how to spell structeres but any way my level dosen't pass the boundries and has way more then 1 sector It is larger then arid canyon zone act 1 please help yours truly --This was done by Eggmanfan you have been warned 17:43, 8 September 2009 (UTC)
How big is your biggest sector? How long is your longest linedef? How many sectors and linedefs do you have? –SonicMaster 03:07, 11 September 2009 (UTC)
What happens now?
At this point it must be obvious how uncared for this section of the wiki is – big question is: do we keep it and improve it, or just trash it? I'm leaning heavily towards the latter since I'm not convinced many people actually use it at all. (Help:Troubleshooting itself apparently has only 53 views as of this time of writing)
If we could sort this out at last that'd be brilliant, I'm tired of seeing all these Troubleshooting red links swamping Wanted pages. --Monster Iestyn Talk 12:03, 15 September 2014 (CDT)