ObjectDock eating up system resources

For you ObjectDock users out there... have you noticed any significant performance losses while running ObjectDock? I have noticed that even simple tasks such as moving a window around the desktop will bring my CPU usage to 100% if ObjectDock is running, which results in very choppy motion and other slow-down effects. Quitting ObjectDock fixes the problem. This occurs on both of my computers (one is a p4 1.6ghz dell laptop and the other an athlon xp2100+ oc'd to 2.2ghz, asus A7N8X dlx mobo, 9700pro vid card, 512mb corsair PC3500 ram). The effect is MORE severe on my athlon system which seems somewhat odd since it pretty much blows away my laptop in most respects. I like the look of ObjectDock a lot but cannot justify its use if it puts such a heavy load on my resources. Any comments or suggestions??

Oh yeah... I also use IconPackager and WindowBlinds but the problem I'm talking about deals specifically with ObjectDock. Thanks!
[Message Edited]
2,563 views 3 replies
Reply #1 Top
Did you try the different "Drawing Technologies" settings to see if it made a difference?
Also, "Magnification Mode" settings?
Something else might be an application that is being skinned which needs to be excluded.
You might want to turn off the "Dock Taskbar Enable" to check that.

If you find out what is causing it, you can then work out why it is causing it possibly.

just some thoughts on possibilities to start checking from...
[Message Edited]
Reply #2 Top
Look in 'Performance Tweaks' settings and see if it is set to 'custom engine' or 'GDI+- engine'. Whatever it is, change it and see if it makes a difference.



Powered by SkinBrowser!
Reply #3 Top
I tried changing the "drawing technology" from GDI+engine to custom but it didn't help. Actually, it made all the icons in ObjectDock appear distorted. I also played around with the different magnification modes but no luck there either. I had already disabled the dock taskbar so I know that's not it. I'm not sure there's much else I can do. Is anyone familiar with how this application is written, i.e. could it be optimized for the P4? As I mentioned, the problem is much less severe on my 1.6ghz P4 laptop as opposed to my 2.2ghz athlon system.