 | | 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)
|
| |
| | Re: Trouble with POV 3.5 (a solution)
|
|
(...) 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 the line: #version 3.5 before #include "colors.inc" and the line: (...) (22 years ago, 28-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) Since the release of POV 3.5, there seems to be a general re-writing of history as people delete their MegaPOV-specific pages. Most of my MegaPOV tutorial links are 404'ing now. Looking on the bright side, the state of documentation can never (...) (22 years ago, 26-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) like, how? (22 years ago, 25-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) I have found 3.5 to be almost twice as fast as 3.1 with the same files - tested on a PII, P3 and P4. Most incompatabilities can be removed with the version directive. (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
<snip> (...) Try this link: (URL) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) Can't help it, I'm an upgrade junkie. Been that way for years :) Anyway, is there a good tutorial on MegaPOV? I have not used that yet, still using L3P. (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
"Sproaticus" <jsproat@io.com> wrote in message news:GzrFGw.AJx@lugnet.com... [ ... snipped ... ] (...) that (...) I too had problems with 3.5 so went back and installed 3.1. WRT MegaPOV - where is the best place to download the current version of (...) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) I was also having the same problems and I spotted this: (URL) he suggests adding a #version 3.5; line at the top of the file. This worked from me but I am still having other issues with the orthagonal view. I guess I'll just have to go back to (...) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) I loaded POVRAY 3.5 and started using it to render my LDraw designs and noticed right away that it is slower on my machine and it leaves areas of the render with an odd color and fuzzyness to the image. in some areas it is almost transparent. (...) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
| |
| | Re: Trouble with POV 3.5
|
|
(...) Unfortunately, the POV dev team has a history of breaking backwards compatability in their revisions. Think back to how they mutilated the halo feature of 3.0 when they introduced media in 3.1. Their goal is to force everyone to use the latest (...) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
|
