legolijntje

LDD Regulator
  • Content count

    2962
  • Joined

  • Last visited

3 Followers

About legolijntje

  • Birthday January 22

Profile Information

  • Gender
    Male
  • Interests
    LEGO of course, mostly technic.
    I also like digital things, like LDraw, making building instructions etc.

Extra

  • Country
    The Netherlands
  • Special Tags 1
    http://www.eurobricks.com/forum/style_images/tags/ldraw_indexer.gif
  • Special Tags 2
    http://www.eurobricks.com/forum/public/style_images/tags/technicgear2.png
  • Special Tags 3
    http://www.eurobricks.com/forum/public/style_images/tags/technic_pneumatic.png
  • Country flag
    http://www.eurobricks.com/forum/style_images/flags/dutchflag.gif

Recent Profile Visitors

3315 profile views
  1. Help with Digital Renders

    You can import LDD files into mecabricks and then use the Mecabricks Blender plugin to create renders or use the (paid) Mecabricks online rendering feature to create renders super quick on their rendering farm. Mecabricks renders are by far the best renders I've seen so far in my opinion.
  2. [MOC] Executor class Star Dreadnought

    Nope, you're right. I misinterpreted the software.
  3. [MOC] Executor class Star Dreadnought

    I believe it's about 50cm.
  4. Constrictor II - Imperial Interdictor (w Instructions)

    That's because I fixed the rebrickable link ;)
  5. Online Rendering

    You can also build a model in LDD and then import it into Mecabricks. Maybe best of both worlds?
  6. It also feels a lot faster and more responsive to me, but not sure if that's a placebo or not
  7. Sounds interesting! Do you have any more information on that?
  8. https://www.bricksafe.com/pages/afol1969/Instructions
  9. Hmm... I only recently used this technique, but it was on a very big model. I did notice that I had to manually adjust the placement of the assembly image because it seemed cut off a little bit too much. I think it was actually the same problem as yours, but I didn't really experience it as a problem due to the size of the model. And maybe it really isn't a problem with cutting off too much, but only a placement problem (pretty stupid nonetheless). When you place the assembly so that the cut lines up with the bottom of the page, that is the true placement. Then there's a lot of whitespace above the assembly, which means you can place your random brick closer to the model. Move closer until enough of the model is visible. Then move the assembly again so that the cut lines up with the bottom of the page and optionally copy/paste the placement to any next steps. If that makes sense Yeah, that's true. And for me personally, only LDCad and LPub3D have to support it. I don't use buffer exchange in any other programs. That sounds doable to me
  10. Both things can be done with LDCad + LPub3D, but are a PITA to do and are more of a hack than a real 'feature'. For the first one, you can use buffer exchange like you use it with arrows. But, instead of an arrow you add a ring (I usually use ring10.dat from the official library, scaled up). It's very frustrating to place the ring in the correct spot though and it requires a bit of trial and error (and swapping between LDcad and LPub3D) to get the circle in the correct spot. The 'hack' for the 2nd question is a little easier to implement, it just creates a mess in your file. LPub3D always zooms in on the center of the assembly image. So... the trick is to replace the center of the image. To do that you can place a random brick far far away from your model (in the direction you want to move the center of the image). I usually have to place the brick 1000-2000 LDUs away. You obviously don't want the random brick in your parts list or permanently move the image-center, so you have to wrap it in some buffer exchange. Then, the center of the image has been replaced and you can zoom in (scale) in LPub3D. It's pretty easy to implement, but it gets annoying when you want to use this trick on multiple consecutive steps: you have to repeat the buffer exchange for every step. It's not a lot of work (just copy/paste), but it creates a god-awful messy file. If only someone would ever create a new version of buffer exchange, so much things would become easier. The only thing we'd need is something like a 'buffer exchange end' command to tell the software where the buffer exchange ends. Then you could place a buffer exchange in step 10 and retrieve it in step 20 without constantly store/retrieving the same shit on every step. Then the software would know that steps 11-19 aren't part of the buffer exchange. Oh, and cross-submodel buffer exchange would be nice too
  11. Just to make clear to anyone reading this and willing to help out, the problem has already been solved on the LDraw forums
  12. You should be able to (re?)download them from sellfly. But @Raskolnikov knows more about that, so if it doesn't work you should send him a message
  13. Yup, 1.31 is the latest version. And, there isn't any news about the Interdictor yet
  14. That was indeed a problem in the earlier instructions, but it has already been fixed in version 1.3