|
 | | 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
(score: 0.432)
|
|
| | 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)
| |
|
rendering
(score: 0.432)
|
|
| | 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)
| |
|
rendering
(score: 0.430)
|
|
| | Re: lgeo renders wrong part
|
| just to reexplain the problem. 3939 renders as 3942 and 3942 renders as 3943. while 3943 renders as LDraw 3943 because there is no 3943. (hahah) here is the header for my LCAD 3939.dat 0 Slope Brick 33 3 x 6 0 Name: 3939.dat 0 Author: James Jessiman (...) (22 years ago, 10-Sep-02, to lugnet.cad.ray)
| |
|
rendering
(score: 0.429)
|
|
| | Re: lgeo renders wrong part
|
| (...) You have to modify the *.inc files in your LGEO installation. An easy way to resolve the problem with part 3939 would be to rename/delete the file lg_3939.inc. When L3P can't find this file, it will use the regular LDraw 3939.dat as the basis (...) (22 years ago, 9-Sep-02, to lugnet.cad.ray)
| |
|
rendering
(score: 0.429)
|
|
| | Re: Weird Logo Issue at L3P Quality Level 3
|
| (...) I dunno... I'm still coming to grips with the whole BFC thing, so this subpart whatsit doesn't seem like too much extra typing! That reminds me--is BFC-compliance mandatory for new parts submissions, or is it simply a good idea? I confess that (...) (22 years ago, 9-Sep-02, to lugnet.cad.ray)
| |
|
rendering
(score: 0.429)
|
|
| |
|
rendering
(score: 0.428)
|
|
| |
|
rendering
(score: 0.428)
|
|
| | Re: L-GEO
|
| (...) Only one small problem which I SHOULD have caught when I edited the tutorial. Nowhere does it say HOW TO USE LGEO Library parts. =( Jeroen do you have time to add a section on how to use the LGEO library files. Rene Virsik for now here is a (...) (22 years ago, 31-Aug-02, to lugnet.cad.ray)
| |
|
rendering
(score: 0.428)
|
|
| | Re: invisible transparent part
|
| thanks for the heads up to check the part. I checked in MLCAD, and the part was set to ghosted. Here is the rendering: (URL) canopy is temp until the actual part is released. The part, just incase someone cares, is: 41883 Smoke Windscreen 4 x 6 x 2 (...) (22 years ago, 29-Aug-02, to lugnet.cad.ray)
| |
|
rendering
(score: 0.428)
|
|
| | Re: L3P Options?
|
| (...) That is excellent news! I missed the first post (ref'd above) but that is exactly what I meant. Would it be possible to include a file in the directory with a name like L3Colours.inc or something that declares any modified colours one wishes (...) (20 years ago, 13-Apr-05, to lugnet.cad.ray)
| |
|
excellent
(score: 0.427)
|
|
| | CORE_SETTINGS.INI
|
| ; CORE_SETTINGS.INI ; ; included by RENDER.INI ; external animation loop Clock=0 ; internal animation loop Final_Clock=1 Final_Frame=-1 Initial_Clock=0 Initial_Frame=1 ; subsets of animation frames Subset_End_Frame=-1 Subset_Start_Frame=-1 ; cyclic (...) (22 years ago, 15-Aug-02, to lugnet.cad.ray)
| |
|
rendering
(score: 0.425)
|
|
| | 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)
| |
|
rendering
(score: 0.425)
|
|
| | 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)
| |
|
rendering
(score: 0.423)
|
|
| | 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)
| |
|
rendering
(score: 0.423)
|
|
| | 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)
| |
|
rendering
(score: 0.423)
|
|
| | 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)
| |
|
rendering
(score: 0.423)
|
|
| | 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)
| |
|
rendering
(score: 0.423)
|
|
| | Re: Trouble with POV 3.5
|
| <snip> (...) Why are we trying to use Pov 3.5? What is computer user's *NEED* to have the latest and greatest? Does Pov 3.5 provide the LDraw rendering community anything NEW that 3.1 did not? Why go thru all the headaches of learning 3.5 when 3.1 (...) (22 years ago, 24-Jul-02, to lugnet.cad.ray)
| |
|
rendering
(score: 0.422)
|
|
| | Re: Aspect ratio (via L3P)
|
| "rmelkert" wrote... (...) For the coming release I have just added -car<ar> camera aspect ratio, default is 1.333 (4/3) User must remember to change the size of the rendering to the same ratio. /Lars (22 years ago, 24-Jun-02, to lugnet.cad.ray)
| |
|
rendering
(score: 0.417)
|
