 | | Re: MOC: Apollo lunar module (repost) —Jeremy H. Sproat
| | | | (...) 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) —Steve Bliss
| | | | | (...) 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) —Don Heyse
| | | | | (...) 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) —Paul Gyugyi
| | | | | (...) 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)
| | | | | | |
