Superkalle

It turns out the expected ratio for requested parts is pretty good. Last time I think we got most parts we fans requested (except for a few older parts that apperantly didn't exist CAD-files at TLG). However, getting the mini antenna as separate part is highly unlikely that it will happen. The principe used in LDD is that parts that come assembled from factory are assembled also in LDD. This also includs parts that are supplied un-assembled, but once assembled, they cannot be taken apart. Examples include the 2x2 turntable. However, in this particular case, it would probably be easier to which for the 2x2 turntable base, since it was used in some recent official sets (like Taj Mahal). The same principle applies to mini-fig hands. They are not supplied from TLG as loose parts, and hence are not in LDD. Basically, one can say that parts in LDD are supplied only as they would be available to a TLG-designer.

Which shoulder pad is it?

Grouping in LDD is basically only a way to create a collection of bricks for easy selection. There is no more additional functionality to groups, then it is to simply do a manual multi select of bricks.

I think it fits fine here

Hi, I'll try to answer your questions too, and taken together with the others, hopefully you'll get a good view on the situation. 1) A little bit difficult to tell from the picture. Post the LXF and it will be easier to help out with this one. 2) Not possible unfortuntately. LDD will only allow usage of parts as supplied from TLG in official sets). There are few exceptions but this is the general rule. As a purist I don't mind about this at all, but I know a lot of people don't agree with me. 3) You can in most cases add a single stud into a technic hole in LDD (like a 1x1 round plate, a 1x1 plate and a 1x1 round brick). But no more then one stud is allowed. It is often belived that it is because children cannot pull more then one stud out of technic holes (because of the increased friction in technic holes), but this is not the case. 4) I haven't tried it, but it might be possible to nudge the tile by manually editing the LXFML file (another story how to do that). As long as the collission volumes (that inside each brick in LDD) do not collide, you can "freeplace" any brick in any place/position. It is much more cumbersome then in LDdraw based tools, but it can be done. 5) Not that I know of. The technique was bad in the old days (but this was unknown then), and is bad today as it destroys the bricks. That's why LDD won't allow it. TLG does not want to encurage users to use a techniqe that is not healthy for the bricks. 6) Yes, most likely by scafolding and/or nudging in LXFML file. Also, I agree that LDraw is better if you want more freedom, specially with old and/or illegal assembly methods. However, LDD is IMHO much faster to use, thereby allowing you to quickly try out various designs. I might be going out on a limb here, but I'd say that LDraw is better for documenting existing designs/MOCs, while LDD is better as support tool during the design process.

Good request. Parts that have been used in many sets are always easier to get through. At least that's my experience.

Besides the lookup table between LDD DesignIDs and BL ItemIDs, there is also the mapping of decorations, something that takes much some time to do and keep updated (I owe Aanchir for help with that). So if you are interested in buying bricks with decorations from BrickLink, that data is required also. There is also the matter that BL constantly is updated. Between two updates of LDD Manager I'd say that about 20-50 parts have changed ID, so there is also work to constantly re-map parts and keep them updated. And naturally to find which are the new parts in each LDD release. In the last release we got a list of numbers, but that hasn't always been the case. Then there is the thing of mapping which parts in LDD correspond to which in BL. Sometimes you have a 2>1 match, sometimes the other way around. In LDD for example, there is about 50 parts that are mapped to one or more BL ID's. And if you chose the wrong one, and upload to BL, you might find that that part has not been made in that color (compare a, b and c versions in BL). In LDD Manager, I've taken into account so the mapping to a, b and c version takes into account which is the "high volume one" with most seller and colors. Also, in LDD Manager you will also get notified if the color you've chosen exist in an a or b version, or even a similar brick with another ItemID all together. Then there is the color conversion, but that's easier - possibly with the exception that the Peeron table that is mostly commonly used is incomplete and has errors. I've spent considerable time to verify and update the LDD to BL color table, also for old obsolete colors. Countless hours of phone calls to LEGO Customer Services to ask about DesignID's and what MaterialID's they have in the their databases, and then what the corresponding BL color is. I'd also like to mention the color lookup in LDD Manager that allows you to check if the parts have been made in the colors you've used, and at which volumes (i.e if it's rare or not). It's annoying to upload the XML-file to BL and just to find that the parts has not been made in that color, and then you have to re-do the whole process. In LDD Manager you can also simply see which colors the part has been made in. I don't think too many people use that to be honest, but it's there. So, it's not only a matter of simply mapping the LDD numbers to BL numbers. There's a lot more going on behind the scenes and lot's of work to keep the whole thing updated and running smooth. Just wanted to mention it

