sure in 4v4s when maxed armys clash and motherships cloak evrything it reall drops down but opther then that it works super fine.
Starcraft 2 Ultra Video Card Review - Page 2
Forum Index > Tech Support |
BeMannerDuPenner
Germany5638 Posts
sure in 4v4s when maxed armys clash and motherships cloak evrything it reall drops down but opther then that it works super fine. | ||
SkullOne
United States52 Posts
As for AA not working with AMD cards this is because Blizzard technically doesn't have the native ability to apply AA based on DX9/DX10 specs. NV allows you to force it through their control panel. Forcing AA has always been problematic because it can sometimes lead to instability and performance drops. AMD usually doesn't release driver updates for specifics like AA for beta software. I assume that come the actual SC2 release a future Catalyst update will provide the ability to force AA through the CCC. | ||
Sanasante
United States321 Posts
| ||
Snuggles
United States1865 Posts
I'm playing on my laptop right now. Here's the specs: CPU - Intel Duo Core P8600 GPU - GeForce 9600M GT 4 GB RAM Windows XP ----------------------------- Where does my laptop stand compared to other gaming rigs? Average or somewhat good? I get pretty low frames when I try to play the game on Medium and high settings, like say 30 - 50 frames, it's just way too uncomfortable for me to play (I like 70 - 100 frames). I have a Desktop with a less than decent CPU... if I stuck a HD 5750 in there would it be able to run on medium or high settings with 80 - 100 FPS? Or would the CPU hold it back? It's worse than what I have on my laptop. | ||
route_Map
United States28 Posts
Win7 64-bit 6 GB RAM Core 2 Duo 3.16 Ghz GeForece 9800 GTX All Settings defaulted to Ultra on install and the performance was fine. GPU fan did kick into gear when the engine loaded up. p.s. haha, nice Nomad screenshot. | ||
QuothTheRaven
United States5524 Posts
On July 21 2010 22:45 Konsume wrote: Yes I know how to fix it... it's a KNOWN bug spread around the 4xxxx, 5xxxx HD series. They fixed it on the 9.x drivers and it's back in the 10.x drivers. So basicaly what you should do it you don't want to deal with this bug is: Delete 10.6 drivers (or what ever driver you're on) Reinstall 9.12 drivers Hey voila! no more corrupted pointer for you! There has been a problem with 10.x drivers that are known they just can't fix it for some reason. So revert back to 9.12 till they fix their driver problem... which they said it will be "SOON!" That being said, 9.12 runs SUPER fine with SC2 and I run with an Eyefinity setup (tho it's not working for sc2). here is the link if you're on Vista/Win7 x64 http://support.amd.com/us/gpudownload/windows/previous/Pages/radeonaiw_vista64.aspx I think you might be thinking of the enlarged cursor bug, not the corrupt cursor bug. The corrupt cursor bug only occurs for users with 2+ monitors. Here are some characteristics: + Show Spoiler + The glitch can be reproduced most easily on a two monitor setup, by rapidly sliding the mouse across the bottom edge of the desktop such that it crosses display boundaries repeatedly until the glitch occurs, the glitch will appear on the left monitor (the right monitor will remain unglitched), on a single monitor setup it is much more difficult to trigger but can still be triggered by very rapidly moving the mouse between the top left and bottom right corners repeatedly (a 5600 or 5700 DPI gaming mouse is ideal for this, yet still challenging), which also works for triggering it on the rightmost monitor in a multimonitor setup. The glitch occurs separately on each display (each one has its own glitched/not-glitched/differently glitched state). This glitch occurs when moving the mouse across monitors at the very bottom edge of the desktop. The glitch persists regardless of which cursor image is displayed, all are displayed wrong (looks as if a scroll register is messed up), mouse pointer size becomes 16x16 even if the image appeared to be smaller previously, and the image will often repeat in some way to fill out the allotted space. The mouse pointer size does not change (other than the padding to 16x16 pixels as described above). The animated busy pointer illustrates how the glitch is scrambling the pointer, and is perfectly captured in Willis's picture, the animation looks kind of like it is showing on shards of broken glass, every pixel of the pointer has its place, but the placement is wrong. The way the image is scrambled is not completely consistent, the same image might look different each time the glitch triggers - but will be consistent as long as the glitch is present. One can cause the glitch to mutate to different forms of image scrambling by reproducing the same conditions that trigger it in the first place. One can glitch a single monitor by itself by moving the pointer extremely rapidly (5600 or 5700 DPI gaming mice are ideal for this purpose) between the top left and bottom right corner of the monitor repeatedly until the glitch occurs. The glitch persists across disabling/enabling monitors. Each monitor's respective variant of the glitch belongs to the respective ACTIVE monitor list, this means that if you glitch two monitors (challenging!) you can disable the lower numbered monitor and the higher numbered one will now demonstrate the first monitor's variant of the glitch, reenabling the first monitor restores the glitch variants to their rightful places, disabling the second monitor has no effect on which variant the first monitor shows. The glitch does not affect any displays hooked up to cards whose chipsets are not ATI. The glitch has occurred for many people for years now, on catalyst versions ranging back to 9.11 if not earlier. The glitch still occurs on 10.6 as of this writing. The glitch occurs at the following resolutions: 1280x800, 2560x1600, 1920x1080, 1680x1050, and probably all others. The glitch occurs on all types of video port. The glitch disappears on a reboot (but of course can occur again). The glitch occurs on Windows 7. The glitch does not occur on Linux. Edit: corrected earliest catalyst version to 9.11. Taken from: http://forums.amd.com/game/messageview.cfm?catid=279&threadid=122476&STARTPAGE=1&FTVAR_FORUMVIEWTMP=Linear The issue has existed for 2 years, and reverting to 9.12 or older drivers will not solve it. After struggling with this for a few months, I've managed to *almost* eliminate it by flashing the BIOS on my graphics cards to the latest version and installing 10.6, which has made some improvements. I can still corrupt the cursor by rapidly sliding the mouse left to right across the bottom of the screen between the two monitors, but it rarely happens unless I force it to. Anyways, to the original person with this problem: If you're up to it, consider doing a VGA BIOS flash. Also, update to 10.6 if you haven't already. 10.6 won't fix the problem, but for a few people (including me) it makes it occur less frequently. (Btw, if you only have a single monitor, then you're suffering from the "big cursor" bug, not the "cursor corruption" bug. If you're on a 1-monitor setup, ignore everything I just said and try Konsume's advice, though ATI has claimed that they "fixed" the big cursor bug in later 10.x drivers.) | ||
Daniri
387 Posts
| ||
PcChip
United States50 Posts
After updating the motherboard's BIOS and the 5850's drivers, it has dissapeared* * - every once in a while I do get a temporarily corrupted cursor in SC2, but it usually goes away soon | ||
Nihilnovi
Sweden696 Posts
IMO graphic cards are GREATLY overrated when it comes to games, the card development is years ahead of what any game can actually use, the only possible reason I can think of is that the 2xx series lacks dx11 support. | ||
RA
Latvia791 Posts
And most importantly, any of these top-notch cards would run game perfectly, comparing a few minor performance differences is so elitist and quite pointless. I have ASUS GF250GTS and I'm damn happy how it worked. I hope campaign doesn't disappoint on performance | ||
SkullOne
United States52 Posts
So those AMD owners who hate jaggies can rejoice. Frankly I'd still just rather boost my resolution with Eyefinity instead of AA. | ||
Santriell
Belgium151 Posts
Considering I'm running an HD4670 512DDR3 perfectly on high settings, why in the hell would you buy an overpriced 1gb ddr5 card for about the same quality but five times the price ? If you need to improve, get a mid-range card for now and wait for the super-duper cards to drop in prices in a few months. Buying things that just got out to achieve extreme resolutions is not only stupid in the PC world, it's also one of the worst ideas considering GPUs because it usually takes 1 to 2 years of driver updates for the new cards to be able to run at full performance. | ||
Konsume
Canada466 Posts
On July 22 2010 02:26 QuothTheRaven wrote: I think you might be thinking of the enlarged cursor bug, not the corrupt cursor bug. The corrupt cursor bug only occurs for users with 2+ monitors. Here are some characteristics: + Show Spoiler + + Show Spoiler + The glitch can be reproduced most easily on a two monitor setup, by rapidly sliding the mouse across the bottom edge of the desktop such that it crosses display boundaries repeatedly until the glitch occurs, the glitch will appear on the left monitor (the right monitor will remain unglitched), on a single monitor setup it is much more difficult to trigger but can still be triggered by very rapidly moving the mouse between the top left and bottom right corners repeatedly (a 5600 or 5700 DPI gaming mouse is ideal for this, yet still challenging), which also works for triggering it on the rightmost monitor in a multimonitor setup. The glitch occurs separately on each display (each one has its own glitched/not-glitched/differently glitched state). This glitch occurs when moving the mouse across monitors at the very bottom edge of the desktop. The glitch persists regardless of which cursor image is displayed, all are displayed wrong (looks as if a scroll register is messed up), mouse pointer size becomes 16x16 even if the image appeared to be smaller previously, and the image will often repeat in some way to fill out the allotted space. The mouse pointer size does not change (other than the padding to 16x16 pixels as described above). The animated busy pointer illustrates how the glitch is scrambling the pointer, and is perfectly captured in Willis's picture, the animation looks kind of like it is showing on shards of broken glass, every pixel of the pointer has its place, but the placement is wrong. The way the image is scrambled is not completely consistent, the same image might look different each time the glitch triggers - but will be consistent as long as the glitch is present. One can cause the glitch to mutate to different forms of image scrambling by reproducing the same conditions that trigger it in the first place. One can glitch a single monitor by itself by moving the pointer extremely rapidly (5600 or 5700 DPI gaming mice are ideal for this purpose) between the top left and bottom right corner of the monitor repeatedly until the glitch occurs. The glitch persists across disabling/enabling monitors. Each monitor's respective variant of the glitch belongs to the respective ACTIVE monitor list, this means that if you glitch two monitors (challenging!) you can disable the lower numbered monitor and the higher numbered one will now demonstrate the first monitor's variant of the glitch, reenabling the first monitor restores the glitch variants to their rightful places, disabling the second monitor has no effect on which variant the first monitor shows. The glitch does not affect any displays hooked up to cards whose chipsets are not ATI. The glitch has occurred for many people for years now, on catalyst versions ranging back to 9.11 if not earlier. The glitch still occurs on 10.6 as of this writing. The glitch occurs at the following resolutions: 1280x800, 2560x1600, 1920x1080, 1680x1050, and probably all others. The glitch occurs on all types of video port. The glitch disappears on a reboot (but of course can occur again). The glitch occurs on Windows 7. The glitch does not occur on Linux. Edit: corrected earliest catalyst version to 9.11. Taken from: http://forums.amd.com/game/messageview.cfm?catid=279&threadid=122476&STARTPAGE=1&FTVAR_FORUMVIEWTMP=Linear The issue has existed for 2 years, and reverting to 9.12 or older drivers will not solve it. After struggling with this for a few months, I've managed to *almost* eliminate it by flashing the BIOS on my graphics cards to the latest version and installing 10.6, which has made some improvements. I can still corrupt the cursor by rapidly sliding the mouse left to right across the bottom of the screen between the two monitors, but it rarely happens unless I force it to. Anyways, to the original person with this problem: If you're up to it, consider doing a VGA BIOS flash. Also, update to 10.6 if you haven't already. 10.6 won't fix the problem, but for a few people (including me) it makes it occur less frequently. (Btw, if you only have a single monitor, then you're suffering from the "big cursor" bug, not the "cursor corruption" bug. If you're on a 1-monitor setup, ignore everything I just said and try Konsume's advice, though ATI has claimed that they "fixed" the big cursor bug in later 10.x drivers.) No... I'm on an EYEFINITY setup so I'm definatly with not 2 but 3 monitors all samsungs HD gaming series. I had the corruption bug and was wondering what went wrong cause I went from 9.12 to 10.6 and never experienced that bug before updating to 10.6. The cursor is distorted, than transforms in wierd arrows and than lines and get back to somewhat a normal cursor with lines in it and than goes back to some type of arrows...... and the only way I could get a normal arrow was to reboot my system. To be honest at 1st I was thinking my card was burning and that I might have to think about replacing it but... since it was an HD5870 1go... I tryed to find a solution and I found out when browsing many shooters forums that the corrupted bug is know and that the 9.12 driver set was the only drivers it was ok. So I reverted back to 9.12 for about a month an half and... guess what? never had this bug again. So again, those with corruption bug... get the 9.12 cataclyst set and everything will run fine! | ||
Tazza
Korea (South)1678 Posts
| ||
SCbiff
110 Posts
On July 22 2010 19:00 Nihilnovi wrote: I'm playing 2500x1600 everything possible on ultra/turned on and no fps drops ever(even in 200 supply battles, never noticed any type of drop), on a single oc'ed 275. I do also have 6gb of game performance ddr3 ram(cl5) and a i7 system. I really dont understand why anyone would ever need a graphic card better than 275, I run crysis with everything maxed @ 2500x1600 with Fraps with no FPS drops IMO graphic cards are GREATLY overrated when it comes to games, the card development is years ahead of what any game can actually use, the only possible reason I can think of is that the 2xx series lacks dx11 support. Define "no FPS drops". I guess you mean it sucks and doesn't go any lower? Because I promise you you aren't runing Crysis @ 2560x1600 maxed with >= 4x AA without seeing abysmal frame rates. I have a gtx 480 and a 30" monitor, and I can't even run that without noticing it. Hell, even SLI can't do it and stay > 60 fps over the benchmark. | ||
PGHammer
United States132 Posts
On July 21 2010 22:05 Jenslyn87 wrote: That test has a few problems... the game has gotten progressively harder to run with the patches released during the beta, and I'm not sure the test shows accurate numbers. It has very high minimum fps, but seriously during a big battle even very strong pcs will drop way down in fps. http://www.tomshardware.com/reviews/blizzard-entertainment-starcraft-ii-benchmark,2611-6.html is probably more representative of actual performance. But yea, the game is pretty cpu demanding That is precisely the issue: SC2 (toward the beta's late stages, and at launch) is proving to be heavily CPU and I/O bound (as opposed to GPU bound); I've noticed that when things slow down I'm also getting a lot of hard drive I/O (Windows 7 x64). While I have 3 GB of RAM, I have about 20 GB of drive space free at present, and a SATA main drive that dates back to 2004 (therefore, drive cache and drive performance is not the best it can be by any means). How does WD's Cavbiar Black 1 TB SATA HDD perform in terms of SC2 use? | ||
Egnarts
Denmark33 Posts
| ||
| ||