 | | 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)
|
| |
| | Re: Assembled parts, ~ and categories
|
|
(...) The part you mentioned is certified a long time ago and rules changes over the time. So you will find surely old part in the library that are not according our current rules. Also the ...Cxx only advices that the real part is assembled by some (...) (15 years ago, 18-Nov-09, to lugnet.cad)
|
| |
| | Re: Assembled parts, ~ and categories
|
|
(...) Hi, I read the above article and is OK, but many parts do not follow these requirements: for example part 71427C01.DAT distributed as official is named as assembly but contains the whole part definition inside with no references to any (...) (15 years ago, 18-Nov-09, to lugnet.cad)
|
| |
| | *** LSynth 3.1 Released ***
|
|
Hi folks, Don Heyse, has asked me to announce the release of LSynth 3.1 which is now available for download from: (URL) he has done all the coding for this update. My role was nothing more than whining when things didn't work as I expected them (...) (15 years ago, 18-Nov-09, to lugnet.cad, lugnet.announce, lugnet.cad.dev.org.ldraw) !!
|
| |
| | 2009/2010 LDraw Standards Committee (LSC) Election is open
|
|
The 2009/2010 LDraw Standards Committee[1] election is now open. To vote, please visit (URL) and log in with your user account. Next, visit the ballot page on LDraw.org here: (URL) LDraw organization members may vote and you may vote for up to five (...) (15 years ago, 17-Nov-09, to lugnet.cad, lugnet.cad.dev.org.ldraw, lugnet.announce)
|
| |
| | Re: Datsville Link
|
|
(...) Maybe Google Code + Google Wave? Preferably something that won't break if the person hosting the site has a HD crash or looses his password... Plus, I already have a gmail account! :) Mike (15 years ago, 17-Nov-09, to lugnet.cad)
|
| |
| | Re: Datsville Link
|
|
(...) -Orion (15 years ago, 15-Nov-09, to lugnet.cad)
|
| |
| | Re: Datsville Link
|
|
(...) I whouldn't lose hope we can go back in time and see it all over again (URL) (15 years ago, 15-Nov-09, to lugnet.cad)
|
| |
| | Re: Datsville Link
|
|
(...) I suggested several months ago to open source it and host it on Source Forge or somewhere. I and everyone else seem to have forgotten about it though. It would still be a neat idea. Mike (15 years ago, 14-Nov-09, to lugnet.cad)
|
| |
| | Re: Assembled parts, ~ and categories
|
|
(...) Thanks for make that clear now. I have just also link this post in the wiki ((URL) so we can find it much quicker in the future. I have also put there a lot of other stuff that I feel we should keep for future use. cu mikeheide (15 years ago, 14-Nov-09, to lugnet.cad)
|
| |
| | Re: Assembled parts, ~ and categories
|
|
(...) 1) the leading ~ should be enforced for files in parts/s. 2a) a leading ~ is optional for files in parts, but should be present for physical components that are always delivered in combination with another. 2b) we need a better way to deal (...) (15 years ago, 13-Nov-09, to lugnet.cad)
|
| |
| | Re: Assembled parts, ~ and categories
|
|
(...) As I am in the beta testing for the new DATHeader I need to have decisions for the above questions. At present many of the above is mixed on the PT. cu mikeheide (15 years ago, 13-Nov-09, to lugnet.cad)
|
| |
| | Re: New parts and color definition
|
|
(...) That's nothing to do with the rendering software, it's due to overload on the webserver, causing the script that queues the rendering request to fail. I requeue them manually when I notice. Chris (15 years ago, 13-Nov-09, to lugnet.cad)
|
| |
| | Re: LPub newbie
|
|
(...) Parts.lst is crude and kind of annoying but given your desire for 'just works' (which I highly commend) could you not generate one to help other software to come a bit closer to that goal? Tim (15 years ago, 12-Nov-09, to lugnet.cad, FTX)
|
| |
| | Re: LPub newbie
|
|
(...) FWIW if you want to generate the parts.lst file yourself, the OS-X version of ldglite comes bundled with a mklist executable. If LPub needs a parts.lst file perhaps it could be bundled with mklist as well. (15 years ago, 11-Nov-09, to lugnet.cad, FTX)
|
| |
| | Re: LPub newbie
|
|
(...) Allen - Thanks for that response. So to any other newbies, I simply downloaded the latest parts update from ldraw.org, and grabbed the parts.lst file and copied into my LDRAW folder under the Bricksmith folder. After this, the per step parts (...) (15 years ago, 11-Nov-09, to lugnet.cad, FTX)
|
