We've also noticed disappearing textures in our terrain visualization app.
We store several hundred textures for the terrain tiles in a quadtree, and
use a level of detail algorithm in conjuntion with a Switch node to enable
and disable the terrain tiles that are visible. This works fine, and all
textures
are visible. Its when we start applying mulititexturing to some of these
tiles
in the scene to show the results of some Line Of Sight operations that we
start to see textures disappear. I wrote a test app that tried to isolate
the
problem, and I severerly stressed the rendering system by loading large
numbers of textures and multitexturing them, but it worked fine. This
poster's
observation of Switch nodes and disappearing textures is interesting to note
since my test app did not use a switch node to store the tiles, and the main
terrain visualization app does. I plan on going back and adding a switch
node
system to the test app to see if I can consistently produce disappearing
textures.
-Pedro
----- Original Message -----
From: "Stedum, Harry van" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 05, 2001 4:22 AM
Subject: Re: [JAVA3D] disappearing texture - a bit long
> Hi Kelvin,
> well, by using v1.2.1 beta2 I had my textures back, which solved my
original
> problem, but elsewhere in my app I saw changes that i've not seen before:
on
> pages unrelated with the textured object, I lost complete subtrees out of
my
> scenegraph ... I related this to some bugs in the new buglist, like for
> instance #4399760, but am not too sure about that; it may be that part of
my
> code reacts differently to the changes and improvements in the latest
Java3D
> beta. Anyways, paired with a our project decision to use Java SDK/JRE
1.2.2
> and not 1.3, I decided to go back to the latest final release of Java3D,
> v1.2. Our IDE runs Java 1.1.7 and an app build with Java3D 1.2.1 b2
wouldn't
> start in this environment; in a test setup with JRE 1.3, it started but
> showed the scenegraph with lost subtrees, mentioned earlier. In the docs
of
> v1.2.1 b2 recommends usage of JRE1.3, I can see that :-).
>
> Back to the textures then: i have not isolated the problemcode so I'll
just
> describe what happens here: I may have some workaround fixed: i have
several
> pages, which share a static canvas3d and one scenegraph. The pages can be
> separated in ones which do show the textured plane (representing a square
> area with a depth-survey) and ones which do not show this plane. The plane
> is in a subtree rooted by a Switchnode, somewhere in the scenegraph. I
> toggle the plane when switching pages by means of the Switch node. Now
when
> switching between two pages which both show the textured plane, the
texture
> disappears; switching to a page with the same view of the plane, the
texture
> does not show. Now if I switch to a page which doesnot show the plane
> subtree, thus which swites of the subtree and then switch back to a page
> which shows the plane the texture will reappear again. So, uoy say, it is
> the switch, try force this by switching it off and on every time you enter
> such a page; I tried this but it isn't working yet ... but I'll try this
> direction a little harder.
>
> I think it may be related to updating live or off/on-screen data and/or
> geometry; i'm guessing though: elsewhere in my app I have dynamic geometry
> build of reference type point data, which changes according settings in
some
> GUI panel or calculationmodel data. Using Java3D v1.2 if I changed
offscreen
> data and geometry, it would not show changes when the page was switched to
a
> view on this geometry. Changing this geometry when onscreen works fine.
> Using v1.2.1 b2 it worked as expected (also offscreen), as did the
textured
> plane.
> Then the problem may also be related to the mixing of the Java3D thread
> and the Swing thread, or so it seems; not too sure about this one either,
> but I had some work getting the JPanels (in a JTabbedPane) and the static
> Canvas3D to work.
> Then I may yet have to delve in some unexplored functionality of
Java3D,
> like offscreen rendering e.a. But right now I will fiddle with the
switches
> some more.
>
> thanks for your attention, keep up the good work!
>
> Harry
>
> > -----Original Message-----
> > From: Kelvin Chung [SMTP:[EMAIL PROTECTED]]
> > Sent: Friday, March 02, 2001 7:41 PM
> > To: [EMAIL PROTECTED]
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: [JAVA3D] disappearing texture
> >
> > Hi Harry,
> >
> > What problem did you encounter when using v1.2.1 beta ?
> > Please send us a test case for investigation. I don't know
> > if there is workaround for this without using v1.2.1 beta2.
> >
> > Thanks.
> >
> > - Kelvin
> > --------------
> > Java 3D Team
> > Sun Microsystems Inc.
> >
> > >MIME-Version: 1.0
> > >Date: Fri, 2 Mar 2001 11:18:09 +0100
> > >From: "Stedum, Harry van" <[EMAIL PROTECTED]>
> > >Subject: Re: [JAVA3D] disappearing texture
> > >To: [EMAIL PROTECTED]
> > >
> > >Hi, after my initial joy over solving this problem using the v1.2.1
> > beta2, I
> > >soon discovered new problems were introduced, but since this is a beta,
i
> > >can perfectly understand that. Part of it has to do (or so it seems)
with
> > >the use of a specific Java SDK/JRE. I read 1.3 is recommendend, but in
my
> > >project we have to use 1.2.2. I'll have to use the latest final release
> > of
> > >Java3D then, v1.2. Now, could you or anyone suggest a workaround for
the
> > >disappearing textures; maybe shed some light on how it is fixed in the
> > >newest beta such that I can fix something up myself? That would help me
> > >greatly!
> > >
> >
>
>
===========================================================================
> 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".