Messages

241

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-08, 16:54:34 »

Yes, I have.
But sadly I can't open the file, because we are still on Max 2017. We do not use any newer version in production, because we do not update yearly for pipeline integrity.
Most recent version I have installed would be 2018. Can you save with backwards compatibility?

Here is 2017 version:

https://drive.google.com/file/d/1aeA5Z8rfh0U2_iBp6PuOYU15N3UrT8AZ/view?usp=sharing

Dammit, I saved as 2017 then I archived it to zip. Unless 3dsmax resaves as 2020 when it archives.

Erm, I still can't open that one up. The last file from your download, vray material tests 2017.
Did you make sure you saved with backwards compatibility to Max 2017?

242

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-07, 23:58:36 »

Yes, I have.
But sadly I can't open the file, because we are still on Max 2017. We do not use any newer version in production, because we do not update yearly for pipeline integrity.
Most recent version I have installed would be 2018. Can you save with backwards compatibility?

Here is 2017 version:

https://drive.google.com/file/d/1aeA5Z8rfh0U2_iBp6PuOYU15N3UrT8AZ/view?usp=sharing

243

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-07, 15:44:17 »

I tried to download your scene, but it seems I have to request permission for this?

sorry, you should have permission now.

244

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-07, 05:03:44 »

kosso_olli, Did you figure out the Vray normal issue?

245

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-04, 17:46:40 »

You can tell that Redshift does heavy clamping by looking at the highlights in the glass. In the Corona version you get glare through the refraction, in Redshift you don't. It is one of the engines which cut many corners to gain render speed. You decide if that's the right way...

Okay here is a new render at 25 subsampling intensity.  Looks good to me now and the weird thing is it actually rendered faster, 5min 24sec opposed to 5min 44sec.  What do you think?

246

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-04, 17:34:06 »

You can tell that Redshift does heavy clamping by looking at the highlights in the glass. In the Corona version you get glare through the refraction, in Redshift you don't. It is one of the engines which cut many corners to gain render speed. You decide if that's the right way...

That might have to do with the fact that Redshift transparency and reflection refraction depth is not high, nor can it be set higher. This is going to be fixed with 3.0 and suppose to be even faster doing it.  Also Redshift uses 4.0 Max subsample intensity, I can try changing that to 25 like corona and see what happens.

Vray scene: https://drive.google.com/file/d/1PjdcY9oQFshSPGCEBuSRspLgie9Xbkd-/view?usp=sharing

247

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-04, 17:23:15 »

To me the normal issue seems to be related to the red and green channels, and/or gamma. There is a little tip here by Vlado, which should give you a hint. It seems the Corona version is the correct one, but I think it can be fixed.
If you could share the scene I could help you out.
Also, do you have any issues with the glass in this particular setup? Looks good to me!

I had to flip the Green channel to get correct.  Played with both gamma and channels, still get weird results. Let me package the scene it's about 500MB. Glass no, in Vray I always do reflect back side and turn up the reflection/refraction depth to 25. I do notice sometimes that the glass doesn't behave correctly still, but then all of a sudden it will render correctly, almost like a bug or something, but it's random.

Attached is something interesting, render comparing Corona and Redshift.

Corona render: 26min 36sec, was only maybe 1/4th done with rendering so expect 1-1.5 hours render.  But Corona also ran out of Ram gave me info about needing more ram in pop-up message.

Redshift render: 5min 44sec, Render was complete.  Had no message or issue with Ram let alone Vram.

248

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-04, 01:11:29 »

Since you guys are avid Vray users, what is going on with Normal maps? Do they not work correctly or am I doing something wrong? Below is two renders one is Vray and the other is Corona, you can see how much more realistic Corona handles the Normal Maps. Especially in the Stucco.

Vray I'm using the Vraynormal map node.

EDIT: Okay so the stucco looked more correct when I imported the Normal map as gamma 2.2 or automatic, which makes no sense because all other renderers look correct when It's imported as Gamma 1.0

249

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-03, 21:12:16 »

Yes vrays supported features are amazing. Wish they would develop faster with gpu though, development on that is so slow.

250

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-03, 17:57:17 »

