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