 | | Mac Brick CAD and the Imerial Star Destroyer —Andrew Allan
|
| | | Following the comments by James with Orion Pobursky's version of 10030 (Imperial Star Destroyer), I took a look at the file. In it's original form there was 3 problems: 1. MBC is case sensitive when referencing sub-models (don't know if this is good (...) (20 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| | | |
| | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Tom Bozzo
|
| | | | | (...) Thanks for the MBC update! PowerBook G4, 400MHz, 512MB RAM, IBM TravelStar 40GN 40GB HD (4200 RPM), OS X 10.3.3 (build 7F44), 8MB Rage128. I don't have the .mpd extension mapped to MBC, so I dropped the Star Destroyer MPD on the MBC app. Timed (...) (20 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| | | | | |
| | | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Andrew Allan
|
| | | | | | (...) I'm aware of this and you'll find that when you save and re-open the file, MBC will have truncated these very small numbers to 0, this code should however one day be incorporated into the rotation routines. Andrew... (20 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| | | | | | |
| | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Travis Cobbs
|
| | | | Just out of curiosity, do you cache pieces once they have been loaded, so they only get loaded once? If not, you can speed things up rather enormously by doing so. --Travis Cobbs (20 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| | | | |
| | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Andrew Allan
|
| | | | (...) Yes, When loading I make a list of all the unique bricks in the model (colour and type) these are then cached as OpenGL lists of so when drawing, I then just call the various OpenGL lists. For the imperial star destroyer, this means even a (...) (20 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| | | | |
| | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Travis Cobbs
|
| | | | | (...) I have a few comments--based on my experience writing LDView--that I think could improve your load performance. First of all, I believe what you are saying above (and a little later in your post) is that you only cache complete bricks. If this (...) (20 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| | | | | |
| | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Travis Cobbs
|
| | | | | (...) Your expectation is certainly justified. I don't know what the driver architecture is on the Mac, but I suspect that the video hardware manufacturers are responsible for the OpenGL implementation for their own hardware, just like on the PC. If (...) (20 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| | | | | |
| | | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Andrew Allan
|
| | | | | | (...) Travis Having done some experiments and research over the last couple of days, it seems that to get very fast drawing in OpenGL generally, vertex arrays are necessary. OpenGL has specific commands such as glBufferDataARB that will explicitly (...) (20 years ago, 20-May-04, to lugnet.cad.dev.mac)
|
| | | | | | |
| | | | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Travis Cobbs
|
| | | | | | (...) Just as a note, I found that Vertex Buffer Objects (VBOs) would crash my ATI card in Windows when used inside a display list. As far as I can tell, this isn't supposed to happen. Regular vertex arrays work fine inside a display list. General (...) (20 years ago, 21-May-04, to lugnet.cad.dev.mac)
|
| | | | | | |
| | | | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Don Heyse
|
| | | | | | (...) Yeah, watch out for that software rendering on the Mac. It sneeks up on you. I know it can switch you over while your program is running, but I don't know what causes it to happen other than resizing a window. You might want to query it about (...) (20 years ago, 21-May-04, to lugnet.cad.dev.mac)
|
| | | | | | |
| | | | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Travis Cobbs
|
| | | | | | (...) Actually, the same thing can happen in Windows if you resize a window too big (say 1600x1200) on an older video card. However, I'm not sure you can tell that it has switched to software mode on Windows, because as far as I know it is still (...) (20 years ago, 21-May-04, to lugnet.cad.dev.mac)
|
| | | | | | |
| | | | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Christopher Masi
|
| | | | | | (...) I think this is what Don is refering to. Using Don's ldgliteargs to 800x537 on my aging 8 MB VRAM machine so ldglite would launch using the ATi renderer. GL_VENDOR ='ATI Technologies Inc.' GL_RENDERER ='ATi Rage 128 Pro OpenGL Engine' (...) (20 years ago, 25-May-04, to lugnet.cad.dev.mac)
|
| | | | | | |
| | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Travis Cobbs
|
| | | | 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, (...) (20 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| | | | |
| | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Don Heyse
|
| | | | | (...) 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 (...) (20 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| | | | | |
| | | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Orion Pobursky
|
| | | | | | (...) 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 (20 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| | | | | | |
| | | | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Travis Cobbs
|
| | | | | | (...) Well, for what it's worth, here are my numbers on a P4 2.4GHz, ATI 9700 Pro 128MB: Load: 3437 ms Draw: 1907 ms It's worth noting that if I load the file a second time, the load portion drops to 313 ms, so the only way to be sure that disk (...) (20 years ago, 18-May-04, to lugnet.cad.dev.mac)
|
| | | | | | |
| | | | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Don Heyse
|
| | | | | | (...) Ah, that explains my mysteriously low load time. I did the measurement on the 2nd try. So, I'd say anything drawing in the fps range is certainly getting some benefit from the opengl acceleration. Don (20 years ago, 18-May-04, to lugnet.cad.dev.mac)
|
| | | | | | |
| | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Andrew Allan
|
| | | | (...) 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 (...) (20 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| | | | |
| | | | | | Re: Mac Brick CAD and the Imerial Star Destroyer —Don Heyse
|
| | | | (...) 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 (...) (20 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| | | | |
