Page 1 of 1

1.04b2 error at line 35 reading file races.txt

Posted: Mon Apr 26, 2010 3:16 pm
by Imrryran
Hi,

I still have this error systematically, after installing the game (from "DistantWorlds-SetupRelease-DR-v103.exe" downloaded from you site). I tried patching it to 1.04 beta 2 (and even to 1.02) but it did not change anything.

I have read the "Tech Support FAQ" topic and obviously this problem is not corrected in 1.02.

Please note it disappears if I change my settings to "English (US)" in Windows (I use Windows 7 64 bits if it matters).

Regards

RE: 1.04b2 error at line 35 reading file races.txt

Posted: Mon Apr 26, 2010 3:18 pm
by Erik Rutins
Imrryran,

Hm, the issue with language format is fixed, I wonder why it would still show up for you?

Can you please post a DxDiag for us?

Regards,

- Erik

RE: 1.04b2 error at line 35 reading file races.txt

Posted: Mon Apr 26, 2010 3:25 pm
by Imrryran
Of course.

I uploaded a DxDiag report.


RE: 1.04b2 error at line 35 reading file races.txt

Posted: Mon Apr 26, 2010 3:26 pm
by Imrryran
And a screenshot of the error in case it helps you.

Please note that if I change the language format on my computer to English I can enter the game menu and see the version number is 1.0.3.0.

RE: 1.04b2 error at line 35 reading file races.txt

Posted: Mon Apr 26, 2010 3:49 pm
by Erik Rutins
Imrryran,

I assume your normal setting is French, but could you confirm for us exactly what your language and regional settings normally are so that we can try to duplicate this here?

Regards,

- Erik

RE: 1.04b2 error at line 35 reading file races.txt

Posted: Mon Apr 26, 2010 4:06 pm
by Imrryran
Erik, I'm awfully sorry, I cleaned windows temporary files (under C:\Users\[my user]\AppData\Local\Temp) then re-installed the game and it works now (re-installing it without cleaning temporary files did not seem to solve it though).

Sorry again for any inconvenience caused.

RE: 1.04b2 error at line 35 reading file races.txt

Posted: Mon Apr 26, 2010 4:12 pm
by Erik Rutins
Very interesting - thanks for letting us know what fixed it, though I'm still not sure why that would have caused this!