Alright, well, I think I might try the "polling" technique, since my
general question did not get any responses. Hopefully, someone will get
the idea, and get sick of all of my questions to figure out what it is
that I need. I hate to clutter everyone's mailboxes, but here I go with
question numbe
: <[EMAIL PROTECTED]>
> Sent: Saturday, February 10, 2001 8:07 PM
> Subject: [JAVA3D] Projection Matrix
>
>
> I am trying to compute the projection matrix Java3D uses based on the
> information in mainly the View class, but it also depends on the Canvas3D,
> Screen3D, Phys
e best thing we can do
is keep submitting solutions and explanations to Justin Couch to add to the
FAQ pages.
Dave Yazel
- Original Message -
From: Blaine Alex Bell <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, February 10, 2001 8:07 PM
Subject: [JAVA3D] Project
I am trying to compute the projection matrix Java3D uses based on the
information in mainly the View class, but it also depends on the Canvas3D,
Screen3D, Physical Body, and Physical Environment (and possibly more?).
My frustration is building up based on poor documentation and complicated
policie
Hi
Made the same experience - we had to use compatibility mode because we wanted a
canvas which an aspect ratio different from 1.
I spent almost a week with getting picking working again, afterwards - and this
only after I had dropped the API - picking stuff out and written a workaround.
Someone
> My problem is that a lot of things like picking, zooming, field of view
> setting, eyepoint setting start behaving unexpectedly once I enable the
> compatibility flag for getting the projection matrix.
This is what the Java3D API specification says of the compatibility mode:
"Note: Use of thes
