[0.23][Bug/Graphics] Indescribable graphical error

I've been getting a lot of graphical errors since the 0.23 update.  Before then, the game would just crash around this time.  This is the most obvious of those errors.  DxDiag.  Underneath the black thing are my 11 cities.  Graphical errors in general seem to occur once I get about 10 cities.  I'd get more screenshots, but the only way I know to take a screenshot is with printscreen, alt-tabbing into Paint, and pasting into Paint.  But when I tab back, this crashes the game, so it's slow going.  Here's another one showing a more typical error:

3,901 views 7 replies
Reply #1 Top

Haven't seen that one yet. I have to ask the obvious question...Are your graphics drivers for your card up to date? I'm sure you thought about that already, always safe to check though.

Reply #2 Top

190.62 is the latest version for your card, but you're running 190.38.  Since that's not an ancient driver, I'm guessing that's not your problem, but it's still something to check out I guess.

Reply #3 Top

Hitting PrintScreen takes a screenshot and puts it in the My Documents\My Games\Elemental\Screenshots\ folder, and it makes a new shot for each time you take one.  You don't need to use Paint at all, and you can set it as .png or .jpg in the options screen.

Also, you can find your debug.err file in My Documents\My Games\Elemental\ and post it on pastebin.com as well.

That's also a pretty sweet glitch.  Good job!

Reply #4 Top

ahh gotta love it when a vengent god smites your cloth map with the giant obsidian knife of doom.

Reply #5 Top

My spider sense says that may be a quad batch bug.  Could you dig up and post your debug.err as well?  Thanks!  :)

Reply #6 Top

Quoting DoomBringer90, reply 4
ahh gotta love it when a vengent god smites your cloth map with the giant obsidian knife of doom.
End of DoomBringer90's quote

Nice!

Reply #7 Top

I'm having a hard time reproducing the exact same errors as before.

Here's a different one.  Debug.err.  This session ultimately ended up crashing on its own, shortly after.  I submitted a bug report for the crash: 70578_tt1d.  I'm not sure that they're the same bug.