Readable Editor Doesn't Work

[AluminumHaste]

I can try to change the way the GUI renderer dispatches the draw calls for the text, but this takes a while. It would be nice to have some sort of GL debugger which tells me exactly what the problem is, I have no idea what I might be doing wrong.

 

That said, I'm soon going to get a new laptop with an ATI card, so with a bit of bad luck I'm going to experience this problem myself.

 

OMG don't say that lol, these issues can be sooooooooooooo annoying, especially if you are the only one having them.

[Bikerdude]

so with a bit of bad luck I'm going to experience this problem myself.

LOL, why does that sound perverted....

 

How would he get a debug out from Dr greebs or have you already mention the how to in this thread..?

Edited October 1, 2010 by Bikerdude

[greebo]

Well, by using the Glintercept stuff from earlier in this thread I learnt that the OpenGL driver is crashing right after submission of the GUI text's vertices. As I don't know yet what I have done wrong here (I was following recommended examples when implementing that, as I'm by no means an OpenGL veteran) I can only try to change the rendertext to use regular vertex arrays instead of VBOs.

[Fidcal]

There is a tiny flaw: the editor won't let you type a space in the inv_name, eg, "log book". This can be easily entered in entity inspector though. Want me to add this to bugtracker?

[greebo]

There is a tiny flaw: the editor won't let you type a space in the inv_name, eg, "log book". This can be easily entered in entity inspector though. Want me to add this to bugtracker?

Yes, please.

[greebo]

crashed.

Here's an experimental build with disabled VBOs, the GUI renderer is now using regular vertex array draw calls. Please check it out:

 

http://www.dramthethief.com/darkmod/files/darkradiant/darkradiant-1.5.0pre6.exe

[ungoliant]

holy shit it works!!!!

thank you so much Dr. G!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!11!1!!!one!!eleven1!

[greebo]

That's good to know.

 

Now I'd be curious what I've been doing wrong. Would you be willing to run a few further tests such that I might be able to narrow down the cause?

[ungoliant]

sure, I'm down. Let me know.

[Bikerdude]

Ungol, youll need to reinstall Teamviewer for Greebs, so he can remote in if need be etc..

 

btw whats the status of the build, do I still need to give you a hand etc..?

[greebo]

No need to hurry, I need to compile a fresh build with some further changes. I'll let you know as soon as a Teamviewer session is useful for me.

[ungoliant]

perhaps the remainder of this conversation should be moved to 1.5.0pre-release thread, as the readable editor does work now (for me), and probably won't benefit anyone looking for useful info about fixing readable editor problems.

[greebo]

sure, I'm down. Let me know.

Here is another release build with OpenGL error handling switched on: http://www.dramthethief.com/darkmod/files/darkradiant/darkradiant-1.5.0pre7.exe

 

Please check it out. In case of OpenGL errors, a popup should be displayed right before crashing, with some info, hopefully.

[Bikerdude]

I will test it for my crashing when closing after 10mins bug..

[ungoliant]

well i can't use it on the readable crash (because its fixed in this release). Tried it for crash using F3 on a huge map. only got windows error report.

[greebo]

Hm. I must have forgotten something, it should crash on typing in the readable editor. I'll get you another build:

 

http://www.dramthethief.com/darkmod/files/darkradiant/darkradiant-1.5.0pre8.exe

[ungoliant]

ok that build crashed the readable editor when text is entered, but no pop-up window, sorry.

[greebo]

Hm, then I'm a bit at a loss here. Maybe or probably I'm doing something wrong which lets the driver go nuts, but I can't really tell what that might be.

 

Perhaps I can whip up an isolated test program sometime, which narrows down the issue.

[Bikerdude]

Greebs, I think you need to remote into Ungoliants pc, as I have found him doing stuff differently to most people. He has Teamvier installed etc as I remoted in there the day before last.

[greebo]

I appreciate the offer, but at this point there's nothing more I could do while being connecting to his machine, other than watching DarkRadiant crash myself. It's a thing happening in the drivers, and not even setting up a Visual Studio build environment is going to help here, as the driver sources are not available.

 

I'll look around for some fixes as I'm curious, but it's a huge time burner to find the root cause, for an issue which is worked around by now anyway.

[Bikerdude]

It's a thing happening in the drivers,

he has gone back to 9.11, as he was getting some visual corruption with 10.2 - I imagine he will post here wityh exact details why etc.

[ungoliant]

oh yea, forgot to mention that tidbit. I've been on catalyst 9.11 for quite a while to fix some really annoying texture morphing issues in DR. 9.11 is the only driver set i found that actually fixed it for me. Anyway, since the readable issue got fixed i rolled back from 10.2 to 9.11 to re-fix this issue. I doubt that has anything to do with why the opengl error report/log window didn't pop up, though.

[Bikerdude]

I doubt that has anything to do with why the opengl error report/log window didn't pop up, though.

Is windows error reporting still turned on ..?