Poser translates 1 Native unit to 103.2 inches.

Do the same thing on Poser5 and the result will be 100 inches.

Joint Editor for example, Antonia. I had a hope in P6 it would respect units, but not ... :(

Thanks. I missed the readme. So, from now on, we have consistecy on units ... good. Still need to see how old stuff will fit on this.

Same slowdown here. And I have a modern nVidia card (6600 GPU with 256 MB) and using the very last drivers from nVidia.
6 WinterQeens (Jessica) are consuming my 1GB memory.
Any action I execute (anywhere) is also consuming 100% of my AMD64 3200.
In the Keyframe Editor, I see a similar slowdown as yours.

I use CATIA (a heavy CAD to make airplanes and I don't see CATIA puting this system on the knees like Poser6 is doing).

Yes, considering these major issues, lets leave my minor point regard "expecting more from Poser6 OpenGL" for the future.

We all know Poser6 now has 2 render engines for the "Preview render" - ScreeD and OpenGL.

As pointed by Kingfisher, I agree the only difference in terms of quality between Poser5 "Preview render" and Poser6 "Preview render" is the Transparence (unless I'm missing something). But such introduction came with a price: Performance slowdown.

Now, in terms of performance, for a nVidia 6600 graphics engine, OpenGL render is 60% faster than ScreeD (using the WinterQueen as reference: ScreeD renders it @ 4.2 fps and OpenGL @ 2.6 fps).

My point is that I was expecting an improved quality and performance with the OpenGL render compared with the ScreeD, starting from the "eye higlights".

Sorry if my comment triggered a discussion about OpenGL render can replace FireFly render in Poser6 version. (It may in Poser9 ... lol)

You should be in a place like the picture above.
Go down looking in the left colum for file extension PZ3.
Only Poser application should be there ...

Poser6 + Content Update
1GB memory system.

WindowsXP + Norton + Poser6 loaded = 290 MB peak
previous + 1 WinterQueen loaded = 440 MB peak

Render Auto Min shading Rate 1.25 = 655 MB peak
Render Auto Min shading Rate 0.10 = 1.7GB peak

Both render finish ok.
Are those numbers the same for you ?

Operaguy: CATIA has a Photorealistic render application for final render. And the RTR (real time render) for design, like here in Poser.
The most RTR gets closer the Final Render, the better.
And there are many features (not being used) on current hardware/drivers today to acomplish that.
But today, RTR is not substitute of Software render.

Kingfisher: My system is able to render @ 4 fps (frames per second) in OpenGL (preview) a WinterQueen's animation. That means a scene with 4 WinterQueens will render only @ 1 fps in preview mode. And it gets difficult to work (too heavy).

Jimmy1: Thanks. Even that way, results are very different.

kawecki: Thanks. Good information for me.

Kingfisher, not sure if I understood. With your 9800Pro, do you get that "light reflection" on the eyes ? Thanks

Regard performance, CATIA also has an interesting approach. The geometry is tessalated (triangles) and you can control it. So when there are too many parts in the scene, and the graphics card starts to slow down, I just reduce the tessalation level.

I have only the standard Poser5 stuff. So I tested with the dog. The texture is blured, not sharp (but in DirectX or OpenGL, the textures are perfect).

So, even if GPU real-time display render is not there (yet), in this point Curious Lab is not helping.

I still wonder if Curious Lab is doing all the real-time display render 100% software based ("flat" as you say). It seems (for me) they pass something to the GPU.

In parallel, I read DirectX 10 will NOT be available for at least the next 2 years. The reason is because Vendor implementations of current capabilities of DirectX 9 is far from the edge.

Maybe nVidia, introducing GELATO, is trying to push Microsoft and also see how much developers support that.

We face a paradigm: "Today's real-time renders is not good enough for photorealism in complex scenes".

It's a chicken-egg circle (Application Render Developers versus "Real-time GPU-aided" Render Vendors)

It's nice to see Curious Lab providing the feature to generate AVI from the "display" render, but unfortunately they are not stressing the "display" quality as it is possible today.

Marcio

Gelato includes:

• Fast anti-aliasing
• True displacement
• Motion blur
• Layered shaders
• Full-range of geometric primitives
  -- NURBS, bicubic, and bilinear patches
  -- Polygon meshes
  -- Subdivision surfaces
  -- Hair
  -- Particles
  -- Plug-in API for procedural geometry
• Automatic adaptive tessellation
• Both scan-line and ray-traced rendering
• Global illumination
• Ambient occlusion
• Image output can be 8-bit, 16-bit, and floating (per channel)
• Output image channels for any value computed in shaders

My point is that GPU Industry is pursuing the following: GPU real-time render based on DirectX, OpenGL or GELATO (back to RealDeal initial post) can achieve equivalent quality as "software-based render (FireFly, 3DS, Maya or any)" in higly complex scenes.

I see you dont belive that is possible ... I respect that.

We are using extremes to compare (low end and high end).
I agree I used a very simple scene, but it was just to ilustrate.

Any way, I think that this is what this GELATO is proposing.

Marcio

So Curious Lab is inventing the wheel, and btw, they did it good.
I'm including an image (assembly from 2 screen copies) to compare the render quality. Sure FireFly is better, but (imho) lets say the real time render is close to 90% FireFly quality (lets get hair render aside for a while).

Using the real time render (and accepting 90% FireFly in quality), a 60-frames AVI, no-antialias, 640x542, takes less than a second to be generated.

It is also possible to adjust several controls in the GPU driver to increase quality reducing speed a little, but it seems Poser is not recognizing them (they are DirectX and OpenGL only - I see now ...)

Marcio