 | | Re: Animation using Datsville —Michael Horvath
|
| | | (...) 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 —Travis Cobbs
|
| | | | (...) 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 —Michael Horvath
|
| | | | (...) 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 —Travis Cobbs
|
| | | | (...) 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 —Michael Horvath
|
| | | | (...) 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)
|
| | | | |
