Hi,
I just upgraded my ATI Radeon 9500 Video-driver to the newest one, in order to fix some redrawing-issues in the newest Battery 2-version. They were fixed, but unfortunately I'm now getting terrible statics produced in Scope, when I use the Scope-interface (Ie: browse through the menues of Scope), while the sequencer is running.
I can't really go back to the old driver, because that would just reintroduce the issues in Battery.
Does anyone in here have any tricks up their sleeves as to how I can fix this problem? Are there some settings in Windows I could fiddle with?
Cheers!
Thomas
Statics produced in Scope after ATI Video-driver update
-
irrelevance
you could try reducing colour bit depth from 32 to 16bit if you havent already.
try changing screen resolution.
in the vga software you may have the option to allow vga to use pci buss if you do and this is ticked it will cause problems. Thats all i can think of for now without being in front of pc.
try changing screen resolution.
in the vga software you may have the option to allow vga to use pci buss if you do and this is ticked it will cause problems. Thats all i can think of for now without being in front of pc.
-
irrelevance
Shouldnt have to reduce accelaration.
if you're using catalyst driver suite then check out this guide
http://www.tweakguides.com/ATICAT_1.html
if you're using catalyst driver suite then check out this guide
http://www.tweakguides.com/ATICAT_1.html
So many answers! The real problem is likely to be the PCI latency for the ATI card. You can use DoubleDawg to set the PCI latency. Another option I've discovered is using the Omega drivers. They use modern catalyst drivers that have been 'massaged' and seem to default to a PCI latency of 64, at least on my laptop and old AMD box.
ATI tray tools will allow you to set the PCI latency as well in the advanced options or whatever. It's buried on page 10 of the tweaking guide. However I switched over to using doubledawg because I use it on all my other machines and don't tend to have a lot of tasktray apps running on boot.
Lowering accelleration might help as well, particularly disabling advanced UI crap, but all of my machines here work fine with it set to full AND with custom skins (I just disable dropshadows and useless eye-glitz).
Lowering accelleration might help as well, particularly disabling advanced UI crap, but all of my machines here work fine with it set to full AND with custom skins (I just disable dropshadows and useless eye-glitz).
Thanks to all who replied to my problem here!
And sorry for not posting before now - But I posted this problem the day before I went to Norberg festival and just came back last night.
I tried to fiddle with the accelration bar a bit, and it ended in the lowest position possible.
I also tried out "dbldawg" which in combination with the hardware acceleration bar gave me a useful result.
I think My next move will be to try out the Orion-driver, all though I remember having a not too good experience with it in the past.
Anyways - I'll keep you posted on how in turns out.
Cheers!
Thomas
<font size=-1>[ This Message was edited by: petal on 2006-07-31 09:30 ]</font>
And sorry for not posting before now - But I posted this problem the day before I went to Norberg festival and just came back last night.
I tried to fiddle with the accelration bar a bit, and it ended in the lowest position possible.
I also tried out "dbldawg" which in combination with the hardware acceleration bar gave me a useful result.
I think My next move will be to try out the Orion-driver, all though I remember having a not too good experience with it in the past.
Anyways - I'll keep you posted on how in turns out.
Cheers!
Thomas
<font size=-1>[ This Message was edited by: petal on 2006-07-31 09:30 ]</font>
-
irrelevance
a quote from the link i posted above
"it's important to understand that the Omega drivers are actually based on the Catalyst drivers themselves, of course with lots of tweaking. However any significant underlying problem in the Catalysts often comes through in the Omegas, since Omegadrive does not rewrite this code."
Catalyst has alot of tweaks in the suite so any problems I have found (I recently installed a new vid card) can be resolved through this software.
anyway hope you get it sorted.
"it's important to understand that the Omega drivers are actually based on the Catalyst drivers themselves, of course with lots of tweaking. However any significant underlying problem in the Catalysts often comes through in the Omegas, since Omegadrive does not rewrite this code."
Catalyst has alot of tweaks in the suite so any problems I have found (I recently installed a new vid card) can be resolved through this software.
anyway hope you get it sorted.
sorry for jumping in here,
but what if the pci latency tool mentioned above only shows my two creamware cards and nothing else? does my graphic card (ati radeon 300 somewhat) not show up in the tool because it's a pci-e card?
question 2: to which pci latency value should two creamware powerpulsar 2 be set?
cheers
roman
but what if the pci latency tool mentioned above only shows my two creamware cards and nothing else? does my graphic card (ati radeon 300 somewhat) not show up in the tool because it's a pci-e card?
question 2: to which pci latency value should two creamware powerpulsar 2 be set?
cheers
roman