GregHess
08-02-2003, 01:34 AM
A fellow discreet user (sergio) discovered a rather large bug with the current FireGL drivers with Max6 at siggraph.
I'm sure that since max6 isn't shipping yet, that this will most likely be addressed by the time it finally ships.
But I felt I should mention it just the same...to let anyone planning on upgrading to either a new system, or max6 understand a particular issue with this combination of hardware.
If your working on a rather complex character rig, and you go to modify the envelopes on said character...the FireGL X1 dies. I mean it chugs all to hell. It becomes completely unusable.
I mirrored this effect on other machines running both max6 and a variety of FireGL's.
Basically FPS went from the upper 100's, to below 1. (If you panned the viewport, you actually had to wait for it to figure out what was going on, before it would display the data).
This bug does NOT occur on nvidia quadro FX's. Performance is still reduced (when compared to not being in envelope mode) but its still usable.
I'm preparing a bug report to send to ATI so they'll hopefully address this issue.
What could be causing it?
1) Max6's current build.
2) The fact that everyone was trying to show off nifty little Dx8/9 shaders in the viewports (thus forcing D3D instead of OGL).
3) The FireGL drivers were beta's.
I'm sure that since max6 isn't shipping yet, that this will most likely be addressed by the time it finally ships.
But I felt I should mention it just the same...to let anyone planning on upgrading to either a new system, or max6 understand a particular issue with this combination of hardware.
If your working on a rather complex character rig, and you go to modify the envelopes on said character...the FireGL X1 dies. I mean it chugs all to hell. It becomes completely unusable.
I mirrored this effect on other machines running both max6 and a variety of FireGL's.
Basically FPS went from the upper 100's, to below 1. (If you panned the viewport, you actually had to wait for it to figure out what was going on, before it would display the data).
This bug does NOT occur on nvidia quadro FX's. Performance is still reduced (when compared to not being in envelope mode) but its still usable.
I'm preparing a bug report to send to ATI so they'll hopefully address this issue.
What could be causing it?
1) Max6's current build.
2) The fact that everyone was trying to show off nifty little Dx8/9 shaders in the viewports (thus forcing D3D instead of OGL).
3) The FireGL drivers were beta's.