Hi,

I've started adding a list of third part software to the website:

http://www.ldraw.org/downloads-2/third-p...tware.html

I case your interested seeing your prog on the list just send an entry following to pattern below:

• Forum and Flickr feed on home page broken.
  

Main site is back and operational. Please report any issues via the Website Suggestions forums.

-Orion

Over the years different programmers have added a snapping feature to their programs. This thread aims to work out a standard which they can adopted or modified to their needs.

Some theoretical work has already been done, see:

http://sourceforge.net/projects/jbrickbu...f/download

http://www.melkert.net/LDCad/tech/meta

Placeholder for Bricksmith

http://sr3dbuilder.altervista.org/TechnicalIssues.html
http://forums.ldraw.org/showthread.php?t...84#pid8184

Keep up the good work!

w.

Dear friends,

due to other things which I have to do and I just do in my free-time [ I play the Cello for about one year... ], I intend to make a little LDraw development break for about a month, but I will still read the forums from time to time.
Just for your information!

Cheers & leg godt

Nils

• First question is how translate length from Z axis to physical metric.
  
• Second question is when you have LDU how get width and height in physical metric.
  
• I know about LDCalc but we work in this scenario with 3D without scaling and without transformation.
  

Hope this is OK to post here, if not my apologies.

Here is a thread for LEGO parts that you wish existed, but don't currently.
Please feel free to post DAT files, or if you don't have skill with LDraw then you can post images instead.

My first submission is a 1X1 pyramid sloped at 75 degrees (I think that was the angle)


It does look like LEGO will be coming out with a somewhat similar piece though sloped at 31 degrees.

Attached Files

Thumbnail(s)
   

  pyramid.dat (Size: 982 bytes / Downloads: 18)

Hello

I hope that anyone of you has imitation the part 6797 for MLCAD.
Need it for the McLaren P1 as exhaust.

Partname: Technic Engine Air Scoop 4 x 4 x 1 1/3

Can you help me there?

So in working on adding some part snapping info I've got some questions about guidelines. Maybe it's the perfectionist in me and I'm over thinking this, but I'm not sure about the "correct" way to add snapping meta to a couple parts I've run across. I'm also pretty new to all this, so maybe it's spelled out somewhere else and I just haven't run across it yet. Anyway, two examples below with questions about how to "correctly" add the snap meta.

First Example:

   

Above is Part 60849, Minifig Hose Nozzle with Side String Hole Simplified. For this piece, it would make sense to stop a piece from sliding past the trigger on the nozzle and the handle, highlighted in green in the picture on the left. However, if you configure it this way and as you can see in the middle picture, the red area has no snap meta and parts will not snap to that area. Clips should, however, be able to snap to the red area. If I modify the part to allow clips to snap to the red area, then that allows parts to slide past the handle and end up in an "illegal" (overlapping) position, as in the picture on the right.

Second Example:

   

Same as the first example, but with part 3959, Minifig Torch. If you want to prevent pieces from sliding past the handle, as in the top set of pics, you'll end up with an area (see red square on second row) where there's no snap meta and pieces (clips) will not snap to that location. However, clips should be able to snap to the red area.

Also, as you can see in the bottom set of pictures, depending on the piece, one could end up colliding with the nozzle and end up in an overlap position.

So, my questions...

It would seem that in order to get clips to snap in the red area you would also have to allow pieces to end up in positions where they overlap. Same goes for allowing all parts to travel the full distance of the handle in the second example. Is this how it should be done (i.e. allow overlap)? Or, is there a way to add meta to allow all of these combinations without allowing overlap? Are there any guidelines I should be following in situations like this? Am I over thinking this?

The 2015-01 LDraw Parts Update has been now been released. This adds 502 new files to the core library, including 338 new parts and 34 new primitives. This update includes an unusually large, but welcome, proportion of improved and corrected parts. This is largely due to the work of Roland Melkert with the 'libfix version' of LDCad. Significant effort has also been expended by Magnus Forsberg to inline dithered colour subfiles (a now obsolete technique). Most of the obsoleted subfiles will be released in a future update.

Thanks are once again due to all the part authors who created or corrected parts for this release. The reviewers also play an important role in keeping files moving through the tracker and deserve just as much credit. Whilst I can see the attraction of working on new parts, it is slightly disappointing to me that the number of parts held for further work is not decreasing.

With the main LDraw website currently out of commission, you can preview the new parts in 2015-01 here, download the zip-file update here or download the Windows install package here. Alternatively you can use the LDView menu option File | Check for Library Updates... to install the update.

Once again, no new "Physical colour" parts are included in this update as we still intend to move these to a separate section of the LDraw file structure, to more closely fit with the "DesignID" vs. "ItemID" concept. A number of such parts on the Parts Tracker are awaiting admin review, but will not be released until this concept has been implemented. I am conscious that support for texture maps also needs to be added to the Parts Tracker and have that on my to-do list.

This update has only just kept pace with the number of new files submitted since Parts Update 2014-02 was released in December 2014. I'd like to repeat my appeal for authors and reviewers to try and reduce the backlog of held or insufficiently reviewed parts. Let's see if we can certify enough of these for the traditional end-of-year holiday season update.