LDD 4.3.6 bugs

[Calabar]

The page you linked above reports: "Alternate Item No: 6143, 6116"

Maybe there are little differences due to plastic or minimal particulars that don't compromise brick's functionality.

[Classicsmiley]

If you look at the Bricklink page, you'll see the alternate design ID's for that piece. They've updated the mold over the years. Bricklink keeps using the first design ID that was entered, and LDD uses the most recent ID for the opaque version. If you check Brickset, you'll see that there's also a design ID for the transparent version of the part.

http://www.brickset.com/ajax/getParts.aspx?Design=6116&aid=hsi6116

http://www.brickset.com/ajax/getParts.aspx?Design=6143&aid=hsi6143

In short, the design ID in LDD is not a bug.

[___]

The page you linked above reports: "Alternate Item No: 6143, 6116"

Maybe there are little differences due to plastic or minimal particulars that don't compromise brick's functionality.

If you look at the Bricklink page, you'll see the alternate design ID's for that piece. They've updated the mold over the years. Bricklink keeps using the first design ID that was entered, and LDD uses the most recent ID for the opaque version. If you check Brickset, you'll see that there's also a design ID for the transparent version of the part.

http://www.brickset....116&aid=hsi6116

http://www.brickset....143&aid=hsi6143

In short, the design ID in LDD is not a bug.

Oh, sorry for that - my fault, it looks like I am too quick even for my own brain or something

Edited June 11, 2013 by bublible

[Superkalle]

Oh, sorry for that - my fault, it looks like I am too quick even for my own brain or something

You are singled handely increasing the traffic to the Digital Designer forum by 50%

[legolijntje]

There is nothing wrong with that. If you look at the page linked by you, you can see on the left "Alternate Item No:" which lists the (if available) alternate item numbers. You can see there that 6143 is one of them

[___]

You are singled handely increasing the traffic to the Digital Designer forum by 50%

well, what to say...

There is nothing wrong with that. If you look at the page linked by you, you can see on the left "Alternate Item No:" which lists the (if available) alternate item numbers. You can see there that 6143 is one of them

OK, sorry once again for that

[Hinckley]

I'm on a MAC and can't save over a file. It crashes every time. If I try to open a file I saved at work and save it on my MAC, it crashes. Has this bug been reported anywhere? Anyone know what I can do to fix it?

[legolijntje]

OK, sorry once again for that

Well, I thought nobody had replied yet, but for some strange reason the last page didn't show up on my pc.

[___]

Well, I thought nobody had replied yet, but for some strange reason the last page didn't show up on my pc.

no problem

[Aanchir]

I'm on a MAC and can't save over a file. It crashes every time. If I try to open a file I saved at work and save it on my MAC, it crashes. Has this bug been reported anywhere? Anyone know what I can do to fix it?

My MacBook Pro doesn't have that problem. Does it have anything to do with the filename? If you can't get it to work, perhaps try using File>Save As (shortcut keys: Command+Shift+S) and saving it with a new name. Even if the filename isn't the problem, this could perhaps let you save your changes: it just adds a couple extra steps (saving it to a new name and deleting the older version of the file).

Also, you're building with LEGO at work? How scandalous!

Edited June 12, 2013 by Aanchir

[pbat]

I'm on a MAC and can't save over a file. It crashes every time. If I try to open a file I saved at work and save it on my MAC, it crashes. Has this bug been reported anywhere? Anyone know what I can do to fix it?

Dump that MAC and get a real PC . No, I'm just kidding. I observed a similar behaviour on a "real" PC as well. Is that behaviour occuring on any arbitrary file, or just at one single special one? When I failed to save over an already existing LDD file, it turned out it was another program having an open handle on that file so that the file was locked for LDD; if I recall it correctly, it was some antivirus scanner examining that file at the same time I was trying to save it. Closing this handle manually helped; I can't however tell you how to manually close a file handle on a MAC.

Do you get any error message? If so, is it always the same error message or do they vary? Can you export / import your model instead of save / load it? Is your computer at work a MAC, too, or was the file that makes your MAC crash originally created at a "real" PC? If so, how do you transfer your file? If you burn them on any optical medium like CD or DVD, they automatically get a write-protect attribute: Even if copied back to a harddrive, you can't alter them until the write-protect attribute is removed manually. This, however, shouldn't crash LDD, neither on a MAC nor on a "real" PC.

So if this issue is still urgent, please do provide some more details.

[Hinckley]

My MacBook Pro doesn't have that problem. Does it have anything to do with the filename? If you can't get it to work, perhaps try using File>Save As (shortcut keys: Command+Shift+S) and saving it with a new name. Even if the filename isn't the problem, this could perhaps let you save your changes: it just adds a couple extra steps (saving it to a new name and deleting the older version of the file).

Also, you're building with LEGO at work? How scandalous!

I'm a LEGO model designer for LEGOLAND. I do use "Save As" and I do try to save a new version and that's where the problem happens. If I do the initial save at any point but right when I open the new file, the entire program just shuts down.

Dump that MAC and get a real PC . No, I'm just kidding. I observed a similar behaviour on a "real" PC as well. Is that behaviour occuring on any arbitrary file, or just at one single special one? When I failed to save over an already existing LDD file, it turned out it was another program having an open handle on that file so that the file was locked for LDD; if I recall it correctly, it was some antivirus scanner examining that file at the same time I was trying to save it. Closing this handle manually helped; I can't however tell you how to manually close a file handle on a MAC.

Do you get any error message? If so, is it always the same error message or do they vary? Can you export / import your model instead of save / load it? Is your computer at work a MAC, too, or was the file that makes your MAC crash originally created at a "real" PC? If so, how do you transfer your file? If you burn them on any optical medium like CD or DVD, they automatically get a write-protect attribute: Even if copied back to a harddrive, you can't alter them until the write-protect attribute is removed manually. This, however, shouldn't crash LDD, neither on a MAC nor on a "real" PC.

So if this issue is still urgent, please do provide some more details.

Um, no. The MAC outperforms every program I use on the PC and I need things done quickly and something that can process without wetting it's electronic pants, so I'll stick with the MAC. But, I'll look to see what the error says and post it here next time. Sometimes it doesn't give me the error at all, just asks for a detailed description of what was happening when the program crashed. It's really aggravating. The entire program just closes. Even if I try to copy the content from one file to another, if I don't save the new file first, before pasting the model in, it shuts down the whole program.

[Toa_Of_Justice]

I cannot insert part #6536 onto the red axle as shown:

However, part #42003 works fine:

LXF File

-Toa Of Justice

[pbat]

I cannot insert part #6536 onto the red axle as shown: [images not quoted, see original post]

However, part #42003 works fine: [images not quoted, see original post]

Are you sure this really is a bug? Is there an official set that combines 6536 and 32310 in the depicted way?

Please do closely compare the parts 42003 and 6536 at the images you posted: At part 42003 there is a small gap or offset between the two pin holes and the rest of the part, so that the pin holes fit tightly into the respective cutouts of part 32310. At part 6536, however, the single pin hole does not jut out and does not protrude from the rest of the part, so that part 6536 will interfere with part 32310.

Please put 42003 and 6536 onto the same axle and you'll see that the lower part of 6536 is way more projecting than the lower part of 42003.

Taking these facts into consideration, it is quite comprehensible that 42003 will fit and 6536 won't, as (according to the images you posted) 42003 isn't simply a 2-pin-hole version of 6536, but has a slightly different shape.

[Superkalle]

This was an odd one.

The 42003 can fit in the position you mentioned Toa, but even at that position it seems to be in collision (blue arrow below).

[PeabodySam]

42610 Hub Ø11,2 X 7,84 cannot be attached to the top stud of 4733 Brick 1X1 W. 4 Knobs, even though it can be attached to any of the side studs. This attachment is used in 10192 Space Skulls, a set that was tailor-made to be built in a previous version of LEGO Digital Designer, suggesting that this attachment was once possible but for some reason cannot be done in the latest version (LDD 4.3.6).

[pbat]

42610 Hub Ø11,2 X 7,84 cannot be attached to the top stud of 4733 Brick 1X1 W. 4 Knobs, even though it can be attached to any of the side studs.

This issue is not limited to the said hub, but rather seems to occur on almost every part with a technical hole; I've tested so far the parts 90202, 6541, 3700, 32000, 3701, 3894, 3702, 2730, 3895, 32018, 3703, 32324, 32531, 32532, 32555, 32009, 6629, 32271, 32348, 32526, 32140, 60484, 43857, 32523, 32316, 32524, 40490, 32525, 41239, 32278, 42003, 98285, 98286 and 11458: Their technical holes can be attached to each side stud of 4733 but not on its top stud.

Edited July 6, 2013 by pbat

[LUModder]

This bug has been here for a while, but it still annoys me, head does not go down all the way with cape on, making it so you have to use the axel trick.

(If the image is too big, I can resize it)

[Calabar]

@LUModder

The image is regular, but if you prefer you can use a thumnail or a text link.

I think the problem is due to the fact that the cape is very thin, while the distance among the head and the torso is thought for plastic nec accessories, that are thicker.

[Aanchir]

Bugs in new parts:

• Part 87800 should be able to be dual-colored, as in the case of Element 4578971
  
• Part 87803 should be able to be dual-colored, as in the case of Element 4615736.
  
• Part 11101 should be able to be dual-colored, as in the case of Element 6037158.

[sheo]

It seems that there is a bug with part 62531 Technic, Panel Curved 11 x 3:

No other part can be placed in front of the panel's corner.

Sorry if this was already mentioned.

Edited September 5, 2013 by sheo

[obsidianheart]

Don't know if this is a LDD bug, but everytime I try to use the Flex tool on a 16L chain, the program hangs and has to be shut down from Task Manager.

[Masta' Blasta']

Don't know if this is a LDD bug, but everytime I try to use the Flex tool on a 16L chain, the program hangs and has to be shut down from Task Manager.

It works fine on my end, so I don't know what to tell you.

[weavil]

Found a bug for Technic. Part 32494 no longer snap into part 92909. It did before the parts update.

[Gnac]

I just managed to slide a technic bush over the edge of a steering wheel (2819).

This is also highly noticeable with a half bush, but just about anything with a technic hole seems to intersect like this. Weird!

LXF example