Having started this discussion I then stupidly forgot to take my notebook
on holiday and now observe that the thread has drifted a little so?.
1) I strongly suspect that my problem and Lewis Walkers are related but are
not the same as I do not get the flickering. Once an object vanishes it
stays vanished unless I change its material again at which point it may
reappear (or may not) so the Shape3D itself isn't damaged.
2) The problem occurs with 1.3 and 1.3.1 but not 1.2.1
3) What do you mean by "the behaviour thread". I change the material for
the appearances used by several Shape3Ds and randomly some may vanish.
They vanish immediately - its not dependent on any mouse action. The
change is made from the main thread (i.e. the one that handles the Swing
GUI). There are three behaviours around to handle view rotation, scale and
pan (I don't trust orbitBehaviour) but no special threads have been set up
beyond whatever the mouse behaviours set up by default. Am I missing so
mething here? However, the vanished Shape3Ds never reappear on their own
(e.g. is I move the mouse or resize the screen) and only ever reappear if I
change their material again.
4) I'm working on Windows (Shame), OpenGL (OK) and (for the record) NVIDIA
Quadro2 Pro
5) I can think that I can provide a free standing example fairly easily.
Alex Bowden
[EMAIL PROTECTED]
-----Original Message-----
From: Mark Hood [SMTP:[EMAIL PROTECTED]
Sent: 11 July 2003 20:50
To: [EMAIL PROTECTED]
Subject: Re: [JAVA3D] Changes of material not being displayed at java1.3
> Date: Fri, 11 Jul 2003 08:54:35 +0100
> From: Lewis Walker <[EMAIL PROTECTED]>
> Organization: Rhema Designs
>
> If I am highlighting only one shape at a time, the problem doesn't seem
> to manifest. If I highlight many shapes at once, however, some of them
> sometimes don't get updated in the view.
We haven't seen this problem. There have been a lot of bug fixes from
Java 3D 1.3 to 1.3.1; you may want to try upgrading to see if the
problem is still there in 1.3.1.
> I can (I think) get rid of the problem by putting in a time delay
> between the calls to change the material colors of each shape - It would
> seem that having too many calls to setMaterial in a row with no pause
> between them is the problem. This rather points at thread issues in the
> Java3D code.
Where are you performing the call? Attribute changes won't necessarily
be synchronized with rendering unless they are performed from the
Behavior thread.
-- Mark Hood
===========================================================================
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".
===========================================================================
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".
