 | | Re: Excellent rendering...
|
|
photoshop? autolevels... autocolors? -tk "Orion Pobursky" <bilthefish@IHATESPAMyahoo.com> wrote in message news:H2r5CJ.25A@lugnet.com... (...) (22 years ago, 21-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: Excellent rendering...
|
|
I thought I'd throw my contribution into the frey: (URL) (Warning to modem users, 259K) Took about 45 minutes to render on my machine. One thing though, the colors seem to be "washed out". Is there anyway to fix this? -Orion (22 years ago, 20-Sep-02, to lugnet.cad.ray, lugnet.starwars)
|
| |
| | Re: Excellent rendering... (need new l3p)
|
|
(...) Yes, I really appreciate that Lars C Hassing contacted the POV-Ray forum for new ideas to improve the renderings. By the way, has anybody tried to combine the "new style" rendering with the edge detection concept in MEGA-POV? Perhaps that (...) (22 years ago, 20-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: Excellent rendering... (need new l3p)
|
|
(...) Gotta love the radiosity pics! So the big question now is how close is the next release of l3p? You know, the one that supports all this on the command line with -ib -ie -il and -ci as mentioned in this thread. (URL) can't wait. Don (22 years ago, 20-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: Excellent rendering...
|
|
Ooohh let's see! (...) I thought I was a big man w/ a 1.0 GHz PC! (...) hhhhmmmm don't know what that means but I look forward to it! (...) (22 years ago, 20-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: Excellent rendering...
|
|
Here's some renders I've done as a result of this thread: (URL) render times ranged from 1.5 to 3.5 hours on a 1.7 GHz PC. I'm slowly working on an include file for color definitions. (...) (22 years ago, 20-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: Excellent rendering...
|
|
Just to add that I made my pictures with L3P parts. Started a picture with LGEO parts over an hour ago, and it's still only on line 129 of 480. No traces of any black spots yet, though. I don't want to think about doing this rendering with (...) (22 years ago, 19-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: Excellent rendering...
|
|
Hello, this is my first time posting in this group. I just wanted to say that I have been looking around at some of these images and all of them are just fantastic. So real looking! Really really impressive. I would like to make a point of keeping (...) (22 years ago, 19-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: Rendering of a Bryce Rollins model
|
|
Maybe I'm not an impartial viewer but that looks really nice. I like how you've given the part borders a nice thick line. For some reason that gives it an appealing look - sort of like a polygonal CGI model with cel shaded textures. Also, kudos for (...) (22 years ago, 19-Sep-02, to lugnet.cad.ray)
|
| |
| | Rendering of a Bryce Rollins model
|
|
Just finished some renders of Bryce Rollins' SH-60. Coloration may be off from his z-renders but it's pretty close. All of Bryce's models are great, but I thought he really captured the feeling and flair of the SH-60 Seahawk. Anyway have a look: (...) (22 years ago, 18-Sep-02, to lugnet.build.military, lugnet.cad.ray)
|
| |
| | Re: Excellent rendering...
|
|
"Coby Bassett" <coby@tubafrog.com> skrev i meddelandet news:H2LqHH.Hzo@lugnet.com... (...) test (...) pieces. (...) Hmm, I've made some tests too, but not seen anything like what you describe. Veeerrryyy slow to render with radiosity, though, and a (...) (22 years ago, 18-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: Excellent rendering...
|
|
Here's a little followup about my experimentation (along with a new test image-> (URL) ). My festivities have hit a big snag when I tried using transparent pieces. I guess these pieces send the radiosity rays ascattering, creating a tremendous load (...) (22 years ago, 17-Sep-02, to lugnet.cad.ray)
|
| |
| | all hail the hex
|
|
ok, this was a miracle. I went to the bar, came home and read the post to this thread and scratched my head. searched for a hex editor which i've never even hear of... and found Hex Workshop demo. these guys are great. I ended this problem in an (...) (22 years ago, 12-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: lgeo renders wrong part
|
|
and a hex editor is? we're getting way the f--- outside of my range of expertise... but i'm still pointed in the right direction. And motivated enough to work all the way through this. I have this odd stinking feeling this is going to be a lot like (...) (22 years ago, 12-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: lgeo renders wrong part
|
|
(...) You're going to need a hex editor - them thar file's got binary values in 'em. Steve (22 years ago, 11-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: lgeo renders wrong part
|
|
"travis" <phree@attbi.com> wrote in message news:H29AHE.HCA@lugnet.com... (...) for (...) seemed (...) ideas? (...) You might try editing it with VIM - (URL) - it is the infamous VI editor souped up and ported to Windows (and other playforms as (...) (22 years ago, 11-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: lgeo renders wrong part
|
|
ok, did some investigation, and there are 3 .tab files in the /lgeo directory. one is the elements of the library. however when i removed the entries for 3939 and 3942, the -lgeo option in LP3AO would not render a .pov. It seemed to error right (...) (22 years ago, 11-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: lgeo renders wrong part
|
|
(...) Does anyone know where this list resides? I'm going to murder it textually -tk (22 years ago, 11-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: lgeo renders wrong part
|
|
(...) Sorry, my bad. :( I didn't realize there was a data store for LGEO parts. I assumed L3P was checking the LGEO directory for .inc files. Silly me. (...) I'm guessing it's either (a) LGEO has a list of parts somewhere that L3P is referencing or (...) (22 years ago, 10-Sep-02, to lugnet.cad.ray)
|
| |
| | Re: Weird Logo Issue at L3P Quality Level 3
|
|
(...) :) It's not much extra typing, it's just one more thing to understand, or more guideline to follow... (...) It's simply a good idea. (...) There are two primary benefit: 1. It *can* boost rendering speed, if the viewer is coded to take (...) (22 years ago, 10-Sep-02, to lugnet.cad.ray)
|
