I checked the tut. That is some model! Excellent work.
Thanks for the tutorial.
I checked the tut. That is some model! Excellent work.
Thanks for the tutorial.
@solo said:
if anything wait for Podium version 2 as it will not be KT based.
I may have seen 'something' by now. Let me put it this way: I got my wallet handy, as Podium's future looks very, very bright. Some may even be quite surprised.
Nuff said - I don't want Sepo and TBD coming after me.
These look good, no doubt about it. But ... how about KT's interface? Has it become even more, errr, "whoa, I must've stepped into a cockpit"?
Did anyone mention Podium's ease of use yet? Not to be overlooked, I think. Ease of use = speed and effiency.
@solo said:
Oh crap!!
I just offered you grass over the internet
And you posted renders of POTs at TBD Towers. I see a pattern emerging.
Ah. Now I understand. When you wrote:
“From the images posted, I really don't see what there is to get excited about. All the images are grainy and aren't anywhere near as good as what VrayforSketchUp (...) can produce.”
you actually meant:
“From the images posted, I really don't see what there is to get excited about. All the images are grainy and aren't anywhere near as good as what VrayforSketchUp (...) can produce. Then again, the annotations say these were done on a pretty low-grade machine, using an unbiased render method. So, in fact, it’s quite feasable that if one were to render these on a decent computer for the same amount of time, the result would be quite different. Let me rephrase that: that’s a certaintity. So ... in the end, it might be quite possible that KT can in fact, given you have the time, produce images that are better than Vray’s, as unbiased rendering, in terms of quality, generally is the better solution.”
It seems we agree. Which, of course, is a good thing.
What are you trying to point out here? That KT can't produce decent images? Or that KT can produce decent images, though it might take some time?
@dzinetech said:
@unknownuser said:
Read what's under the pictures, please.
Your point being? Of course I've read the annotation below the images. What counts is the quality of the final image produced before post-processing and in my opinion its not that impressive based on the examples provided. Yes the KT team do an admirable job working on a program that is free for all to use yet I personally dont think that it should be used as an arguement for the image quality it produces.
Let me walk you through it. "Rendered in MLT(BPT) mode for 5 hours... (single core machine)"
Unbiased render method. Thus grainy result after rendering on a single core machine for only 5 hrs.
I could go on like this, but sometimes you just gotta with Mies and think: less is more.
I'm neither a Max or a KT user, but I feel the need to add something nonetheless. I'm like that. Ask me mum.
Here it is: http://usa.autodesk.com/adsk/servlet/item?siteID=123112&id=5666143&linkID=5572501
Opinion's free, but facts are sacred.
@dzinetech said:
From the images posted, I really don't see what there is to get excited about. All the images are grainy and aren't anywhere near as good as what VrayforSketchUp (even in its frustratingly buggy first release) can produce.
Read what's under the pictures, please.
I had a quick look. http://www.3dworldmag.com/page/3dworld?entry=3d_world_99_s_sketchup
Edit: always second ...
"Lux need to work the importer so it only opens the SketchUp layers that are turned currently turned on. That would be a help."
I agree, that would be great. Come to think of it, you'd expect a feature like that for the price they're charging.
"Also, there are times that the imported geometry cannot by selected. It's very strange and seems to import duplicate geometry with some odd icons. None of this geometry can be selected using poly, edges or vertices."
Yeah ... I've noticed that. Very annoying. Lux better get that sorted out before the official version of the translator is released.
As for the 99 $ - I really don't care. But I do expect everything to work as it's supposed to.
"I would think just about every modeler would want to put good inferencing and snapping like SU in their application."
Aye, that's one the things about SU I simply love. Would be better if the boys at Google would make SU able to handle high poly models, though.
That would be ... drooling
You’re right it’s not explicitly meant for arch viz - SU’s far more efficient for that. Hence the ‘SU translator’. As far as rendering goes, it’s good, though.
As you can surely tell, I’m not all that great at texturing and lighting just yet, but I’ve rendered some fairly complex test scenes on an 8 core machine, and I must say: modo delivers good quality at blazing speeds.
Biggest downside is indeed modo’s complexity. I’m putting in two 12 hour days a week to learn how to use the app at a decent level, and I’m pretty sure it’ll still take me many, many (many, many ...) months.
Nevertheless: I’m intruiged by it.
Let's see how Podium V2 compares to it ...
Imported this model (it's an Evermotion one) into modo using Luxology's new SkethUp Translator, of which a beta has been released recently. Not that impressive, as I currently haven't quite figured modo out yet. But! It rendered @ 1800 x 1600 / 300 dpi in 7 minutes and 34 seconds on a moderate dual core. Modo's rendering speed scales up almost linear with every core you throw at it, so this'll most probably render in 2 minutes on my octo core. Not bad!
@roger said:
Stinkie, I don't understand what you meant about vegetation on mountains. Out here in the Sonoran desert the only vegetation on the mountains is more rocks. It looked like home to me .
Hmm. Guess I'm used to 'European looking' mountains. The ones Solo used looked rather, er, exotic to me. Not too many deserts in Belgium.
Advertisement