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
    Which doesn’t make copyright and pattents laws disappear. Which is what I meant by “except for interoperability purposes, in some countries.” The original comment has been hidden, but it talked about disassembling, modifying and redistributing a program, which is totally illegal, anywhere (unless expressly/explicitely stated in the licence). Nevertheless, the second point (difficulty) was my main point.
  2. SylvainLS
    Two main problems with that: First, legally, you don’t have any right to disassemble a program or study its operations (except for interoperability purposes, in some countries), even less modify it and even even less redistribute it. You know, copyright and pattent laws, and that EULA thing you accepted when you downloaded it? Second, disassembling doesn’t give you the source code, it gives you the assembly code. When the source code says something like “benefits = revenues - expenses,” the assembly will say something like “take the value in memory cell #23445 and put it in register A, take the value in memory cell #34566 and put in register B, substract registers A and B, put the result in memory cell #45624.” Now imagine that for something as complex as LDD…. (And I won’t even talk about obfuscation techniques that make all that even less understandable.) Even if tools can help you see some assemblies (blocks, parts), you lose too much information. Disassembling a program like LDD is like exploding the Eiffel Tower into bolts and beams, or rather, it’s like having a million “there is a 3001 brick in red at coordinates X,Y,Z and rotated this and that” instead of a nicely printed 10000-pages instruction manual . A better thing to do is mimic the program: understand the file formats and use them, and get inspired by the UI (but beware round corners pattents ) So, adding LXF support (if legally possible) or part-snapping or collisions in existing Lego CAD programs (LDraw-compatible or not) or improving their UI would be an easier and quicker path.
  3. SylvainLS
    The shift is very very small. It’s smaller than the difference between a “proper” SNOT brick and a technic brick with a 4274 peg w/ stud, and that construction is used in official sets (even with bricks on top, which should be forbidden). I think you need a tortuous mind to manage to use a lot of them in a way that compounds the shifts sufficiently to have a problem. With 16 of them in a “row,” the shift is visible but I still can bridge the gap (the red tile): Or, in less words, I’d really be interested in an example.
  4. SylvainLS
    Well, since you succeeded, it’s kind of a moot point, but for the sake of precision, that was my mistake: it’s an LZMA2 archive, so .xz should be the right extension. (Still, either your extractor doesn’t know what LZMA2 is (and is obsolete), or it’s stupidly hellbent on file extensions. )
  5. SylvainLS
    Self-extracting archives are archives. The only problem you might encounter is the program you use to extract not recognising the extension. So, just change the extension to zip.
  6. SylvainLS
    There were 5x Blue 4598 in Benny’s Spaceship, Spaceship, SPACESHIP! And, according to Bricklink, these past years in Star Wars, Ninjago and Swamp Police. They also were in the last real space theme of 2013: Galaxy Squad. They say memory is what goes first
  7. SylvainLS
    As far as I know, you can’t do that in LDD. And you shouldn’t do it with real bricks: that stresses the pegs’ ends too much.
  8. SylvainLS
    Sorry if I offended you. I just wanted to make things clear by purposefuly quoting only the part that I think misguiding. Starting with “Just an installer” is ambiguous: 0. “Installer” means “Windows only program” (or, at least, “archive with bells and whistles that needs special programs to extract (when not on Windows)”). 1. As you just repeated, you state the opposite just after. 2. That’s the first thing you say, a short sentence that’s understood as a sum up of what you say after (which is the opposite), so it’s what stays in memory, especially for people who’ll just skim the forum in search for a quick answer. As you say, the question was about clarification, I wanted to warn you about that ambiguity/imprecision in your answer. Again, I’m sorry if my tone or phrasing didn’t carry my purpose and offended you.
  9. SylvainLS
    Please, don’t call it an “installer.” “Auto-extractible archive” is way less ambiguous. In the Windows world, “installer” refers to an installation (and uninstallation!) program (Winshield, CABs and whatnots).
  10. SylvainLS
    For the background color, check that you have this in your scene.sc: background { color { "sRGB nonlinear" %BACKGROUND_COLOR% } } That’s because the field is for the number of steps (or images), not the angle (in degrees or radians or grades or whatever). This option is to help make “360°” animations of your model. That’s just a documentation problem
  11. SylvainLS
    Darn those tiny fonts with Wine
  12. SylvainLS
    I’ve never heard about a BoM inside LDD. I don’t use the Instruction mode often, except to have a little fun: it’s way off even for simple builds. As for the hinge tool, I’d rather compute the right angles myself and use the rotation tool. The hinge tool tends to move every parts (try closing a simple triangle, all segments are moved even a baseplate). Sometimes, it even rotates hinges that have no relation to the ones you try to connect.
  13. SylvainLS
    I mean: save the file, then reload it (or restart LDD altogether). If you only save the file and continue editing, the values still in memory are the one that cause the crash. Also, I should have said “works… sometimes.”
  14. SylvainLS
    LDD is just plain crashing. I figure it’s something like an uncatched “divide by zero” while it tries to solve the angles. It also happens with the simpler rotation tool. Simply retrying just after restarting LDD and reloading the file works. (I think that’s because saving/loading truncates the values so they are slightly different and that changes the equations and avoids the error.) So, always save your work before trying a complex operation.
  15. SylvainLS
    Plus, again, what does “update” mean? If it’s about LDD 4, the software, well, we already knew or assumed that (apart from hopes for an LDD 5 because of Worlds). If it’s about the parts, well despite the fact that they haven’t been updated in a while and our hope is dwindling, objectively, we still don’t have any unequivocal/unambiguous answer.
  16. SylvainLS
    White is called “White” (#1). Black is called “Black” (#26). Other “basic” colors have fancier names: red is “Bright Red” (#21), yellow is “Bright Yellow” (#24), blue is “Bright Blue” (#23), green is “Dark Green” (#28) (here was the catch), dark grey is “Dark Stone Grey” (#199), and (light) grey is “Medium Stone Grey” (#194). I think that’s all the “basic” colors (of your childhood?). Some less basic but often used/found: “Reddish Brown” (#192), “Bright Orange” (#106) and “Brick Yellow” (#5) (tan color). Oh, if you want the greys and brown from before 2003-2004, they are available in the extended mode, under legacy, as “Grey” (#2), “Dark Grey” (#27) and “Brown” (#217).
  17. SylvainLS
    Yes, I missed them, I already flogged myself after Superkalle corrected my mistake: I suppose I should have made my autocritique public.
  18. SylvainLS
    Latest LDD is 4.3.8. Latest brick update is 1564.2. You can see the versions in Help | About (F3), top right. The last brick update dates from october 2014 (I think). Yes, they are automatic but we’re fevrishly waiting for a new one: http://www.eurobricks.com/forum/index.php?showtopic=108005 As for the technic panels, they don’t seem to be available (yet… or ever). Welcome to LDD.
  19. SylvainLS
    Great! Keep on the good work
  20. SylvainLS
    Hi! I just noticed plates 4x10 and 6x8 don’t have logo on studs.
  21. SylvainLS
    The paint tool works differently in “LDD” and “Extended” modes. In the “Extended” mode, you have the secondary toolbar where you have: paint tool | color | pick | decorate Click on “paint” and click on a part (yes, one by one) to apply the color shown in “color.” Click on “color” to select a color from a palette. Click on “pick” to select the color of a part in your model (the selected part then “pulses”). Click on “decorate” and click on a part to have a dialog with the available decors for that part (nothing happens if the part can’t be decorated). In the “LDD” mode, you click on a part and a dialog appears with the part in the available colors and decors for that part (the current color is not shown, the order of the colors changes with the current part (nearest colors first, I think)).
  22. SylvainLS
    I was about to say it’s doable just before I saw your update. You want rules… eh, an observation first: your 1st floor has lots of studs on top, ground floor has tiles; LDD seems to prefer to connect the 1st floor under the ground floor because more studs will connect. So for a first rule: try to have more studs where you want the connection (hide the offending anti-studs or place tiles). For the view angle, sometimes, LDD is more inclined to place on top if you look from the top, sometimes, LDD prefers you to look almost horizontally…. Another note: you can grab the selection by any of its bricks, so this particular brick is under the mouse and easier to place.
  23. SylvainLS
    You need at least Java 8.
  24. SylvainLS
    Maybe you can try to update sets to the latest version?
  25. SylvainLS
    No problem with physical bricks. A little friction when the roof is rotated from a vertical position but not enough to pull the wall or hinges or to separate bricks. (I’ve the set but that’s also easy to test without it.)
×
×
  • Create New...