This is the first program I have wrote that does not follow the framework of the demos included with the demo package. For some reason the display method in the GLEventListener is called repeatedly until I shut the program down. The screen flickers but I think that has to do with the poor videocard on my dev machine. When I followed the demo examples the diplay function would be called on a repaint or after a resize event, not constantly. Any ideas? I am using doublebuffering so that is not it and I even changed the frames backgrounds color to black so it isn''t repainting a white screen then a black one. I wanrned you! Didn't I warn you?! That colored chalk was forged by Lucifer himself!

I messed with magician for a bit a while back. It was flickering a tiny bit for me too. I only had about 4 med res polys on the screen. I stopped playing with it because I didn''t know much programming or what to do.

I had a similar problem with flickering and even occasional crashes with the Magician API - it turned out to be my video card drivers. The problem occurred when I used the drivers that shipped with my Prophet Ge-Force DDR graphics card. I switched to the Nvidia reference drivers and the flickering and the crashes disappeared. I have had fairly good results since.

On the down side the Nvidia reference drivers do not support the TV-Out option on the Prophet, but I have seen much more stable performance in almost all of my 3D applications since I upgraded.

I put the glcomponent on its own thread and the flickering stopped. Who knew? I am wondering if either of you have tried to share textures and display lists between two glcomponents via the drawablefactory. I get an error in the native code when I try. I am working around it right now by haveing separate glcomponents but it is annoying me that it does not work.

I wanrned you! Didn't I warn you?! That colored chalk was forged by Lucifer himself!