 | | Re: New LDConfig.ldr color file
|
|
(...) I have a few comments here. First of all, if you're going to load a huge model in LDView, it's usually best to set its "Memory Usage" setting to Low (especially on old hardware). Secondly, as has been pointed out, LDView takes a lot longer to (...) (15 years ago, 11-Aug-09, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) Did you have any suggestions for him? I did not, other than that he does not have his paths set up correctly (which was already mentioned). I do not even have LPub 2 installed anywhere anymore. Do you? If so, maybe you could help him. I'd (...) (15 years ago, 11-Aug-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) That is not correct. The 1.8 sec are the drawing time. If you will have a look into 'statistics' you will see that most of the time the loading will take and then 1.8 sec. for the drawing is used. So this comparison is not correct, but you are (...) (15 years ago, 11-Aug-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) That is just so not true. (...) Well then, welcome to my reality. Viewing just a small portion of Datsville on my AMD1100, for example TOWN-10.ldr, takes 1.8 seconds in L3Lab. But several minutes in LDView - if it doesn't crash. I am (...) (15 years ago, 11-Aug-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New LDConfig.ldr color file
|
|
(...) So far we have much more TLC color numbers than in LDraw (Bricklink) with TLC apparently not going further than 300. Therefore a numbering starting with 3000 would be fine. w. (15 years ago, 7-Aug-09, to lugnet.cad.dev.org.ldraw)
|
