Jump to content

SylvainLS

Eurobricks Counts
 View Profile  See their activity

  • Posts

    1,356

  • Joined

  • Last visited

 Content Type 

Everything posted by SylvainLS

  1. SylvainLS
    I didn’t test all the bricks (about 1700), just a few that work and a bit more that don’t. The ones that work are orthogonal (±0.0005). I also opened the file in LeoCAD (to be sure of the line numbers): LeoCAD has some troubles matching the mouse with the parts. (LDCad has no problem.) The first brick (works): [ [-0.304, 0.31, 0.901], [ 0.002, -0.945, 0.325], [ 0.953, 0.1, 0.287] ] Very similar to the examble above, but this one is a rotation matrix. I fear your “flipping” doesn’t transform a rotation matrix into a rotation matrix.
  2. SylvainLS
    Thanks for the file. As I surmised, the offending parts are wrong in the LDraw file. A rotation matrix should be orthogonal (M x Mt = Identity = Mt x M) and its determinant should be 1. As we’re working with floating point numbers, we have to be lenient but, take any of the parts’ matrices, e.g. line 2057 (9 last numbers are the rotation matrix): [ [-0.304, -0.31, -0.901], [-0.002, -0.945, 0.325], [-0.953, -0.1, 0.287] ] If you multiply this matrix by its transposed (mirror by the diagonal / colums become rows), you get: [ [1.000317, 0.000733, 0.062125], [0.000733, 0.998654, 0.189681], [0.062124, 0.189681, 1.000578] ] which is far from Identity (almost 1 on the diagonal (which we have here), and almost 0 everywhere else (which we haven’t)). Naughty LDraw file
  3. SylvainLS
    Oops. Naughty copy+paste I continue to think the transformations are okay because, mathematically, they can’t be wrong: If a 90° rotation were missing for these parts, it would be missing whatever their LDraw position and orientation. They can’t work sometimes and not others, and they work on all the examples I can get or contrive. Unless either 1. the times they don’t work is when the LDraw matrices aren’t rotation matrices or 2. LDD does something strange (like using Euler angles and falling into a gimbal lock, which would be terminally stupid considering LDD uses matrices and quaternions everywhere else). So, again, unless someone is willing to give me examples of LDraw matrices that lead to wrongly imported parts, I can’t do anything but repeat I have nothing to fix because nothing is broken.
  4. SylvainLS
    Update 2017-08-01 Added: 24130 / 24130.dat Hemisphere 4 x 4 x 1.667 Bottom with Faceted Inside 24132 / 24132.dat Hemisphere 4 x 4 x 1.667 Top Ovoid with Faceted Inside md5sum: 6a6303924da9d84de260c1786239c721
  5. SylvainLS
    LeoCAD works with the official complete.zip file, or you can point LeoCAD to a directory (e.g. “Custom Parts Library” in View|Preferences…|General (first tab) or see the other ways on the web page). http://www.leocad.org/docs/library.html
  6. SylvainLS
    I don’t import much (only for testing purposes), but I’m guessing some of the red parts are marked only because of collision errors (that is, there are correctly placed and orientated but collide with each others), no? Could you (Renderbricks or legolijntje), make a small model, try it and send it to me? (A few parts of the nose maybe?) Anyway, if it’s because LDD can’t handle some peculiar input or “simplifies” or “normalizes” too much, I don’t think there’s much that can be done ldraw.xml-wise
  7. SylvainLS
    As my IRL name is Herlock Sholmes, I infer that you’re trying to import an LDraw Star Wars UCS Whatever into LDD and that doesn’t go smoothly. Furthermore, the model and my more than human eyesight tell me the red parts, the naughty ones, are pretty common plates and wedges, whose transformations are pretty straightforward and well-tested. So, to understand what happened and if it can be fixed: Did you try with the version of ldraw.xml included with LDD? If no to 1, please try. If yes to 1 or after trying, does it work better? How did you build the model? With a “mirror” tool? Could you send me the offending model, or part of it, or a smaller one giving similar results? (Either a link here, or in a PM, or in an e-mail (address in the ldraw.xml file), or a link in a PM, or a link in an e-mail, or smoke signals… er, no, not smoke signals. And no avian carriers either: they’ll be eaten with small peas.) Thanks.
  8. SylvainLS
    Update 2017-07-28 Added: 10312 / 10312.dat Windscreen 6 x 10 x 3 with 1 x 2 x 1 Cutout - Ovoid 21709 / 21709.dat =Excavator Bucket 6 x 3 with Click Hinge 2-Finger Corrected: 50986 / 50986.dat Windscreen 6 x 10 x 3 Ovoid Rematched: 4287 / 4287b.dat Slope Brick 33 3 x 1 Inverted with Notch and Thin Front md5sum: 2d54122bc38398f97e510dca4f7e972e
  9. SylvainLS
    Welcome! You can check the index on the first page of this very thread.
  10. SylvainLS
    Update 2017-07-10 Added: 20693 / 20695.dat Minifig Pumpkin Carved 30380 / 30380.dat Minifig Helmet SW Mandalorian with Rocket Pack md5sum: 1881492c3f302a520193d0ebe916b11a
  11. SylvainLS
    Update 2017-07-03 Added: 98969 / 98969.dat Minifig Cleaver 98383 / 98383.dat Minifig Oil Lamp md5sum: 0913e89bead2f73f0b42c7fa7375afc7
  12. SylvainLS
    I just built one of my models. Oh boy! Those pesky hinges! Some are too strong and prefer snapping out to hinging, and some are too weak and the #@! thing won’t stand up! That kind of thing in a free CAD? Not for tomorrow.
  13. SylvainLS
    Actually, there’re at least about 1000 parts that exist and are not present in LDraw Official and Unofficial Libraries. They are present in LDD and on digital-bricks.de (but they need work!). And I won’t even talk about decors/patterns. There’s a lot of work to do yet! What are you all waiting to join?
  14. SylvainLS
    To complete: Instructions: Blueprint makes instructions from LDD files (LXF). Snapping: Stud.io also has snapping and a “connected parts“ selection tool (and is LDraw-based). And you can easily export from LDD to LDraw (the other way around isn’t always easy though), within LDD or with lxf2ldr.
  15. SylvainLS
    It’s a secret. We don’t tell secrets. More seriously, I think (hope? I don’t want to be alone!) everyone has that problem. Even tools that check connections (LDD, Stud.io) are sometimes wrong: connections that’re not solid enough or that don’t even hold. (Not even talking about wrong models….) For instance, your axles in a brick round 2x2: LDD told me it was okay to have two pin-axles meet half-way, IRL, it didn’t hold. That’s because the axle isn’t held all the way inside the brick. Only the top of the brick holds the axle. Fortunately, I had a plate round 2x2 on top of the brick (round brick + round plate + round tile with hole = 5 plates high = 2 studs = the axles of 2 axle-pins), so I just needed to put it under the brick to hold the first pin-axle and the top of the brick to hold the second. It works for me because it’s not heavy/high and the stud connections between plate and brick is enough to hold the whole thing. I don’t think that can help you with your rocket though Anyway, after some time, you learn (by testing or looking at official models) where your models will be weak and need to be made stronger and how to do it (SNOT is great for that). You also need to not build too sturdily, too packed: that makes some parts of the build too heavy for no reason and weaken the connexions. Yeah, some Physics student will come and say it’s all computable… till they realize testing with real bricks is way easier and more accurate, besides being where the fun is
  16. SylvainLS
    Because of the way they work and communicate. When I came out of my dark ages, the MOC shop was a few months old: Apparently something no one asked for, no one needs, and no one uses. Seller tools and instant checkout are most awaited (I’m a buyer only but it’s what I get from the forum). They updated the website last year: full of bugs, missing features, still no seller tools, no instant checkout, documentation missing, no answer to questions. They just released Mosaick: another tool no one asked for, no added value relatively to existing mosaic programs, some problems (rare & expensive colors used, dimensions in inches or studs only…). They just released an instant checkout preview: missing features, a lot of unanswered questions, deployment postponed sine die. Any professional team needs a simple, efficient way for users to report and follow bugs. All we, users, have is a forum for both Stud.io and Mosaick: very few answers from admins, very few informations. (Some simple things get answers, or vague “thank you, we’ll look into it,” but the bulk of the answers is made by users. And don’t go technical on them, they don’t answer. Myself, I tried to talk to them about helping them with their (buggy) LXF import: never heard back from them.)
  17. SylvainLS
    Update 2017-06-30 Added: 18165 / 18165.dat Minifig Crown with 4 Spikes 18041 / 18041.dat Minifig Harpoon with Smooth Bar 15341 / 15341.dat Minifig Robot Arm md5sum: 6bad9c4866e24417820e43bd2567b9d9
  18. SylvainLS
    Pins just need to match. It’s the fact there’re several that confuses LDD (too many/strong constraints). You’ll notice rotation is smoother when there’s only one rotation point. And the difference between friction pins and non-friction pins is… friction! IRL, with non-friction pins, your door will fall, with friction pins, it’ll stand still, even half-open. LDD doesn’t have gravity but friction pins add more constraints to rotations.
  19. SylvainLS
    (Trying to answer to paragraph by paragraph, quoting is a pain.) When the green circle appears, it’s centered on one of the possible rotation points of the part you clicked. If you click again, the circle will cycle through the other rotation points. When your mouse pointer is on the circle, the green is stronger, dragging will rotate. A good viewing angle is necessary otherwise you won’t have precision. To rotate more finely, use the text box under the hinge tool icon. You can also enter decimal points. To pane the view, use Shift+right mouse button. There’s no mirror/inverse tool. Tiles have no stud, so no connection on top, so no way to put anything on top except by “scaffolding” (temporarily replacing the tile with a plate). You’ll notice that official models with tiled floors often have some studs mixed in, so it’s the same in real life Your bricks are all red because you’re in LDD Extended mode. Use “View / New themes / LDD” to use the simple mode. Though be aware that some bricks are only available in Extended. And the coloring and decoring of the bricks are different: You click the part to paint/decor it and a few possibilities are presented (not necessarily real-life-possible). The number of decors (and parts) in LDD is limited, and it doesn’t seem there’ll be more in the future (the last parts updates didn’t add many decors and a new is much awaited). You can group (and subgroup) bricks. Use the third tab (Bricks | Templates | Groups, on top of the bricks palette). To select a group, you have to click the group in that tab. If you click on only an element of the group in the building screen, only that element is selected. If you want to keep a group (or a bunch of parts) to reuse in several models, use the Templates tab (different templates in Extended and normal modes). Yes, unfortunately, you need to buy a new laptop or use an external display or a virtual screen (does that still exist for the newer Windows?). Hinges made with multiple Pins with friction (or multiple clips, or even mutliple hinges sometimes) are problematic: Even if LDD manages to rotate around one of the pins, the other pins don’t have the exact same rotation. Sometimes, it’s just a few decmals, sometimes, it blocks the whole hinge or makes strange things happen. My solution: (save the model) remove all pins but one, rotate, put the pins back.
  20. SylvainLS
    That’s what Umbra-Manis talked about in the 2nd post. If it’s a bug in LDD, LEGO won’t do anything as LDD isn’t maintained anymore. If it’s a bug in how that particular part is described, maybe in the next (most awaited) part update, but I wouldn’t hold my breath.
  21. SylvainLS
    In Extended mode, there’re two MF legs assembly: the simple one, 73200, and the one with colorable feet, 21019.
  22. SylvainLS
    Update 2017-06-19 Added: 87561 / 87561p01.dat Block 6 x 4 x 1 with Handles and Minifig Outline with Han Solo in Carbonite Pattern 90395 / 90395.dat Minifig Lifeguard Float md5sum: e9adf2b09c69489821aa278d8233290b
  23. SylvainLS
    Yeah! Just about a full week, no? Now, how about an update?
  24. SylvainLS
    Here’s what I tried to explain: setting java.library.path only works for libraries that are loaded via JNI’s System.loadLibrary, not dependency libraries (loaded via ld.so). lwjgl (for instance) is correctly loaded with java.library.path, glfw isn’t. To be precise, I used strace to track where the files were looked for: lwjgl is correctly searched and found in native first as per java.library.path, glfw is first searched in the JRE lib dirs, then ld.so.cache, then /lib/…, /usr/lib/…. So adding native to LD_LIBRARY_PATH solves the problem (quickly because LD_LIBRARY_PATH dirs are on top of the list).
  25. SylvainLS
    Known since at least 2007: http://www.brickwiki.info/wiki/LDD_developer_mode (third link in google; content is a bit outdated). For me LDD still can’t connect. I never used the Gallery, is there another way to submit?
×
×
  • Create New...