Topic for the Space / Blacktron II theme.

I am building a big thing (that I cannot show) in tan on a green baseplate. I set the fade color to dark tan.
The thing is that it being a mono color model the fade color option is needed to clearify the new pieces.
However, the baseplate must remain green, because it is very ugly to see that in dark tan too in every next step after the first.
So I used a buffer exchange in every step that simply removes the baseplate and adds a new instance of the baseplate so it is not faded.

Then the fade color does something strange: the first new brick in line right after the STEP command is faded too.
Is this a know problem? Examples attached.

Attached Files

Thumbnail(s)
   

  fadetest.ldr (Size: 765 bytes / Downloads: 0)

Topic for the Space / Blacktron I theme.

10212 UCS Imperial Shuttle [Star Wars]



Download MPD-file (OMR compliant)
Done with LDCad 1.5 Beta 2a

Errors:
- no stickers
- wrong patterned parts (cockpit, minifigs)

The mpd-file contains 114 submodels, 5 minifigs and 628 steps.

According to the instructions, this model is in a “certain kind of disorder”. Usually the main model grows step by step by adding submodels to the main model. For the 10212 set this is kind of different. The main model switches from time to time: A new submodel is built and then the supposed main model is added to this new submodel. So the submodel gets the new main model. Usually it’s vice versa.

Hello,

here is a new bugfix for LDPatternCreator with one new feature!

Download and install the latest LDPatternCreator release directly from sourceforge.net.

Change log:

New feature:

• You can now choose wether to use pattern slicing or not (SlicerPro post processing, default setting is not to slice)
  

• Fixed a little memory leak
  
• The post processing info was not stored correctly (Rectifier, Unificator, ...)
  
• Fixed possible dirty filename and path settings for "Open File" and "Save File As"
  
• The LPC-Unificator could crash if the metadata contained linetypes 2 and/or 5
  

Do any of you have the new WeDo 2.0 set?
I'd love to have LDraw files for the new electronics. (All the other elements appear to be in the LDraw tracker already)

Particularly I'm interested in the 19071 hub and the 21980 motor (the motor is very similar to the PF M motor, but it only has 3 pin holes at the front and 4 studs at the top).

Much less important are the other elements:
20841tilt sensor
20844 motion sensor

As far as I can tell those are identical to the sensors from WeDo 1. However, these elements also use new cables (6 wires) and connectors.

While I am learning LDCad, I am making various official models.
Here I will post the Microtechic models.
http://brickset.com/sets/theme-Technic/s...crotechnic

Hi folks,

Sorry to have been of the radar a bit now that we really got things going discussing LPub3D, LDCad and all interesting stuff.
I've been a bit busy with other stuff then LEGO and LDraw... :-(

However, I got around again practicing LDCad an decided to try to model this cute little technic set:
http://brickset.com/sets/8203-1/Rover-Discovery
It has a rubber band rather typically shaped by the way it is in the model.
I tried to model this band like it would fit the model (not the way I want exactly yet).
See this screencapture video: https://www.youtube.com/watch?v=wo_lp3S9NrA
It looks nice but when I save the file, close it and re-open it, the band is totally messed up.
Doing some work on it again to get it a bit like the way it was, saving, closing and re-opening it even messes up further.

How can I solve that?
Is this the same issue that I had with the small minifig chain assembly I posted before? Is the band simply to small to calculate?

Then: how do I create a rubber band that mimics this band the way it is in the model?

Thanks.

Mike,

when Datheader downloads the category.txt, ldconfig.ldr, primitivescale.txt files it will download them to prog folder and obviously they end up under:

C:\Users\<username>\AppData\Local\VirtualStore

could you please look into it.

Thx, w.

Hi,

had anyone running LDCalc successfully under Windows 10. Tried tweak compatibility, rights, turned of antivirus, created a fake LDCalcIni.xml ... no chance.

Do I need some special runtimes?

w.