 | | Re: Mac Brick CAD and the Imerial Star Destroyer
|
|
(...) 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 (...) (22 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| |
| | Re: Mac Brick CAD and the Imerial Star Destroyer
|
|
(...) 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... (22 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| |
| | Re: Mac Brick CAD and the Imerial Star Destroyer
|
|
(...) 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 (...) (22 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| |
| | Re: Mac Brick CAD and the Imerial Star Destroyer
|
|
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 (22 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
| |
| | Re: Mac Brick CAD and the Imerial Star Destroyer
|
|
(...) 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 (...) (22 years ago, 17-May-04, to lugnet.cad.dev.mac)
|
