Skip to main content

1.3.2-beta2 build

15 replies [Last post]
kcr
Offline
Joined: 2004-03-17

The beta2 version of Java 3D 1.3.2 is now on java.net in the usual place:

https://j3d-core.dev.java.net/servlets/ProjectDocumentList

It can be found in the "Experimental_Builds/1.3.2-beta2" folder. As always, please let us know if there are problems or file an issue. Thanks.

Btw, We'll post a list of fixed issues shortly. The webstart version of this will be available tomorrow.

NOTE: there is still the outstanding issue of a regression due to our fix to Issue 5. For this reason, we are planning for a beta3 release, but our main focus is going to be on 1.4. Unless a serious regression is found, we don't plan to fix any more bugs.

-- Kevin

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
jada
Offline
Joined: 2004-03-17

>Is it possible that the properties obtained from Canvas3D
>queryProperties() must be obtained after the canvas is >"realized" or something?

No. Look at QueryProperties.java that comes with our examples.

>Also, how do I select the Direct 3D driver - it's a system >property, right?

The property to select Direct 3D driver : -Dj3d.rend=d3d
eg. java -Dj3d.rend=d3d foo

- Chien.

Message was edited by: jada

Russell East

Thanks Chien.

How "soon" does the "j3d.rend" property need to be set?

What I mean is, can I set it using System.setProperty() and
expect that it will work properly? If yes, do I need to use it before
doing anything, like creating a Canvas3D?

-- Russell

java3d-interest@javadesktop.org wrote:

> >Is it possible that the properties obtained from Canvas3D
> >queryProperties() must be obtained after the canvas is >"realized" or
> something?
>
> No. Look at QueryProperties.java that comes with of examples.
>
> >Also, how do I select the Direct 3D driver - it's a system >property,
> right?
>
> The property to select Direct 3D driver : -Dj3d.rend=d3d
> eg. java -Dj3d.rend=d3d foo
>
> - Chien.
> ---
> [Message sent by forum member 'jada' (Chien Yang)]
>
> http: //www.javadesktop.org/forums/thread.jspa?messageID=50262ì‘–
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
> For additional commands, e-mail: interest-help@java3d.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
For additional commands, e-mail: interest-help@java3d.dev.java.net

jada
Offline
Joined: 2004-03-17

> What I mean is, can I set it using System.setProperty()
> and expect that it will work properly? If yes, do I
>need to use it before doing anything, like creating a
>Canvas3D?

Yes, you can, but have to be before Canvas3D creation or MasterControl.loadLibraries() take place.

- Chien.

paulby
Offline
Joined: 2003-06-13

Thanks for the correction Justin.

jada
Offline
Joined: 2004-03-17

Here is the up-to-date list of enhancements, new properties and bug fixes in Java 3D 1.3.2 beta2. We have added 5 new fixes ( issue 5, 15, 86, 88 and 91) since beta1.

Java 1.3.2 enhancements
=======================

1) Improved the speed and quality of scene antialiasing (from 2 samples to possibly 8 samples) if pbuffer is supported.

2) Eliminated memory bloat for IndexedGeometryArrays with USE_COORD_INDEX_ONLY flags set.

Java 1.3.2 new properties
==========================
j3d.rend - Specified the renderer that will be used for Java 3D. Recognized values are "ogl" and "d3d" (Windows-only). The default value is "ogl".

j3d.viewFrustumCulling - If this flag is set to false, the renderer view frustum culling is turned off. The default value is true.

Note: Java 3D uses a 2 pass view culling. The first pass is a loose view culling of the spatial tree, and the second pass is a tight view frustum culling in the renderer before sending the geometry down to the low level graphics API. The j3d.viewFrustumCulling property is to control the renderer view frustum culling, and it will not affect the first pass view culling.

j3d.transparentOffScreen - If this flag is set to true the background of the off screen canvas is set to transparent. The default value is false.

j3d.usePbuffer - If this flag is set to false pbuffer will not be use for off screen rendering. The default value is true.

j3d.audiodevice - Takes the name of a concrete subclass of com.sun.j3d.audioengines.AudioEngine3DL2 that will be constructed by Viewer.createAudioDevice(). The default value is null, which means that audio is disabled by default for applications that call Viewer.createAudioDevice().
For more information See also : http://www.javadesktop.org/forums/thread.jspa?threadID=6102&tstart=120

