 | | Re: 606p01b.dat (Was: LGPL Datsville)
|
|
(...) It's in town_full.dat, right after tbfire.dat. By the file name it sounds like a "plane" for the "X" and "Z" axes. So it probably was just used for orienting other models. Would it be safe to simply replace 606p01b.dat with 606p01.dat? Mike (15 years ago, 22-Nov-09, to lugnet.cad)
|
| |
| | Re: LGPL Datsville
|
|
(...) Thanks! But, is PD compatible with a LGPL or CC project? (...) I'd like a copy. Do you have any documentation describing what you did and why you did it? Mike (15 years ago, 22-Nov-09, to lugnet.cad)
|
| |
| | Re: LGPL Datsville
|
|
(...) All models I have created for Datsville are to be treated as Public Domain. Feel free to use it, update file headers and part references, file names, file extensions etc. If anyone is interested in my work to rename, categorize, edit headers, (...) (15 years ago, 22-Nov-09, to lugnet.cad)
|
| |
| | 606p01b.dat (Was: LGPL Datsville) [DAT]
|
|
(...) Please tell me where the reference to plnxzb.dat is. (Parent file, line nr) /Tore 0 Datsville Baseplate 0 Name: 606p01b.dat 0 Author: John VanZwieten 0 Inlined:1 16 0 0 0 1 0 0 0 1 0 0 0 1 606p01.dat 0 Baseplate 32 x 32 Road Straight with Road (...) (15 years ago, 22-Nov-09, to lugnet.cad)
|
| |
| | Tmmayor.dat (Was: LGPL Datsville) [DAT]
|
|
(...) Try this one, I don't know the status for it, and it looks a little wierd, but no errors. /Tore 0 Datsville Mayor 0 Name: Mlzmayor.ldr 0 Was: Tmmayor.dat 0 Author: Leonardo Zide 0 Unofficial Datsville Minifig Model 0 Parent: Bjvthall.ldr 0 (...) (15 years ago, 22-Nov-09, to lugnet.cad)
|
| |
| | Re: LGPL Datsville
|
|
(...) Here's a link to the project's wiki: (URL) (15 years ago, 22-Nov-09, to lugnet.cad)
|
| |
| | Re: LGPL Datsville
|
|
When loading the Datsville MPD file in MLCAD, it asks for two files that I can't find anywhere. 1. plnxzb.dat 2. 606p01b.dat Anyone know where I can find these, or how to resolve the issue? It also reports an error for "tmmayor.dat", but I think I (...) (15 years ago, 22-Nov-09, to lugnet.cad)
|
| |
| | Re: LGPL Datsville
|
|
(...) Forgot to add: 1) The license for programming code (POV-Ray, etc.) is LGPL. 2) The license for content (LDraw models, etc.) is CC-BY-SA. Mike (15 years ago, 22-Nov-09, to lugnet.cad)
|
| |
| | Re: MPD header info?
|
|
(...) Thanks! Mike (15 years ago, 22-Nov-09, to lugnet.cad)
|
| |
| | Re: LGPL Datsville
|
|
(...) By searching LUGNET I was able to determine that you created a petroleum station, but I couldn't find the actual model. Could you please re-upload this file? Mike (15 years ago, 22-Nov-09, to lugnet.cad)
|
| |
| | Re: LGPL Datsville
|
|
(...) I finally got around to creating a repository. You can find it here: (URL) are only a few files in "trunk/". I need to contact all the original authors for permission to use their models. Mike (15 years ago, 22-Nov-09, to lugnet.cad)
|
| |
| | Re: MPD header info?
|
|
(...) Please have a look at the specification for MPD at (URL) you add your content before the first 0 FILE line as comments, then all should be ok also for applications using it. cu mikeheide (15 years ago, 22-Nov-09, to lugnet.cad)
|
| |
| | MPD header info?
|
|
I would like to add a header with information about myself to an MPD file. What is the best way to do this? Should I worry about possibly breaking the file and making it unusable by programs? Thanks. Mike (15 years ago, 21-Nov-09, to lugnet.cad)
|
| |
| | Re: DATHeader (The Reviewer Tool) Version 3.0
|
|
(...) I have to say it's awesome! I like the tabbed interface. We'd be kind of screwed if we didn't have DATHeader... the amount of features now contained in it makes it almost deserve a name change. :) The website is cool too, much better than the (...) (15 years ago, 21-Nov-09, to lugnet.cad)
|
| |
| | DATHeader (The Reviewer Tool) Version 3.0
|
|
Today I have finished the work on the new DATHeader version 3. There are only a few new functions build in but a major redesign of the GUI. I hope you like the changes. As my standard webspace is currently down, you can download the new version from (...) (15 years ago, 21-Nov-09, to lugnet.cad, lugnet.announce)
|
| |
| | BlockCAD moves!
|
|
As a first step in the move from my current ISP (which will discontinue personal web pages!) I have registered the domain blockcad.net. If you have saved a link to BlockCAD, please update it to www.blockcad.net (or just blockcad.net) (15 years ago, 20-Nov-09, to lugnet.cad)
|
| |
| | Re: Assembled parts, ~ and categories
|
|
(...) Maybe you are trying to interpret too much from the naming convention. A composite part (*cNN.dat) isn't necessarily comprised of parts that can move relative to each other, It might just be made of two or more separately moulded elements that (...) (15 years ago, 19-Nov-09, to lugnet.cad)
|
| |
| | Re: Assembled parts, ~ and categories
|
|
(...) I can understand the problem of aged parts, but, again from a programmer approach, I have to manage both "old" and "new" parts, so it will be very helpful if all parts can follow the same coding and naming standard. Please, consider the (...) (15 years ago, 19-Nov-09, to lugnet.cad)
|
| |
| | Re: Assembled parts, ~ and categories
|
|
(...) Working with the new version 3.1 I've announced today you'll notice that we included unhidden version of the Minifig Chain and String parts along with the LSynth constraints to work around this problem so changing the standard is no longer key (...) (15 years ago, 18-Nov-09, to lugnet.cad)
|
| |
| | Re: Assembled parts, ~ and categories
|
|
(...) Please understand that the LDraw Parts Library is over 12 years old and standards evolve over time. Things that were done in 1999, when 71427c01.dat was created, wouldn't necessarily be done the same way now. *dNN.dat files are parts with (...) (15 years ago, 18-Nov-09, to lugnet.cad)
|