I was going through your list when I spotted this, and it is allready in LDD

Just found this free screen sharing tool: https://join.me/ Has anyone here tried it? I was thinking as a way to share a LDD session with someone (when discussin design solution over Skype or the phone with someone).

Please add your wanted parts here

As with your other topic, I'm moving this over to the SW section.

I recommend that you post these kind of MOCs at the Star Wars section. To post LXF MOCs here at the LDD section, they have to be a bit more advanced so they can be interesting for other LDD users to study techniques etc. I'm moving it over to the SW section.

As general information, WantedBricks is a bit outdated and doesn't support all the new bricks in LDD. Otherwise it's a great piece of software. In some respects even better then LDD Manager since it doesn't require Access to run.

Graphics card acceleration and handling visuals.

Probably some version issue. I developed in Access 2003, and I'm guessing you're running some other version. I'll have a look at it. In the meantime, you can actually just copy/paste into Excel from LDD Manager. Simply select all the rows you want to copy and paste in excel. EDIT: I like your username. Everyone tells me mine is really corny with that "super" in it, but now I see there is another one

For anyone who wants to let LEGO know they feel, the best thing is also to contact LEGO Customer Support and state your view. The message should reach the right people within TLG.

Example please

First, adjusting the Compatability in LDD has nothing to do with opening the UnplaceableBricks file or collission control for that matter. Let's start from the beginning; There are two kind of "errors" when opening a file 1) The brick does not exist in the database (the DB.lif file). In this case naturally LDD can not visualize the brick, because the data for it is simply not there. This is quite rare, because normally no bricks are removed in later versions of LDD. 2) The brick has been incorrectly placed and is colliding with the collision volume of another bricks. So how can a brick be inncorrecty placed in the first place? There are (at least) two ways: a) The real-time collision control (at the time when the brick is placed) in LDD is somehow missing the control (don't ask me how that can happen ) b) You are opening a more recent LXF file in an older LDD/Brickset version (where collision volumes may be different). Now, with the theory in place, let's look at the UnplaceableBricksDump.lxfml file. It is basically a file that LDD is creating where the offending bricks (causing a collision) are colored red, and all other bricks are yellow. Open it in notepad. Search for bricks that are red (materials="21"). For that row - look at the DesignID (e.g. designID="53562") - that will give you the brick(s) that was removed. PS: The UnplaceableBricksDump.lxfml is located here C:\Users\[uSERNAME]\AppData\Roaming\LEGO Company (for Win7 at least)

Unfortunately there is no way to strip down within LDD. But the feature to do a post check will be added to LDD Manager again (it was there until 4.2.5 was released since I didn't think it would be needed, but apperantly it is. About populating the Pab site with bricks directly from LDD Manager; I have looked into it, but haven't managed to do it. From what I recall, there is someone who has done a script for it though. An updated version of LDD Manager should be out in a few days. It will also "support" the new 604.1 brickset.

Good idea to make a general topic about the tool (like proposed by Calabar).

Just spotted a discussion over at BrickLink forums about part 93059. It used to be called "chinamans hat", but now it's "figure head clothing no 7". I think TLG got accused for using a poor name for that parts and changed it and that's the reason for the update.

I have no clue.

I agree - great stuff!

To be honest though, it seems the 64 version of office is not something that MS recommends. By default, Microsoft Office 2010 installs the 32-bit version of Office 2010 even if your computer is running 64-bit editions of Windows. The 32-bit version of Office 2010 is the recommended option for most people, because it prevents potential compatibility issues with other 32-bit applications, specifically third-party add-ins that are available only for 32-bit operating systems. You can also read more here about the shortcoming of 64-bit office and here from MS. Seems the only reason to use 64 bit is if you have >2Gb Excel files or Access Databases, and who has that? So a solution would be use Office 32-bit instead.

It works for me - you have to position the gears exactly, like within 1 degree and then the 12 tooth gear will slide all the way in. But it's not optimal in LDD - there should be a bit more tolerance.