Bug fixed
==========

Bugs fixed in Java 3D 1.3.2 beta2; since Java 3D 1.3.1 FCS:

Issue Summary
------------------------------------------------------------------------------------------
3 lg3d: gets unsatisified link error on various ATI cards
4 Speed of OffScreen Canvas3D
5 Frequent native exception: Canvas3D.destroyContext
11 Seemingly inconsistent delays in updating attributes
12 Frame counter isn't always incremented correctly
13 J3DTimer fails on Windows XP with P4 3GHz
14 Random NullPException in uninitialized SoundSheduler
15 Model Clip planes not correctly set when view changes
16 Issue with Runtime instantiation of Canvas3D
18 Geometry missing in OnScreenCanvas when OffScreenCanvas is resized
19 Resizing off-screen Canvas3D hangs on Solaris
20 Off-screen rendering doesn't work on Linux
21 Exception in WakeupOnElapsedFrames behavior stops renderer from running when it should
23 Enhancement to Reduce Memory Bloat in IndexedGeometryArray
26 Texture3D not displaying when size over 512X512
27 Shapes mistakenly culled when they are visible
28 Combine Mode & Missing Texture in OffScreen snapshot on Win/XP
33 Texture updates fail w/ Multitextured BY_REF Geoms
36 Vector3d hashCode() method distinguishes between -0.0 and 0.0
38 ConfiguredUniverse throws an exception when using Java Web Start
66 NullPointerException in renderOffScreenBuffer
71 OGL: OffScreen canvas ignore GraphicsConfigTemplate under windows
72 Exception in setOffScreenBuffer when Canvas3D not in View
73 Quat4f#interpolate: incorrect when q1*q2<0
74 Texture/color math difference (D3D vs OGL)
76 OffScreen rendering should use Pbuffer on Windows / OpenGL
77 Scene antialiasing is disabled on Windows / OpenGL
80 libj3dcore-ogl.so fails to load on Linux systems without certain GL extensions
81 SimpleUniverse.cleanup() doesn't dispose of all threads
83 Deadlock when removing Canvas3D and universe
86 ModelClip affects Java2D graphics in mixed-mode rendering...
88 Ambient Lighting corrupted by Mixed-Mode rendering...
91 add new key/s to Canvas3D.queryProperties() for graphics card info

Russell East

Any chance of a WebStart page update as well?
Thanks,
-- Russell
-----------------------------------------------------------------
java3d-interest@javadesktop.org wrote:

> The beta2 version of Java 3D 1.3.2 is now on java.net in the usual place:
>
> https://j3d-core.dev.java.net/servlets/ProjectDocumentList
>
> It can be found in the "Experimental_Builds/1.3.2-beta2" folder. As
> always, please let us know if there are problems or file an issue. Thanks.
>
> Btw, We'll post a list of fixed issues shortly. The webstart version
> of this will be available tomorrow.
>
> NOTE: there is still the outstanding issue of a regression due to our
> fix to Issue 5. For this reason, we are planning for a beta3 release,
> but our main focus is going to be on 1.4. Unless a serious regression
> is found, we don't plan to fix any more bugs.
>
> -- Kevin
> ---
> [Message sent by forum member 'kcr' (Kevin Rushforth)]
>
> http: //www.javadesktop.org/forums/thread.jspa?messageID=48520불
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
> For additional commands, e-mail: interest-help@java3d.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
For additional commands, e-mail: interest-help@java3d.dev.java.net

kcr
Offline
Joined: 2004-03-17

> Any chance of a WebStart page update as well?

Just did that. Thanks for the reminder.

-- Kevin

mikofclassx
Offline
Joined: 2003-07-02

Very good Kevin,

please do not forget this feature for 1.4
http://www.javadesktop.org/forums/thread.jspa?forumID=55&threadID=5104&m...

Cheers,

Mik
--

kcr
Offline
Joined: 2004-03-17

> please do not forget this feature for 1.4
> http://www.javadesktop.org/forums/thread.jspa?forumID=55&threadID=5104&m...

We'll look into it, but it may not make the list without help defining and implementing it (especially the implementation, since we aren't otherwise planning to touch the Text3D code).

-- Kevin

mikofclassx
Offline
Joined: 2003-07-02

