Superkalle

I can't replicate. Can you show a screenshot? (I suppose you mean a 3022 under a 4151)?

No worries

Just to mention it, the latest news was actually that we could expect some maintenance releases and that LDD wasn't dead. I think the massive support in the online community the past week showed TLG how many people actually use LDD, so we'll have to wait and see.

IMPORTANT INFORMATION May I kindly ask you not to discuss the specific process or tools for extracting data from LDD here at EB. There are a couple of reasons for this: First, it is against the EULA of the program. Secondly, we have a great relationship with the LDD Team in the forum which has given us a lot through the years (for example many of the special or legacy bricks the brickset updates), and it's a unique co-operation we want to maintain. Thirdly, it is pretty meaningless to hack or extract data from LDD, since it will always be a shady business and you can't build a genuine community platform on it. Fourthly, if you want to edit, add or manipulate bricks, there is always Ldraw which is an excellent platform. I hope for your understanding in this. Note, you are certainly allowed to discuss about how great it would be to get your hands on the LDD data, or problems associated with it, but please don't post links to tools which only purpose is to extract LIF-data. I can also comment about some questions I've gotten about how LDD2PovRay and BlueRender can be allowed to access LDD resources. In the case of LDD2PovRay, it has been deemed OK since the used brick geometries are protected by a virtual file system (the "driver" that is installed with the program). In the case of BlueRender, the used geometries are hidden from users and only used for the render engine. Hope that clarifies things. More important information If you follow this thread you already know, but let me summarize the events the past couple of days: 1. Yesterday it was posted in the Ambassadors forum (at LEGO, not the one here at EB) about the end of LDD support which caused a wide-spread discussion here and on other AFOL forums about the end of LDD. 2. Today this was reversed, and it was communicated that LDD maintenance is continued on the same basis as previous years, i.e. with updates on a semi-regular basis (without guarantees for when or what content). Yes, it's been a long while since the last update so naturally we are getting worried, but let's still hope for an update in the not to long future.

Looking forward to it

@Lychir and ClassicSmiely Your reasoning sound logical, and suddenly I feel I'm not sure anymore. I know that hinges that are not centered, and then gets re-aligned, will brake the models. If this is also true for nudging stud-connections, I can't swear on.

The bricks that were chosen (if I remember correctly) was 1x1 tiles with printed letters. Then time went on and I believe the bricks where eventually ready for release, , but then came the Big Draught....and we're still waiting for a new brickset....

