 | | Re: Problem creating .pov using LGEO parts in L3PAdd-on
|
|
<snip> (...) I suspected something along those lines, but I wouldn't have had any idea how to fix it, so thanks, I wil try it tonight (...) Ahui sent me a link to the relevant help page on Ldraw.org (URL) (...) tim (20 years ago, 28-Oct-04, to lugnet.cad.ray)
|
| |
| | Re: Problem creating .pov using LGEO parts in L3PAdd-on
|
|
(...) the problem is that LGEO doesn't use the same origin - at least with the libraries I have installed. So, to fix it, add the following directive at lines 159 and 308 of the LGEO file lg_6187.inc: translate <0, 0, -2*LG_BRICK_WIDTH> (...) I had (...) (20 years ago, 28-Oct-04, to lugnet.cad.ray)
|
| |
| | Re: Problem creating .pov using LGEO parts in L3PAdd-on
|
|
(...) a quick fix for that is to create a subpart for your model, with just the bar in it, then inline. that was part (bar 1 x 4) is really named something different.. when it goes thru l3p, it doesnt use the lgeo part. (20 years ago, 27-Oct-04, to lugnet.cad.ray)
|
| |
| | Re: Problem creating .pov using LGEO parts in L3PAdd-on
|
|
(...) The wrongly positioned parts can be seen in these two images Non-LGEO version, in correct position (URL) version, parts moved down (URL) error when rendering the .pov file in POVRay 3.5 can be seen (URL) same file renders without error (...) (20 years ago, 27-Oct-04, to lugnet.cad.ray)
|
| |
| | Re: Problem creating .pov using LGEO parts in L3PAdd-on
|
|
(...) Having got the .pov file created I did have to include a Library path to the LGEO.inc files folder. Once that was set I managed to get a render in 3.1 but got more errors in 3.5, something to do with version levels. I also got a strange (...) (20 years ago, 27-Oct-04, to lugnet.cad.ray)
|
| |
| | Re: Problem creating .pov using LGEO parts in L3PAdd-on
|
|
(...) Woohoo, thanks, that worked! (the path was just set to C:\) I wonder why it wasn't set correctly? Tim (20 years ago, 26-Oct-04, to lugnet.cad.ray)
|
| |
| | Re: Problem creating .pov using LGEO parts in L3PAdd-on
|
|
(...) Maybe you have a Libray_Path wrong in POV, so it's looking for include files in the wrong place? POV: 'Tools' -> 'Edit Master POVRAY.INI', go to the end of the file, You may have any number of lines like these: Library_Path=C:\Program\POV-Ray (...) (20 years ago, 26-Oct-04, to lugnet.cad.ray)
|
| |
| | Re: Problem creating .pov using LGEO parts in L3PAdd-on
|
|
(...) Hi Tim, I have everything running on my E drive, so it is possible. :-) Here's my thought... There should be an LDRAW.INI file in your Windows directory. Make sure you have the "LgeoDirectory" entry set correctly under the "[LDRAW]" section, (...) (20 years ago, 26-Oct-04, to lugnet.cad.ray)
|
| |
| | Re: Problem creating .pov using LGEO parts in L3PAdd-on
|
|
(...) No, sorry, its not either of them, L3PAO knows the location correctly. the filename is ccb2.pov (mirroring the .mpd filename) and so it is not too long and has no spaces. I don't think its a problem with your auto-installer, I used to get the (...) (20 years ago, 26-Oct-04, to lugnet.cad.ray, FTX)
|
| |
| | Re: Problem creating .pov using LGEO parts in L3PAdd-on
|
|
(...) Try the following. 1) Open L3PAO 2) On the file menu select "TOOLS -> LOCATE LGEO LIBRARY" If L3PAO does not know where the LGEO library is at it will prompt you for the path. In your case choose D:Program FilesLdrawAppsLGEO] 3) Also make sure (...) (20 years ago, 26-Oct-04, to lugnet.cad.ray, FTX)
|
| |
| | Problem creating .pov using LGEO parts in L3PAdd-on
|
|
I have always had problems with the -lgeo (Use LGEO Library). At first I put it down to incorrect installation but I recently re-installed using the all-inone installer. My installation is to D:\Program Files but other than that is pretty much (...) (20 years ago, 25-Oct-04, to lugnet.cad.ray)
|
| |
| | Re: Gray parts in LPub
|
|
(...) I have modified LPub to recognize this case and automatically add a second part to work around this problem. Kevin (20 years ago, 4-Oct-04, to lugnet.cad.ray)
|
| |
| | Re: Minimum distance?
|
|
(...) Hi Jaco, It has been a long time and I was not able to go to the URL listed above. I have reworked the minimum camera distance concept, and have realized the wisdom of Lars' camera placement use of vaxis_rotate..... Now I just change the (...) (20 years ago, 4-Oct-04, to lugnet.cad, lugnet.cad.ray)
|
| |
| | Re: Radiosity example (F1 Ferrari) once again
|
|
"Travis Cobbs" <tcobbs@REMOVE.halibut.com> wrote in message news:I4vn98.21q3@lugnet.com... (...) there. (...) sure (...) made (...) spectacular (...) I have used the anti-aliasing quite extensively, although just by using the defaults I've never (...) (20 years ago, 4-Oct-04, to lugnet.cad.ray)
|
| |
| | Re: Radiosity example (F1 Ferrari) once again
|
|
(...) After looking closely at the forklift image, I think the stair-step effect is happening due to POV-Ray's adaptive antialiasing algorithm. It's much quicker to render the image at the desired resolution with adaptive antialiasing enabled in POV (...) (20 years ago, 30-Sep-04, to lugnet.cad.ray)
|
| |
| | Re: Radiosity example (F1 Ferrari) once again
|
|
"Nico Kaiser" <nico@siriux.net> wrote in message (...) Are you 100% sure about this? Usually the stair effect is caused by a lack of anti aliasing. Rendering the image at a huge resolution then doing a resize with proper resampling is more or less (...) (20 years ago, 30-Sep-04, to lugnet.cad.ray)
|
| |
| | Re: Radiosity example (F1 Ferrari) once again
|
|
Am Sonntag, den 26.09.2004, 10:46 +0000 schrieb Jan Folkersma: (...) Well, I don't have a problem with "mixed" models with LGEO elements and standard parts. The big advantage of LGEO is, that the edges are rounded a bit, so you don't need the gap (...) (20 years ago, 30-Sep-04, to lugnet.cad.ray)
|
| |
| | Re: Radiosity example (F1 Ferrari) once again
|
|
Mine look purhaps abit 'edgy' since I don't like to use the lgeo library. Too many parts are not available and if I combine them with the standard parts it don't look all that good. (2 URLs) first attempt>> This is my first attempt with Nico's (...) (20 years ago, 26-Sep-04, to lugnet.cad.ray, FTX)
|
| |
| | Re: Radiosity example (F1 Ferrari) once again
|
|
(...) Yours look good as well but the edges seem a little "jaggy". Are you using anti-aliasing? The good news is that Nico's setting are a snap to implement. -Orion (20 years ago, 25-Sep-04, to lugnet.cad.ray, FTX)
|
| |
| | Re: Radiosity example (F1 Ferrari) once again
|
|
Aaaarrghh! I thought my renderings were the bomb (URL) galery>> but now I've seen Nico's pictures, I guess I'll have to start all over! :) (20 years ago, 24-Sep-04, to lugnet.cad.ray, FTX)
|