Need some coding ? I'm here!

Of course I would like to know the API details.
You were talking about a getTriangles() method. I could implement it if you want.

Mik

Russell East

Hey,
nice additions to Canvas3D.queryProperties() !
New keys appear to be:
native.renderer native.vendor
texture3DDepthMax texture3DHeightMax texture3DWidthMax

Can anyone tell me what it means when texture3DAvailable=false ?

I am now getting this on a Windows XP that is running inside of VmWare
v4.5.2, that is running within Fedora Core 3. I think it was running
fine just a week or so ago, but Fedora just had a couple new changes to
GTK and kernel (unsure about openGL) - VmWare remains unchanged.

The same app running in the Fedora looks great, but not in the VmWare -
colors are all messed up.

-- Russell

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
For additional commands, e-mail: interest-help@java3d.dev.java.net

paulby
Offline
Joined: 2003-06-13

texture3DAvailable=false means you graphics hardware does not support 3D textures. This is a very high end feature used in medical imaging, oil exploration etc.

Justin Couch

java3d-interest@javadesktop.org wrote:

> texture3DAvailable=false means you graphics hardware does not support 3D textures. This is a very high end feature used in medical imaging, oil exploration etc.

That's very wrong. Every consumer level video card since the GeForce2
has supported 3D textures. One of the laptops here is has a Geforce4 2Go
in it, which is the GF2 core and we happily do 3D textured rendering on
it. Not huge stuff, but reasonable size. In fact, most consumer cards do
far better at volume rendering these days than the "CAD" cards. I have a
small demo I'm working on right now that's easily displaying a segmented
512^3 volume at 50 FPS on a nVidia 6800 GT. Once I do some optimisations
of the rendering setup using some of the newest shader-assisted
techniques, I expect to be up around 80-90 FPS on that same data set
size. 3D textures are used an awful lot in current games, so it's not
like they're anything special anymore.

--
Justin Couch http://www.vlc.com.au/~justin/
Java Architect & Bit Twiddler http://www.yumetech.com/
Author, Java 3D FAQ Maintainer http://www.j3d.org/
-------------------------------------------------------------------
Programming is essentially a markup language surrounding
mathematical formulae and thus, should not be patentable.
-------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
For additional commands, e-mail: interest-help@java3d.dev.java.net

Russell East

But the weird thing is, even with "texture3DAvailable=false" the
textures were being displayed, just the colors were incorrect, mostly at
the peripheries - see attached screenshot.

This was all working when the host machine ran Fedora Core 2 with
Windows XP "guest" inside of VmWare. Just the change to Core 3 made the
difference I think. The VmWare display adapter is listed as:
native.renderer=GDI Generic
native.vendor=Microsoft Corporation

I am seeing a similar thing with one particular (older) IBM laptop that
has an ATI Radeon, as far as the bad colors are concerned.

Is it possible that the properties obtained from Canvas3D
queryProperties() must be obtained after the canvas is "realized" or
something? I am getting them when the application is still in the
process of starting up.

Also, how do I select the Direct 3D driver - it's a system property, right?

-- Russell

Russell East wrote:

> Hey,
> nice additions to Canvas3D.queryProperties() !
> New keys appear to be:
> native.renderer native.vendor
> texture3DDepthMax texture3DHeightMax texture3DWidthMax
>
> Can anyone tell me what it means when texture3DAvailable=false ?
>
> I am now getting this on a Windows XP that is running inside of VmWare
> v4.5.2, that is running within Fedora Core 3. I think it was running
> fine just a week or so ago, but Fedora just had a couple new changes to
> GTK and kernel (unsure about openGL) - VmWare remains unchanged.
>
> The same app running in the Fedora looks great, but not in the VmWare -
> colors are all messed up.
>
> -- Russell
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
> For additional commands, e-mail: interest-help@java3d.dev.java.net
>

[badcolors.jpg]
---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
For additional commands, e-mail: interest-help@java3d.dev.java.net

Russell East

I read in a previous java3d-interest email, that BufferedImages of the
above type are most efficient for Java3D/OpenGL. But I also vaguely
remember seeing that Windows/OpenGL prefers TYPE_3BYTE_BGR instead. Can
anyone confirm?
-- Russell

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
For additional commands, e-mail: interest-help@java3d.dev.java.net