 | | Re: BFCFixer
|
|
(...) I think it can be done for simple objects, by choosing a random winding for 1 polygon, then processing all touching polygons so they're wound the same way (when looking from the same side - out ot in). This would produce a result that is (...) (20 years ago, 3-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: BFCFixer
|
|
(...) I may be being dense here, but I dont understand how this can be done programatically. The point of BFC is to allow renderers to understand if a particular polygon is facing the camera or facing away from it. If all polygons are wound (...) (20 years ago, 3-Feb-05, to lugnet.cad.dev)
|
| |
| | BFCFixer
|
|
(...) Well, I had some spare time today... so I wrote one. It goes through a single LDraw part file and reorients all the polygons in it to have the same winding. It comprehends the notion of subfiles and already BFC compliant parts, and puts the (...) (20 years ago, 3-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) <snip> (...) Yes, I use MLCad in conjuction with LDDP/LDView for parts authoring. My method is to build the part in MLCad since it does all the rotaion calculations for me and then clean in up and fine tune ithe part in LDDP/LDView. As far as (...) (20 years ago, 3-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) Hi Stefan: I'm chiming in late here, but I've crafted at least a few unofficial LDraw parts, and I thought I might offer some thoughts. My original composing tool of choice was the shareware text editor "PC-Write v4," which no longer appears (...) (20 years ago, 2-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: Bricksaic version 0.1.0
|
|
(...) Xposted to cad.mlcad Perhaps Michael L. could speak up about whether MLCad reads that file, what the proper superset of colors ought to be and other topics. (20 years ago, 1-Feb-05, to lugnet.build.mosaic, lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: Bricksaic version 0.1.0
|
|
(...) Bricksaic is using the ldconfig.ldr in it's directory but the problem with the unused colors seems to be that MLcad does not recognize the following colors: Reddish_Brown, Stone_Gray, Dark_Stone_Gray, and Dark_Green. there may be more colors (...) (20 years ago, 1-Feb-05, to lugnet.build.mosaic, lugnet.cad.dev)
|
| |
| | Re: Bricksaic version 0.1.0
|
|
(...) Larry, I looked into what you said and it is correct: Bricksiac is using the ldconfig.ldr file in it's installed directory and MLDraw is using a file named the same ldconfig.ldr in it's installed dirctory. Then if one of the other has a (...) (20 years ago, 31-Jan-05, to lugnet.build.mosaic, lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) Oh, yes. Definitely. (...) :) [snip a lot of stuff with which I agree] (...) nod, yes. That makes a lot of sense. (...) Very cool. :) Steve (20 years ago, 31-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) no, he didn't. when I last met him at legoworld 03 he promised to do it but actually never did (as far as I remember at the time windz had an error quote of 2-3 percent - too much from his point of view :-(( w. actually I'll add the (...) (20 years ago, 31-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) It has been done before. Ildefonso Junior Zanette wrote a program called Windz, I use it all the time when I author parts. I can't remember if he publically released it. -Orion (20 years ago, 30-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) It doesn't matter, actually. In one way or another, optional lines are required. In general, the "magic halo" effect only highlights _outside_ edges, but for a non-convex object, that won't necessarily be adqeuate. You can't even get away with (...) (20 years ago, 30-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) Ok, I drew a better picture (2 planes in space and a floating eye) and I'm starting to see. Maybe you're onto something. It takes 2 surface normals and one point on the edgeline to divide space into 4 quadrants. Then you only need to figure (...) (20 years ago, 29-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: BMP2DAT question (problem?) [DAT]
|
|
(...) If I understand the problem correctly, you have to scale down the output file. This can be easily done by pretanding that it is a sub-part Rename it to pattern.dat for example. Then create a new part that calls to that pattern with the line: 1 (...) (20 years ago, 29-Jan-05, to lugnet.cad.dev)
|
| |
| | BMP2DAT question (problem?)
|
|
Hi, I made some stickers for one of my trains. Now i'm making building instructions for this train and would like to add the stickers i made in the LDRAW design. Therefore i use the BMP2DAT utility found in LDAdd-On from Steven Bliss. This works (...) (20 years ago, 29-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) What you are describing is in fact a very old and basic edge rendering algorithm, which can be found in most detailed textbooks on computer graphics. CAD style and wire frame rendering went out of style during the 90's, so some recent "fancy (...) (20 years ago, 29-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
Thanks for your suggestions, the message I received is: "Yes, a good and useful translator would be appreciated." One brief comment on the issue of whether we want clean, compact and well structured files or not: of *course* we want clean files! A (...) (20 years ago, 29-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: l3p as open source
|
|
(...) L3P is available for the Mac and Linux.... Kevin (20 years ago, 29-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) Actually, one can bring the number of transformations down to 1 for the entire _object_. Interesting what can happen when an idea sits in the brain and percolates for a couple of days. A new idea I had was to just transform the camera position (...) (20 years ago, 29-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Bricksaic version 0.1.0
|
|
(...) I ran into this too while betatesting. If you were using, for example, MLCad, it might be a problem with the color definitions that MLCad is aware of. Bricksiac is getting its color info from the ldconfig.ldr file in the install dir, I think. (...) (20 years ago, 28-Jan-05, to lugnet.build.mosaic, lugnet.cad.dev)
|
| |
| | Is there someone interested in making icons for me
|
|
Hello, I'am working on LD4DModeler V2 (see (URL) i want to make it better in every aspect over V1 am looking for some artist who is willing to make some (mostly) 16x16 pixel icons for me. I think people who used V1 know why I rather don't do it (...) (20 years ago, 28-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: l3p as open source (was: Re: Anatomy of a POV file (e.g. L3P suggestions))
|
|
(...) I knew I'd forgotten something in here! That function sounds interesting and could help a bit, but I'm not sure it's possible to turn an .inc around, but I'll look into it when I get the time. Thanks -NB (20 years ago, 27-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) I don't see it. Are you sure this works in the perspective projection? Because I can't quite figure out what the magic view vector is in that case. I think you'd need to calculate one view vector for each edge endpoint, which brings the number (...) (20 years ago, 25-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
Okay.... having had a day to think about it and a night to sleep on it, I think I've figured out something.... But it would only work if the optional lines were incident to edges of polygons that are part of the object being drawn. I'm not sure if (...) (20 years ago, 25-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) I'm not 100% sure, but I believe most (if not all) of these outlining algorithms expect you to know the difference between the front faces and the back faces. It could be that they could be adopted for use when you don't have this information, (...) (20 years ago, 25-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) I'm not sure it's possible to implement for real without serious slowdowns. It might be possible to implement in a vertex program, but I haven't studied vertex programs, so I really don't know. (I'm pretty sure you can't throw out a vertex (...) (20 years ago, 25-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Cross platform GUI
|
|
(...) The look and feel is one of the reasons why I rejected GTK (...) To me, compile times are a non issue. However the non-free nature of Qt leaves a bad taste in my mouth (and I not even a Open Source zealot). I can however develop a Qt based (...) (20 years ago, 25-Jan-05, to lugnet.cad.dev, lugnet.off-topic.geek)
|
| |
| | Re: Experimenting with camera.dat and look_at.dat
|
|
(...) It would be nice if there were also a part used to store points. It would then be declared at the end of the .pov file as a uniquely named vector. (20 years ago, 25-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) You're right about the performance hit. We've discussed this issue previously on lugnet, because quite a few of the renderers out there use opengl (ldview, leocad, ldglite, Mac Brick Cad...) Source code is available for all of these if you (...) (20 years ago, 25-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Rendering implementation details
|
|
(...) Someone once suggested to me (Dan from Microsoft maybe?) that given today graphics libraries, one could probably get away with ignoring op-lines altogether and use edge detection. This would present a potential problem since edge color is (...) (20 years ago, 24-Jan-05, to lugnet.cad.dev)
|
| |
| | Rendering implementation details
|
|
I was envisioning how an LDraw renderer would be implemented if it were done with OpenGL, and I've arrived at some questions that I can't answer for myself. I'm particularly wondering about line type #5, the optional line. According to the LDraw (...) (20 years ago, 24-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Experimenting with camera.dat and look_at.dat [DAT]
|
|
(...) I updated the camera.dat and look_at.dat so they don't need to be REMmed out: 0 ~Camera Position 0 Name: Camera.dat 0 Author: Tore Eriksson 0 Un-official part 2 24 -4 0 0 4 0 0 2 24 0 -4 0 0 4 0 2 24 0 0 -4 0 0 4 0 L3P IFNOTPOV 1 0 0 25 37 1 0 (...) (20 years ago, 24-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Experimenting with camera.dat and look_at.dat
|
|
(...) Yes,I am very well aware of the multitude of camera settings POV offers, and I haven't yet decided which way to go. The fastest way may be to run my own race using my own META statements: 0 LDA CAMERA.POSITION x y z 0 LDA CAMERA.LOOKAT x y z 0 (...) (20 years ago, 24-Jan-05, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Cross platform GUI
|
|
Personally I don't think using GTK under Windows is a good idea. I've worked with it before and even released an application that used it and you won't believe the amount of people that have trouble using a Windows application with controls that (...) (20 years ago, 24-Jan-05, to lugnet.cad.dev, lugnet.off-topic.geek)
|
| |
| | Re: Experimenting with camera.dat and look_at.dat
|
|
(...) POV-Ray cameras can do alot. Besides just having a location and direction, you can have a zoom, focus, you can specify the direction in the form of "look at", and more. If you are going to have a camera.dat, you might consider having it be (...) (20 years ago, 24-Jan-05, to lugnet.cad.dev)
|
| |
| | Experimenting with camera.dat and look_at.dat [DAT]
|
|
I created these three files and ran them through L3P: - - - - - 0 Test 0 Name: test000.ldr 0 Author: Tore Eriksson 1 2 0 0 0 0 0 -1 0 1 0 1 0 0 700.dat 1 15 0 -24 100 1 0 0 0 1 0 0 0 1 3001.dat 1 4 0 -48 100 1 0 0 0 1 0 0 0 1 3001.dat 1 15 0 -72 100 (...) (20 years ago, 23-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) I'm sorry if I was unclear. Earlier in the thread I put forward Bens wheels as an example and continued that example here. I realise they would not be eligible for inclusion in the official Ldraw library, and would not submit them. This thread (...) (20 years ago, 23-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) Maybe I'm missing the point here, but if this whole discussion is about Ben's excellent independently produced wheels, then whether or not they are modelled appropriately for inclusion in the official LDraw library is academic. The official (...) (20 years ago, 23-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) (I'm going to try not to sound like a jilted lover here, bear with me) If you're not already a parts author, you have to ask for permission to submit a part to the Parts Tracker. I've been told translated-from-other-CAD (i.e. messy) parts (...) (20 years ago, 23-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) No DAT part can provide a perfect render without using some substitutions - flat polygons just can't do perfect curved surfaces. But that's another issue. I have recently finished re-authoring Ben's wheels (URL) (waiting for his OK before I (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) I should probably find then for what is LDraw library aimed at. If it's something like as perfect as possible renders or some quick mockup prototyping. (...) Wouldn't it be possible to be the parts as accurate as possible and then (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Cross platform GUI
|
|
Well I'm kind of of pissed. ** begin rant ** Curious to find an acceptible substitute for Java, I was looking into cross platform GUI toolkits. GTK+ came to mind but alas no Mac support for the latest version. Then I thought of Qt. I visited the Qt (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev, lugnet.off-topic.geek)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) Well, rendering time gets affected too, right? It's harder to build a model if it takes MLCad 20 seconds to redraw once... Oh, you mean for the rendering in POV when doing the animation? Well, file loading time, memory consumption, etc. etc. (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: l3p as open source
|
|
(...) A nice thing about open source would be that it would be possible for other people to work on ports to different architectures other than the microsoft-based platform. While emulators may exist to allow people to get by for the time being, (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) If for nothing else, to permit them to be used as the basis for the manual creation of similar parts, and abstraction into resuable sub-components. Not a strong reason, but worth considering. (...) To use just one example - the STUD primitive (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) Yes, since it is text based. Also, a most new authors learn by examining the code. (...) Unneccessary memory usage and file size. (...) L3P (and other converters/viewers) detect these primitives and convert them to smooth objects (e.g. L3P (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: l3p as open source (was: Re: Anatomy of a POV file (e.g. L3P suggestions))
|
|
(...) Why don't you create your main scene file that never changes and then just include the l3p output file into your scene file. I believe Lars is working on options that leave out the povray code that is required to be in the main file (like (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) Why? Is the .DAT file supposed to be readable by humans? Why? ;) What's wrong with the larger number of polygons? What positives (from the side of the automated rendering process) does bring the existence of primitives? What's wrong with the (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: l3p as open source (was: Re: Anatomy of a POV file (e.g. L3P suggestions))
|
|
(...) Hi Kevin Thanks for your tip, but even though it seems to solve the amb/dif/reflection-problem, it unfortunately doesn't cover the need for special pov-ray objects like special lights, fog etc, as it's also based on L3p. Another thing I just (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev, FTX)
|
| |
| | Re: l3p as open source (was: Re: Anatomy of a POV file (e.g. L3P suggestions))
|
|
(...) An alternative to open source is to post process l3p output to change things the way you want. This is what I do in LPub. L3P output is simple text and extremely consistant, making it easy to modfiy the contents. Kevin (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | l3p as open source (was: Re: Anatomy of a POV file (e.g. L3P suggestions))
|
|
I don't know if this is besides the topic, but what I would really like was the ability to edit the "text" with the default settings l3p uses to create the pov-file (after all, it's a program that converts a textfile into another textfile). When (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: BigBen Bricks! (Was: Parts editing made easy...?)
|
|
(...) Tore, those are parts made on Stratasys and zCorp Rapid Prototyping machines. Rapid Prototyping is a way of using machines to take digital data and create models in an additive fashion, built up layer by layer. zCorp machines build the layers (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev, FTX)
|
| |
| | Re: BigBen Bricks! (Was: Parts editing made easy...?)
|
|
(...) Sorry Tore, I thought you read the article. Here's a brief summary: Mike Pique of Scripps Research Institute, Molecular Biology Department, did some LEGO bricks in the rapid prototype machines in his department. He plans on using them to teach (...) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: BigBen Bricks! (Was: Parts editing made easy...?)
|
|
(...) My eyes see the most beautiful things, but yet they don't understand. I looked for some text that explained who/where/how this lovely sight is made possible. Please let me have some more information! /Tore (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | Re: BigBen Bricks! (Was: Parts editing made easy...?)
|
|
(...) Ahem... (URL) (20 years ago, 22-Jan-05, to lugnet.cad.dev)
|
| |
| | 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)
|
| |
| | 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)
|
