Eurobricks Vassals
  • Content Count

  • Joined

  • Last visited

About mfeldt

Spam Prevention

  • What is favorite LEGO theme? (we need this info to prevent spam)

Recent Profile Visitors

240 profile views
  1. I've played around with studio 2.0 recently, attempting to generate some instructions, but it still feels like alpha stage software. I'm running under wine on Linux, where LDD does an excellent job. Studio is dead slow, incredibly heavy on the CPU even if doing nothing, buttons that can be clicked but show no effect... unusable for anything productive.
  2. Interesting - doesn't seem to work for my current model, the "download result" remains grey. Any way to gather useful information what's wrong?
  3. So far I found way more resource hungry than LDD. It's actually hard to get it work reasonably on hardware ~5 years old. Plus it cannot handle LDD groups when importing -> no incentive to switch.
  4. I did. You can find the new version on Github. It's handling lxf just the way as it does lxfml, and additionally it checks that there are no un-grouped parts in the file! It's now however much less elegant and readable, so next I'll do some refactoring before proceeding to reporting *which* parts may be un-grouped by changing their material to something really rare in the output!
  5. OK.... thanks for the feedback! I didn't see the lxfml as a problem so far since LDD reads and writes these directly - no need to unpack or repack anything! The zip step wouldn't be over-complicated, but personally I work with lxfml anyway since they're simply more comfortable! I'll follow the idea with the executable once I've implemented more checks to enhance usability. Of course the script handles subgroups! As many as you wish... and this is actually used for creating the substeps in the BI! I tried to have LDD auto-generate BIs on finely sub-grouped models, but they didn't seem to follow the grouping in any way.
  6. Just to let everyone know, I made a python script that does exactly as proposed before by hrontos. It operates on an exported lxfml and uses the group information to create building instructions. It also directly creates a new lxfml file that can be imported into LDD, so no more copying and pasting by hand. So far, it works fine. More refinements are conceivable, such as checks that the groups are well-formed and all parts are actually in a group and only in one group. I'll get to these as the need will arise. You can find the script here: And a somewhat lengthy video tutorial how to make instructions with it here:
  7. Really! I'm curious how that could work, because for me the inability to move the camera view port renders any attempt to make readable instructions for a model of such dimensions futile
  8. And - anything you can recommend to get at least recognizable results?
  9. Newly found: PyBrick brickrake: There seem to be more interesting things out there... simply try to search for bricklink on guthub.
  10. Sorry, I don't have an answer - but I do have the same issue. And in large, complex model it's really annoying as the only solution I came across is to reduce the magnification factor for assemblies. This will put more of the complete model into view, but either tiny or at completely crappy resolution. So I second a request for being able to - either allow larger output images completely used for the model - or the ability to point the camera to a specific section. I would guess the first solution is probably easier to implement - maybe some invisible window is generated where the content is copied from and one just needs to increase the hard-coded size of that?
  11. It's about as cumbersome as it can get. It starts with the "easybuy" button, which is anything but easy. It finds a nice combination of stores and gives a quote. However, next you discover that the quote is not worth the bits its made from, because store rules imply heavy surcharges due to small lot sizes. Next come some additional charges for certain payment methods. In one case a Polish seller wanted 5% extra for paypal, where paypal already quoted a crappy Zloty exchange rate. Next you have to agree to buy without knowing the actual shipping fees - ridiculous. The site is great in principle, but totally impracticable to use. Nice design, but purchasing a large inventory from different stores is not any easier than on bricklink.
  12. I just wanted to follow up and note that this was solved by making Blueprint use an updated version of the db.lif. Now I have another question: Blueprint can highlight the current parts added in a particular step. Is there any way so influence the color used to highlight? I don't particularly fancy the pink....
  13. Yep, I know there are tools out there that can do part of the job... let me maybe describe the use case: You design a model in your favourite digital design software. Next step is to generate instructions and actually build it. Now you realize there are parts in the model that actually do not exist, in 99% of the cases because of color issues. But then, replacing individual parts can actually spoil the whole design, as color is quite important! So my vision: A tool that reads the model file (lxf or ldr), comes up with a list of all parts unavailable due to color (I know this exists) When clicking on a specific unavailable part, it shows all the other parts in the model of the same color. In the resulting list, I can mark parts that I want to be of the same color The tool comes up with a suggestion of colors that are available for *all* the parts now selected The tool modifies the source file. Of course I can do that already, but with a combination of tools, and usually the "modify the source file" part is pretty tedious and must be done in the design tool.
  14. Yes, but simply buying the parts is not the goal. I'd ultimately like to modify the lxf-files to only contain parts that are actually available. In this way I hope to get around the gaps that usually occur when exporting to ldraw, or devising building instructions. Sigh, I guess I'll have to make my own attempt then.
  15. Just about to start work on something similar, I could as well ask here: What about checking the availability of a part on bricklink? Mostly in terms of color - and if unavailable, list the available colors? As a very advanced feature: Find all parts with the same color, and check in what *common* color they would all be available on bricklink...