Hi,
Does anyone know why canvas capturing doesn't work
with ati radeon 9200 graphics card. Other cards I have
tested, it works fine.
I have used example code at j3d.org web page:
http://www.j3d.org/faq/examples/CapturingCanvas3D.java
-mikko
Hi,
I've been pleased to see the interest in skin & bones animation
triggered by Mark's contribution recently. These are once again exciting
times now that the Java3D code has become an open source Java.net project.
OK, enough of that, on to my problem...
I'm trying to morph between objects created
I have an application that is supposed to record the intersection point
of a mouse click location and a Shape3D, *after* the user selects
a particular menu option. I've set up a user-defined clickBehavior
that gets triggered when the user selects the menu option and then
performs a mouseclick. Mo
Paul Brown wrote:
Hi,
I've been pleased to see the interest in skin & bones animation
triggered by Mark's contribution recently. These are once again exciting
times now that the Java3D code has become an open source Java.net
project.
OK, enough of that, on to my problem...
I'm trying to morph betwe
Hi, All,
Here is the problem:
We have multiple machines in Windows XP that has intel P4 2.8G Hz+ CPU with
Hyper Threading enabled. We found Java 3D picking action become very slow,
even slower than machines with less than 1G Hz CPU. The
pickCanvas.pickAllSorted() method is taking more than 10 tim
Hi,
that sounds like a graphics driver problem. Have you tried it with the
OpenGL- and the DirectX-version of Java3D?
Michael
On Wed, 30 Jun 2004 13:51:34 -0500, Hong Cao <[EMAIL PROTECTED]> wrote:
Hi, All,
Here is the problem:
We have multiple machines in Windows XP that has intel P4 2.8G Hz+ CPU
i think this is due to erroroneous mouse click. it happens in my program
also. many times click is not considered by java. it is bcoz a small drag
event get fired. i also solved the problem by considering the length of
drag
> I have an application that is supposed to record the intersection point
Hong Cao wrote:
We have multiple machines in Windows XP that has intel P4 2.8G Hz+ CPU with
Hyper Threading enabled. We found Java 3D picking action become very slow,
even slower than machines with less than 1G Hz CPU. The
pickCanvas.pickAllSorted() method is taking more than 10 times its original
Thanks -- I'll check whether a drag event is fired.
Lola
On Jun 30, 2004, at 3:36 PM, MUNDE SANDEEP VIJAYKUMAR wrote:
i think this is due to erroroneous mouse click. it happens in my
program
also. many times click is not considered by java. it is bcoz a small
drag
event get fired. i also solved the
I checked Java 3D source code, their handling of picking is not related to
the graphic driver. Java code will calculate everything. So graphic card
driver problem is ruled out. (Remember when disable HT, everything is fine.)
As to OS, we did have similiar, actually more serious problem when we
ins
I wanted to chime in on this.
It is possible that hyper threading is making a difference because it does
require support at the OS level. (If I am not mistaken). Given that, it
is possible that something within the OS (including such things as
graphics drivers) might not be handling hyper threadin
I want to point out that picking is *heavily* related to graphics
drivers/cards. Java code may be used to process results of picking, but
picking itself is a hardware operation that occurs during rendering to
framebuffers.
This is at least the case in OpenGL, and im sure its the same in directX.
Ian M Nieves wrote:
I want to point out that picking is *heavily* related to graphics
drivers/cards. Java code may be used to process results of picking, but
picking itself is a hardware operation that occurs during rendering to
framebuffers.
No it's not. In both Java3D and Aviatrix3D we do pickin
Hi Mark,
sorry I shouldn't have put my comment about skin & bones animation in my
message about morphing. It's just that I'm so excited about what is
happening in Java3D these days and I welcome the interest being shown by
people like yourselves for include skeleton rigging in the core system
or, a
It's possible the order of the vertices is being messed up by our loader
as I use:
gi.recomputeIndices();
// "gi" is an instance of GeometryInfo
and
s3d.setGeometry(gi.getGeometryArray());
So if GeometryInfo alters the order of the vertices this could account
for the problems seen.
- John W
15 matches
Mail list logo