 | | Re: MOC: Apollo lunar module (repost)
|
|
(...) For viewing the model as a whole I'd recommend l3lab (it's fast and it works), and of course for everything else ML-CAD (assuming you have a windows machine). WRT to my L3PAO problem, I just installed the up to date versions of everything I (...) (25 years ago, 27-Apr-00, to lugnet.cad.dat.models)
|
| |
| | Re: MOC: Apollo lunar module (repost)
|
|
(...) Hmmm. I wonder why L3Lab works where LDLite breaks. Cheers, - jsproat (25 years ago, 27-Apr-00, to lugnet.cad.dev)
|
| |
| | Re: MOC: Apollo lunar module (repost)
|
|
(...) I've tried with the current version and I get the same result. If I remove the the piece at which LDLite stops (a 3024, plate 1x1), it jumps to the next submodel (the ascent stage) and renders this, but only to a certain point also. No matter (...) (25 years ago, 27-Apr-00, to lugnet.cad.dat.models)
|
| |
| | Re: MOC: Apollo lunar module (repost)
|
|
(...) I've tried with the current version and I get the same result. If I remove the the piece at which LDLite stops (a 3024, plate 1x1), it jumps to the next submodel (the ascent stage) and renders this, but only to a certain point also. No matter (...) (25 years ago, 27-Apr-00, to lugnet.cad.dat.models)
|
| |
| | Re: MOC: Apollo lunar module (repost)
|
|
(...) LDLite has always been slightly flakey on MPD files. I think v1.6 is better than v1.5, but I'm not in a position to make absolute statements--I use L3Lab these days. Steve (25 years ago, 27-Apr-00, to lugnet.cad.dev)
|
| |
| | LDLITE cache limit bug (Was Apollo lunar module)
|
|
(...) at (...) works), (...) Yeah, this is a caching bug in the ldlite parser. I get the same problem in ldglite when I use the ldlite parser, but not with the L3 parser. I think it's because one of the caching structures is full before it gets (...) (25 years ago, 27-Apr-00, to lugnet.cad.dev)
|
| |
| | Re: LDLITE cache limit bug (Was Apollo lunar module)
|
|
(...) Heh, um, I also use L3Lab nowadays, actually. :) LDLite v1.6 is better than 1.5 at MPD files. (...) [...] (...) You did it the right way. Actually, the log output should show warnings about files not being cached, although it does not mention (...) (25 years ago, 28-Apr-00, to lugnet.cad.dev)
|
