Maxwell V2 is out
-
I guess thats one of the things that having a studio feature has at advantage, it is so fast to go through a list of materials for editing where one can drag and drop maps from other materials and / or replace materials to geometry. And of course to do this without full entourage where it can be gragged in later.
The light layers functionality sounds great!!!
-
Most likely using proxies. If you call your tree component "tree" then make a new component of a tree shaped box and call it "tree_dummy", all the "tree_dummy" components will be replaced with "tree" components on export.
-
I just downloaded SKindogo and I am impressed. After working with Maxwell since it came out I think its time for a chance. NL(Maxwell) has a company-character bug that could be described as indifference toward their clients. Maxwell by itself is a rather superb application but the userinterface just does not make sense. That is because they hire the wrong people to do the job. They don't see it themselves and due to the amount of modeling app's they cater to they can not really provide service or decent plugin's update to keep up with the bugs.
I now own the v2 of Maxwell but can not use the appropriate plugin to render with, I have to reinstall the old plugin to export to Studio and render from there. If they had tested this at all on an OSX system they would have fixed it before releasing the update. Another problem is that NL markets Maxwell v2 as something big for a while so you get all excited. It feels like having tickets for a big show and when you have seated yourself to watch it happen a curtain rolls down before your OSX-SU seat that reads sorry we did not expect you here, wait till the next show.....
For how many times would you put up with that. I do not give up so easily were I should have quickly moved on. I am going to seriously look into Indigo, tx Kwistenbiebel for showing me your examples. How did you do the trees rendered in SKI ?By the way Richard, you are right about the rather messy new layout in Studio. even though it is advertised as comletely new and rewritten it still lacks hiärchy. Its hard to find what you need and it is needlessly complicated to work with.
-
I didn't use proxies in those images.The tree in the front isn't really that high poly and there's a 2D clipmap tree line in the background.
The whole scene doesn't weigh more than 11 Mb. -
I have to agree with Whaat.
Indigo, even though it is unbiased, works very well in a design workflow of trial/error and constant design changes.
The biggest advantage of Indigo over Maxwell is that the workflow is 'non-destructive' as you don't have to export to a 'studio' every time you do design changes.
Also, you can easily launch several renders at the same time (I sometimes launch 5 simultaneously on my octocore using Indigo 64 bit, while still being able to continue modeling!).The only disadvantage of Indigo, but that counts for Maxwell as well, is the render time to get things clean.
That is the reason why I also use Vray.An example of how I use Indigo for pre-design (extension of an existing office building):
Those 4 images were rendered simultaneously. Launched all of them in the evening, put together on a sheet the next morning, ready for review.
The fastest workflow I experienced using any render engine,especially in terms of material and light setup!
-
Ok I've had a play with Indigo again and see there has been some huge development on that side!!
Speed of initial clean up (my biggest concern) I'll still stick with my initial thoughts that it's slow in that regard, rendering out at 640 x 480 res allowed by the demo seemed very slow in comparison to Maxwell when rendered in any of the unknown terms!
There certainly are thing that REALLY shined in regards to the tonemapping, camera, film etc settings once rendering and these seem to be the real beauty of indigo though man are there still so many darn tech terms and thing for me that could be made so much more simple!
Being able to select from multiple film responses and adjust sky and sun levels independantly was a beauty though I so wished these and other lighting layers could be named rather than trial and error! How does on zoom in on the render window?
Still have little understanding of the material editor eg is 20 for bump high? (who knows without reference limits), what does the power slider do? Is it an exponent increaser for all settings? And for god sake why does Indigo have to utilise every single terminology adverse to the norm if x=R, y=G, Z=B why not just RGB and have it done with it! Not an individual biggy but just reinforces I guess my belief that the developers have always just taken the tact of proving one up on the understanding of all the techno talk that goes into producing an engine!
Material blending is still feeling clunky and the need to go back into SU each time to make a material change when preview is painfully slow
How does one stop the material preview for generating? And again the material preview is SO slow!!!!OK these are just initial thoughts but many however do in some way reinforce my earlier feelings, that said howvever I do see some of the inherant beauty of Indigo as a useful tool just seems it's still a ways off being particularly user friendly and still feels beta like!
Seriously I do't wish to sound negative I do see some amazing potential here but just wanting a much faster and intuitive workflow I guess! Well done has to be said on some of the Indigo features all round!
-
@richard said:
How does on zoom in on the render window?
The plus and minus keys on the numberpad. Pressing 0 gets you back to the original view.
@unknownuser said:
Still have little understanding of the material editor eg is 20 for bump high? (who knows without reference limits), what does the power slider do? Is it an exponent increaser for all settings? And for god sake why does Indigo have to utilise every single terminology adverse to the norm if x=R, y=G, Z=B why not just RGB and have it done with it! Not an individual biggy but just reinforces I guess my belief that the developers have always just taken the tact of proving one up on the understanding of all the techno talk that goes into producing an engine!
bump is measured in meters, so yes, 20 is high
As a general rule everything in indigo is done in SI units, so usually something to do with meters or stuff per meter.The power slider increases the power in watts, although usually i find it a lot faster to use one of the presets and tweak that if necessary rather than faff about making a new emitting material.
Might be worth having a look at the material editor while your in the business of trying out indigo. Its much better at putting units next to everything, and has lot of nice little colour pickers etc. the interface is a little clunky, though.
As for the general speed concerns, i have a feeling maxwell has a separate preview engine (and indigo doesnt), although i might be making that up.
-
@remus said:
bump is measured in meters, so yes, 20 is high
As a general rule everything in indigo is done in SI units, so usually something to do with meters or stuff per meter.Really? Oh.
Thanks!@unknownuser said:
Might be worth having a look at the material editor while your in the business of trying out indigo. Its much better at putting units next to everything, and has lot of nice little colour pickers etc. the interface is a little clunky, though.
I've been using the material editor I think (the material button on the indigo tool bar)!! How else can one set attributes for material values?
@unknownuser said:
As for the general speed concerns, i have a feeling maxwell has a separate preview engine (and indigo doesnt), although i might be making that up.
Yes mate you can chose either of two engines for material preview, the cleaning of the material preview is very fast and clear, I haven't really waited long enough for the indigo mat preview to clean to anything really that clear enough for reference!
I found something of a manual in the application folder though just covers render settings yet nothing about materials, I'll look through that and see what I can work out!
Thanks for your help mate!
-
If you have a look in the forum the latest beta version includes a standalone material editor (although you have to look for it in the program files folder.)
Its a bit more comprehensive than the skindigo material editor and i think doing blends is meant to be a bit easier, although i havent tried it myself.
-
Well a patch is out and SO many fixes! Will be good to see when Plugin fixed / improved with new developer!
-
Richard, have you tried it with the new patch? Looked promising from the release notes but I haven't gotten a chance to test it yet.
-Brodie
-
So far, I would like to say that MWR2 is amazing, but sadly, i cannot. I DL'ed it to try it to see if there was a boost in render speed and so on, but thus far, I cannot even render after DL'ing.
The Sketchup export no longer works for MWR1.7
I have no rendering functionality whatsoever as it stands. My opinion is to not update or even try MWR2 until these issues are fixed.
And, yes, I DO own a license and 2 seats.
-
Mate I think I read of a similar incident and it was suggested an uninstall of 1.7's plug and 2's be removed and 1.7's reinstalled!
I worried of such a problem so never installed the plugin - just worked on existing exports from 1.7 while trialling v2 demo!
The new improvements look great though the plug needs attention quickly obviously! It's under a new developer so we could be looking sweet!
I'd suggest making V2 copies of old materials and export through the old plug, you'll want to edit them likely anyway, bump will for most be through the roof on old materials given the improvements to bump!!
-
Richard, indeed, I'm excited about JDHill developing the plugin as well. I THINK he did the Rhino plugin which looks great. Can't wait.
-Brodie
-
Hm, yes, looks like things have taken a turn for the better. Let's wait and see.
Advertisement