Reply #2 Top

I also get the same error whenever I alt-tab or (if I'm in windows mode) if the screen saver kicks on. Very annoying. I'll post a error file in a sec.

Reply #3 Top

Me too.  Alt Tab now always returns this error.  Previously (perhapse before Day 0, maybe also with Day 0) I could alt-tab and get back in about 80% of the time.

Reply #4 Top

Well, but if you just don't alt+tab, you can play the game. I CAN NOT PLAY MORE THAN 3 TURNS, when it colapses.

I already PAID for a game that DOESN'T WORK. Next wednesday I will ask my money back.

Reply #6 Top

If this is not caused by alt-tabbing, does it make any difference if you set windows to use US number settings (comma for thousands and period for decimals)?

Reply #8 Top

Could be. Twenty turns and no crash. Incredible. :omg:

Reply #9 Top

EDIT: But now, when alt+tab --> DX Error: Invalid call. :S

Reply #10 Top

Running in windowed mode (looks the same as fullscreen at desktop res) will avoid that one if you can live without edge scrolling.

Reply #12 Top

Rigth.

Anyway, it's supossed the problem with the number settings would be solved in the near future? I live in Spain, here we use period for thousands and coma for decimals...

Thanks for working in this problem. Sorry for my clumsy english.

Reply #13 Top

The game is supposed to override the regional setting within itself to prevent issues like this from occurring, so yes, the devs are looking into how the system could be overriding the override (as it can cause issues with reading in any sort of data containing decimal values).

Reply #14 Top

Interestingly, I have never had the pleasure of experiencing this glitch/crash until updating to 1.1.  Now with 1.1, I get the "DX Error: Invalid call" crash upon every single time I alt+tab. 

Too bad this still isn't fixed... wish I didn't love edge-scrolling so much. :(