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