 | | Re: Why does it take long?
|
|
(...) Good idea I was thinking to do that but I was not sure if was best to do it but now that you told me I use that technic instead the long one. (...) (22 years ago, 13-Aug-02, to lugnet.cad.ray)
|
| |
| | Re: Why does it take long?
|
|
(...) Probably because you render every picture three times! Don't use POVRay for generation of time delay in an animation, use the animation software instead (setting time for a frame, duplicating a frame etc) -- Anders Isaksson, Sweden BlockCAD: (...) (22 years ago, 13-Aug-02, to lugnet.cad.ray)
|
| |
| | Re: Why does it take long?
|
|
(...) Ray tracing is very CPU intensive, and I guess also quite memory hungry. If you've got SDRAM then that could be a bottleneck. A P4 or AMD XP CPU running much faster with DDR would probably make a huge difference in this case, but I'm not (...) (22 years ago, 13-Aug-02, to lugnet.cad.ray)
|
| |
| | Why does it take long?
|
|
I have a P-3 at 867mhz with 256MB RAM with 2 hds C: 80GB and d: 20GB I'm using XP Pro. I used Pov-ray 3.1 with a resolution of 320x 240 no AA Initial_clock = 1 Final_clock = 75 Initial_Frame = 1 Final_Frame = 75 Cyclic_Animation = on Why does it (...) (22 years ago, 13-Aug-02, to lugnet.cad.ray)
|
| |
| | Re: Nice microfig Star Trek render
|
|
(...) Bummer. I've been working on a realistic planet generator in POVRay for a while now, and was hoping someone had a better solution than mine! :-, But thanks for the link, just looking at the output from Lunarcell is giving me new ideas... (...) (22 years ago, 8-Aug-02, to lugnet.space, lugnet.cad.ray)
|
| |
| | Re: Nice microfig Star Trek render
|
|
It's the same picture of the Constitution from the microfigure gallery. Sorry to disappoint you, but it's not Pov-Ray. I used Adobe Photoshop on it. I used the filter "Lunarcell" to make the planet, then I added the Constitution, I noticed the (...) (22 years ago, 8-Aug-02, to lugnet.space, lugnet.cad.ray)
|
| |
| | Nice microfig Star Trek render
|
|
...From Chris Rudesill, in his Brickshelf folder (warning, large image): (URL) how'd you render this? Is it POVRay? I really really like the planet and its features. The lighting is amazing too -- it's an effect I've been trying (in vain) to (...) (22 years ago, 7-Aug-02, to lugnet.space, lugnet.cad.ray)
|
| |
| | Re: POV Color Cheat? [DAT]
|
|
(...) [ snipped ] Intresting, and yes it will work but with a few buts. First you will need to do the color-declaring before you do your model. And you have to (well, not "have to" but is saver to) "undeclare" (or undef) the old color definition. (...) (22 years ago, 5-Aug-02, to lugnet.cad.ray)
|
| |
| | POV Color Cheat? [DAT]
|
|
Would it be possible to inline certain hard-to-achieve POV-Ray colors in a primitive file so that the color would be available in rendered models without having to tweak the output file? Something like this: 0 stud.dat primitive 0 L3P IFNOTPOV 1 16 (...) (22 years ago, 5-Aug-02, to lugnet.cad.ray)
|
| |
| | Re: PovRay Error
|
|
"Mike Walsh" <mike_walsh@mindspring.com> wrote in message news:H08IDo.L01@lugnet.com... (...) [ ... snipped ... ] (...) I looked at the LGEO files for 3194 and 3195 and it turns out that at the beginning of 3194 it declares LENGTH like this: (...) (22 years ago, 2-Aug-02, to lugnet.cad.ray)
|
| |
| | Re: PovRay Error
|
|
"Mike Walsh" <mike_walsh@mindspring.com> wrote in message news:H08I45.Juq@lugnet.com... (...) [ ... snipped ... ] (...) [ ... snipped ... ] The error message from Pov is different when only this part is rendered. object { lg_knob } sphere { (...) (22 years ago, 2-Aug-02, to lugnet.cad.ray)
|
| |
| | Re: PovRay Error
|
|
"Mike Walsh" <mike_walsh@mindspring.com> wrote in message news:H046yE.4z1@lugnet.com... (...) with (...) for (...) [ ... snipped ... ] (...) [ ... snipped ... ] I started trying to track down this error. It was tedious process as I started (...) (22 years ago, 2-Aug-02, to lugnet.cad.ray)
|
| |
| | Re: logos
|
|
(...) all 1x1 bricks. Maybe someone from the ray tracing groups have some insight. Steve (22 years ago, 2-Aug-02, to lugnet.org.us.indylug, lugnet.cad.ray)
|
| |
| | Re: LGEO orientation problem
|
|
(...) Yes, some of the parts in the LGEO library are wrongly oriented. I've also noticed that the technic triangle was wrong. I've reported these two parts to the author (IIRC), but in the mean time, you can add an ad-hoc rotate statement to these (...) (22 years ago, 1-Aug-02, to lugnet.cad.ray)
|
| |
| | LGEO orientation problem
|
|
I'm sure I saw something about this some time ago, but I can't find it 8?( When I render using the LGEO library, some parts are rotated by 90 degrees from their correct orientation, eg 6536.dat (Technic axle joiner perpendicular). What causes this? (...) (22 years ago, 1-Aug-02, to lugnet.cad.ray)
|
| |
| | Re: PovRay Error
|
|
"Sproaticus" <jsproat@io.com> wrote in message news:H04BGJ.I9L@lugnet.com... (...) you (...) [ ... snipped ... ] I made this change and it has made it through the parse stage. We'll see how it looks in about eight hours when it is done rendering. (...) (22 years ago, 31-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: PovRay Error
|
|
"Sproaticus" <jsproat@io.com> wrote in message news:H04BGJ.I9L@lugnet.com... [ ... snipped ... ] (...) there (...) The second error was almost straight from L3P. The only thing I did was to delete the light definitions and replace them with a (...) (22 years ago, 31-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: PovRay Error
|
|
(...) This is because there are a few LGEO parts that are missing their _clear definitions. I think you can get around this by putting this line after you #include "lg_defs.inc": #declare lg_6081_clear = lg_6081; (...) No idea on this one. I can't (...) (22 years ago, 31-Jul-02, to lugnet.cad.ray)
|
| |
| | PovRay Error
|
|
I have run into errors with the last two models I have tried to render with POV (3.1) and LGEO (update 15). I am using the same process I have used for last six to eight months. This is the error messages I am receiving (hopefully line breaks aren't (...) (22 years ago, 31-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5 (a solution)
|
|
sorry, I made a typo, here is the correct text: I noticed that is happens when you use the LGEO-parts. Everything is okee when you don't use LGEO. But the solution is pretty easy: Open the lg_color.inc in a text-editor and add the line: #version 3.5 (...) (22 years ago, 28-Jul-02, to lugnet.cad.ray)
|