There are two tools to do that: LDDManager and BrickUtils. Both will create BOMs (Bill of Materials) that you can export/use in Bricklink directly. However, both tools haven't been updated in a little while. LDDManager only works on Windows, but BrickUtils work on Mac too (Java based if I remember correctly). Also, you can export a BOM directly within LDD on the File > Export BOM. The main issue with LDD at the moment is that we are unsure about future updates to the program itself and to the brick database. There is a discussion about it in the Digital Design forum here at EB. Just to mention it too, there is also the LDraw ecosystem of tools as well as an online tool called Mecabricks. And no, digital MOCs are not discouraged, but even I as a "digital guy" prefer physical MOCs and I see digital tools are a support in the creative process towards building with real plastic. But that's just me. And starting a topic with [LDD MOC] is a good idea (or [Ldraw MOC] if that platform is used.

Incredible that this has never been seen before! Well spotted! I'm not sure it will/can be fixed though, because moving connection points on a brick will break any models in which the brick has been used (i.e. bricks will be removed when opening LXF-file). Only way to fix it would be to handle this in code (a new version of LDD would be required).

Being your first post, welcome to Eurobricks and the Digital Desing forum! The helmet protection can be placed on 3838 Oxygen Tanks, which can then be placed on a minifig body. Then place the head and finally the helmet. (in that order). But I agree, it should be possible to put the 6158 Smoke Helmet Protection directly on the body+head without the use of the oxygen tanks as an intermediary. Thing is though that then you wouldn't be able to put the oxygen tanks on, since the head would be pressed all the way down. So I guess the solution in LDD is the best overall? Here's a picture with the whole assembly for reference: http://www.bricklink...ic.asp?S=6459-1 PS: You first posted in an old bug report topic dating back to LDD 4.3.6 and in the process bumped a 3 year old topic. I moved to this more recent/current topic.

Merged two topics and updated topic title

Oh, OK. But I didn't mean products that are in the Office installation, but later installations that somehow overwrite the Office files. Could be even non-MS products.

OK, good that it got solved, but it shouldn't really be necessary to install Office 2010. Sometimes installing another Microsoft product (e.g. One-note) will mess up the installation for existing Office installations. Maybe this was the case?

No problem with the Danish Jeg forstår nokk dansk rimligt godt. I've had a look. In the code it tries to make a connection (Application.CurrentProject.Connection). Why it then throws you the dialog to chose a data source I'm not sure about. I did some googling on it, and found this, so my best recommendation is that you make a repair of your Office 2013, so that necessary files are re-installed/re-registered? You shouldn't need to download anything - just a repair installation should do it. Another thing to do can be to try LDDManager on another computer with Office/Access (32-bit) and see if it works there.

Hi snakebyte. I haven't heard about any ODBC issue before (or maybe I just forgot ) Unfortunately I don't know what the problem can be right of the bat. Everything in LDD Manager is "self contained", i.e. there are no references to any data sources outside the program. Can you please post more exactly what the error message is and when you get (in which window) and I'll try to investigate.

I'm not sure what the problem is. Can you explain what you see in Bricklink. Does not the Items column add up to 878 bricks? Or does it only add up to 167? EDIT: I just imported your file into LDD Manager and then uploaded it to a Wanted List, and it looks all good, see attached image. PS: Is it going to be a toy? Why don't you make the scope hollow so you can see through?

@Darknight17 Please don't bump old topics if doesn't shed new light on the topic as such. This topic was about the brickset when it was just released a year ago, discussing the new bricks etc. If you want to ask if a brick is in LDD use this topic If you want to discuss a potential new brickset, use this topic @CM4Sci - we really don't know anything about if a new brickset will be released for 2016 or not, so best not to say either "probably" or "probably not". It's all a big unknown IMHO.

I don't know what this can be. The only problem could be if the LXF-file is for some reason saved as a text-file (i.e. a LXFML-file saved with LXF-extension). To make sure this isn't the case, open one of your LXF-files in LDD and then chose "Save-as" and save it as LXF with a new name. This will make sure it's saved as a "true" LXF, (i.e. a zipped LXFML). The try to open it in LDD Manager. If that doesn't work, send me the file, and I'll have a look at it (mail address is in the help-file). Please note though that LDD Manager hasn't been updated for a while, so some bricks may not be properly mapped to BrickLink. I may release an update if there will be an update to LDD in the future.

File > Export Bom

One massive post that is

I know there is general recommendation from LEGO Customers Services to visit this forum for updates to the Ldraw/XML file (so LDD better can convert to/from Ldraw), but that's all. We don't have any updates to LDD itself (bricks etc). It would have been interesting to read both your question and the response from LEGO, to better decipher exactly what was meant.

Just download the LXF and have a look (and besides, the original poster hasn't been active at EB since 2013, so probably little chance he will fix any picture links)

One of the 57539 will to connect, see attached image. The trick is to first insert the end through the neck using a temporary 32002 placed in the hole behind the head, and then remove the 32002 and "pull" the cord through. It will then attach to the other side. The other 57539 could possible be made to "float" in the right position (perhaps better then having it on scene floor, I don't know). Just temporarily replace the 57558 (which is correctly named 57557 at Brickset) with some other suitable brick that has a hole in the right positoin, place the cord, and then put the 57558 in place. The 60930 will connect if you rotate it some degrees (tip: remove the 87820 first). Give it a try and see if you can fix it

Closing this topic since same question was posted here (Please don't crosspost!)

As for finding bricks in LDD, it might be a good investment to just take the time to browse the brick library in LDD and figure out how bricks are categorized. It's a bit different from how BrickLink organizes bricks. Another tip is to use one of these online databases to find the brick ID, and then use that to search for the brick in LDD: http://brickset.com/parts http://www.bricklink....asp?itemType=P Using the later for example, I found that the ID for the Technic panel is 64782 and entering that in the LDD search gave me the brick. Also note that LDD hasn't been updated for about 9-10 months, so any bricks newer then that will not be in the brick database. We're all waiting for a new brick update, but at the moment there are no news as to when one will arrive. Finally, even though I appreciate the idea with a separate topic for your questions, I'd prefer if you post "find-that-brick" type of questions in this dedicated topic we have for it. Thanks. And good luck with your project