 | | Re: Animation using Datsville —Michael Horvath
|
| | | Also, it would be nice if LDBoxer could replace bricks that have only their bottoms or only their tops covered, as opposed to replacing only those bricks that have both their bottoms and their tops covered. This, however, would necessitate the (...) (21 years ago, 5-Mar-04, to lugnet.cad.ray)
|
| | | |
| | | | | Re: Animation using Datsville —Tore Eriksson
|
| | | | (...) I've been doing some experiments with different variants of LDBoxer, and also a hing called LDFilTEr. There is a semi-automatic version of LDBoxer where you can pick parts one by one and the interface lets you filter out parts irrelevant for (...) (21 years ago, 5-Mar-04, to lugnet.cad.ray)
|
| | | | |
| | | | | | Re: Animation using Datsville —Orion Pobursky
|
| | | | | (...) Not that I'm aware of (...) I have MPD files of the individual town sections (i.e. Town02, Town10, etc) that have been run through LDBoxer. I can't send them to you if you'd like and then you could just Un-MPD them for the individual files. (...) (21 years ago, 5-Mar-04, to lugnet.cad.ray)
|
| | | | | |
| | | | | | | Re: Animation using Datsville —Orion Pobursky
|
| | | | | | | (...) Typo in the above message. Change "can't" to "can". -Orion (21 years ago, 5-Mar-04, to lugnet.cad.ray)
|
| | | | | | | |
| | | | | | | Re: Animation using Datsville —Tore Eriksson
|
| | | | | | (...) Well, I've found one at: (URL) it's from Sept. 2001, and I don't even remember how to use it. (...) Yes please! I would be very happy if you did this. (I've added the exception keyword "Datsville" to my (very conservative) spam filter, so it (...) (21 years ago, 5-Mar-04, to lugnet.cad.ray)
|
| | | | | | |
| | | | | | | | Re: Animation using Datsville —Orion Pobursky
|
| | | | | | (...) 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 —Tore Eriksson
|
| | | | | | (...) 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 —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)
|
| | | | | | |
| | | | | | Re: Animation using Datsville —Michael Horvath
|
| | | | (...) What I meant was that this should be done by POVray within the .pov file, not in the the .ldr file. It is my understanding that one can put ifpov & ifnotpov statements into an .ldr file. They are, however, intended to be used solely by POVray. (...) (21 years ago, 6-Mar-04, to lugnet.cad.ray)
|
| | | | |
| | | | | | Re: Animation using Datsville —Michael Horvath
|
| | | | | (...) On second thought, this would be a bad idea, because objects outside the view cone could affect things, like reflections, shadows, and fog (important!!!). (21 years ago, 6-Mar-04, to lugnet.cad.ray)
|
| | | | | |
| | | | | | Re: Animation using Datsville —Michael Horvath
|
| | | | (...) I wasn't able to pull it off. The ifpov and ifnotpov insert their own if/else statements into the .pov file, itself. They break the if/else statements that I'm trying to create. (21 years ago, 10-Mar-04, to lugnet.cad.ray)
|
| | | | |
