RE: GraphicsModeControl.setPointSize with a DisplayImplJ3D underwin2k

• To: <dmurray@xxxxxxxxxxxxxxxx> <visad-list@xxxxxxxxxxxxx>
• Subject: RE: GraphicsModeControl.setPointSize with a DisplayImplJ3D underwin2k
• From: "Howell, Greg" <greg.howell@xxxxxxxxx>
• Date: Wed, 26 Feb 2003 07:37:29 -0500

Thanks --- I've got it resolved now.  It turns out using 2048x768 resolution 
[with jdk 1.4.1, j3d 1.3 (openGL), and my dual-monitor Radeon 7000 card) worked 
fine, whereas 2560x1024 didn't.  After rooting around on the web I came across 
this:
        http://www.ati.com/support/infobase/4030.html
which states there's a directX problem at higher resolutions than 2048x768 on 
win2k.  But 2560x1024 resolution can be made to work with java3d if under 
Display->Settings->Advanced->Troubleshooting you disable hardware acceleration 
for DirectDraw & Direct3D.

Many thanks,
Greg

-----Original Message-----
From: Don Murray [mailto:dmurray@xxxxxxxxxxxxxxxx]
Sent: Tuesday, February 25, 2003 6:43 PM
To: Howell, Greg
Subject: Re: GraphicsModeControl.setPointSize with a DisplayImplJ3D
underwin2k


Greg-

Howell, Greg wrote:
> Thanks Don & Mathias --- I've upgraded to jdk 1.4.1, j3d 1.3 and actually the 
> openGL & directX packages both solved the pointSize problem, but caused 
> another (less serious from my point of view) problem.

With Java 1.3.1, Java 3D 1.3 and DirectX 8.1, LineWidth settings do
not work.

> I've got a two-monitor "Radeon 7000" series adapter running 16-bit color 
> 2560x1024 which (oddly enough) only works with Java3D when one monitor is 
> disabled.  I say "oddly enough" because originally, when I was just having 
> the pointSize problem, both monitors were enabled.  Now if I disable one and 
> run in 1280x1024 all's well.  Hate to press my luck by asking two questions 
> on my first day on this list but I've tried everything I can think of.

Don't know about this.  I do know there is a problem with
1.4.1 with the mobility Radeon on my thinkpad:

http://mozart.chat.net/~jeske/unsolicitedDave/thinkpad_ati_java_bug.html

which is why I'm stuck at 1.3.1.  1.4.2 is supposed to fix the
problem.

Don
*************************************************************
Don Murray                               UCAR Unidata Program
dmurray@xxxxxxxxxxxxxxxx                        P.O. Box 3000
(303) 497-8628                              Boulder, CO 80307
http://www.unidata.ucar.edu/staff/donm
*************************************************************