C3POwen
-
Posts
426 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Everything posted by C3POwen
-
If you can instead go to "Edit > Copy Pane" within POV-Ray and then paste the results into a plain text document, it will mean I can see all of the render data. -
5867 Super Speedster (Model D) [Creator, 2010] MPD file This one is a "rare" LEGO Club exclusive alternate of 5867, which forms a "D" model. For those interested, I have uploaded the instructions here.
-
I have to say I already do this myself, as I like to use floor and light settings that are different from LDView's default settings, so use this function. If you're rendering things and you want to keep the same settings between renders, this is very, very useful! My current file is set up like this. Incidentally, LDView Travis, is there any news on the next update to LDView? Would you be able to supply a copy of the Messages pane from POV-Ray from after you've finished a render?
-
Funnily enough, I was thinking of doing a small explanation at some point, probably with some example images. I will update the guide with some extra information on this, for those that are interested. I usually set the fogging to sit a certain distance away based on the model's size. As long as you place this below all of the declarations of an LDView-generated POV-Ray file, I find that the following works quite well: // Fog #if (LDXFloor != 0) fog { distance LDXRadius*50 color rgb <255, 255, 255> } #end This will only use fogging if the floor is switched on, and should place it far away enough to not cause an issue. You can change the colour to something more appropriate using standard RGB. The second issue with the blobby artifacts in the shadows is due to the radiosity settings. I use settings based on some posted by whitew0lf, which I use to replace the default "Radiosity_Final". Navigate to your POV-Ray includes folder (usually at "C:\Users\[uSERNAME]\Documents\POV-Ray\v3.7\include" and find the "rad_def.inc" file. This contains all of the radiosity settings. Look for a section that starts with "#case (Radiosity_Final)" and modify the below options to match this: pretrace_start 0.08 pretrace_end 0.005 count 800 nearest_count 20 error_bound 0.02 recursion_limit 1 low_error_factor 0.25 gray_threshold 0.0 minimum_reuse 0.015 brightness 1.0 adc_bailout 0.01/2 Render time will increase (and hugely so for transparent parts) but the artifacts will be gone. Some of the numbers are probably overkill, but I haven't had time to test this with trial and error.
-
GUIDE UPDATE: I have updated the LGEO-Update.zip file in the Downloads section with 13 new parts and 1 updated part. The UPDATED and NEW LGEO parts from the 2013-01-06 update Another relatively small LGEO update, but this time with mainly new parts.
-
30184 Little Helicopter [Creator, 2013] MPD file 31003 Red Rotors (Model A) [Creator, 2013] MPD file 31003 Red Rotors (Model B) [Creator, 2013] MPD file 31003 Red Rotors (Model C) [Creator, 2013] MPD file
-
31006 Highway Speedster (Model A) [Creator, 2013] MPD file 31006 Highway Speedster (Model B) [Creator, 2013] MPD file 31006 Highway Speedster (Model C) [Creator, 2013] LDR file Next up... 31003 Red Rotors.
-
Happy New Year, all! GUIDE UPDATE: I have updated the LGEO-Update.zip file in the Downloads section with 8 new parts, 1 updated part and 5 fixed parts. The FIXED, UPDATED and NEW LGEO parts from the 2013-01-01 update
-
40030 Duck with Ducklings [seasonal: Easter, 2012] MPD file
-
[Software] SR 3D Builder Lego simulator
C3POwen replied to xSergio74's topic in Digital LEGO: Tools, Techniques, and Projects
Milky White is a translucent colour that started being used by Lego in the 1960s, and was often used for Technic axles. BrickLink groups it with the Glow in the Dark colours, which can be seen on their colour guide under "Milky Colors". It exists in the official LDraw colour file (last updated in September), under "LDraw Milky Colours" and has the LDraw number of 79. The official Lego colour name is "Nature", which is Lego colour number 20, and can be found in LDD (although LDD shows it as too transparent). -
The third of 2012's LDraw updates was released yesterday, and the zip file containing the new and updated parts can be found here. The rundown of the update is as follows: Total core library files: 829 New core library files: 564 New parts: 354 New subparts: 154 New primitives: 31 New hi-res primitives: 25 New alias parts: 8 New physical colour parts: 17 A preview of the parts can be found on this page, although it is fairly image-heavy and may take a short while to load. There are some new parts from the Friends, Super Heroes and Lord of the Rings themes, as well as other assorted pieces. All-in-all, some excellent work from the LDraw Parts Tracker contributors. For those interested, parts still awaiting certification can be found in this list of unofficial LDraw parts.
-
A couple more seasonal models as the year draws to a close... 30008 Snowman [Creator: Seasonal, 2009] LDR file 30009 Christmas Tree [Creator: Seasonal, 2009] LDR file For those interested, the snowy backdrop was created by adding the "normal" line to the floor setting in POV-Ray: // Floor #if (LDXFloor != 0) object { plane { LDXFloorAxis, LDXFloorLoc hollow } texture { pigment { color rgb <LDXFloorR,LDXFloorG,LDXFloorB> } finish { ambient LDXFloorAmb diffuse LDXFloorDif } normal { bumps 1 scale 200 } } } #end
-
A few small Creator sets I was surprised to not see in the index. 7803 Jeep [Creator, 2009] LDR file 7804 Lizard [Creator, 2009] LDR file 7805 Shark [Creator, 2009] LDR file
-
Well, both the arms and legs need a little work on them, as they're not perfect, so you may want to hold off for the time being. The legs have a few small gaps on them which can be seen when rendering, and the connection points on the arms need to be carved out a bit, as they currently go through the torso, rather than just the arm holes.
-
GUIDE UPDATE: I have updated the LGEO-Update.zip file in the Downloads section with 3 new parts, 7 updated parts and 1 fixed part. The FIXED, UPDATED and NEW LGEO parts from the 2012-12-26 update Well, I've finally passed the 100 part mark for my LGEO Parts Pack. An update that those who render with minfigs are likely to appreciate. It seems that the LGEO.xml file for LDView was set to point to the old naming conventions for the minifig body pieces, so I have updated them to match the current LDraw numbers and they should now render using native LGEO parts, which have been there all along.
-
I have to say that that's often what I look for in sets I build digitally. Of course, sometimes a quick easy build is just as good as a complex one! Thank you for your kind words! Happy Winterval to all!
-
A festively-coloured render before Christmas fully takes over. 8157 Ferrari F1 1:9 [Racers, 2008] LDR file Errors: - Missing stickers A larger version of this image can be found here.
-
21102 Minecraft Micro World [CUUSOO, 2012] MPD file
-
55001 Universe Rocket [LEGO Universe, 2010] LDR file
-
I don't normally build Technic models, but liked this one enough to give it a go. The flexible parts (which aren't perfect) will only show in MLCad and LDView if LSynth is installed. 8256 Go-Kart [Technic, 2006] MPD file
-
7601 Go-Kart [Creator, 2006] LDR file 7602 Hummer [Creator, 2006] LDR file 7603 Dump Truck [Creator, 2006] LDR file
-
GUIDE UPDATE: I have updated the LGEO-Update.zip file in the Downloads section with 6 new parts, 1 updated part and 31 fixed parts. The FIXED, UPDATED and NEW LGEO parts from the 2012-12-15 update The main improvement here is that the tips for a lot of slopes now render at the correct height (about the same height as a stud). There are some slope parts that I still need to fix, and not all of them are particularly straightforward. I've also started to play with image maps, where a part is overlain with an image (such as with the two 1x8 tiles from the Architecture series). The colour definitions also includes the Chrome Gold update from the 12th.
-
Well, better late than never... I've updated the colour definition for Chrome Gold (which I think looks a bit more accurate) and I've updated the current version of the LGEO Parts Pack download with this definition. For a comparison, please see the below images, which are from 79000 Riddles for The Ring. Before: After: I've also been working on a few new parts, as well as a number of part fixes, and will look into releasing a full update to the parts pack soon.
-
Some more of the latest Creator sets. The joints of the two robots can be rotated on their correct axes when using MLCad. 31007 Power Mech (Model A) [Creator, 2013] MPD file 31007 Power Mech (Model B) [Creator, 2013] MPD file 31007 Power Mech (Model C) [Creator, 2013] MPD file Errors: - None 31008 Thunder Wings (Model A) [Creator, 2013] LDR file 31008 Thunder Wings (Model B) [Creator, 2013] MPD file 31008 Thunder Wings (Model C) [Creator, 2013] LDR file Errors: - Missing 2x 61254 Tire Offset Tread - Band Around Center of Tread [substituted with 3483]
-
@hrontos is indeed correct. When you export a model from POV-Ray, if you use a transparent part it will use the "clear" variation of a part where it is merged together to create a completely "solid" part. If you look through your POV-Ray file, you'll see parts appended with "_clear", so a standard 2x4 brick would show as "lg_3001_clear". If you remove the "_clear" from the end of the part name, then it will use the standard non-merged part, where you'll notice some of the component shapes used to create the shape that would not normally show when being rendered with a solid/opaque colour. I ran some tests using a transparent blue 2x4 brick rendered at 1600x900 with anti-aliasing turned on and no radiosity, and the results were as follows: "Standard" LGEO part: 33 seconds "Clear" LGEO part: 42 seconds I then changed the colour to solid/opaque blue, and rendered both variations of the same brick, using the same settings as above: "Standard" part with solid colour: 03 seconds "Clear" part with solid colour: 04 seconds Although using the "non-transparent" part may be slightly quicker, the more transparency you use will still cause it to render slowly. If you're using transparent bricks to render your water, then that could take days! If you're using a plane to render the water, and just wish to apply some ripple effects, then perhaps try using a solid colour with some reflectivity to simulate a water effect. Some good guides on this can be found here: http://www.f-lohmuel...grnd/p_wat1.htm http://www.imagico.d...ter/water01.php