 | | 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)
|
| |
| | Re: Restart of LDA Project (using LDraw models - L3P - POV)
|
|
(...) I'd agree with this. But what I do with an L3Lab output (which is how I generate my static images in POV from LDraw files) is immediately strip the camera and viewpoint stuff out and make it into an .inc file, my main file just includes what (...) (20 years ago, 16-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Restart of LDA Project (using LDraw models - L3P - POV)
|
|
(...) You mean LD4D and you or POV-Ray and you? (...) You really need to look at how POV-Ray does animation. It has all of this built in. I think one reason why animation is so hard is because L3P's output is overwhelming. It is not good for newbies (...) (20 years ago, 16-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Restart of LDA Project (using LDraw models - L3P - POV)
|
|
(...) Yes, that's why I also make this little humble program to see if my ideas work put to practice. (...) ... and that program crasches on all of my PC:s, expect the very first beta version he released... :(( (...) Maybe, maybe not. I recall James (...) (20 years ago, 15-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Restart of LDA Project (using LDraw models - L3P - POV)
|
|
(...) I have no idea. Anton always include the ini with the pov file, so perhaps whatever tools come from this can just auto create the ini file as well. (...) Hey! Cool! I know the syntax alone wont be much good. If there aren't tools that use it, (...) (20 years ago, 15-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Automated Inventory Ordering through Bricklink
|
|
---snip--- There are two soultions that I know of. 1) Create a .LDR file with the parts you want to buy 2) Download and install (URL) 3) Upload your .LDR file to briktrak and it will link to bricklink and provide you a list of stores that have your (...) (20 years ago, 15-Jan-05, to lugnet.inv, lugnet.cad.dev, lugnet.cad.mlcad, lugnet.market.brickshops)
|
| |
| | Re: Automated Inventory Ordering through Bricklink
|
|
I wrote a utility, for my own use, about two years ago that takes a .dat file and attempts to find "best" way to buy the parts via BrickLink. I'd planned to produce custom sets and source the parts for them this way. It was working well when last I (...) (20 years ago, 14-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 already am. :) I noticed that L3P already marks the beginning of these blocks: // Camera (Latitude,Longitude,Radius = 45,45,0) and // Lights: Now, I've asked Lars to let L3P also mark the ends of these blocks. (...) No it isn't. Btw, I'm (...) (20 years ago, 14-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Restart of LDA2001 Project (using LDraw models - L3P - POV)
|
|
(...) In the coming L3P each section is tagged with POV comments like //// ModelObject //// Camera //// Lights exactly to help cutting out the interested POV code. (...) I'm reluctant to adding too much complexity into L3P to suit different special (...) (20 years ago, 14-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Restart of LDA2001 Project (using LDraw models - L3P - POV)
|
|
(...) Since L3P is released only every four years or so, it shouldn't be a problem :-) /Lars (20 years ago, 14-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Automated Inventory Ordering through Bricklink
|
|
(...) You could try BrikTrak. If I recall, it has a DAT file upload feature and it interfaces with Bricklink. (URL) (20 years ago, 14-Jan-05, to lugnet.inv, lugnet.cad.dev, lugnet.cad.mlcad, lugnet.market.brickshops)
|
| |
| | Re: Restart of LDA2001 Project (using LDraw models - L3P - POV)
|
|
(...) I guess we would have to work with Lars on that. Because your app is in Delphi, I would be interested in the syntax you develop. Implementing on different platforms is not as big of a deal in my opinion. I am mostly interested in this because (...) (20 years ago, 14-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Automated Inventory Ordering through Bricklink
|
|
Greetings all, I was discussing some time-saving MOC parts ideas and I came up with an idea for a software utility that could significantly reduce the amount of time spent digging around for loose parts. Currently, to the best of my knowledge, when (...) (20 years ago, 14-Jan-05, to lugnet.inv, lugnet.cad.dev, lugnet.cad.mlcad, lugnet.market.brickshops)
|
| |
| | Re: Very small triangle and a quad that thinks its a tri
|
|
(...) Silly question time. Where can I download the latest versions from. My usual place (the zip files on your web site) are still dated sometime in 2001! thanks William (20 years ago, 14-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Restart of LDA2001 Project (using LDraw models - L3P - POV)
|
|
(...) I've been thinking a lot about that. I think you can find a couple of threads here if you perform a search on "post-processing" or "post-processor". But... What if a futureversion of L3P has some new improvement and changes the syntax of the (...) (20 years ago, 14-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Very small triangle and a quad that thinks its a tri
|
|
(...) That's a small triangle! Side lengths: 0.0684 0.0671 0.0132 The reason it doesn't show in L3Lab is that you have color coded it in your file! Back in 1998 PovRay would crash if it was given a triangle with collinear vertices and a texture (...) (20 years ago, 14-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Restart of LDA2001 Project (using LDraw models - L3P - POV)
|
|
(...) That is what I was going to do too. (...) I guess what I was thinking was exporting a file that could either be povray format, a format that l3p could convert (preserving unions, macros, etc), or a format that I would use with Anton's library (...) (20 years ago, 14-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Restart of LDA2001 Project (using LDraw models - L3P - POV)
|
|
(...) Thanks for the response. Just a qiuck reply, got to go back to work... LDA outputs both .dat files for the indiviual frames but also one master .dat that has references to the single-frame files, separated by CLEAR and STEP. L3P supports (...) (20 years ago, 13-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | Re: Restart of LDA2001 Project (using LDraw models - L3P - POV)
|
|
(...) Tore, I think I know what you could do that would meet even my needs. Here is my idea. Output one pov-ray file. Have it export valid pov-ray format using unions, macros, clocks, switches, ranges, etc. Then, with that, it will be easy to add (...) (20 years ago, 13-Jan-05, to lugnet.cad.ray, lugnet.animation, lugnet.cad.dev)
|
| |
| | LDraw.org Contributer Agreement Affirmation
|
|
Hi all, Thanks for all the words of support regarding the LDraw.org Contributer Agreement. We've received quite a few responses but would like to wrap up this issue as quickly as possible. For those who haven't heard of the CA here's the (...) (20 years ago, 12-Jan-05, to lugnet.cad, lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Change to existing policy regarding the subfiling of dithered colors
|
|
(...) many, many thx to the LSC for getting the job done so quickly :-)))) w. (URL) (20 years ago, 9-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Very small triangle and a quad that thinks its a tri
|
|
(...) I'll send you the whole file (its not complete yet), but the values for the tri are A (0.989107, -1, 0) B (0.997785, -0.98677, 0.06652) C (0.997785, -1, 0.06652) William (20 years ago, 8-Jan-05, to lugnet.cad.dev)
|
| |
| | RE: *** SPAM *** Re: Very small triangle and a quad that thinks its a tri
|
|
(...) Only at 5dp (ie -det/-dist of 0.00001), but then as the values are only to 5dp this is not surprising! The co-linear vertices are reported for any -det/dist values from 1 to 0.00001 William (20 years ago, 8-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Very small triangle and a quad that thinks its a tri
|
|
(...) I think so too. William, could you please e-mail me the actual coordinates of A, B, etc., and perhaps the whole file. (...) Good question! (...) The colinearity test currently has a hardcoded threshold of 0.01. The colinearity test is carried (...) (20 years ago, 8-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Very small triangle and a quad that thinks its a tri
|
|
(...) I'm guessing this is a limitation of the accuracy of the l3p -check, so probably ignorable. Does the -dist option affect this test too, or just the coplanar quad test? Maybe there could be another option in l3p to adjust the accuracy of the (...) (20 years ago, 8-Jan-05, to lugnet.cad.dev)
|
| |
| | Very small triangle and a quad that thinks its a tri
|
|
Whilst working out the non-right-angled cylinder intersection sub-parts for the Boat Rigging pieces I have run into two related problems 1) I have a triangle A-B-C that is so tiny that L3P reports it as co-linear and L3Lab doesn't render it (it (...) (20 years ago, 7-Jan-05, to lugnet.cad.dev)
|
