[BUG] Display, Menu and Save problems

from Elemental Forums

Here is the Debug info: http://pastebin.com/m40fed04a

and my system specs: http://pastebin.com/m38204fe5

 

Generic Specs are a Vista Ultimate Laptop.

 

There are a several bugs that my machine has currently.

1. I can't pull up a save/quit menu.

2. Kingdom Info is inaccessable.

3. Population menu is inacessable.

4. Display has black squares, or black and parchment areas striped like a tilled field. [*Mostly fixed by Graphics Card driver update, still has occasional splotches.]

5. I cannot scroll down or right.

6. [resolved] Title Screen Crash (fixed by deleting familytreesubwnd.dxpack).

1,889 views 6 replies
Reply #1 from Elemental Forums Top

6. [resolved] Title Screen Crash (fixed by deleting familytreesubwnd.dxpack).
End of quote

That "fix" causes the first three issues.

Galactic Civilizations IV
Reply #3 from Elemental Forums Top

Okay, with updated drivers and such, the game will crash on launch unless familytreesubwnd.dxpack is deleted. If I tab out and restore the file afterwords, everything is fixed except #4.

Reply #4 from Elemental Forums Top

Is your #4 glitch anything like this?  If so, reducing to mipmap level 1 fixes it.

Reply #5 from Elemental Forums Top

Quoting kryo, reply 1

6. [resolved] Title Screen Crash (fixed by deleting familytreesubwnd.dxpack).
That "fix" causes the first three issues.
End of kryo's quote

You can get partway back to 'real' functionality by deleting the FamilyTree stuff, starting the game in windowed mode, waiting for the main menu to appear, and then restoring the files from your recycle bin. But a kludge is still a kludge, so I'm not calling anything else weird I see a 'bug' until I can get a full game instance running without doing workaround weirdness.

Reply #6 from Elemental Forums Top

Quoting scottrycroft, reply 4
Is your #4 glitch anything like this?  If so, reducing to mipmap level 1 fixes it.
End of scottrycroft's quote

Yeah, that's actually what it looked like before I updated the drivers, now it's not quite as bad.

Quoting GW, reply 5
Quoting kryo, reply 1
6. [resolved] Title Screen Crash (fixed by deleting familytreesubwnd.dxpack).
That "fix" causes the first three issues.
You can get partway back to 'real' functionality by deleting the FamilyTree stuff, starting the game in windowed mode, waiting for the main menu to appear, and then restoring the files from your recycle bin. But a kludge is still a kludge, so I'm not calling anything else weird I see a 'bug' until I can get a full game instance running without doing workaround weirdness.
End of GW's quote

Yeah, that solution is actually working pretty well.