render creation failed, no help from rightnow
- Thread starter Warr|
- Start date
If DAoC is the only one you might want to make sure your user.dat isnt borked and contains a correct resolution setting. (I had my user.dat corrupted once after my system crashed during logging out.)
It should contain a valid screen resolution for your card like:
[main]
...
screen_height=768
screen_width=1024
...
Alternatively you can move the user.dat out of your DAoC folder (dont delete it since it contains your complete keyboard settings.
) And see if the game runs when it creates a blank one.
It should contain a valid screen resolution for your card like:
[main]
...
screen_height=768
screen_width=1024
...
Alternatively you can move the user.dat out of your DAoC folder (dont delete it since it contains your complete keyboard settings.
) And see if the game runs when it creates a blank one.- Thread starter
- #5
Jeriraa said:If DAoC is the only one you might want to make sure your user.dat isnt borked and contains a correct resolution setting. (I had my user.dat corrupted once after my system crashed during logging out.)
It should contain a valid screen resolution for your card like:
[main]
...
screen_height=768
screen_width=1024
...
Alternatively you can move the user.dat out of your DAoC folder (dont delete it since it contains your complete keyboard settings.
Mine reads,
[quick]
setentry=0
[main]
setserver=[EN] Prydwen
setaccount=0
EULAdates=1106137516
dates=1105630760
accounts=stuvsez66
Something wrong ?....
Thats ALL it contains? If so then it doesnt contain any graphics settings at all, neither key bindings or quick-logins. Its more or less empty.
Remove it from the folder and see if the game creates a new one. Afaik it should. If it doesnt try putting these lines below the [main] tag and see if you get to the options screen at least:
screen_height=768
screen_width=1024
windowed=0
Remove it from the folder and see if the game creates a new one. Afaik it should. If it doesnt try putting these lines below the [main] tag and see if you get to the options screen at least:
screen_height=768
screen_width=1024
windowed=0
Funnily enough if you search the RightNow FAQ base for 'Renderer Creation Failed' it brings up two results. One tells you to upgrade your graphics drivers and reinstall DirectX, the other tells you to delete your user.dat file.....Jeriraa said:No problem, wasnt all that hard after all.
Perhaps you should point the rightnow guys to this so they have a solution next time.
The system is set up so that you have to search for an answer before you can ask a question for this very reason.
Requiel said:
I dont wanna be a smartass Requiel but the RightNow interface design is mostly a misconception. I dont know who designed it but he didnt bother about setting up a frontend that actually guides the user on the way to a solution of his problem.
Thats what I see on the screen on entering RightNow:
Find Answers
Ask a question
My Stuff
90% of the users that have a problem will NOT click find answers because thats not what they have in mind! They will want to "ask a question" so your nice database of solved problems is mostly useless due to being ignored.
Also the Find Answers leads me to a page with ALOT of info that a) doesnt help me and b) I dont care about right at the moment. What I (the user) care about is my problem and not:
How to use RightNow?
Release Note 1.75
Release Note 1.74[
About clustering
Release Note 1.73
Release Note 1.72
What video cards are currently supported and not supported for Catacombs?
Are Shrouded Isles and Trials of Atlantis required to play Catacombs?
What is sponsorship?
Release Note 1.71
Respec stones granted with the release of New Frontiers
Temporary Keep and Tower Cost Reductions
Tradeskills updates
New Grouping Level Range Changes
Siege weapons
Battlegrounds
Boats in New Frontiers
Getting to the new Frontier Zones
Rewards and captures/defences of keeps
New features about the /release command
You are flooding the user with tons of unwanted info and the one really intersting entry "How to use RightNow?" is easily overlooked.
Also keep in mind that the majority of DAoC users are not forum users and as such most likely not used to a search interface like the one you present them. (Hell, even most of the users on FH probably dont know the meaning of the button "search".
)Ok, had a shower and some food and since I still have a little over 20 minutes before I have to leave for work I'll throw you some key bits:
Biggest mistake ever: Naming your support tool "Right Now"! (Think about it for a minute.)
Guiding the user: For something like a customer support tool I'd suggest multiple choice forms. Ofc there are many different approaches to this problem but in my own opinion a couple of well asked questions give you a good idea about what the user wants very fast.
Ideally at first the user should be asked what he wants to do:
Hello <Name>, this is the Dark Age of Canelot Customer Support.
How can we help you?
-choices- (ideally the most frequent on top and the least frequent at the bottom)
Examples: "I have a problem with my account.", "I want to report a bug.", "I have an ingame problem.", "I have a technical problem.", "Other."
In our case the user would have selected "I have a technical problem.". The next question should determine if it has to do with sound, gxf or perepherials.
After 4 to 6 questions you should usaly have a good idea of wich info to present to the user and wich not.
The problem in this thread takes 4 to come to a point where you can already suggest possible solutions:
What type of problem? -> Technical
Gfx, Sound or Input? -> Unsure
Are you getting an error message? -> yes
Wich one? -> Render creation failed.
(Ofcourse entering "render creation failed" into the search field of the database provides the same result but that expects the user to take actions on his own rather than guide him.)
Save the questionaire and ask the user if the given suggestions solved his problem. (This might have to be done the next time he logs into the tool.) If they didnt let him describe the problem in his own words and have a techie deal with it. (Give the techie the questionaire too.)
Biggest mistake ever: Naming your support tool "Right Now"! (Think about it for a minute.)
Guiding the user: For something like a customer support tool I'd suggest multiple choice forms. Ofc there are many different approaches to this problem but in my own opinion a couple of well asked questions give you a good idea about what the user wants very fast.
Ideally at first the user should be asked what he wants to do:
Hello <Name>, this is the Dark Age of Canelot Customer Support.
How can we help you?
-choices- (ideally the most frequent on top and the least frequent at the bottom)
Examples: "I have a problem with my account.", "I want to report a bug.", "I have an ingame problem.", "I have a technical problem.", "Other."
In our case the user would have selected "I have a technical problem.". The next question should determine if it has to do with sound, gxf or perepherials.
After 4 to 6 questions you should usaly have a good idea of wich info to present to the user and wich not.
The problem in this thread takes 4 to come to a point where you can already suggest possible solutions:
What type of problem? -> Technical
Gfx, Sound or Input? -> Unsure
Are you getting an error message? -> yes
Wich one? -> Render creation failed.
(Ofcourse entering "render creation failed" into the search field of the database provides the same result but that expects the user to take actions on his own rather than guide him.)
Save the questionaire and ask the user if the given suggestions solved his problem. (This might have to be done the next time he logs into the tool.) If they didnt let him describe the problem in his own words and have a techie deal with it. (Give the techie the questionaire too.)
VidX
One of Freddy's beloved
- Joined
- Dec 24, 2003
- Messages
- 589
Jeriraa said:
Or you can do what just about every other search engine in use on the internet allows you to do and enter 'renderer creating failed' in the hopes that it will bring up the results... and wadda ya' know! it does!
Oh wait, Req already said that
I guess they could implement what you said, but if people use their brains and actually search for the problem in the hope that it has already been asked before and documented then, like in the situation above, they will get the answer in a few seconds rather than a day or so (or longer if it's the weekend).
There just is no solution that GOA can provide for idiocy.
You know, its as simple as that: Most people calling for support actually want support and not dig around in a database.
Like most people dont bring their car into a garage to repair it on their own. They bring it their to get it repaired and they expect the techies to tell them whats wrong.
Like most people dont bring their car into a garage to repair it on their own. They bring it their to get it repaired and they expect the techies to tell them whats wrong.
VidX
One of Freddy's beloved
- Joined
- Dec 24, 2003
- Messages
- 589
A guy drives into a garage and asks the mechanic:
'Hi, the lights don't seem to work on my car, can you fix them?'
'Have you tried turning them on?'
'No, of course not, I just want you to fix them'
'**** off you idiot!'
Yeah, people don't want to bother looking for and fixing problems themselves. I work in second+third level support for a VERY big company and if I point out to people that there is actually a place they can go to and look for the fixes for problems before calling tech support they usually appreciate it, simply cause they don't want to sit in a call queue for 5 minutes, don't want to have to talk to someone and explain the problem, and because they know that if they need to open a ticket it might take a few hours before someone can look at their problem cause there are other idiots who are wasting time by demanding tickets be opened because their computer isn't working due to them spilling coffee on it.
Once again, people prefer to get the problem fixed fast and the fastest way in this case is for people to check the very-simple-to-use database before opening a RN request for an issue that is well documented.
And personally, if I could actually repair or service my car myself, I'd do it. Would save an absolute fortune.
'Hi, the lights don't seem to work on my car, can you fix them?'
'Have you tried turning them on?'
'No, of course not, I just want you to fix them'
'**** off you idiot!'
Yeah, people don't want to bother looking for and fixing problems themselves. I work in second+third level support for a VERY big company and if I point out to people that there is actually a place they can go to and look for the fixes for problems before calling tech support they usually appreciate it, simply cause they don't want to sit in a call queue for 5 minutes, don't want to have to talk to someone and explain the problem, and because they know that if they need to open a ticket it might take a few hours before someone can look at their problem cause there are other idiots who are wasting time by demanding tickets be opened because their computer isn't working due to them spilling coffee on it.
Once again, people prefer to get the problem fixed fast and the fastest way in this case is for people to check the very-simple-to-use database before opening a RN request for an issue that is well documented.
And personally, if I could actually repair or service my car myself, I'd do it. Would save an absolute fortune.
VidX
One of Freddy's beloved
- Joined
- Dec 24, 2003
- Messages
- 589
Interesting link, if you even put 'renderer creation failed' into google, guess what the first hit is...?
http://www.google.com/search?biw=1004&q=renderer+creation+failed
http://www.google.com/search?biw=1004&q=renderer+creation+failed
