To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cadOpen lugnet.cad in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / 5427
5426  |  5428
Subject: 
Re: On the difficulty of making building instructions
Newsgroups: 
lugnet.cad
Date: 
Fri, 9 Feb 2001 08:20:27 GMT
Highlighted: 
(details)
Viewed: 
544 times
  
In lugnet.cad, Don Heyse wrote:


This lead me to lie sleepless most of the night trying to
figure out how to solve this problem. So far I have come to the
conclusion that our problem is that we attempt to _draw_
instead of _build_ - we move the parts around until the drawing
looks right, whereas we with the real thing have the benefit of
connecting the parts to each other.

I think you've got it just right with this, Jacob.

Back when I worked in a certain 2D CAD industry we used a simple
mechanism that allowed the user to propel an object along a 2D vector
until it hit another object.  At that point it would either stop or
continue moving along a different vector as long as the dot product of
the new and original vectors was positive.  Various options could be
applied to this motion such as stopping at the first point of contact,
wiggling a bit for a better fit, or snapping to a grid (think stud
spacing).  Unfortunately I have no idea as yet how to easily generate
a 3D vector (rather than a 2D vector) to propel a brick along.
Perhaps with a spaceball instead of a mouse?

One problem with LEGO is that people want to build by "clicking" pieces
into place.  Putting two bricks side by side doesn't count as building a
model.

So collision detection is just a first step.  But a very important step.

What we really need is a way to mark up the part files with connection
information.  Like Koen pointed out, this can be done (somewhat or fairly
well) by using the stud*.dat files as the connection points.  But LEGO
pieces can be connected in a fair number of different ways.  So maybe we
need special notation for connection points?

In my mind, recording connection information is one big reason to develop a
special LDraw II language, rather than reusing an existing GDL for a new
parts library.

Steve



Message is in Reply To:
  Re: On the difficulty of making building instructions
 
(...) BlockCad (and perhaps other programs) does some collision detection when moving the bricks to assist in the placement. You could enhance this by inventing a mouse that provides some tactile feedback (ala playstation controllers) when the (...) (24 years ago, 7-Feb-01, to lugnet.cad)

7 Messages in This Thread:





Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR