[KEY TOPIC] LDD 4 Bugs and brick errors

[Superkalle]

Not sure if this one has been posted or not...part 4715 (underpart for stretcher), works with the stretcher, but doesn't connect with part 4276 (either just one or a pair), even though it is supposed to??

Trying to build set 6480 at the moment.

Yes, that seems like a bug. Haven't seen that reported before.

Good find.

[Lyichir]

With the last version of LDD I have continuous problems with baseplates. I have not to move them if put under a building or LDD simply closes...

How big is the building on top of the baseplate? It sounds like your LDD is crashing because of the number of polygons it's having to render. When a baseplate (or any part on LDD, really) has bricks on top of it so that the studs aren't visible, it doesn't render those studs in an effort to ease the graphical load. But baseplates, being large and covered with cylindrical studs, are loaded with polygons when nothing is built on them. I think when you're moving the baseplate out from under the model (which, depending on size, may be pushing LDD's rendering capabilities close to its limit already), LDD is having to render all those studs as you move the baseplate around, and thus crashing under the load.

I can't think of an effective solution for your problem if this is the case (I'm no expert on rendering, and in my answer I'm only applying facts I picked up from more knowledgeable users). Perhaps if you copied a portion of your building into another file, deleted it in the original, moved the baseplate, and then finally copied the portion of the model you removed back into the original file, it would work? Or maybe if you lowered your graphics settings temporarily while you moved the baseplate it'd work better. Hopefully someone who understands more about LDD's polygon limits can add their two cents.

[JGW3000]

PF part 58118, Extension wire 50 cm, accessible in LDD extended mode, correctly has two plugs; but, unlike the other PF parts in which the plug can be moved independently of a motor, for example, the two plugs move together rather than separately when repositioning one of the plugs, rendering the part mostly useless.

[Takanuinuva]

Part http://www.bricklink...tem.asp?P=32187 will not connect to pins such as http://www.bricklink...Item.asp?P=6558 but connects fine to studs and axles.

[bak318]

When LDD closes if you move a baseplate, you're at the end of the capacity of LDD/your graphic card.

You made something very large.

Effecting LDD to close is when it becomes physically big, lots of bricks, lots of hinges, or many different (transparant) colours.

LDD closes too when there is a slight offset.

When some bricks don't line up.

That means if there is just one brick that is not placed corretly it can't handle it and LDD closes.

That happens when you make something in an angle and that angle moved both sides.

Is the baseplate accepted for a part before it closes or directly when you try to move it?

[Aanchir]

Today I tried taking a screenshot of a building technique on my Mac using Command+K (the LDD screenshot tool keyboard shortcut). The first couple times I attempted this, the PNG image file that LDD saved was completely blank/transparent (no image). Subsequent attempts have caused LDD to crash before the file can even save. This seems to happen whether I am in Build Mode or View Mode, and it is quite frustrating, as I had grown fond of the LDD screenshot tool. When used in build mode, it used to save screenshots of a model with a transparent background, unlike the Mac screenshot tool which would capture the whole screen, backgrounds and all. Now, it doesn't save screenshots at all.

I hope this is fixed soon. It might have to do with my operating system, which recently updated to OSX 10.9.2. The screenshot tool was working just fine as recently as this past January, as I used it to take this screenshot. Needless to say, I'm perplexed and frustrated.

[bak318]

Did you update the drivers for your graphic card as well?

Perhaps that this is the reason for this behaviour.

I'm not familiar with the mac, only windows.

But since i updated my drivers two yaers ago i have no problems.

Even with models with over 25.000 bricks it keeps on working fine.

Oke, slow but it is working.

[JGW3000]

I found this collision error between technic pin (also happens with 3M pin) and battery box...

[JGW3000]

Cross-posted from LDD update topic:

In the new brickset 1392, found a major (well, for some people) error. IN LDD extended and regular mode, part 76537 (two instances in regular mode - white/black and yellow/black), shock absorber, extra hard, is listed by image in the brick palette, but can't be dragged onto the screen. It is between parts 53533 and 98989. Moreover, models using this part get a bad part error.

Also, part 58118 (FUNC EXT. Wire 50 CM.) has been deleted from the new brickset.

There appears to be superfluous part 95292's in the brick palette in LDD extended mode

Edited May 2, 2014 by JGW3000

[bacem]

would this count as an error?

[Superkalle]

would this count as an error?

Yes. Not severe...but still....

[Calabar]

That's interesting... maybe the problems I've with the Intel HD Graphics is due to the few shared memory. I should make a try.

[kamos]

Not a severe bug...

Parts 71137 Exhaust pipe w. grooves and 40620 Exhaust pipe m/snap can be inserted way too inside the 4070 Angular brick.

Clipping issues between 71137 / 40620 and 4070 (2370 x 1325)

Left side: 71137, right side: 40620

top, green - how it should be

bottom, red - how it's possible to insert them into 4070 / how it shouldn't be

Part 85861 PL. Round 1x1 w. trough hole can go inside 71137 / 40620.

Clipping issues between 85861 and 71137 / 40620 (3148 x 826)

Top: 71137, bottom: 40620

Left, green: how it should be

Middle, red: how it's possible to insert it into 71137 / 40620, how it shouldn't be

Link to LXF file

LDD doesn't recognize them as bugs / collision errors, it's possible to open file without them being removed.

(and also these aren't new bugs, these also worked in previous brick library 1264)

[Superkalle]

Not a severe bug...

Parts 71137 Exhaust pipe w. grooves and 40620 Exhaust pipe m/snap can be inserted way too inside the 4070 Angular brick.

Part 85861 PL. Round 1x1 w. trough hole can go inside 71137 / 40620.

Good report. I'll put this on the bug-list.

[Bob De Quatre]

Got a "major" bug with the color palette showing too much legacy colors and so preventing from selecting the regular solid colors.

Palette trouble... by BobDeQuatre, on Flickr

[mzoli]

Brick version 1392 has introduced the legacy Rim 6582 (with tyre 6581).

I think the center of the rim should be 1 unit wide but it is slightly wider.

It does not fit Axle 5M for set 8282 Model B.

LXF file

Reference picture

[t-brick]

Today I tried taking a screenshot of a building technique on my Mac using Command+K (the LDD screenshot tool keyboard shortcut). The first couple times I attempted this, the PNG image file that LDD saved was completely blank/transparent (no image). Subsequent attempts have caused LDD to crash before the file can even save. This seems to happen whether I am in Build Mode or View Mode, and it is quite frustrating, as I had grown fond of the LDD screenshot tool. When used in build mode, it used to save screenshots of a model with a transparent background, unlike the Mac screenshot tool which would capture the whole screen, backgrounds and all. Now, it doesn't save screenshots at all.

I hope this is fixed soon. It might have to do with my operating system, which recently updated to OSX 10.9.2. The screenshot tool was working just fine as recently as this past January, as I used it to take this screenshot. Needless to say, I'm perplexed and frustrated.

I have the same screenshot problem (Mac OS X 10.9.2 on an iMac). Since the update it doesn't work anymore, just crashes :-(

[kevin8]

How big is the building on top of the baseplate? It sounds like your LDD is crashing because of the number of polygons it's having to render. When a baseplate (or any part on LDD, really) has bricks on top of it so that the studs aren't visible, it doesn't render those studs in an effort to ease the graphical load. But baseplates, being large and covered with cylindrical studs, are loaded with polygons when nothing is built on them. I think when you're moving the baseplate out from under the model (which, depending on size, may be pushing LDD's rendering capabilities close to its limit already), LDD is having to render all those studs as you move the baseplate around, and thus crashing under the load.

I can't think of an effective solution for your problem if this is the case (I'm no expert on rendering, and in my answer I'm only applying facts I picked up from more knowledgeable users). Perhaps if you copied a portion of your building into another file, deleted it in the original, moved the baseplate, and then finally copied the portion of the model you removed back into the original file, it would work? Or maybe if you lowered your graphics settings temporarily while you moved the baseplate it'd work better. Hopefully someone who understands more about LDD's polygon limits can add their two cents.

When LDD closes if you move a baseplate, you're at the end of the capacity of LDD/your graphic card.

You made something very large.

Effecting LDD to close is when it becomes physically big, lots of bricks, lots of hinges, or many different (transparant) colours.

LDD closes too when there is a slight offset.

When some bricks don't line up.

That means if there is just one brick that is not placed corretly it can't handle it and LDD closes.

That happens when you make something in an angle and that angle moved both sides.

Is the baseplate accepted for a part before it closes or directly when you try to move it?

Thank you for the kind answers... I'm sorry I didn't noticed...

Actually my graphic card is 2Gb ram and it's just 1 year older. The file is 6000 pieces... this is strange for me... If I move Moc made of 10000 pieces with no baseplate there's no problem...

Edited May 5, 2014 by kevin8

[mzoli]

Another issue I've found:

neiter side of 32126 Toggel Joint allows stud connection.

[Superkalle]

neiter side of 32126 Toggel Joint allows stud connection.

You've got sharp eyes....but this one has actually been reported before. I was hoping the LDD team would have fixed it for the 1392 brickset, but it will hopefully be in the next

[Lyichir]

I found an error when attempting to build the new Sandcrawler set.

http://www.brickshelf.com/gallery/Lyichir/LDDSets/LDDReference/LDDErrors/55013_error.png

Unfortunately, it looks as though my issues with the screenshot tool made it so that the part in question doesn't appear in my screenshot, so I'll attempt to explain verbally. Do you see how the end stop of part 37083 (Cross Axle 4M with End Stop) in this picture is able to sink partway into the opening of the Technic axle hole? That's how it's supposed to work, but unfortunately part 55013 (Cross Axle 8M with End Stop) doesn't do the same thing, stopping with the end stop still outside the Technic axle hole.

[Superkalle]

I found an error when attempting to build the new Sandcrawler set.

http://www.brickshel...55013_error.png

Unfortunately, it looks as though my issues with the screenshot tool made it so that the part in question doesn't appear in my screenshot, so I'll attempt to explain verbally. Do you see how the end stop of part 37083 (Cross Axle 4M with End Stop) in this picture is able to sink partway into the opening of the Technic axle hole? That's how it's supposed to work, but unfortunately part 55013 (Cross Axle 8M with End Stop) doesn't do the same thing, stopping with the end stop still outside the Technic axle hole.

Gotcha!

[___]

not sure if it can be considered as error but see this post of mine (having no reaction yet) http://www.eurobricks.com/forum/index.php?showtopic=95280

[AndyC]

Thank you for the kind answers... I'm sorry I didn't noticed...

Actually my graphic card is 2Gb ram and it's just 1 year older. The file is 6000 pieces... this is strange for me... If I move Moc made of 10000 pieces with no baseplate there's no problem...

It's not just about polygons. When you move a piece, LDD has to recalculate all the possible "snapping" points that the piece could attach to, so it can figure out where to display it. When moving a piece like a baseplate, that has a high number of connection points, under a large model the number of possible connection combinations becomes very large and that is both CPU and memory intensive.

[bak318]

It's not just about polygons. When you move a piece, LDD has to recalculate all the possible "snapping" points that the piece could attach to, so it can figure out where to display it. When moving a piece like a baseplate, that has a high number of connection points, under a large model the number of possible connection combinations becomes very large and that is both CPU and memory intensive.

That could be true but there must be more.

I know that problem.

Last i build my opreahouse 2.0 that contains almost 26.000 bricks.Moving a baseplate is no problem.

I started building a zoo with an aquarium in it.

It has a lot of transperant plates and floating parts.

In that model i'm not able to move a baseplate.

In my experience, if you use a lot of transperant colours, your graphiccard has a lot to do.

Ones i build a flat, only about 9000 pieces but a lot transperant.

I had a lot of problems with it.

Recoloured in plain red there wasn't any problem with moving or adding bricks.

So perhaps this can help you.