C3POwen
-
Posts
426 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Everything posted by C3POwen
-
The results look very realistic thanks to the lighting, although the colours look a bit washed out. I certainly wouldn't advocate doing this in regards to any software. -
Now that's some render time! I'm using a slightly less fast Core i5 750, running at 2.67 GHz, so would be interested to know which flavour of i7 that you're using. That's an interesting point. I guess that large flat areas without much in the way of reflection would perhaps not benefit from worrying too much about how well POV-Ray can antialias. I still find that complex transparent parts (essentially the corners of windscreens or anything with lots of studs) can slow things down a lot, as I found with this old render. The transparent red wings took forever. Would you recommend using different AA settings? Perhaps AA 0.0 for better quality, rather than 0.3?
-
To be fair, I have used a tweaked version of POV-Ray's Radiosity_Final setting, which is set to create images of slightly higher quality than the default version included. Also, the 8+ hours is rare for most of the renders I do, with 1-3 hours being more common. See it as a warning for anyone wishing to render anything with a lot of transparency!
-
7347 Highway Pickup (Model A) [Creator, 2012] MPD file For those wondering on render times for an image like this, with complex transparent parts (windscreens, light bricks) and the use of radiosity, the render time at 3200x1800 was... wait for it... 8 hours 31 minutes and 37 seconds. Test renders were, of course, much quicker, as they were rendered at a low resolution with fast, low-quality radiosity settings.
-
I'm afraid not, and I currently have no plans to start experimenting with Blender or 3ds Max. A Blender import script seems to exist, but is quite possibly incredibly out of date, and 3ds Max is paid-for software, which I feel automatically excludes those who do not wish to purchase it (i.e. me). POV-Ray is free, can utilise the LGEO library, and the latest version works without any real issues, so that's good enough for me.
-
Not a problem. A lot of people here are non-English, it being Eurobricks. However, the "16 or 32 bit" question does not seem to relate to any previous posts or your current query, hence the confusion. When I first create my model in MLCad, the first piece is always laid at the 0,0,0 and I build from there. If you need assistance with MLCad, then I would recommend the link I suggested earlier. If you mean within POV-Ray, I can see no real need to force it to be positioned at these co-ordinates, as LDView works the rest out automatically.
-
Again, you're going to have to be more specific. 16 or 32 bit what? If there is something from a previous post that you are referring to, it would help both me and the length of this thread if you can use the "multiquote" function so that you can include whatever it is you're referring to (excluding previously-posted images) in your post. That way I do not need to create a new post just to find out what you're asking about. If I'm able to, I'm more than happy to help with any POV-Ray questions (even though I'm by no means an expert and the answer might mean redirecting you to another site with more information), but would appreciate some clarity to the questions being asked.
-
I might need you to be a little more specific about which bit you're referring to. I did notice that your model is not technically facing forward but to the left, which I corrected prior to exporting from LDView for the purposes of my render. I've also clarified the radiosity section. You need to ensure that you are using a fresh POV-Ray file before copying and pasting the settings in, and this should allow the render to produce something similar to the image I posted.
-
Thanks for the comments, guys. I've just started submitting some (fairly basic) parts to the LDraw Parts Tracker, so can hopefully add more to the LDraw community if I can.
-
The exact settings that I used are in the guide. Under "7.6 Radiosity". The link I posted is a starter for HDR, which is mainly for creating realistic lighting. For a non-LEGO example of using HDR to create reflections, please have a look at the right side images on this page.
-
My settings are in the guide -- I feel it is fairly well explained, and all anyone really has to do is simply copy and paste the settings into their POV-Ray file. I may update my lg_color.inc file to make the parts slightly more reflective when I've done some testing, as I do feel that they are a little too flat. To get other reflections would perhaps require the use of HDR lighting, which I do not plan to cover at the moment. There are plenty of sites that explain how to achieve this. A good start would be bricks'n'gears. To make the wheels look like rubber, you need to set them to "Rubber Black" in LDraw/MLCad before exporting the model to POV-Ray.
-
I use radiosity on my more recent renders, which produces better general lighting as well as allows simplified shadows that don't leave parts of the model blacked out. I've run a render of your model using these settings to show you the outcome: You can find info about it at the end of the second post, under 7.6 Radiosity.
-
has an unhealthy obsession with the LEGO games, and can't wait for LEGO Batman 2 and LEGO Lord of the Rings.
-
-
If you look at the beginning of the guide that this thread has carried on from, then directly under 3. MLCad, I advise on different rotation settings and how to set them up. This will allow you to rotate the model with more fine-grain control. There are plenty of guides online to using MLCad and LDraw. Perhaps you should have a look at Holly Wood's tutorials for more tips.
-
I'm glad you got it working, although there is definitely something odd going on there. Have you thought about upgrading to POV-Ray 3.7 at all? A fresh install may fix your issues, and it's much quicker on multi-CPU systems.
-
@hrontos is right. The "Messages" tab contains conflicting information. The label for the resolution is "1280x1024", but POV-Ray sees 320x240: Preset INI file is 'C:\PROGRAM FILES\POV-RAY FOR WINDOWS V3.6\RENDERER\QUICKRES-B.U.INI', section is '[1280x1024, No AA]'. Output Options Image resolution 320 by 240 (rows 1 to 240, columns 1 to 320). Try using my version of quickres.ini instead: quickres.ini Make sure you browse to wherever it's stored in the Render > Edit Settings/Render window before rendering, and select the desired output size.
-
Looking at your file, POV-Ray is rendering the file at 320x240 -- look at the first line under Output Options: Output Options Image resolution 320 by 240 (rows 1 to 240, columns 1 to 320). Output file: C:\Users\admin\Documents\6941 Battrax.bmp, 24 bpp (system format) Graphic display......On (gamma: 2.2) Mosaic preview.......Off CPU usage histogram..Off Continued trace......Off Can you go to Render > Edit Settings/Render and under INI File click on Browse and select the "quickres.ini" file. Now from the dropdown to the right of Section select the resolution you want to use (e.g. 1280x1024, No AA) and click on the Set but don't render button. This will close the window. Now render the image and, if it does not render at a size higher than 320x240, can you please attach the subsequent "Messages" information.
-
Could you please supply a copy of the "Messages" window from AFTER you have run a render that has not rendered at the selected size.
-
9497 Republic Striker-class Starfighter [star Wars, 2012] MPD file (not all submodels shown, but included in file) The wings pivot correctly on the main part of the fighter, and the cannons pivot correctly on the wings (see below image). Errors: - Missing 1x 92081 Minifig Hair Combed Front to Rear - Missing correct printing The Striker-class starfighter with closed wings:
-
Can you attach one of your *.pov files in a zip file, so I can see if there's anything odd going on in it? It looks like something isn't working properly in POV-Ray. Looking at the file will help me determine if it's a declaration in the file that's causing a problem, or POV-Ray itself. Could you also copy the details of the "Messages" pane into a text document (open the "Messages" tab, go to Edit > Copy Pane and then paste into a text file) and include that in the zip file as well?
-
Have you checked the quickres.ini file to make sure that the resolution preset has not been altered to something else by accident? You should be able to do this from Tools > Edit resolution INI file within POV-Ray. [You may also want to resize the images you posted, so they stay within the 800x600 limit on Eurobricks.]
-
7959 Geonosian Starfighter [star Wars: The Clone Wars, 2011] MPD file (not all submodels shown, but included in file) Errors: - Missing 1x 61189pb04 Minifig Helmet SW Clone Trooper with Holes, Orange Stripe Pattern - Missing 1x 61190c Minifig Helmet Visor SW Clone Trooper - Missing 2x 61190d Minifig Helmet Rangefinder for Helmet SW Clone Trooper with Holes - Missing 2x 61190e Minifig Helmet Floodlight for Helmet SW Clone Trooper with Holes - Missing 1x 92751pb01 Minifig Head Modified Geonosian with Black Eyes Pattern - Missing 1x 92753pb01 Minifig Headdress SW Cerean Skull Top with White Ponytail Hair Ki-Adi-Mundi Pattern - Missing correct printing
-
5984 Lunar Limo [space Police III, 2010] MPD file (not all submodels shown, but included in file) Errors: - Missing 1x 87781 Minifig Helmet Space - Missing 1x 90322 Minifig Head Modified Jagged Bottom Edge - Missing 1x 90322pb01 Minifig Head Modified Jagged Bottom Edge with Eyes Pattern - Missing 1x 92553pb01 Minifig Head Modified Jawson with Fins and Teeth - Missing stickers / correct printing Mainly they're models that have been half-finished, such as Darth Vader's TIE Fighter. Rendering is the bit that seems to take forever! I tend to go via Brickset. If there are no official PDF instructions for the older sets, the "Links" tab for each set has an "Instructions" section with a link to Peeron, which has a lot of scans of older sets. Failing that, I'll also go to BrickFactory.
-
8017 Darth Vader's TIE Fighter [star Wars, 2009] MPD file Errors: - Missing stickers
-
5983 Undercover Cruiser [space Police III, 2010] MPD file (not all submodels shown, but included in file) Errors: - Missing 1x 85959px1 Wave Rounded Large (Flame) with Marbled Trans-Yellow Pattern - Missing 1x 87781 Minifig Helmet Space - Missing 1x 92553pb01 Minifig Head Modified Jawson with Fins and Teeth - Missing correct printing / stickers
