 | | Re: Animation using Datsville
|
|
(...) All I did was MPD the Town sections and then ran the MPDs through LDBoxer. I tried to run an MPD of the entire Town.ldr file but it was really slow and LDBoxer exited with a access violation. -Orion (21 years ago, 5-Mar-04, to lugnet.cad.ray)
|
| |
| | Re: Animation using Datsville
|
|
(...) Sorry, LDBoxer does not "unpack" and re-parse MPDs. Therefor, the output will not be trustworthy. Someday I may be able to make programs that can handle MPDs correctly... :/ (...) I can understand that. The entire Town.ldr is an extreme task. (...) (21 years ago, 5-Mar-04, to lugnet.cad.ray)
|
| |
| | Re: Animation using Datsville
|
|
(...) It worked fine for me. But then, I had to split it up into sections, just like Orion did. (21 years ago, 6-Mar-04, to lugnet.cad.ray)
|
| |
| | Re: Animation using Datsville
|
|
(...) It's not exactly surprising that it worked ok, but if he didn't include any MPD support, then the results aren't necessarily correct. Since he presumably only pays attention to the locations of parts that he's willing to box, the references to (...) (21 years ago, 6-Mar-04, to lugnet.cad.ray)
|
| |
| | Re: Animation using Datsville
|
|
(...) True, but that would be an example of sloppy modeling on the part of the author ;) . (21 years ago, 6-Mar-04, to lugnet.cad.ray)
|
| |
| | Re: Animation using Datsville
|
|
(...) I know you're being tongue-in-cheek, but what it sounds like you are saying couldn't be further from the truth. I suspect it is due to your misinterpreting what I was trying to say. Given that it isn't exactly a trivial thing, that's not too (...) (21 years ago, 7-Mar-04, to lugnet.cad.ray)
|
| |
| | Re: Animation using Datsville
|
|
(...) Oh. I thought you were talking about overlapping walls. I also just remembered that I had used an earlier version of LDBoxer, that replaced bricks regardless of position, to convert Datsville. (21 years ago, 7-Mar-04, to lugnet.cad.ray)
|
