PDA

View Full Version : Windows 7 x86_64 graphic issues


bzykubd
10 Nov 2012, 20:17
Hello,

i have graphic issues while playing. When i had Windows 7 32 bit, i were killing explorer.exe and everything were working good. Now it doesnt work.

I were trying to:
+ kill explorer.exe and other not unnecessary tasks
+ manipulate video options in game options (problem gone when im not using double buffering, but thats not a solution ;) game works too slow then)
+ manipulate compatibility options in windows

Nothing works. Do you know how to fix it? My graphic card is an AMD HD 6950. I have also latest version of worms. Everything fully updated.

And strange thing, when i take caputure of screen with Fraps (i wanted to show you) - screen is good :D Without issues. Maby fraps is so fast and take screens between new screen reload by double buffering ;p

CyberShadow
11 Nov 2012, 01:42
Have you checked palette.log?

http://worms2d.info/Troubleshooting_FAQ#The_game_colours_get_all_messe d_up

bzykubd
11 Nov 2012, 10:42
Hmm, yeah, csrss is there. But i have noticed that my graphic issues are other than on screen. My screen is corrupted mostly on edges, body of objects is not currupted. When im playing big map like Tower Race, game is "playable".

So, conclusion is - my system is not compatible with Worms and probably its not possible to solve problems?

CyberShadow
11 Nov 2012, 10:47
That's a strange description. Can you take a photo? (Palette corruption isn't registered on most screenshots.)

The next update should take care of any palette-remaining problems.

bzykubd
11 Nov 2012, 11:14
Heh, i dont have high end camera to show it good. But ive done screenshots with laptop, maby you will notice something.

http://i.imgur.com/Z6fCt.jpg
http://i.imgur.com/KQU0k.jpg

Here it doesn't look so strange. While playing its pretty annoying.

CyberShadow
11 Nov 2012, 11:31
That's interesting... palette corruption manifests as some colors being replaced with others, but in the first screenshot, it looks like the entire button is filled with garbage? Perhaps this is another form of graphics corruption, unrelated to the palette.

Have you tried updating your video drivers?

Pac-Man
11 Nov 2012, 12:15
Not only the button is garbage, also the group box borders are rainbow styled, the drop down arrow is also messy.
1. Update graphic card drivers
2. Check if there are bugs in other (DX7) games to find out if your hardware has a problem or not
3. Try the window mode stuffs for W:A maybe?
3. Blame AMD for finally dropping correct DX7 support

bzykubd
11 Nov 2012, 13:22
Yeah, ive updated graphic card drivers.

Hmm, i dont have any game using DX7. I will try later to run game in window mode. I have game using DX5 and DX9 - running correct.

And what about AMD, hmm. I wont blame them :) I think that back supporting is in fact problem of nowadays computing. x86_64 is the best example, not so good architecture ;) I will install older os or try using wine.

StepS
11 Nov 2012, 13:38
try to temporarily run it with windowed mode (http://forum.team17.co.uk/showthread.php?t=57737). if the problem is gone, then the problem is related to old renderer support and it will be solved in the upcoming update. as for now, a full solution for in-game is project x.

bzykubd
11 Nov 2012, 13:50
In windowed mode - completly black screen (if i move mouse in that window im hearing sounds from controls, so worms are working just with black sreen ;p).

StepS
11 Nov 2012, 15:53
disable SlowFrontendWorkaround and try again.

Muzer
11 Nov 2012, 17:08
Yeah, ive updated graphic card drivers.

Hmm, i dont have any game using DX7. I will try later to run game in window mode. I have game using DX5 and DX9 - running correct.

And what about AMD, hmm. I wont blame them :) I think that back supporting is in fact problem of nowadays computing. x86_64 is the best example, not so good architecture ;) I will install older os or try using wine.
Wine should work fine, let me know if you have problems with it. It'll work even better in the next update (but that might also fix it in Windows).

bzykubd
11 Nov 2012, 18:27
disable SlowFrontendWorkaround and try again.

No differences ;/