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
    LDD doesn’t want to rotate bricks that are connected at both ends. (Rotate tool has no effect. The bricks are blocked.)
  2. SylvainLS
    2 ways (one that can work elsewhere, the other, simpler, that will work there but not necessarily elsewhere): 1. Put the brick to rotate without the plate. Rotate it. Elsewhere, prepare two plates, one a plate-height higher. Select these two plates together to put one on top of the rotated brick and the other one on the longer plate behind (hence the height difference). Grab the selection by the plate that will end on the longer plate behind. (If you grab the selection by the 1x1 plate that goes on the rotated brick, all the selection will rotate to match the rotation.) 2. Remove the longer plate behind, rotate the brick, then rotate the plate, then replace the longer plate behind. Happy Big Ben building ;)
  3. SylvainLS
    A stud or an axle can fit in the center tube. I’d use an axle, then a 2x2 round plate…
  4. SylvainLS
    Sure, should have done that first. Here it’s: radiosity { pretrace_start 64/image_width // 64/image_width pretrace_end 4/image_width // 4/image_width count 800 // 800 nearest_count 20 // 20 error_bound 0.2 // 0.2 recursion_limit 1 // 1 low_error_factor 0.7 // 0.7 gray_threshold 0 // 0 minimum_reuse 0.005 // 0.005 brightness 1.0 // 1.0 adc_bailout 0.01/2 // 0.01/2 normal on media on } (I keep “default” values in comments to remember where I started when I tweak them ) It’s almost Radiosity_Final, with nearest_count increased and pretrace_* adjusted to image_width (as per comments in Povray’s doc). I assumed Povray’s defaults were tuned to 800x600 (pretrace_start of 0.08 for 800 = 64/image_width). One day (or rather, one month), I may try to better fine tune it to speed it up….
  5. SylvainLS
    Try lowering pretrace_end. Values have to be tweaked according to the model (e.g. an all white model needs lower value than a darker one). I generally use 4/image_width for pretrace_end (~0.0005 for 1920x1080) but can lower it to 1/image_width (~0.000125) with an all white, shiny model. (pretrace_start of 64/image_width; but my count is at 800 only and other values differ from yours.) I started from Povray’s predefined settings but finding the right values is difficult and tweaking the wrong one may greatly increase rendering time without real difference in the results.
  6. SylvainLS
    LDD’s instructions are awful (even for small MOCs): parts that are inserted too late, no sub-model…. The amount of work needed to trick LDD is better spent with Blueprint or LPub3D.
  7. SylvainLS
    Update 2017-01-28 Added: 16477 / 16477.dat Windscreen 16 x 8 x 6 Curved with 3 Pin Holes md5sum: 6c56659a358e2163e3bf3be9f6b36e80
  8. SylvainLS
    Update 2017-01-17 Added: 94161 / 94161.dat Window 1 x 2 x 2.667 Shutter with Rounded Top md5sum: f335240105b9f065590f06a8027eeaec
  9. SylvainLS
    Be prepared for that to happen again: Philo has the good habit to look here for missing parts to create.
  10. SylvainLS
    Yes, the lever is 73587 MINI ANTENNA in LDD. It’s an assembly of two subparts, 4592 ANTENNA, BASE and 4593 ANTENNA, MAST. You can’t separate an assembly’s subparts directly in LDD. What you can do, though, is place an antenna in LDD and then export in LDraw (using the right ldraw.xml, for example mine: http://www.eurobricks.com/forum/index.php?/forums/topic/137193-more-up-to-date-ldrawxml-lddldraw-conversion-file/ ), move the subparts with an LDraw program (for example LDCad), and then import the result in LDD. Exporting “separates” the subparts (so that they can move/rotate in LDraw). And importing will re-pair the subparts. If you decide to move a base (or a mast) in LDD, the other subart (resp. mast or base) will also be moved. So you need to move them in LDraw. You can’t totally remove a subpart. You need to move it out of sight. I think there’s also some trick to color the unwanted subpart in an invisible color….
  11. SylvainLS
    The b was added when I went over all the parts, back in September or a bit before. I had a little program that searched LDraw IDs that could match LDD’s IDs. I then chose between the available variants. Generally, the -b variant is newer than the -a one, so that’s the one that was chosen. I wasn’t thorough enough then to verify it was actually correct. Actually, I still don’t know if it’s correct as LDraw is the only one having variants for 3665. Anyway, I can change it to 3665a but not to 3665, as 3665 is renamed “~Moved to 3665a” in LDraw Unofficial, which is my reference. And as 3665a is, like 3665b, only in Unofficial, it won’t change much either way. Not a maybe. Parts like hinge plates are two different parts, else you wouldn’t be able to move them separately (hinge them). LDD calls them assemblies and the subparts are what is exported to/imported from LDraw. LDraw doesn’t allow you to move subparts/parts-of-a-submodel, so we have to import/export them as separate parts. Same goes for minifigs parts. For example, the LDD minifig standard torso is an assembly that is split up in 5 parts: 2 hands, left and right arms, and torso.
  12. SylvainLS
    Will certainly do. Thanks! (And thanks for the explanations, I had forgotten there was a Mac version ) 24316, and 48729b are in the Official LDraw Parts Library as of version 2016-01 (that’s the first (and last) update of 2016, dated December 31st). 15207, 3665b, 92582, 24299, and 24307 are still Unofficial parts for now. There’re other parts that are not available on LDraw.org but make-dos are available at digital-bricks.de.
  13. SylvainLS
    Use the hide tool: place the plates, hide them, change the bricks back, unhide.
  14. SylvainLS
    Update 2017-01-11 Added: 19215 / 19215.dat Wheel Cover 5 Spoke Thick with Edge Bolts 18990 / 18990.dat Windscreen 4 x 4 x 1.667 Canopy Half Sphere with Handle Bar md5sum: d11a8d0900d0925e28d444530b5922a0
  15. SylvainLS
    ldraw.xml is the file LDD uses to convert to/from LDraw. It’s part of LDD. So, if LDD works, you just need to replace LDD’s version (just find where ‘C:\Program Files\LEGO Company\LEGO Digital Designer\’ actually is on your disk) with the one downloaded from the link above (“downloaded,” not opened and copy-pasted or whatever else that could mangle the file; there’s an md5 for the latest version in the latest comment in the thread).
  16. SylvainLS
    Have you tried with my updated ldraw.xml conversion file? But note that in LDraw, technic holes are not placed correctly (they are at the same place as side-studs, too low with respect to reality) whereas, as you experienced, in LDD, they are placed higher (a bit too high with respect to reality), so pins are exported as LDD places them and end up not centered in the technic holes in LDraw.
  17. SylvainLS
    Sorry, those three parts aren’t in LDD. Out of production parts rarely are.
  18. SylvainLS
    Update 2017-01-02 Rematched: 11140 / u9081c01.dat Wheel Rim 26 x 7 with Rip Cord Gear Axle [494] and Tyre [16] md5sum: 85e7607e31310c4656e9c4a641e3a82c (LDraw’s moving fast these days )
  19. SylvainLS
    Update 2017-01-01 Added new LDraw colors (official update 2016-1). (Imported as Black for now.) Corrected: 11140 / 11140c01.dat Wheel Rim 26 x 7 with Rip Cord Gear Axle and Tyre md5sum: 7efa1f772e520e54b64d302052a08174 I don’t know. Maybe you could ask BrickLink/Stud.io?
  20. SylvainLS
    Hadn’t tried that yet. I proposed them on their forum to use my version or bits of it. No answer yet. Though, Stud.io’s ldraw.xml seems machine generated, and raw. no comment, no spaces, no order. Maybe it’s easier to them to maintain their own version.
  21. SylvainLS
    Yes.
  22. SylvainLS
    Maybe “How to add the ‘turn’ symbol (two arrows head-to-tail)?”
  23. SylvainLS
    Okay. Maybe I should go to bed now (midnight here) but “some say this” in each of your answers to my posts and our latest bout made me to assume that. Anyway, I already stated my opinion on ToS in general: overreaching CYA. I quitted using a lot of proprietary softwares because of their leonine licences a long time ago (and also because they suck ). As for BL’s uploading/publishing ToS, I don’t think they are after our MOCs, but I do think, like Superkalle just pointed, that some points are still unclear (mainly due to the nature of MOCs). Legalese is about making things cristal clear. (Or it should be. I know some (patents…) are more about obfuscating things in order to cover more and hide what should be there.)
  24. SylvainLS
    Oh come on. If something is cut, it’s because it’s too long. Because if it’s the right size or too short, it does not need to be cut. It was cut, hence it needed to be cut, hence it was too long. End of story. That it is or not still too broad is an opinion, but not the fact that it was already restricted. And as I didn’t answer to the end of your previous post, I won’t answer to the rest of this one either. My name is not “some.” If you want to accuse me of something or put words in my mouth (like you already did before in this very thread), have the courage to say so.
  25. SylvainLS
    There’s no point of view here: it’s legalese, if it needs to be restricted, that means it was too broad. That’s just fact and deduction. That they changed the ToS quickly (and had (already? I don’t know the exact timeline) said as much to Huw/Brickset (reported on their review)) is to be put to their credit but that doesn’t change the fact it was needed.
×
×
  • Create New...