 | | Re: Mac Brick CAD and the Imerial Star Destroyer
|
|
(...) Maybe you're running into one of those weird oddities of the Apple opengl drivers. For example rendering to the GL_FRONT buffer really renders to a hidden back buffer. There are times where this setup causes you to use triple buffering, which (...) (22 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| |
| | Re: Mac Brick CAD and the Imerial Star Destroyer
|
|
(...) Travis, Generally I have to agree with you: According to the Apple literature non-OpenGL aware graphics cars (such as the Rage128) gain significant benefit from vertex arrays but with OpenGL aware graphic cards (such as the 9000Pro ) this (...) (22 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| |
| | Re: Mac Brick CAD and the Imerial Star Destroyer
|
|
(...) On my laptop with a Pentium-M 1.4GHz, 512MB RAM, ATI Mobility Radeon 9000: Timing: Load: 3325 ms Draw: 3164 ms On my desktop with a P4 3Ghz, 1GB DDR400 RAM, ATI Radeon 9800 Pro 128MB: Timing: Load: 2062 ms Draw: 1204 ms -Orion (22 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| |
| | Re: Mac Brick CAD and the Imerial Star Destroyer
|
|
(...) Since we seem to be talking about performance measurements, what do you think about comparing the the current yardstick: l3lab? On my fairly old 500Mhz PC with a TNT video card l3lab prints this for stats. Timing: Load: 1222 ms Draw: 8442 ms (...) (22 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| |
| | Re: Mac Brick CAD and the Imerial Star Destroyer
|
|
One thing I've forgotten to mention in my previous replies is that it's really unfair to compare the performance of an editor (MBC) with a viewer (LDView), even if both are running on the same machine. A viewer doesn't have to worry about adding, (...) (22 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
