Maxwell Render | Official public forum

all is said in the title
and the cherry on the cake multi render region for fire

Well, that's something Studio can do right now on CPU, isn't it? Not multi region, but single region render.

How do you want to use it? Preview of several regions? Final render using draft engine?

Regards,
Fernando

I think he is referring to ability to crop the region in FIRE. So while FIRE does it's IPR progressive rendering (draft) you can define the are which you want it to refine while the rest is paused at the moment when you started defying the region.
Pretty much like it works with another render engines (say, Arnold).

Basically it just for speeding up the pre-vis process. Could be a handy little thing - altho not sure if it is something that could be added easily

Nasok wrote:I think he is referring to ability to crop the region in FIRE. So while FIRE does it's IPR progressive rendering (draft) you can define the are which you want it to refine while the rest is paused at the moment when you started defying the region.
Pretty much like it works with another render engines (say, Arnold).

Basically it just for speeding up the pre-vis process. Could be a handy little thing - altho not sure if it is something that could be added easily

That sounds interesting to me. Can't promise anything, but I will push it.

Yay!

Oh oh , other cool feature that might improve FIRE (which is already All-Star here) is the debug mode. Say in Fire you'll have a drop down menu, where you could choose to see only the first layer, or only the additive layers, or only the reflections, or only the direct diffuse, only the refractions, only the opacity and so on. That way it would be really easy to create the custom look you're up to and re-use old materials with just a few tweaks. As right now, you have to disable / enable different layers to see only the spec or only the bump, and so on.

Nasok wrote:Yay!

Oh oh , other cool feature that might improve FIRE (which is already All-Star here) is the debug mode. Say in Fire you'll have a drop down menu, where you could choose to see only the first layer, or only the additive layers, or only the reflections, or only the direct diffuse, only the refractions, only the opacity and so on. That way it would be really easy to create the custom look you're up to and re-use old materials with just a few tweaks. As right now, you have to disable / enable different layers to see only the spec or only the bump, and so on.

Same of those things are on Production engine (like reflexion or refraction passes), but it's agains the philosophy of Draft engine (the engine used on FIRE), that engine is simplier to be faster, does less things and some of them with less quality, bus it's faster for previews. Adding a lot of things would make it slower.

Would it ? I think rendering just a reflection is way faster than the complete shader. Plus it would be beneficial to see how your texture looks on a model.

We shouldn't compare FIRE to other IPRs from other engines, but the one that goes with Arnold for instance is very useful for debugging purposes, it might be a switch on/ off feature. If that really slows down the engine.
But having the ability to isolate parameter or channels that you're working with - could really benefit the artists

Just thinking

Maybe a well use of GPU engine can serve for that. GPU engine have channels, and will have passes, and it gives the first few SLs very fast.

Well, then it means Nope for all Mac users

I'm not sure how appropriate it would be to reference other render engine's IPR here.
I'm pretty sure everyone have different approaches and goals here.

Nasok wrote:Well, then it means Nope for all Mac users

Not all, we have GPU working on mac now, and some customer actually using it.

You mean that hacking method with old mac towers which completely removes the warranty ? ) not an option for a big studio more like a home-made solution which is fine - but probably not for the ones who is working in agencies.

We have posted how to do it with an external card. And we made it work on a Mac Cilinder

Right, .. right ..

but neither we or the maker of the computer are supporting it; following this procedure could make you lose the warranty of your machine or make it unusable.

I'll just leave it here.

Look, you guys do what you feel like doing, but I think it is naive to assume that majority are using Windows machines. Used to, but not anymore.
Personally, of course I prefer nvidia over Radeon - no brainier. But if this is the price for the stable operating system without random blue screens and other bugs - well, I'm down for it.

I know, you guys, probably, shouldn't think about who would use your product .. or how would it be used. But I think it is essential that until it get's into an "agencies" and "major studios" environment it will always be a Render Engine that everyone refers to, mentions it in a discussion but barely uses.

But again, don't get me wrong, I'm not criticising you guys, in fact I'm on your side, all I want is for Maxwell Render to get what it deserves. And Maxwell has a truly massive potential. And it's just sad to see how people treat it.

Nasok wrote: Look, you guys do what you feel like doing, but I think it is naive to assume that majority are using Windows machines. Used to, but not anymore.
Personally, of course I prefer nvidia over Radeon - no brainier. But if this is the price for the stable operating system without random blue screens and other bugs - well, I'm down for it.

I know, you guys, probably, shouldn't think about who would use your product .. or how would it be used. But I think it is essential that until it get's into an "agencies" and "major studios" environment it will always be a Render Engine that everyone refers to, mentions it in a discussion but barely uses.

But again, don't get me wrong, I'm not criticising you guys, in fact I'm on your side, all I want is for Maxwell Render to get what it deserves. And Maxwell has a truly massive potential. And it's just sad to see how people treat it.

I think that complain should be to Apple itself. They decided to stop using nvidia cards, they don't have graphic drivers up to date, Mac computers have OpenGL 3.3 or 4.1, both of them 7 years old. And openCL 1.2 (6 years old). It's impossible to develop a decent engine on that environment. We have done a lot of effort to support Mac computers. But we cannot do the impossible. Even if we have choosen to do the gpu engine on openCL (very bad option in my opinion), it wouldn't work on so old version of OpenCL that macs have.

Sounds like you guys are giving up Mac .. sad to hear .. well .. we all know what happens to a software that goes only with one (the easiest and the buggiest) operating system.

Thinking about what is easy to do, and what is necessary is probably two different things. And regarding mac Gpu renders .. well .. then let's not mention radeon ProRender .. GPU for macs .. 'cause that would be impossible .. right

In fact I was not complaining ... but you guys probably need to go out to the industry and see what operating system dominates .. And I can assure you design, media, production and advertising studios they all mostly on macs .. and you guys want to give it all up because you're just pissed at apple giving up nvidia ? ... well .. that is also a strategy .. just don't say it is impossible ... people say it is impossible to render on maxwell because the waiting time is too long .. but once you figure out main principles - you're good to go.