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
    Hi, my first advice is purely selfish: export the model as a separate file from the scene and settings, say “model.inc” for the model and “model.pov” for the scene. For now, I’m using LDView (which works fine with LGEO) and a script to get rid of the scene’s particulars in order to use mine (ground, lights, settings…). As for radiosity, it’s really hard to tune. General settings don’t work (and are not given by official sources (apart from the presettings which are always qualified as “a start before fine tuning”)). I use these settings for HQ, that’s sloowww: pretrace_start 64/image_width pretrace_end 4/image_width count 800 nearest_count 20 error_bound 0.2 recursion_limit 1 low_error_factor 0.7 gray_threshold 0 minimum_reuse 0.005 brightness 1.0 adc_bailout 0.01/2 normal on media on For some scenes (e.g. lots of white bricks/tiles), pretrace_end can go down to 1/image_width. Else, I get artifacts (“dust” in lightly shadowed corners). The shiny nature of LEGO is at play here. I also tried “photons” to get a better feel to transparent parts. That’s not worth it: you need a lot of photons to see something a bit useful and it adds between 1 and 10 times of computation time. As for animations, I dreamt of using POV-Ray’s clock to move groups of parts but only gone so far as automating the render of different poses….
  2. SylvainLS
    You could still attach a high brick under your model to lower the “ground.” It’s more effective: the brick(s) can be higher than the wheel’s bounding box’s corner. Might even be easier to add/(re)move that brick than turning a wheel.
  3. SylvainLS
    Weirder is the fact that the “center” button doesn’t work.
  4. SylvainLS
    Same problem here. However, once exported to LDraw, all the parts are there and centered around 0,0,0. Will look into the LXF… Edit: Okay, didn’t see anything strange. I changed the camera (copied from another file) and it works: http://slswww.free.fr/GDK6_modcam.lxf
  5. SylvainLS
    New Howto! Hi all! I’ve added a howto (in the first post) for the brave ones who would want to plunge into it. Feel free to comment on how it all looks like Greek to you Edit: Okay… The forum ate a few bits and keeps mangling some of the text at each edit. I hope I corrected and foolproofed it now…
  6. SylvainLS
    Update 2016-08-13 Added: 99562 / 96910.dat Gold Ingot Corrected: 2530 / 2530.dat Minifig Sword Cutlass 4499 / 4499.dat Minifig Bow with Arrow 6126 / 6126a.dat Minifig Flame with Pegs 10053 / 10053.dat Minifig Small Sword with Curved Blade 92231 / 93231.dat Minifig Long Bow with Arrow 95673 / 95673.dat Minifig Sword Roman Gladius
  7. SylvainLS
    Update 2016-08-11 Added: 15070 / 15070.dat Plate 1x1 with Tooth Perpendicular Corrected: 2586 / 2586.dat Minifig Shield Ovoid 3846 / 3846.dat Minifig Shield Triangular 3876 / 3876.dat Minifig Shield Round 3957 / 3957b.dat Antenna 4H with Flat Top 10049 / 10049.dat Minifig Shield Broad with Spiked Bottom and Cutout Corner 64647 / 64647.dat Minifig Plume/Flame Triple 75902 / 75902.dat Minifig Shield Round Bowed 87692 / 87692.dat Minifig Plume Triple 87693 / 87693.dat Minifig Plume Small 87694 / 87694.dat Minifig Plume Large 92747 / 92747.dat Minifig Shield Oval 93251 / 93251.dat Minifig Shield Scarab 98367 / 98367.dat Minifig Shield Rectangular Curved with Stud Shields are aligned on the handle, except for 98367 which is aligned on its stud (0.008cm lower than the handle).
  8. SylvainLS
    @Philo: Do you, by happenstance, use a fat mouse lying belly up (or, rather, ball up), er, a trackball? @Roland: Thanks but I’m happy with spin mode
  9. SylvainLS
    Yes, but then, it has turned in a bad viewing angle that’s difficult (at least to me) to get out of. I end up entering the angles in the “specify latitude/longitude” dialog. Besides, I mostly use LDView to export to POVRay. And that was just an extreme example of bad usability (or bad user ). LDCad’s trackball mode in not that bad.
  10. SylvainLS
    Okay, so equivalent to using X and Y of the projection plane (aka the screen). Okay. Thanks. Your moves in trackball mode look way more controlled than mine. I don’t know if it’s because I mostly use a touchpad but trackball is always a pain to me. (Even more in LDView, where the model starts to spin by itself at a whim.)
  11. SylvainLS
    Just by curiosity: For spin, which x/y angles? Yaw and pitch around the scene’s Y and X axes? Or around the projection plane’s Y and X axes? For trackball, which vector? Or do you mean that in spin, each (sub)move of the pointer is either yaw if the submove is mostly horizontal or pitch if it’s mostly vertical, and in trackball, it’s a combination of the yaw and pitch rotations (vector = product(quarternion for yaw, quarternion for pitch))?
  12. SylvainLS
    Yep. Thanks David! Update 2016-08-09 Corrected 3711 / 3711.dat Technic Chain Link
  13. SylvainLS
    In trackball mode, if you move your mouse left, then right by (about) the same amount, you don’t end up at all as you started (before any move). In spin mode, you can more easily undo or adjust your move. I don’t know if there’re other factors at play but I just watched Ryan’s video and it’s painful to see him move around.
  14. SylvainLS
    See what I said about “overly complicated”? I build a minimal model in LDD, export it, check the results with LeoCAD, edit ldraw.xml, re-export with LDD, re-check the results with LeoCAD, rince, repeat…. Yes, there even is a thread hereabout about it. If you imported the LDD in Mecabricks and Mecabricks didn’t modify the position of the red clip to attach it to the flintlock (I don’t know if Mecabricks connects the bricks), then that means that, as LDD and Mecabricks models match, it’s the LDraw version that’s flawed.
  15. SylvainLS
    Your model will stay as it is. The snapping is for placing parts (either by moving them or new ones). LDraw tools don’t test for collisions, parts can happily overlap each others. As for IRL feasibility, LEGO bricks are made to allow for a little room between them. Also, they are more or less supple. Besides, CAD models are not always accurate. Therefore, some builds that do not appear possible in CAD tools are indeed possible with actual bricks (and vice versa). Beware though, some builds stress the bricks (prone to break or deform).
  16. SylvainLS
    Thank you for telling me about it first. Indeed, I began a howto but it’s not easy to come with the right level of details between boringly obvious and overly complicated. As for 2561, the trick I used was placing the part in LDD so that its LDraw Y axis (up) would also end up in LDraw (vertical muzzle for 2561) and attaching clips at key points on the barrel. Once in LeoCAD, I could then translate the musket so that it fit in the clips. The Y translation (actually Z in LeoCAD) becomes ty (once converted from LDU to cm). The horizontal translation is somewhat difficult because which is X and which is Z depends on the rotations, but the absolute values are the good ones, so I just try tx then tz then adjust the sign (Actually, for 2561, the horizontal translation was to be in Z because the horizontal axis of rotation was X. IOW, the part was pitched (LDD center), so its (LDraw) center moved in the YZ plane. But that’s also because both LDD and LDraw centers are on the YZ plane. So trying tx/-tx/tz/-tz is often quicker than figuring it out ) Several parts differ between LDD and LDraw. Look at 2561, the muzzle is slighty different, the stock is a bit longer in LDraw… We also discussed 92692 the other day http://www.eurobrick...75#entry2623239 Also look at the minifig arms. Totally different. I tend to think LDraw parts are wrong because parts are measured IRL for LDraw and that’s not easy to measure angles on round pieces (like MF arms) whereas I prefer to think that LEGO provided the correct geometry for LDD. But, who knows? Maybe both LDD and LDraw are wrong. An audit would be needed
  17. SylvainLS
    Update 2016-08-07 Corrected: 2561 / 2561.dat Minifigure Gun Musket 2562 / 2562.dat Minifigure Gun Flintlock Pistol 88811 / 88811.dat Minifigure Weapon Bladed Claw 88812 / 88812.dat Minifigure Weapon Hand Dagger 97782 / 97782.dat Figure Friends Cutlery Knife 98721 / 55707c.dat Minifig Batarang Thanks Theodor! For 2561: I think it only needed a sign change but I started anew and recalculated everything, and ended up with a little different translation (And I may not be consistent with what I say below for 2562 but I calculated the translation relatively to the barrel, not the stock, as the barrel is along an axis in LDraw (Y).) For 2562: There is (again) a difference between LDD and LDraw. The transformation only needed a little vertical push to be correct if the handle is the reference (as I think it should be as, most often, it’s the way it will be attached to a minifig). It’s totally off if you want to attach it by the barrel. See attached picture.
  18. SylvainLS
    The wheels don’t attach, they are wrapped around by the treads. And it can be difficult and time consuming to get the treads to attach together in a loop in the end, and to do it with the same number of treads you could do it with in real life or on what LEGO instructions say. So, when you eventually manage it: save it and remember where you put it for reuse As for your selection problem (that you obviously managed to overcome), a simple solution is to use the second selection tool (the arrow with the plus sign). It avoids the need to hold the CTRL key down. Feel free to try the other selection tools, they can be very useful.
  19. SylvainLS
    Makes sense, somewhat I’m more used to POVRay’s problems and limit Bluerender to 1920x1080 “thumbnails.” Ray tracing is good to find problems
  20. SylvainLS
    The client JVM always has a default max up to 1 GB, even if you have 16 GB or more. The server JVM has always a default max of one fourth, so 4 GB if RAM is 16 GB and so on. I only know Linux/Unix versions and server has been the default version for a long time there. Anyway, you can always set it to whatever you want, so it’s just a useless digression Now, going back to Bluerender, sunflow doesn’t use that much RAM. I never encountered RAM problems even with tens of thousands of parts to render on the 4 GB machine I use (with no Xmx option set). So checking other greedy programs might be a good idea.
  21. SylvainLS
    Note that the G suffix is also understood: 2048M = 2G. Shorter to use with nowadays memory sizes By the way, the “up to 1 GB” is valid for the client JVM. Isn’t the server JVM the default one everywhere now?
  22. SylvainLS
    Update 2016-08-05 Corrected: 92585 / 92585.dat Minifig Tool Crowbar 92107 / 92107.dat Plate 6 x 8 Trap Door Frame with Flat Clips
  23. SylvainLS
    For the colors, you can also check with Brickset’s or BrickLink’s inventories (and a conversion table for the names ). And be reassured, not being color-blind doesn’t help with the awful colors of LEGO’s instructions (especially their PDFs ).
  24. SylvainLS
    Update 2016-08-04 Added: 23996 / 23996.dat Panel 8 x 8 x 6 Rock Corner Corrected: 11295 / 11295.dat Plane Bottom 6 x 8 x 1 11301 / 11301.dat Slope Curved 2 x 8 x 2 Inverted Double 30395 / 30395.dat Hook with Towball 30396 / 30396.dat Hinge 1 x 2 Locking with Towball Socket 43122 / 46667.dat Jet Engine Fan with 10 Blades and Technic Pin 90202 / 90202.dat Technic Pin Connector Round with 4 Clips 91347 / 91347.dat Crane Jaw Curved 2 x 7 x 2.5 92402 / 92402.dat Tyre 14/ 50 x 17 with Centre Band 92842 / 92842.dat Propeller 3 Blade 5.5 Diameter with Technic Peghole and Flat End Blades 98282 / 98282.dat Car Mudguard 4 x 2.5 x 1 Rematched: 18041 / 57467.dat Minifig Harpoon 43903 / 43903c01.dat Belt 20 Tooth (Formed for 2 Wheel Rim 14 x 18)
  25. SylvainLS
    On the picture I posted, the gold 15712 is connected by LDD (no trick implied) and is correctly angled with the shaft it is connected to. All parts are. The border support and the shaft aren’t perpendicular (at least in LDD, I haven’t a real one to compare right now). Maybe the 25° angle is for the border support, not the shaft LDraw’s version of 92692 has a different angle for the shaft. The correct one?
×
×
  • Create New...