 | | Re: POV in Part
|
|
(...) I'm not too keen on this idea. While POV-Ray is a nice tool and freeware, I'd like to avoid dedicating ourselves to one tool, not to mention the size increase on all the files. If all you want is nice looking parts for POV try a combo of (...) (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: POV in Part
|
|
(...) Since L3P already supports the LGEO part library, is it possible to just add new LGEO parts and have L3P automatically use them? The only problem I see with this is that the .tab files in the LGEO library are binary files, but the format of (...) (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts, lugnet.admin.suggestions)
|
| |
| | Re: POV in Part
|
|
(...) I agree to that, but since POV-code will be between IFPOV and IFNOTPOV codes will it matter that much? (...) There I disagree: the reason I ask is because of the macaroni-brick. I tried (fairly succesfull) to write the main part as POV-code (...) (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts)
|
| |
| | Re: POV in Part
|
|
(...) Here's a small program to dump the file out as text so we can examine the unknown 8 bit value. It looks to me like it contains some flag bits. Only 3 bits seem to be used (0x01, 0x02, and 0x80). From the output it appears as if bit 0x80 (...) (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts, lugnet.admin.suggestions)
|
| |
| | Re: POV in Part
|
|
(...) Yes, L3P would automatically support new LGEO parts if they were added to the binary l2p_elmt.tab. (...) You can use the -d option to L3P to see the contents of LGEO's *.TAB files: l3p -d -lgeo somefile.dat | more (mentioned a couple of years (...) (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts, lugnet.admin.suggestions)
|
| |
| | Re: POV in Part
|
|
Could folks please trim lugnet.admin.suggestions from this thread? Frank (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts, lugnet.admin.suggestions)
|
| |
| | Re: POV in Part
|
|
(...) The 'dedicating ourselves to one tool' aspect is why I'd rather not allow POV-Ray code to be embedded in official LDraw part files. What I was suggesting was a separate library of POV-Ray parts that was designed from the start to be fully (...) (21 years ago, 21-Jun-03, to lugnet.cad.dat.parts)
|
| |
| | Re: POV in Part
|
|
(...) Are there any significant differences between the two libraries? I assume they both use solid modeling, not surface modeling. I don't think either library offers rounded edges on bricks (something I still miss from the L3G0 library). I've only (...) (21 years ago, 21-Jun-03, to lugnet.cad.dat.parts)
|
| |
| | LDraw-to-Raves (was: POV in Part)
|
|
(...) OK, I've generated a complete translation list, matching up as many parts from Anton's library to LDraw as possible. I also worked through the colors/textures/materials, making as many matches as I could. I've started creating POV-Ray include (...) (21 years ago, 25-Jun-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
In lugnet.cad.dat.parts, Steve Bliss wrote: <snip> (...) I like this quite a bit and if Lar's implements the request I made for L3P to wrap all the part defines in #IFNDEF statments, then these files should be drop in and go --Orion (21 years ago, 25-Jun-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) Hmm, that would be true - if the wrappers use the same names as L3P generates (so the object for the 2x4 brick would be named 3001_dot_dat). Right now, they don't - the names are like ar_3001. Even so, changing '3001_dot_dat' to (...) (21 years ago, 25-Jun-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) [snip] (...) Hi Steve, Have you contacted Anton about this? He's not a bad guy and is willing to help where needed. Jeroen (21 years ago, 11-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) [snip stuff about ldraw-to-Anton] (...) Not yet -- this project's been back-burnered for a bit. I finished making the wrapper files, and got distracted. Steve (21 years ago, 12-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
Just to drop in my 2 cents, I think putting them into one file would be better. Also, could you put up a quality comparison chart? Three shots of a couple of parts, each, so we can compare? Thanks, Mike (21 years ago, 15-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) I'm torn - using a single file in POV-Ray is definitely more convenient, and 750 definitions don't seem to be too much overhead for the parsing engine to chew on. But for (later) updates to the wrapper library, individual files would work (...) (21 years ago, 16-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) I think the 1:1 aproach would be better. Using one main include file might be convienient, but makes it difficult for many authors to contribute to. (...) Something like this? (URL) do not use the part files from there, most of them have been (...) (21 years ago, 17-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) That's it. Do you think you could add to that? I guess a POV file could be made that would automatically generate a gallery. I'll have to look into that. -Mike (21 years ago, 17-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
"Michael Horvath" <mhorvath2161@juno.com> wrote in message news:HI33p4.1w9H@lugnet.com... (...) Isn't very flexible, is it? (...) couple of (...) Before you go and render, think of this: LDraw: rectangles and triangles that make up lego parts, (...) (21 years ago, 17-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) Hmm, thinking more about this, it could be done with individual files, and then a single master file that includes all the individual wrapper files. The master file could be auto-generated whenever the wrapper-library is updated. That would be (...) (21 years ago, 17-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) [snip comparision of libraries] Many parts look about the same, whether their code came from LDraw or Anton's library. Also, there are a number of small differences between the versions of the some parts in the two libraries. Sometimes Anton's (...) (21 years ago, 18-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: POV in Part
|
|
(...) My library is currently being rebuild and all buttons on the bricks are getting a selectable rounded edge, they take up a whole extra amount of rendering time so I've made them an option. Also, I've always looked at new Lego(TM) and there are (...) (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: POV in Part
|
|
(...) How about me, myself and I...? ;-) I've been thinking about a conversion ability between LDraw and my libraries for quite a while now, even talked to a few people about that, leaving me a few options...: 1> Get in contact with Lars and have (...) (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) I'm not certain if I agree with you here... ;-) The part I measured (and digitized) is one that came with my 6981 Aerial Intruder and has the dimensions that I used. (...) Yes, in the past I decided to do the decorated elements as (...) (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) I'm here now... :-) Greetz, Anton (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) I partially agree here, it may not be very flexible but it is better for file systems that use minimal cluster sizes... ;-) (...) Jeroen, I know what I want, and that is renders that look good. Of course us still not having an MLCAD-like (...) (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) For those reading in, non-hollow parts make for far better and more realistically looking transparent pieces! Greetz, Anton (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: POV in Part
|
|
(...) Sorry Steve for not answering earlier, but I would very much like to play. (...) As mentioned earlier I would be happy to support your library in L3P. (URL) a bonus you'll get POV objects generated for parts not (yet) in your library, support (...) (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) Do files have to be named explicitly or is there a notion of includepath or classpath like searching in POV? If so... Would it be possible to combine approaches? Have the base parts all in one file but each release of revs is in another, and (...) (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) YES YES YES! Cool stuff, Paul. C'mon guys open your eyes and look at this: (URL) helmet (very good part writing I must say, I couldn't have done it) 500+ lines. And by adding (just) 36 lines of POV code one gets a real rounded helmet. Now, (...) (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: POV in Part
|
|
(...) Joehoe! Three cheers for Lars, Anton and Steve! When can we download the program? ;-) Jeroen (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) Jeroen, GeoCities doesn't allow deep links to files. You'll have to link to an html page with the image on it. I've had the same problem. -Mike (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) Hmm. I'll haul out some of mine and recheck the LDraw part. (...) Alright, I'll grab some of those 500 model files, and see what's up. Steve (21 years ago, 24-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) For one, I'm not keen on putting POV-Ray code in LDraw part files. Besides complicating the review/certification process, it also ties the LDraw library to one specific renderer, in an official way. Steve (21 years ago, 24-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) AFAIK, they have to be explicitly included. (...) Not really, because then there'd be an issue of search order order, too much complication. (...) I prefer to keep it simple -- either one big file with everything in it, or one master file that (...) (21 years ago, 24-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) Good point. As I wrote in another post, we could keep the individual part files on a dev server, and distribute a single combined file. Or store all the individual definitions in a SQL database. (...) Ack! I better post my work soon, or it (...) (21 years ago, 24-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) Perhaps things like this could be included in the category/list of other .dat libraries that will some day be on LDraw.org. People could go to the respective sites to download POV enhanced parts. Just my $0.02 --Ryan (URL) (21 years ago, 25-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: POV in Part
|
|
(...) I might be imagining things, but the macro'ed baseplate parts seemed to render *excrutiatingly* slowly when I working on the LDraw2Raves wrapper. This was in low-quality mode. I'm assuming that in model files, rendered in higher-quality modes, (...) (21 years ago, 29-Jul-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) What did you come up with...? (...) More and more model files are becoming available as we speak... ;-) Even a few new ones... Greetz, Anton (21 years ago, 6-Sep-03, to lugnet.cad.dat.parts)
|
| |
| | Re: LDraw-to-Raves (was: POV in Part)
|
|
(...) Well, first, lego parts get really dusty when they're left out. They're like little ABS dust magnets. But it looks like the part in LDraw is the right size. At least, it mates up with part 2409(.dat) nice and clean. Maybe they're both wrong? (...) (21 years ago, 18-Sep-03, to lugnet.cad.dat.parts)
|
