• Content Count

  • Joined

  • Last visited

  • Days Won


legolijntje last won the day on November 29 2018

legolijntje had the most liked content!

1 Follower

About legolijntje

  • Rank
    Level 6 Stud

Profile Information

  • Gender
  • Location
    The Netherlands
  • Favourite Set(s)
    852, 8043, 8285, 8455, 42009, 42054

Recent Profile Visitors

1980 profile views
  1. It would be nice if the build options include an option to exclude MOCs that are an alternate model of a real set. Just like there's an option to exclude official B models
  2. Cool! Much better indeed. Many thanks!
  3. Lately I'm often frustrated about the (lack of?) sorting of the quick-search results in the search bar. I'm not sure if this is a regression because I feel like I'm only annoyed about this for a couple of months now. But maybe I just never noticed earlier. Anyway, my problem is that search results are sorted in a weird way. For example, when I search for part 3023 (plate 1x2) this is what I get: The part that has actual part number 3023 is the 6th result (and in this case that means that I even have to scroll to see it). And this is just an example, it happens with a lot more parts that parts that are exactly what I'm looking for are not at the top of the list. I would appreciated it if the search results would be the other way around as how they currently seem to be. In my opinion, this would be the best quick-search sort-order: Part number Set number Part name Moc name Set name So, in the case of 3023 that would mean that 3023 is on top, followed by 30230 (which is currently 7th), followed by set 3023 and then set 30230 and then parts and sets containing 3023 in the name of the part. But, at the very least, I'd like to see results matching the actual part number (or set number for that matter) on top no matter the rest of the sort order. I hope that makes sense
  4. 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
  5. Green: Purple:
  6. I believe the importer was recently updated so maybe you don't need any workarounds anymore. But I'm not sure about that, I don't use
  7. 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?
  8. The most popular CAD tools nowadays are: LDD LDCad 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 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. 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 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 ?
  9. 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?
  10. 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
  11. 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)[ 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
  12. legolijntje

    LDraw line images

    Yeah, I suppose you could
  13. 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)[ 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()
  14. 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.