legolijntje

Members
  • Content Count

    738
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by legolijntje

  1. I was actually kinda surprised that this option is not available. I could've really used it this morning. I'm voting for this too
  2. Green:https://rebrickable.com/parts/92547pr0018/turntable-6-x-6-round-dark-purple-base-with-trans-bright-green-top-and-glow-in-the-dark-opaque-skulls-on-dark-gray-print-ninjago-spinner/ Purple: https://rebrickable.com/parts/92547pr0017/turntable-6-x-6-round-trans-purple-base-with-trans-purple-top-and-black-and-white-print-ninjago-spinner/
  3. I believe the stud.io importer was recently updated so maybe you don't need any workarounds anymore. But I'm not sure about that, I don't use stud.io.
  4. For me it looks perfectly fine. I have enough in my inventory for all the Any Color parts Kinda unrelated, but I just had a thought: @Nathan is the system smart enough to give priority to colored parts when calculating building percentage? E.g. if a MOC uses 6 2x4 bricks in red and 6 2x4 bricks in any color and I happen to have 6 2x4 bricks in red it should give priority to the red parts and not the any color parts. Does it do that?
  5. The most popular CAD tools nowadays are: LDD LDCad Stud.io LDD is made by LEGO itself, though it's not really maintained or updated anymore nowadays (it does sometimes get a sudden Brick update). It has brick-snapping and collision detection which makes it really easy to use and learn, but it can sometimes be a pain to work with (especially with more advanced models and Technic models) due to that same system. Cause it's a proprietary system there's not a whole lot of tools that use the LDD file format (but there are a few). LDCad is based on the LDraw parts library which is open-source and thus has many, many more parts than LDD. LDCad has become the go-to LDraw CAD nowadays (there are many more such a MLCad, LeoCad, BrickSmith etc. etc.) because it's modern, fast and has brick-snapping (no collision detection though). The opinions about the UI are mixed; some hate it, some don't mind at all. LDCad does have a steeper learning curve than LDD or stud.io but it's also more advanced. The file-format is open source and thus there are a bazillion of tools out there that support the LDraw format. Stud.io is the new kid on the block. It's made by Bricklink and is a hybrid between LDD and LDCad (or any other LDraw CAD). It has both brick-snapping and collision detection and it can connect with the Bricklink database to show which parts exists in which colors and what the price is. The file-format is a bit weird though. It is proprietary, but based on LDraw. The .io files itself can thus be easily exported to LDraw. If you want to build Technic models, I'd recommend you use either LDCad or stud.io with my personal preference going to LDCad (disclaimer: because I'm using LDCad and all other LDraw tools for years and years now :P). In the past, there was a great tool called SR3D-Builder. It was a bit like LDCad, but its main focus was (Technic) simulation. You could move gears, open doors, extend/retract pneumatics etc. etc. It was a great, great tool! Sadly the author passed away a couple of years ago 😥
  6. Looks like it isn't real Lego; there is no 'LEGO' written on the top of the studs. Does it say LEGO anywhere else on the part?
  7. legolijntje

    LDraw line images

    Nice! It does about 2-3 parts per second for me Btw, if you want a little 'rounder' studs you should up the curve quality in LDView a bit. Feel free to share it, no problem, but note that it's untested and optimized code. Like I said, the best idea is probably to use LDView's builtin batch functionality
  8. legolijntje

    LDraw line images

    You certainly can. Not sure if you can set all options through parameters, but there's always the option to pass your own .ini file with parameters which can include any setting. Ugh, no idea why. I shouldn't have included those threading stuff without having used it before Try this one without any multi-processing: import glob import subprocess LDRAW_PATH = 'C:/Users/Merlijn/LDraw' LDVIEW_PATH = 'C:/Users/Merlijn/LDraw/Software/LDView/LDView64.exe' OUTPUT_PATH = 'E:/tmp' MAX_WIDTH = '200' MAX_HEIGHT = '200' PART_COLOR = '0xFFFFFF' # Color format standard HEX RRGGBB def main(): ldraw_part_paths = glob.glob(LDRAW_PATH + '/parts/*.dat') for path in ldraw_part_paths: part_number = path.rsplit('\\', 1)[1].rsplit('.', 1)[0] print(part_number) subprocess.call([ LDVIEW_PATH, '-AutoCrop=1', '-SaveWidth={}'.format(MAX_WIDTH), '-SaveHEIGHT={}'.format(MAX_HEIGHT), '-DefaultColor3={}'.format(PART_COLOR), '-SaveSnapShot={}/{}.png'.format(OUTPUT_PATH, part_number), path ]) main() I think LDView's own batch feature is probably better than such a script anyway, but I couldn't quickly find its documentation
  9. legolijntje

    LDraw line images

    Yeah, I suppose you could
  10. legolijntje

    LDraw line images

    Ok, I made something that goes through ALL your LDraw parts and renders an image for it. The only stuff you need to change are the CAPS variables at the top. Also note that I tried multi-threading which I've never done in Python. It seems to work, but I'm not sure if it actually makes the thing go faster You can define the number of threads yourselfes. Note that I made this one real quick and there's little testing or optimization of whatever import glob import subprocess import threading LDRAW_PATH = 'C:/Users/Merlijn/LDraw' LDVIEW_PATH = 'C:/Users/Merlijn/LDraw/Software/LDView/LDView64.exe' OUTPUT_PATH = 'E:/tmp' MAX_WIDTH = '200' MAX_HEIGHT = '200' PART_COLOR = '0xFFFFFF' # Color format standard HEX RRGGBB THREADS = 1 def create_chunks(seq, num): avg = len(seq) / float(num) out = [] last = 0.0 while last < len(seq): out.append(seq[int(last):int(last + avg)]) last += avg return out def worker(paths): for path in paths: part_number = path.rsplit('\\', 1)[1].rsplit('.', 1)[0] print(part_number) subprocess.call([ LDVIEW_PATH, '-AutoCrop=1', '-SaveWidth={}'.format(MAX_WIDTH), '-SaveHEIGHT={}'.format(MAX_HEIGHT), '-DefaultColor3={}'.format(PART_COLOR), '-SaveSnapShot={}/{}.png'.format(OUTPUT_PATH, part_number), path ]) def main(): ldraw_part_paths = glob.glob(LDRAW_PATH + '/parts/*.dat') chunks = create_chunks(ldraw_part_paths, THREADS) threads = [] for i in range(THREADS): t = threading.Thread(target=worker, args=(chunks[i],)) threads.append(t) for thread in threads: print('starting thread') thread.start() main()
  11. legolijntje

    LDraw line images

    I never really took a look at the batch feature. I believe it's also pretty new so there might be a lack of documentation and examples. I can take a look when I get home. Alternatively, you can just create a super basic Python script that runs through all your LDraw parts and calls LDView for every part separately. Should be pretty simple, only a few lines.
  12. legolijntje

    LDraw line images

    EDIT 2: wait a minute. I misread the question the 2nd time. First time was right. I'm tired, I'm going to bed
  13. legolijntje

    LDraw line images

    EDIT: Whoops, I misread the question. I thought it was for singular parts. For a coloring book, I would recommend the same settings is above, except: Always black lines Show edges only That way you get a white image with black lines:
  14. legolijntje

    LDraw line images

    You can batch-render LDraw parts yourself with LDView. To get a proper, good line look like they also kinda look in LEGO instructions use the following settings: Tab General: FSAA: 8x or 16x (depending on your hardware you can't choose 16x) Antialiased lines: ON Background color: White Field of view: 0.1 Tab Geometry: Edge Lines: ON High Quality: ON If you want, you can turn Always black ON too. I personally don't. You gotta experiment a bit with Thickness. It's dependent on your final image size what looks best. I generally use the 2nd notch (from the left). Tab Effects: Lighting: OFF Tab Primitives: Primitive substitution: ON Curve quality: whatever you like. Since the goal here is small images, it probably doesn't need to be very high but if you're rendering single parts the processing time is probably negligible. Use hi-res primitives when available: ON ------------- Furthermore, the LDraw -> Blender plugin I linked a week or so ago also has a line option I believe, but not entirely sure about that.
  15. Are you sure 'Star Destroyer' is an official trademark though? I can't find any European trademark on boip.int and on the global search engine wipo.int I can only find a US trademark (which can also be found on US trademark database uspto.gov ). But that one US trademark has been cancelled/rejected in 1989 👀 Furthermore, that one trademark is in category 022 for 'Games, Toys & Sporting Goods' and if you'd be very literal, building instructions (without any bricks) alone aren't toys 😜
  16. When I add parts to a Bricklink wanted list (using the automatic API version, not the manual export/import) from a custom list, all parts are doubled. I have a list with 391 lots, after adding to wanted list the popup shows 'Added 780 lots to wanted list'. When going to Bricklink, there's a looooong warning that I have double lots in my wanted list which is not allowed. The warning is so long, cause it lists all doubled parts which is essentially the whole list Side question: which Rebrickable color exports to Bricklink's 'Not Applicable' color?
  17. I really like the ability to share custom lists. Great feature! However, when someone views a shared list of mine, he/she can see all my shared lists in the left sidebar. That's a little less great in my opinion. It would be nice if that can be (optionally) turned off so that someone looking at one of my shared lists can't see the other shared lists.
  18. Now you mention it, I can vaguely remember using LdSetsConversion a few years ago. But I forgot about it, completely missed it on the peeron_to_MLCad site too When googling it, I even found posts from myself on the LDraw forums. Thing is, it converts to LDraw and not to LDD which the original question was. Of course, you can import LDraw into LDD, but in that case you gotta be sure there are no clashing parts. There is a native Linux version available, so you don't need Wine right? But, I'm not really a Linux guy, so what do I know? It's completely off-topic anyway.
  19. Not really. The pbg files are only a parts list. So you can build a model in LDCad using a limited number of bricks (for example if you want to build an alternate model, or if you just want to digitally recreate an existing model). There isn't a way to turn that list into an LDraw model. LDD Manager used to be able to turn a parts list into an LXF file, but that software has been abandoned. There is (was) also peeron_to_MLCad which creates an LDraw file from a peeron inventory, but A: that software is ancient by now and B: Peeron is ancient too Ah well, this is all a bit useless. It should work on Linux though... If you have any problems, you can always come by the LDraw forums to ask for help
  20. Oh, now I see. I Didn't notice the difference between the text and the link. I already fixed it yesterday myself anyway. Thanks!
  21. Rebrickable part 973c17 is/was a bit wonky, but the Bricklink ID is not 973c73. 973c73 is DBG, which is this one: https://rebrickable.com/parts/973c44/
  22. I believe this has been discussed by the admins before. And If I remember correctly it was agreed it would be a nice feature, but there was some disagreement about the (technical/under the hood) implementation. But don't quote me on that
  23. legolijntje

    Plan ändern

    I can imagine that is pretty annoying. I think @Nathan should take a look at this.