hello
i’ve been working through “shogi’s learning jogl” tutorials. i previously experienced a problem with my cpu load being 100% whenever i ran my jogl application, with everything in the background slowing down to a crawl. i had implemented my window solely using awt. i then decided to try using swing instead, and the cpu load changed to a pretty 2% average. this was great with the first couple of example applications where no animator was being used.
then today i did the animation bit of the tut, attaching my glCanvas to a new animator object, and then starting the animator thread. running that app has shot my cpu load back up to 100%. i’m not sure why. i’ve tried creating a simple threading application that exectures a couple of threads and the cpu load factor is tiny. so it’s not threads in general, it’s something to do with animator/glCanvas.
i’m using jogl.jar and .dll from 2003, because the more recent versions dont seem to work on my pc. i get “unable to lock surface” errors. i have an on-board graphics card whose openGL capabilities are probably limited, but this is just an assumption. not sure why else the 2003 libraries work, and the later versions don’t. (card = S3 DeltaChrome IGP)
anyone got ideas as to why my CPU load is sky-rocketing with awt and with animator thread?