 | | 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)
|
