Page 1 of 2
Posted: Fri Apr 21, 2006 5:44 am
by paulrmartin
This has been going on for a while now. I searche dthe forum but could not find solutions.
When I right-click a device, my GUI goes out of whack.
This is what I see when I right-click Optimaster:
Any hints as to what to do?
Posted: Fri Apr 21, 2006 5:49 am
by Aries
What's your windows OS?.
Is it with large projects?.
<font size=-1>[ This Message was edited by: Aries on 2006-04-21 06:51 ]</font>
Posted: Fri Apr 21, 2006 5:55 am
by paulrmartin
Never a large project. WinXP, ATI All-in-Wonder graphics card. This doesn't occur only when right-clicking Optimaster.
Posted: Fri Apr 21, 2006 6:00 am
by Shroomz~>
I don't see optimaster in the screenshots Paul.
Posted: Fri Apr 21, 2006 6:03 am
by paulrmartin
It's not important that you see it.
Look at the second screenshot. I am removing Optimaster. The important thing to see is the screwed up graphics.
Posted: Fri Apr 21, 2006 6:10 am
by Shroomz~>
& this only started happening recently?
Posted: Fri Apr 21, 2006 6:10 am
by Aries
I get that with Win98 after a while using lots of graphic resources in projects.
Its because Win98 has limited GDI resources. WinXP has unlimited GDI resources and that should not happen.
It's strange.
What happens if you close other applications down and only have Scope running?.
<font size=-1>[ This Message was edited by: Aries on 2006-04-21 07:14 ]</font>
Posted: Fri Apr 21, 2006 6:13 am
by paulrmartin
On 2006-04-21 07:10, Shroomz wrote:
& this only started happening recently?
Read my first post, Shroomz. It's been going on for awhile now. I just didn't want to bother anybody with it but it's getting to be a pain.

Posted: Fri Apr 21, 2006 6:19 am
by Shroomz~>
oops, I read the first post, but some info went in & straight back out
XP SP2 here & that doesn't happen with optimaster as an STM insert (which is how we normally use it) or as standalone device, so it's not an optimaster bug. That much I know
Is XP running in 'classic' modes with everything tweaked for performance?
Are you running the latest ATi drivers? If so, you might want to try older drivers if all else fails.
Posted: Fri Apr 21, 2006 6:23 am
by Shroomz~>
I think someone here on Z will have the answer for you Paul, but as usual with problems, some more (well, a lot more) info on your system, system settings & graphics settings etc would be a big help in terms of giving you constructive advice.
Posted: Fri Apr 21, 2006 6:23 am
by paulrmartin
Drivers! That could be it, thanks!
I am running in classic mode because I don't like all the eye candy shoots out.

Posted: Fri Apr 21, 2006 7:15 am
by paulrmartin
nope. not driver related...
Posted: Fri Apr 21, 2006 7:24 am
by Aries
What happens if you close all other applications down and only have Scope running?.
Does the screen redraw?.
<font size=-1>[ This Message was edited by: Aries on 2006-04-21 08:25 ]</font>
Posted: Fri Apr 21, 2006 7:35 am
by Shroomz~>
If you're sure it only happens with optimaster, try this:_ remove the optimaster device from it's Scope directory location. Restart Scope with a project which isn't looking for it. Close Scope, Restart computer. Obtain a new copy of the optimaster device file. Put the optimaster device file back in it's intended location & restart Scope. Check if the redraw bug still happens with optimaster & only optimaster.
Posted: Fri Apr 21, 2006 8:22 am
by paulrmartin
Shroomz, thanks for your eagerness to help but I stated in the 3rd post of this thread that it doesn't happen only with Optimaster.

Posted: Fri Apr 21, 2006 8:31 am
by Aries
On 2006-04-21 09:22, paulrmartin wrote:
Shroomz, thanks for your eagerness to help but I stated in the 3rd post of this thread that it doesn't happen only with Optimaster.
What happens if you close all other programs down (sequencer, etc) and only have Scope running?.
Does the screen still not redraw?.
Posted: Fri Apr 21, 2006 8:53 am
by paulrmartin
I looked at my ATI settings and I was not using Default Monitor in there. I changed it back but I have to finish a job before I reboot and check if this fixed the problem.
Thanks for all the help

Posted: Fri Apr 21, 2006 9:30 am
by Shroomz~>
The posts dropped onto this thread so fast that I didn't read that post Paul ... oops
hope you've got it sorted.
Posted: Fri Apr 21, 2006 10:10 am
by paulrmartin
Well, I rebooted and loaded up as many crazy modules I could without a hitch. It must have been the default monitor setting that was messing things up.
Posted: Fri Apr 21, 2006 1:58 pm
by paulrmartin
Well, I just figured out that it happens when I have logic running.
Can Priority settings fix this, maybe?
Low Priority on Scope?