Jump to content

Superkalle

LDD Moderator
  • Posts

    6,069
  • Joined

  • Last visited

Everything posted by Superkalle

  1. Interesting project. Please be sure to let the rest of us know the result
  2. I'm not sure if it's a bug per se. I think it's not supported in LDD, since it's not a "designed" connection. At least, I haven't seen any official sets using the technique with tiles in 2653. On the other hand, today's designers at TLG are using more and more innovative techniques, so who knows. If anyone has seen the technique in an official set, it would definitely make it easier to propose it as a new features in LDD.
  3. Yes And you did right The problem with the two versions of the 2578 is that a virtual ID needs to be introduced, and at the moment LDD is based 100% on the internal databases at TLG which only has one. On a side note, I can mention that I keep a log of all wanted bricks from this topic, and send it to TLG once in a while. So they are definitely aware of what we fans are wishing for, and add as many as they can. Yepp, Calabar is first in line
  4. Added this to "fans most wanted" list.
  5. I found out that it's beause of the slight offset/difference of technic holes in technic bricks (the famous one). Because of it, the 92907 CROSS BLOCK is positioned the 0.1 mm too high, and as a result the 3176 COUPLING PLATE won't fit. But I also found a work-around: Start by placing the 3176, then the short blue pin, then the 92907 and finally the long blue pin. I attached the fix if you want to use it. I think I saw wrong.... So no problem anymore. umbran_mhc_fixed.lxf
  6. Actually, if I remember correctly, the version initially in LDD was actually neither of the two, but some kind of odd hybrid with two hinge brackets (should be three as can be seen on the BL pics). So a decision was made to update it to the most recent (and most commonly used) version, which is the one with the tow-ball. Both physical versions had the same DesignID, i.e. it's one of those rare cases where TLG decided to re-use the same DesignID-number even though the brick is quite clearly physically different. You can see this on the real bricks too, becuase both version have 2578 stamped. Like you suggests, the solution could be to introduce a virtual DesignID in LDD. But to be honest, I'm not sure if/when that will happen, since the hinge variant was only used in one set back in 1991 and thus is quite low on the prio-list.
  7. Like you gussed, the problem is not in the LXF - it opens fine here. Can you share some more info about your MAC-setup (version, driver info etc etc).
  8. Well, in this case it was, since the grey bar did the "half jump" thingy. In other cases, you might not be so lucky (to be honest, I experimented a bit before I got it). And if all else fails, I always revert to the edit-the-lxfml-file-manually trick.
  9. Superpowers Nah, seriously, it only took a minute or two. If you move the grey bar behind (63965) slightly to the left or right, you'll see that it snaps sometimes with "half snaps" (well, it's not that easy to see, but it does). So start by removing all the slopes/clips and then begin the assembly at one end. Move the grey bar around a bit, then try to position the first "pack" of slopes/clips until if fits snugly. If it doesn't, re-adjust the grey bar. Then continue with the next stack and so on. Let me know if you get it, otherwise PM me.
  10. Great job on the train. But I agree - very annoying with the glass in the frame. Strange to see that kind of "common" bug not been discovered before. BTW, I fixed the arrows. You can copy paste from attached file if you want. trainarrows.lxf
  11. Happy New Year to you too.
  12. That is a really interesting find. I'll send in a question to the LDD Team about this. My guess is that internally at TLG there are two versions of the mold design, and the one we see in LDD is based on an earlier version that was never put into production (or was only produced for a brief time). In either case, the one in LDD should definitely be the one that is most commonly produced, so in that sense it's a bug.
  13. Great news Rich. And thank legolijntje for the proposal Now we now LDD Manager works on 2010 runtime as well!
  14. It's the new LSD mode Seriously though, can you share the LXF? I doubt is reproducable on PC, but it's worth trying
  15. A new version of LDD Manager, 1.12, is out now. Changes: All the LDD to BrickLink reference data has been updated.
  16. Can you try to uninstall, then re-install the 2003 runtime. If this doesn't work (it's the first time I ever heard of this problem though ) then maybe you can try to install the 32-bit 2010 runtime like legolijntjes suggest. LINK to Access 2010 runtime 32-bit: http://download.micr...cessRuntime.exe
  17. @legolijntje - I haven't tested with Access 2010 runtime, so that's why I don't recommend it. I've only tested with 2003 runtime. Besides, there really shouldn't be any problem with the 2003 runtime (unless there is another version of Access installed). @Dluders - No, that's not correct. LDD Manager will work on all versions of Windows (XP, Vista, 7, 8 - 32 and 64 bit). However it will not work with Office 64-bit (which is still a quite rare version of Office - not even MS themselmves recommend people to use it due to compatibility issues). My thought at the moment is that Bricksan is having some other odd issue that I'm trying to troubleshoot. But thanks for the suggestions guys
  18. OK, just so I get it right: 1) You installed the Access 2003 runtime. And there is no other Access version on your computer. Is there any other Office version? 2) You have unzipped the content of LDDManager.zip to a folder that is read/write. 3) You double click StartLDDManager.vbs - no response (other then Please wait while Windows configures....) Correct so far? Some things to try then: a) What happens if you try to run the LDDManager.mdb-file. Does it work? b) I attached a very simple Access mdb-file. Can you download it and see if it works to open it. db1.zip
  19. Do you have any other version of Access or Office installed on your computer? The message typically appears when you have multiple versions. Also, if you have another version of Access/Office installed, you don't need to use the Runtime - it's only intended those that doesn't have Access at all.
  20. I'll ask one of the admins to investigate this.
  21. A new edition of the excellent Hispabrick Mag is out. Download it here Discuss it here
  22. That's odd. I just tried it, and it works fine. Can you have a look again. https://docs.google.com/folder/d/0B9Ysf2u0fN8pbzcwVmxWSWthdFE/edit?pli=1
  23. You're right - off course it won't fit - I mistook it for a 2717
  24. No, that was the post I was thinking of. I guess everything is fine then.
  25. I mentioned it here One of the sets I remember was 9446
×
×
  • Create New...