Subject:
|
Re: Question about DAT rendering
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Tue, 16 Apr 2002 13:17:31 GMT
|
Viewed:
|
397 times
|
| |
|
|
In lugnet.cad.dev, Andrew Allan writes:
> Ken,
>
> We are obviously in the same area the moment. After completing the
> conversion of LdGLite to run under MacOS 8.6-9.2 (ie LdGLite (Mac)), I
> turned my attention to the two biggest dissapointments to me, namely slow
> render speeds and quirky shading of models under OpenGL.
Hey, I happen to *like* my default shading settings. ;-) I agree
with you on the speed issue though...
> > I've been toying around with a visual DAT editor/viewer for Mac OS X,
> > and wanted to know if there is supposed to be any kind of guaranteed
> > rendering order on commands within a DAT file.
>
> To date I have got my renderer to produce much better shading and far better
> render speeds. However face normals of vertices is taking most of my time at
> the moment. Simply put they are not wound in a consistent fasion. Further
> more in some cases the same primitive is used to model both inside and
> outside faces (eg box5.dat, 4-4cyli.dat etc). So a system of winding will
> produce inconsistent results in this case.
I'm curious, do you have any numbers on how much slower it is on
accelerated hardware to do two sided lighting with GL_FRONT_AND_BACK?
glLightModeli(GL_LIGHT_MODEL_TWO_SIDE, GL_TRUE);
glEnable(GL_COLOR_MATERIAL);
glColorMaterial(GL_FRONT_AND_BACK, GL_AMBIENT_AND_DIFFUSE);
glMaterialfv(GL_FRONT_AND_BACK, GL_AMBIENT_AND_DIFFUSE, full_mat);
...
Or are you using something entirely different?
> Therefore to counter this I have been modelling the more common pieces
> (stud.dat...) as glu primitives and intercept them at render time (this
> produces excellent shading). Additionally items like box5.dat I intercept
> and test if the primitive is exactly a multiple 20 units in width (ie 1
> brick) then if that is true, I assume the part to be an outside wall or if
> not it's defined as an inside wall.
>
> This process is taking time as each part needs to be considered at the time
> of parsing and saved as an OpenGL list. However as when rendering all parts
> in the model are defined as OpenGl lists I only call the list numbers for
> each part - very fast rendering.
>
> I am open to suggestions as to better ways of doing things.
>
> Andrew...
|
|
Message has 1 Reply:
 | | Re: Question about DAT rendering
|
| (...) Well, on the Mac at least, the only hardware at the moment that supports two sided lighting are the GeForce3, GeForce4 and the new Radeon 8500. Everything else is going to use software T&L. My take on getting the shading to look right has been (...) (22 years ago, 16-Apr-02, to lugnet.cad.dev)
|
Message is in Reply To:
| | Re: Question about DAT rendering
|
| Ken, We are obviously in the same area the moment. After completing the conversion of LdGLite to run under MacOS 8.6-9.2 (ie LdGLite (Mac)), I turned my attention to the two biggest dissapointments to me, namely slow render speeds and quirky shading (...) (22 years ago, 16-Apr-02, to lugnet.cad.dev)
|
8 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
|
|
|
|
