 | | Re: is leocad not developed any more?
|
|
(...) Well, the last message from Leonardo Zide (the developer) is from January. There hasn't been an update for over a year so it looks like it. I think he's simplt too busy on the moment......... Fortunately some other people 'do' the part updates (...) (20 years ago, 3-Aug-04, to lugnet.cad.leocad)
|
| |
| | Re: Brick 1x1 [DAT]
|
|
I think the other explanations have been very good, but if you're still having a hard time visualizing it, take a look at the attached DAT. I color coded the pieces, and exploded it a little. --Travis 0 Brick 1 x 1 exploded 0 Name: 3005-explode.dat (...) (20 years ago, 3-Aug-04, to lugnet.cad.dat.parts)
|
| |
| | Re: I have an idea . What if we make a game
|
|
I made a screenshot of the gui for the game I need help as I don't know how to do it most of it mainly the internet parts (URL) (20 years ago, 3-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Brick 1x1
|
|
(...) Have a look at my Basic Parts Authoring presentation I made up for Brickfest PDX. You can find it here: (URL) under the Parts Authoring section. -Orion (20 years ago, 3-Aug-04, to lugnet.cad.dat.parts)
|
| |
| | Re: Brick 1x1
|
|
(...) The box5.dat files are something we call primitives. A primitive is a assembly of more basic forms, for instance planes and lines, and a dat file in itself. They have been made avaibable to prevent you have to define certain very common and (...) (20 years ago, 3-Aug-04, to lugnet.cad.dat.parts)
|
| |
| | Brick 1x1
|
|
Hello. I'm trying to understand how the 1x1 brick (3005.dat) is drawn. It contains 1 stud.dat two box5.dat (I have not really found out what that is yet), and it contains 4 Quadrilateral commands. The thing right now is how the quadrilateral things (...) (20 years ago, 3-Aug-04, to lugnet.cad.dat.parts)
|
| |
| | Re: Status of BFC
|
|
(...) Some part authors have been making major advances in getting the official library BFC compliant - notably Guy Vivan has been submitting BFCed files almost daily in recent months. These revised parts are in the Parts Tracker waiting for review. (...) (20 years ago, 3-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: complete parts package?
|
|
(...) Yes, part of the reason for the recent license discussion is the combining of the 2 distros into one. -Orion (20 years ago, 2-Aug-04, to lugnet.cad.dat.parts)
|
| |
| | Re: Status of BFC
|
|
(...) I'll be supporting it in the next major LDView version (3.0). I really don't have an estimated completion date for this at the moment, but I at least hope to have it out before the end of the year. There could be minor LDView updates before (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: complete parts package?
|
|
(...) Note that this is due to license constraints. I believe removal of this requirement is being worked on by either the SteerCo, the LSC, or both. --Travis (20 years ago, 2-Aug-04, to lugnet.cad.dat.parts)
|
| |
| | Re: Status of BFC
|
|
(...) Yes it will... Once all the parts in the library are made BFC complient. (...) Since it's not full implemented library wide, most tools haven't been able to take full advantage of the benefit of consistant winding. POV-Ray is a ray tracer as (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: complete parts package?
|
|
(...) There is. It can be found here: (URL) think it's also mentioned on one of the getting started pages. Note that this file is to be used in conjunction with the 0.27 release. In other words, in order to have the full library you must install (...) (20 years ago, 2-Aug-04, to lugnet.cad.dat.parts)
|
| |
| | is leocad not developed any more?
|
|
does anyone know? (20 years ago, 2-Aug-04, to lugnet.cad.leocad)
|
| |
| | complete parts package?
|
|
Why isn't there an complete uptodate package with all the parts? I think that would be nice to have instead of downloading the patches with updates when you are a new user. (20 years ago, 2-Aug-04, to lugnet.cad.dat.parts)
|
| |
| | Status of BFC
|
|
Hi there. I just found this about BFC. As I understand it, it's intended to be used to reduce the amount of polygons etc. in the modell that is renderd, in some way? If I've understood this correctly, is thisthen used in any current tools for (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) I tend to agree with your thought, and I'm going to switch the script over to a flat-list model. Although I think the hierarchy of release -> distr type -> file format makes the most sense; and (somewhat) addresses your earlier question about (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) I actually considered that when you made your original post. However, there are actually multiple different perfectly valid heirarchies, and for this reason I think the flat list is better overall. Here's an example with a different (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) Looking at this some more... The script currently returns XML with 3 lists of distribution files: BASE - file ZIP - file ARJ COMPLETE - file ZIP - file ARJ UPDATE - file ZIP - file ARJ - file ZIP - file ARJ - file ZIP ... It could be argued (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) Thanks, Chris! I'll add this shortly. Steve (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Licensing Update
|
|
(...) As long as the authors realise that it's not just ldraw.org getting the rights (it's the public as well). (...) I think having these notes available to people as they upload their parts is a good idea. Sort of like 'This is the license your (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev.org.ldraw)
|
