 | | Re: Straightening Up the MPD Format
|
|
(...) Then the problem is at MPDCenter. 0 Name is a very good and recommended habit, but not currently required. But I have thought of using 0 Name to solve this problem. When exploding an MPD, the user may be prompted to either use the unique 0 (...) (15 years ago, 2-Apr-10, to lugnet.cad)
|
| |
| | List / Poll of MPD Programs
|
|
Here is a list of programs I've found for PC (Win/DOS only) to handle/create/manipulate MPD files. (I have omitted all those viewers that just support reading MPD files at this stage.) * Which ones have I forgot? * Which one do you prefer/recommend, (...) (15 years ago, 2-Apr-10, to lugnet.cad)
|
| |
| | Re: Straightening Up the MPF Format
|
|
(...) [snip] (...) Related although not the same. I like to use MPDWizard to make sure all part files I use are available in the same version I used (in case any unofficial parts are used) but this has the rather nasty side-effect that these part (...) (15 years ago, 2-Apr-10, to lugnet.cad)
|
| |
| | Re: Straightening Up the MPD Format
|
|
(...) You might want to consider offering Philo's subdirectory approach as an alternative to name mangling. Model1.ldr Model1\File1.ldr Model1\File2.ldr Model2.ldr Model2\File1.ldr Model2\File2.ldr Will be combined into Model3.ldr Model1\File1.ldr (...) (15 years ago, 2-Apr-10, to lugnet.cad)
|
| |
| | Re: Straightening Up the MPD Format
|
|
(...) O NAME is not required for ordinary ldraw files, only official library parts. The only Meta command needed to assemble an mpd file is 0 FILE, so the mpd file from LeoCAD is fine as is. Don (15 years ago, 2-Apr-10, to lugnet.cad)
|
