See title.
I know the program isn’t used that often, but when there’s a lot of samples it’s soooo slow.
It already uses OpenGL… However, it was not optimized for speed of display.
Best regards,
Vlado
I think it’d be faster with d3D than opengl, just make a test in max without maxtreme if you use nvidia or other optimized-driver if you’re using other videocard 
Dx9 in max has a feature called “Mesh caching” which speeds up enormously the manipulation of the VIEWPORT, compared to OGL with the same card for SHADED views.
However, it doesn’t help at all (it actually slows things down by quite a lot) when modelling and changing the topology of a mesh (moving a vertex, for instance) as it has to recache (lag of half a second or so on low end cards and pcs) the geometry every time the topology changes.
I doubt Vlado hasn’t considered this already, however…
And have no clue as to how the IRMap is displayed in the viewer in terms of primitives (large vertices, polys ?)…
So in the end it might, or might not help.
Lele
since the scene shown in the imapviewer is static it should be quite easy to optimize it for speed (vertex caches/display lists or other current stuff i have no clue of
I would like to whip this thread up. Imap viewer is pretty slow on heavy imaps.
Can we expect some optimizations in the future. Or maybe a preview within the Max viewport?
The irradiance map viewer is actually quite a bit faster in newer builds.
We are trying to avoid working on anything viewport-related, until Autodesk completes the overhaul that is currently underway (XBR) 
Best regards,
Vlado
Swell! Looking forward to it