|
 | | 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: 1.304)
|
|
| | 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: 1.302)
|
|
| | 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: 1.302)
|
|
| |
|
rendering
(score: 1.300)
|
|
| |
|
rendering
(score: 1.300)
|
|
| | 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: 1.300)
|
|
| | 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: 1.300)
|
|
| | 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: 1.300)
|
|
| | 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: 1.299)
|
|
| | 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: 1.298)
|
|
| | 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: 1.298)
|
|
| | 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: 1.298)
|
|
| | 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: 1.297)
|
|
| | LEGO Color Reference
|
| I've been playing around a bit with LDraw, L3P, and POV-RAY over the past few weeks. In August I tried to do some rendering of individual LEGO elements and found it to be a lot more challenging than I had expected. After much hair-pulling and (...) (22 years ago, 3-Oct-02, to lugnet.general, lugnet.cad.ray, lugnet.announce) !!
| |
|
rendering
(score: 1.294)
|
|
| | Re: Pov-ray syntax editors?
|
| Ok so we have POVRAY for win32 E-macs Vim that's good but I'm looking for one that is small and bit notepad like vim is nice I tryied it on linux I got lin mandrake on my D:\ drive but I whould like to use pov-ray for dos for rendering and a (...) (22 years ago, 15-Oct-02, to lugnet.cad.ray)
| |
|
rendering
(score: 1.292)
|
|
| | I'm not sure on this error
|
| I'm rendering an animation and some frames they take too long specially on my laptop IBM 770z 128MB of RAM PII 366MHZ aslo in my desktop anyway the error is in "so far, Rendering frame 31 going to 105.camera is inside a non-hollow objec. Fog and (...) (22 years ago, 27-Oct-02, to lugnet.cad.ray)
| |
|
rendering
(score: 1.292)
|
|
| | L3pao/Lgeo problems
|
| - When render a model including Technic liftarms 1x11.5 double bent using Lgeo parts, 2 additionnal holes are generated (see (URL) left half is rendered with lgeo, right half without) - And I have a problem with Lgeo path too: while L3pao correctly (...) (22 years ago, 24-Oct-02, to lugnet.cad.ray)
| |
|
rendering
(score: 1.290)
|
|
| | Re: Rendering over lan?
|
| (...) That is entirely dependent on the rendering engine. PovRay is single threaded, so the only way to do it is to run multiple copies. This has other problems, but there's a bit of a discussion about how to do it here (URL) (22 years ago, 11-Dec-02, to lugnet.cad.ray)
| |
|
rendering
(score: 1.289)
|
|
| | Re: Star Wars related wallpaper
|
| Thanks. The links have been fixed. The 800x600 render was the original version. It's been replaced now. I did use the radiosity feature. Great as it is, radiosity will kill rendering time. The 1024x768 took 12 hr. 15 min 8 sec. Probably would have (...) (22 years ago, 20-Nov-02, to lugnet.cad.ray, lugnet.starwars)
| |
|
rendering
(score: 1.286)
|
|
| | Re: Rendering over lan?
|
| There is another way, but it's not for the feint of heart. It's distributed raytracing. People have hacked pov and made it run across multiple machines. I'm not sure if it's actually been done on Windows OSs yet, bet it has worked for other people (...) (22 years ago, 12-Dec-02, to lugnet.cad.ray)
| |
|
rendering
(score: 1.286)
|
