 | | Re: Parts editing made easy, anyone?
|
|
(...) If you look up my posts on LUGNET, you'll find that's all I've really ever talked about here. (Damn, I'm boring. Well, OK, I also talk about trucks) You've touched on the critical issues I've found over the years: - LDR/DAT files created by (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | BigBen Bricks! (Was: Parts editing made easy...?)
|
|
(...) Like, wow! Triple wow! Fisrt LCAD, and now LCAM! I wonder how expesive that could be! And I wonder if they are willing to make some custom size Classic style windows and not only train wheels! And I wish that LEGO would offer the same service, (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) Hi Stefan, yes I believe there would be interest in such a utility. And yes, I believe most people still used text-based programs to edit parts. There are tools that make it a bit easier, like LDDesignPad, but it's still basically just a text (...) (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| |
| | Parts editing made easy, anyone?
|
|
Are parts authors really using text editors to compose new parts? I find it hard to understand that a text editor is still the tool of choice for this relatively complicated modeling task. I might be wrong and could need an update on what tools (...) (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Anatomy of a POV file (e.g. L3P suggestions)
|
|
(...) When you really get into POV-Ray, you have to deal with multiple files. If you ever include a graphic as a texture, or a height field, there is nothing you can do. You can't combine an image into a text file and have it work well. If you have (...) (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Anatomy of a POV file (e.g. L3P suggestions)
|
|
(...) Hi Lars, I'd prefer that the format is unchanged. Right now LPub post-proceses the one file, greying parts as needed, adjusting camera settings for orthographic, and creating new colors for the greyed pieces.... I'd really rather *not* have to (...) (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Anatomy of a POV file (e.g. L3P suggestions)
|
|
(...) I am anything but an expert on this area, but will not the parts, 3001_dot_dat and so on, also be defined multiple times? (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Anatomy of a POV file (e.g. L3P suggestions)
|
|
(...) For newbies I think it's nice that the POV file is self-contained and ready-to-render. However, using certain coming options you can exclude camera and lights. Why would you like submodels in separate .inc files ? Only to have a smaller (...) (20 years ago, 21-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Anatomy of a POV file (e.g. L3P suggestions)
|
|
(...) Optional, yes that would be nice. But I also see the strength in the fact that all data needed are gathered in the same file. I have downloaded so many pov-files just to discover that they have references to inc files I fail to find on the (...) (20 years ago, 20-Jan-05, to lugnet.cad.dev)
|
| |
| | Anatomy of a POV file (e.g. L3P suggestions)
|
|
Here are the basic components of a POV file, as it is generated by default by L3P. Materials Color declarations Stud-tops Finishes Render-Detail Options Qual SW Bumps etc. Scene-Level Objects Camera Lights Floor Background Parts & Primitives Models (...) (20 years ago, 20-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Automated Inventory Ordering through Bricklink
|
|
(...) If you go into BrickLink's "Search", then "Find Stores", you can upload an XML file of all the parts you want, and it will find the stores which have all (or most) of those parts. There's a help file on how to build the XML file (URL) here>. (...) (20 years ago, 19-Jan-05, to lugnet.inv, lugnet.cad.dev, lugnet.cad.mlcad, lugnet.market.brickshops, FTX)
|
| |
| | Re: Automated Inventory Ordering through Bricklink
|
|
(...) Yes. the sheer number of combinations can quickly get ridiculous and it gets hard to evaluate which is "best." I cheated by making a few asumptions. I'll share them when I dig up the code, I don't remember the details off hand. -JSM (20 years ago, 19-Jan-05, to lugnet.inv, lugnet.cad.dev, lugnet.cad.mlcad, lugnet.market.brickshops)
|
| |
| | Re: Automated Inventory Ordering through Bricklink
|
|
(...) SNIP (...) Yeah I had to have a look up table for that. It was annoying but not insurmountable : ) (20 years ago, 19-Jan-05, to lugnet.inv, lugnet.cad.dev, lugnet.market.brickshops)
|
| |
| | Re: Restart of LDA2001 Project (using LDraw models - L3P - POV)
|
|
(...) The coming L3P has also these new options: -ic[<file>] no camera, optional include file -il[<file>] no lights, optional include file So, l3p -ic -il model.ldr model.inc might just do what you want, assuming you still want color and primitive (...) (20 years ago, 18-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Automated Inventory Ordering through Bricklink
|
|
(...) The problem with this (and with Briktrak) is that there are a few Bricklink parts whose numbers are not the same as the LDraw parts. There was an attempt a while back to normalize the numbering system across the main part cataloging sites but (...) (20 years ago, 17-Jan-05, to lugnet.inv, lugnet.cad.dev, lugnet.cad.mlcad, lugnet.market.brickshops)
|
| |
| | Re: Restart of LDA2001 Project (using LDraw models - L3P - POV)
|
|
(...) Yeah, it'd be very cool if L3P had an option to generate include files instead of full scenes. That way, people could run all their various model files through L3P to generate the definitions in include files. Then they could use all those (...) (20 years ago, 17-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Automated Inventory Ordering through Bricklink
|
|
(...) I beleive that this is the hardest part of the automated 'from-CAD-to-shop' process. There are so many variables, obviously element avaialability but also price and geographical location. Also when using the By Shop sorting feature in (...) (20 years ago, 17-Jan-05, to lugnet.inv, lugnet.cad.dev, lugnet.cad.mlcad, lugnet.market.brickshops)
|
| |
| | Re: Automated Inventory Ordering through Bricklink
|
|
There is of course the option on Bricklink of uploading an XML file into your wanted list. If you could make a program that reformats an MLCad parts list into the required XML format you would be halfway there. I have tested this function with a (...) (20 years ago, 17-Jan-05, to lugnet.inv, lugnet.cad.dev, lugnet.cad.mlcad, lugnet.market.brickshops)
|
| |
| | Re: Restart of LDA Project (using LDraw models - L3P - POV)
|
|
(...) I think I mean... I don't remember! (...) Maybe, but that's not really the problem to me. (...) output files) is having to hunt down all the include files! (...) I'd say let's start with camera.dat and lookat.dat. If we make them with lines (...) (20 years ago, 17-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Restart of LDA Project (using LDraw models - L3P - POV)
|
|
(...) I had no idea that L3Lab had POV output, in spite the fact that I've been using it daily for years! Hmm, very intersting. The alternative approach that comes to my mind is: * LDA creates a static MPD file and runs it through L3P. * The output (...) (20 years ago, 17-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
