Hello, I'm not perfectly sure if this is the right place to address myself to, but since I'm in dire need of some good advice, I'll try anyhow. (Chances are good that some of you might already have had contact with the device.)
I am facing a very embarrassing problem regarding the usage of a Spacemouse / Magellan (6DoF device): after I've added the device, sensor and behaviour to the scene, I am experiencing a ridiculously high CPU load. Adding a few (just as little as 60) geometries causes the load to be permanently stuck at 100%. This puzzeles me, since before the program didn't ever produce such loads - even with a few up to several thousand(!) objects in the contentbranch. Neither increasing the argument of WakeUpOnElapsedFrames() in the SpacemouseBehavior from "1" to "10", nor modifying the argument of setNextSensorRead() from currentTimeMillis() to something a little more further in time did yield the expected result. (Asides from the updates becoming more scarse and the screen updates thus being less smooth.) The CPU usage stays up all the time. I even have the impression that a constantly growing backlog of events is generated, since the system doesn't even react after it has been at 100% for a few moments, anymore. OBTW: AMD XP24+ - the machine should not be the most critical bottleneck. I assume that this extreme load is caused by the J3D softwaredriver since the problem appeared only after adding support for this device. The system runs very well when only using the built-in MouseBehaviors and handles scenes even highly stuffed with objects without problems. Even the vendor-supplied demos run flawlessly, causing just a few % of load. Furthermore the problem's severity grows with the number of displayed geometries. When I shift the model such that no geometries are visible (but still inside the scene's bounds), the CPU drops to 2%. The more geometries - the higher the load. The scene is static, nothing moves - no interpolators. Are there any known solutions other than removing this device's support? Did anyone else experience this? Can somebody help me please? (I'm unexperienced in writing behaviours and device drivers and thus have almost no idea where I shall start to tweak.) SDK: 1.4.2_04, J3D: 1.3.1(DX), 1G2RAM, W2K SP4, javax.comm Thanks a lot in advance. Regards, André =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
