For this particular example at least, I quite like "too localized".
To me, the "too localized" reason is for questions so specific, one would not expect any (or hardly any) other people to have them.
A question about a specific crash on an antique version of blender certainly seems to fit that description, especially as the crash is not readily reproducible ...
I think closing helps encourages the OP to make an effort to clarify their question. If they know no one can answer, they know right away that they aren't getting an answer if the question is left as is.
If it's still technically possible to add answers, then they might (knowingly or not) end up waiting and finding out the long way that no one is answering.
This question appears to be off-topic because it requires step-by-step instructions for a process that is specific to a particular project, and/or demonstrates too little effort on the part of the asker. These kinds of problems have been well solved elsewhere and are beyond the scope of this StackExchange.
There's never a reason to put a perfectly good answerable question on hold. Some questions do need clarification and putting them 'on hold' is the mechanism we use to get it. An OP who is invested enough in getting an answer will stick around and be happy to clarify once prompted.
The question needs to be clear or else the answer will become a meandering ...
I think that this is a bad idea for several reasons:
Closing questions should be avoided whenever possible
I think we should be cautious of just closing questions because they are old and unanswered, even if they do/do not have an answer. I think that would be a very questionable practice.
You should not close a question with an answer unless it is very ...
Source code questions
This question appears to be off-topic because it is about Blender C/C++ source code.
These questions are considered outside the scope of this StackExchange as defined in the help center. Development questions should be asked of the developers directly instead, see the contacting developers page of the blender wiki.
This question appears to be off-topic because it asks about adding features not yet in Blender. These should instead be posted on the requests section of the blender wiki or in the bf-functionality mailing list.
Two general themes to the custom off topic close reasons that I find myself sadly using quite a bit (but with different wording) are:
This question is off topic because it has absolutely nothing to do with blender.
I'm voting to close this question as off topic because it shows very little to no effort researching and/or writing this question.
Yes I whole heartily agree. In fact we have talked about this before, yet we never got around to changing all three of our custom messages.
I too think that a "not about blender" or something like that would be useful.
I even suggested something slimier before, here. (But that idea was met with a good bit of resistances, so some other wording will have to ...
If it was a duplicate (this case it is not) and fits on the other site, you could flag it and ask it to be moved to the proper site where they could mark it as a duplicate.
However it seems like the question you linked to is not what the OP is looking for.
In this case the best thing to do is to simply write an answer to the question on BSE. You can use ...
This questions appears to be off-topic because it is about the operating system, hardware, performance, or compatibility. These questions are considered off-topic because there is often no definitive answer, so they tend to require too much discussion to be suitable for Q&A format. Try asking on BlenderArtists for support instead.
I think I misunderstood the meaning of closing a question. I also discovered that it's possible to use the no answers filter when using the upper unanswered link.
This filter is not visible when choosing unanswered from questions list
So it seems my question is somehow off-topic or useless.
You are quite right, the too localized close reason seems to be used in all sorts of cases.
I've even seen the occasional question with close votes for both too localized and too broad.
In my opinion, this close reason is best suited to very specific questions unlikely to be of much to use to many other users. For example:
How to generate ...
In either of your cases it should be closed.
If it is too unclear to figure out where the problem lays, close it as unclear.
If the problem is clearly out side of blender, close it as off topic.
The obj exported from blender does not display right in my custom built game engine.
Closed as off topic because it is not a problem with blender.
It seems to me that the existing "unclear what you're asking" close reason covers this pretty well already.
I also think it's less likely to come across as "your question is bad", something which "low quality" could quite easily do.
It seems to me that questions that are unclear fall into at least two categories. One category is questions from users whose first language is not English, and as a consequence, the obscurity of the question is perhaps to some extent the fault of Google Translate or Babblefish. Another category is when the problem of clarity lies in the perception of one or ...
The new wording as of September 30, 2015 for the bug report close reason reads:
This question appears to be about an issue caused by a bug in Blender. These should be reported to the official bug tracker.
You can read more about the change here: Cleaning up our custom close reasons.
The fate of the original question aside… the best way to handle this is edit the original question to add (back) enough of the original context so your question can stand on its own. That sort of inter-post dependency works better in a threaded discussion forum, but as the content of this site is always expected to be updated and changed, it is best ...
I think we should only close question as a bug report when there is a high chance that the problem is actually a bug. The users that close it as a bug report should confirm that it is indeed a bug and not a feature or that way it normally would work.
I am not sure how we could close a question for bug report if the bug has been fixed, this would require the ...
Bug Reports for Code by Independent Authors
I think there should be two different Bug report close reasons:
One for bugs in Blender itself: that one should say "report to Blender's Bug tracker"
One for bugs in code from other coders: that one should say "report to code author"
I think this is a very important distinction that OP needs to be aware of, ...
When I look at the second (Techniques for modeling a network of blood vessels) I think it should be closed. It does seam way too broad. I expect now that you have brought more attention to it is will get closed. (I would close it now, except that I want you to get more responses here first.)
The first question is definitely answerable, it just needed to be ...