12 engines, 6 moves? No fullscreen ATI |
| Project: | Space Empires V |
| Version: | 1.17 |
| Component: | Code |
| Category: | bug |
| Priority: | normal |
| Assigned: | Hot-Rod-Lincoln |
| Status: | active |
Description
Ok, so I have 3 bugs to report. the first one is the one I hate most. Say you had a cruiser or any other ship with max engines, say 12, and you get badly damaged in a fight. Sometimes if you repaired it to 100% it would had 12 working engines, use 12 engines worth of supplies but only move 6 spaces per turn. It really bothers me when people put my ships back together with BONDO and DUCT TAPE.......
The second one is pretty simple. So far I have learned that if you have an ATI based video card (not sure what others) you cannot use PRIMARY DISPLAY DRIVER in the settings menu. If you do, it will go fullscreen but....... it will flash so bad that You may have a massive siezure. So you will have to use the ATI driver option instead. This option works on ATI cards but only in windowed mode. TRUST ME I have tried this on multiple computers ranging from Rage 128 pro to Radeon 9000 - 9800 to X-Series X600-X800. I just wish it worked fullscreen, yaknow?
Thirdly, forget closing you laptop lid, going into hibernate or standby, or just letting the screensaver come on. All of these will cause a violent crash, maybe it is because of the ATI issues but be careful.
Ok, thats my rant for the day, try testing some of these. Have fun
Works fine for me with ATI
Works fine for me with ATI with the settings above. Your hibernate problem leads me to believe it's something to do with your drivers.
I use an ATI 9800pro and
I use an ATI 9800pro and have no probs (running cat 6.10 drivers)
Check your control panel, there have been issues with anti-laising on Nvidia cards, make sure its set so the application can control it.
Thanks for letting me know it was working okay for you with those new drivers. I did some trouble-shooting, and found out that if I set anti-aliasing to "application controlled," then the game is okay and won't crash. I had had anti-aliasing set to a manual level, and I guess that's what caused the BLUE SCREEN, however this problem did not happen with older versions of the drivers--except with older versions of the drivers, I got those "flashes" every few second (which I don't have with the newest drivers).
Are you using the latest drivers? If you are and having these probs try an older set.