 | | Re: What'd Datsville look like?
|
|
(...) On the two "newer" (well...) versions of LDBoxer, I've abandoned the *.box extension and instead I use Parts\B\*.dat for boxed versions. Have you tried them yet? Maybe they don't have the same memory limits? I think I changed from Memo to (...) (21 years ago, 30-Jun-03, to lugnet.cad, lugnet.cad.dat.models)
|
| |
| | Re: What'd Datsville look like?
|
|
(...) rev017 available at: (URL) I've lost track of the changes. As usual. :( Documentation is not my strongest side. Keep rev014 in case 017 has errors. /Tore (21 years ago, 30-Jun-03, to lugnet.cad, lugnet.cad.dat.models)
|
| |
| | Re: What'd Datsville look like?
|
|
(...) The next major revision of LDView is far enough along to render Datsville. (The current version will crash no matter what your hardware is, while the new version seems to only use around 170MB of RAM to display Datsville.) It doesn't do so at (...) (21 years ago, 30-Jun-03, to lugnet.cad, lugnet.cad.dat.models)
|
| |
| | Re: What'd Datsville look like?
|
|
Looks great! BTW, if anyone's interested, I used LDBoxer to convert the bricks in Datsville to boxes. This speeds up considerably. It's available at my LDraw page - (URL) LDBoxer I was able to render sections of Datsville in LDView at 6-15fps! There (...) (21 years ago, 29-Jun-03, to lugnet.cad, lugnet.cad.dat.models)
|
| |
| | What'd Datsville look like?
|
|
About a year ago I read a post asking what Datsville looked like since the pictures on the Lugnet webpage are broken links. This inspired me to see if I could render Datsville on my competer. I ran rev014 through L3P and it spit back a 12MB (!) (...) (21 years ago, 29-Jun-03, to lugnet.cad, lugnet.cad.dat.models, FTX) !
|
