Jump to content

Superkalle

LDD Moderator
 View Profile  See their activity

  • Posts

    6,069

  • Joined

  • Last visited

 Content Type 

Everything posted by Superkalle

  1. Superkalle
    I think there might be some confusion: @Sjuip: I belive Calabar needs to know which files you have re-saved as 4.3.6 specifically (as an updated LXF) and which are just compatible (will open in 4.3.6). However.... IMPORTANT @Everyone: I would probably wait with updating sets that have the 3960 Dish. This is such a bad bug, that I'm guessing the LDD Team will make an emergency fix/update for this alone. I'm going to inquire some and get back with more info.
  2. Superkalle
    OK, gotcha guys. That is a bad one
  3. Superkalle
    Good find. It seems the ball now actually connects to the 64275 shooter arm, so that could be the reason? (but it doesn't connect to 98564, so that seems to be bug). Maybe the fruit should should also have the connectivity as 64275?
  4. Superkalle
    What I usually do, is to open LDD via the Start Menu (Win7). When you click on the LDD icon, a list expands with the recently used files. In the top of that lis I have a small, pinned LXF where I collect all ideas and bugs. Starting that allows me to bypass the LDD start screen. But putting there a completely empty file is better, and even better is then o make the link to the empty LXF the start-ikon in itself as you explain. Very clever idea Mr. Toa. Haven't never thought about it, but it's a good point. According to GUI design rule- of-thumb the user shall always have an escape
  5. Superkalle
    Can you share a file where the 3960 get's removed? From what I understand, a connection overrides collision boxes For example, a stud can snap to the underside (anti-stud) of a brick, even though the brick is solid square collision box. However, trying to poke a lightsaber blade in the underside of a brick won't work.
  6. Superkalle
    If you unzip an LXF and view the LXFML inside, you can see the 5 digit DecorationID numbers in there. So that's how you can "test" various decorations if they fit and how they will work (trial and error) - simply enter a decorationID, save the LXFML and open in LDD and see how it looks. As for the list of all DecorationID's themselves, I got a list from the LDD Team and passed it on to Aanchir as I know he knows how to deciffer them . (there might be some internal list at TLG that maps the decorationID's to the correct partnumber/minifig, but if so, it's not something that I get...). Except for the small actuator 92693. But otherwise I agree that there weren't many Technic parts.
  7. Superkalle
    But then I don't get pbk420's remark, because I'm able to attach the skirts to minifig legs, and then put on a torso. Sure, there is a small gap, but it will connect at least. Or am I missing something I guess it's because the is not concidered a technic hole. The hole in the coupling plate can be seen as the same type of hole as is in a technic plate, so therefore it works on that one EDIT: But the ring can put put on the minifig neck.
  8. Superkalle
    nice find pbat. So what to do? LDD cannot distinguish if a stud has been already inserted from one side, so either we get full connectivyt from both sides, or nothing. Does the ring ever get used in an official set placed on a stud? EDIT: Yes, it fit's on a minifig hand of course Which ones to you mean?
  9. Superkalle
    And here is attached for your viewing pleasure a LXF with all the new bricks. Also, below a list I got from the LDD Team with all the brick bugs fixed. I think you'll notice that many of them are the ones you guys posted here in the forum 2350, 2423, 2435, 2626, 2855, 2856, 3665, 3814, 3960, 3960, 4081, 4081, 4489, 6118, 6260, 10113, 10172, 10172, 10172, 10829, 11101, 11113, 11438, 11438, 12618, 12897, 30091, 30139, 30208, 30214, 30338, 30339, 30361, 30385, 32173, 33175, 44358, 44358, 44359, 44359, 44359, 54821, 59228, 59443, 60169, 62701, 64275, 64644, 74698, 74698, 75937, 86500, 87688, 87689, 87690, 87691, 87794, 87841, 88517, 90397, 90540, 92220, 92338, 92690, 92709, 95322, 95323, 95829, 95831, 95832, 96910, 98127, 98127, 98565, 98590, 99008 (thanks to Martin and Paw for this ) NewIn1007.lxf
  10. Superkalle
    Closing this topic. Please use this new one for 4.3.6 instead.
  11. Superkalle
    Time to start a new bug reporting topic for this release. Fire away guys.....
  12. Superkalle
    Can you post the faulty part-numbers too please.
  13. Superkalle
    Yepp, that's bad! I think it came because they opened up for a 3.2 mm lightsaber blade to slide through (which was a bug before), but now also an x-axle can slide through. (For the rest of you - it's 59443 that we're talking about).
  14. Superkalle
    Good news for all LEGO Digital Designer users. A new version was released today - 4.3.6. As the version number implies, it's a small step-up from the previous 4.3.5, so new features to talk about. But the good news is a massive 200+ new bricks and about 80 brick bug fixes. Talk about it over here.
  15. Superkalle
    Some stats I got: 200+ new bricks 75 brick bug fixes 600+ new decorations. Even though no new features, it was a healthy dose of bricks. About all those decorations, I'm not sure how many are actually mapped in the GUI and/or have decorations surfaces that they can stick to. Let's see what Aanchir says.
  16. Superkalle
    Well, I'm not sure to be honest. When LDD was originally developed, and the first bricks made, I'm guessing the collision volumes of the studs where made a bit smaller and more "forgiving", just to avoid that borderline cases wheren't possible to build and kids (in those days) would be annoyed. I'm not even sure that they back then they thought about all the advanced techniques used today. But this doesn't mean that the LDD developers one day can/will increase the collision volumes inside the studs. I suppose it's a fairly easy task programatically since the studs are so normalized. The big problem will off course come when people all over the globe open LXF-files of advanced builds only to get the dreaded "x bricks have been removed from your model..."-error.
  17. Superkalle
    ^ Not sure I follow - how do you mean?
  18. Superkalle
    Don't feel bad - it's a matter of lifting the quality in LDD However, about all intersection problems that have to do with studs, those are all known to TLG (and part of the standard collision volume for all bricks), so in those particular cases there is no need to report them (like the example above). On the other hand collision errors of all other parts of the bricks are interesting if/when they prohibit legal techniques OR allow you to build stuff that is waaay off. The examples Technic parts above are of that class IMHO, particularly the one where the two stabilizer bars intersect when placed next to each other.
  19. Superkalle
    First, I meant "order in BL" off couse, not LDD Secondly, the letters themselves would not be generated programmatically, only putting them together to a string. So it would work like a TrueType font library does. I'm playing around now with some code to capture the letter from an LDD-file (using groups) and then put them in a lookup table. Shall be interesting to see if it works.
  20. Superkalle
    Are they really that hard to pull apart? Otherwise, this would be a bug in LDD I suppose?
  21. Superkalle
    This is an interesting question. Just the other day I was thinking to make a feature in LDD Manager that will do texting. My situation was that I find that sometimes I use LDD to lay out bricks on the scene that I should order in LDD (EDIT: BL I mean) - just to get the overview. And then I need to "write" some simple text in bricks and put next to the bricks, like "ordered", "pending" etc. And then I thought, this should be really easy to do programatically - just a dialog box to specify text and choice of font, and then generate the LXF.
  22. Superkalle
    OT: Is that Galois in your Avatar?
  23. Superkalle
    Great video - that's roughly how I did it too, but your solution was a tad more elegant But I'm wondering if this is not almost a brick "bug". Because in many sets, flexible axles need to be inserted like this into technic holes, but it's not possible to do because the "flex" resistance of the digital axles is to high, so the ends can't pop into place. Anyway, you posted the correct answer, so now you get to post another challenge (if you want to)
  24. Superkalle
    Clever bbqqq - but how did you get the flex elements to snap into the technic x-axle connector in the first place (which you obviously did)? That was the challenge that I had in mind
  25. Superkalle
    Small micro challenge for ya all. I managed to fix it myself only after a long time of fiddling around, only to discover the solution was kind of simple. So, can you do it? This is what we have (curtesey of Balthasar_the_Dark): This is what we want: 8256.lxf
×
×
  • Create New...