Erm, as I said, besides the BMW, all images are full cgi exteriors.

I guess I'm looking at this from more of a Archviz point of view.  I understand that the motion blurred exterior of the mazda is cgi, but hard to tell anything form well all the blurring. The cream side car is only 3 elements in the exterior where the rest is a photo. They look good, but when you have all elements of a full cgi archviz project, things seems to start looking well CGI.  I think the best is to have the same archviz project rendered in both, I'm trying that now and hopefully be pleasantly surprised by Vray, but so far not exactly convinced.

251

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-03, 16:43:38 »

Those are hard to tell anything because Photo-scanned objects can look just as real in a game engine. I'm talking full scenes interior and exterior, the majority of them don't look as realistic as corona.  Like I said I cannot pin it down to Lighting, Shaders, or possibly tonemapping.  I know that I've heard a lot of people also complaining how vray handles Bump mapping, so maybe it is a shader issue.  But I have to say again it's IPR and render speed is pretty amazing.

252

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-03, 16:17:00 »

Thank you kosso_olli for your info and pictures.  I agree that Vray can render cars realistically.  But find some interiors or exteriors with different materials and vegetation.  They seem to always show a plasticy look from Vray to me, now that we are use to the realism of say Corona and Fstorm. There might be a handful of them that look so good I can't tell there Vray. Every time I see a render from Vray now I can tell it is Vray, it has a flat plastic feel. Characters and cars always seem to come out good.  I think one major issue with Vray is how it handles Vegetation also, It always seems to feel less quality than other renderers.  I had to take a break because of work but I want to get back to my testing between the two.

253

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-05-01, 18:04:03 »

Yes Redshift for Archviz, It's super fast and never had a issue with vram.  It is missing some key features though but that is being resolved a lot in version 3.0 that's coming soon. It can handle massive scenes.  I always run into vram issues with Fstorm, especially with exterior vegetation, and it has no OOC.  Nvlink will help but i still see it having Vram issues even then with very large scenes.

254

[Max] General Discussion / Re: Vray Next vs Corona 4

« on: 2019-04-30, 22:15:36 »

That was great danio1011, thanks for your experience. This is what I'm kinda finding also. I am now putting together a scene with Vray Next and then will remake it in Corona. Vray Next GPU is very fast, which is nice but it also is so slow in development. Missing many features you can get with say Redshift.  IPR if it's Vray CPU or Gpu seems much snappier than Corona and I've noticed that issue too with Forest Pack. But the scene I'm putting together with Vray the render is just getting that plastic feeling. Before I rendered with materials I did both scenes in vray and Corona with override shader and the lighting between both where quite different, this is an exterior scene. I know what your saying about depth, Corona feels like the scenes have actual depth where Vray Next feels flat. I also would like to use Next GPU for certain types of animations but the quality just leaves me kinda disappointed so far.  I'm not done with my own internal testing but will see what comes of it. 

I've tried Fstorm while nice I always hit Vram issues, so it's only ever good for small scenes. Octane does better but is limited in shaders and ALWAYS crashes over all the years we've owned it we were never able to use it for production once except one still that had it crashing all the time also, We've owned from the beginning and own the latest versions also.  For GPU nothing really beats Redshift.  Would love to hear more from others.

255

[Max] General Discussion / Vray Next vs Corona 4

« on: 2019-04-28, 00:14:18 »

Wanted to get you guys opinions on Vray Next since most of you came from Vray or still use it but also use Corona.  We own Vray 3x version and Corona among other renderers.  We are going to keep using Corona but might use Vray Next for animations. Had some observations and questions.

We just used Corona 4 nightly for an animation, render quality, user interface & user friendliness is fantastic. Render times get to be quite large compared to Vray Next that we tried for a few small tests, and that can really add up for animation.  Vray Next IPR seems much more responsive and final rendering seems to be much faster.  But my question is about quality, many Corona renders look very realistic compared to Vray.  Not sure if this changed with Vray Next, but I can't place my finger on if it's Coronas lighting or shaders.  Seems to have more depth and reflective properties seem more natural. Like I said we had only limited time with Vray Next trial, so for those who use both would love to hear your opinions or even see you comparisons.