Subject:
|
Re: video card
|
Newsgroups:
|
lugnet.cad.dev.mac
|
Date:
|
Sat, 23 Feb 2002 02:21:55 GMT
|
Viewed:
|
1532 times
|
| |
|
|
In lugnet.cad.dev.mac, Mark Abrams writes:
>
> I have been doing an analysis of the ldglite 0.9.5 code base. Most of
> the ledit commands cause the image to be either invisible or render
> incorrectly. Also, I get a wireframe trail when I use the arrow keys.
> Everything re-renders fine if I cycle through the elements
> (page-up/page-down) in the scene. Is this normal behaviour?
Some of that might be normal behaviour, but I'm not positive from the
description. Using -ledit on the command line turns on the
draw to current piece mode that LEDIT uses. If you just use -le
I think it should draw the whole model. You can also toggle this
behaviour in the Options menu (/OD) but for some reason it doesn't
take effect until you hit the e key (or spin with the mouse) to cause
a redraw. I'll have to look into that one. Anyhow, I tried to make
it as close to LEDIT as possible with -ledit but I may have botched
some things.
For the wireframe trails you can try using uppercase -LEDIT (or -LE
to skip the draw to current piece mode). Uppercase tells it to move
parts in solid mode, which might get rid of the wireframe trails.
Lowercase -ledit uses XOR wireframe mode, but I've run into problems
with the stencil buffer used by this on some cards. (I did a workaround
for the Nvidia TNT by using an opengl extension). I don't know about
the Rage 3D pro-64, but the drivers on my older Rage Pro are so bad
that I use the Microsoft generic Software-only driver instead on my
Win95 PC.
> I suspect this is due to the lack of a video card that supports
> OpenGL (ATI Rage 3D pro-64 iirc). Will a new video card resolve this
> problem, will there be any other noticable performance enhancement
> with a new video card?
>
> It is the stock card in a G3/266/MT with OSX. I am starting the app
> with the command line args '-l3 -ledit -v0 -g myfile.dat'.
What does ldglite print out when you start? It should print out the
opengl extensions, buffer sizes, and say something about the buffer
swap mode and the editing mode. This will tell which methods ldglite
is using for editing mode. I tried to take advantage of some opengl
extensions to make editing faster, but then had to work around some
bugs in various drivers.
Don
|
|
Message has 2 Replies:
 | | Re: video card
|
| (...) I forgot to mention this, but if you only want to look at the model, or *mostly* just want to look, you can skip the -le, -ledit, -LE, or -LEDIT on the command line. Then when you want to edit, just press the INSERT key to enter and exit from (...) (23 years ago, 23-Feb-02, to lugnet.cad.dev.mac)
| | | Re: video card
|
| (...) Here is the printout at startup. GL_VERSION = 1.1 APPLE-1.1 GL_EXTENSIONS = GL_APPLE_specular_vector GL_APPLE_transform_hint GL_APPLE_packed_pixel GL_APPLE_client_storage GL_ARB_transpose_matrix GL_EXT_clip_volume_hint GL_EXT_rescale_normal (...) (23 years ago, 23-Feb-02, to lugnet.cad.dev.mac)
|
Message is in Reply To:
| | video card
|
| I have been doing an analysis of the ldglite 0.9.5 code base. Most of the ledit commands cause the image to be either invisible or render incorrectly. Also, I get a wireframe trail when I use the arrow keys. Everything re-renders fine if I cycle (...) (23 years ago, 22-Feb-02, to lugnet.cad.dev.mac)
|
9 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
