Chaos Corona Forum
General Category => General CG Discussion => Topic started by: JG_monomiru on 2015-04-13, 19:51:23
-
Hi i just read about upcoming release of 3dsmax 2016 http://area.autodesk.com/blogs/max/introducing-3ds-max-2016
even if it lacks some details - the new physical based camera similiar to vray should be interesting.
Hope it helps solving shift and tilt - problems i currently got with corona, using vray physical camera (when heavy shift/tilt is applied)
-
You always can and you could to use Camera Correction modifer with standard max camera to tilt/shift (;
-
Hope it helps solving shift and tilt - problems i currently got with corona, using vray physical camera (when heavy shift/tilt is applied)
What are the issues with Corona using Vray's tilt/shift at the moment ?
-
I'm guessing that you need vray installed ;)
-
MCG looks interesting. Apart from that i don't see anything that would make me want to leave 2014.
-
Watch the xref video and try it once it's out ;) . It's the feature that will make me use 2016, even with the shitty layer explorer. It's a game changer for me.
-
SE (selection explorer) has seen some major improvements. It was the thing that held me back from switching to 2015 but I actually can't wait to install 2016 and start working in it.
Also, viewport speed was greatly improved in 2015, 2016 has seen another boost so anyone getting low fps rates in 2014 will be surprised.
I am also looking forward to work with the physical camera in Corona. I prefer this over the modifier approach, should be straight forward to work with, hopefully.
-
2016 doesn't have any major updates aside from improved VP speed. No new features or anything useful. Same case for most of the 2016 product line, another year wasted.
-
I'm guessing that you need vray installed ;)
:- D Well yeah, but I know he has Vray, and judging from the sentence formulation it seems there is something wrong when using Vray's camera directly.
Interesting that it was developed by Chaos Group.
-
it's a whole plan to replace mental ray as primary 3dsmax renderer in the future by chaos group ;)
-
yes i use vray-camera when rendering corona.
it gives me all the features for vertical and horizontal shifting and also vertical and horizontal tilting. but when using it it renders a wider camera angle than is shown in viewport. Otherwise it is working in corona as it should be - its just a bit of hassle to combine a vray rendering and the corona one - you need to scale it to fit the latter.
-
here i attached some images describing the issue.
Its not really a problem when just using one render-engine for final compositing. I knew that vray had and maybe still has some problems with showing the accurate image in max-viewport when tilting and shifting at the same time - at least in version 2.x it was this way.
And regarding their answer it was an issue on Autodesk side, they couldn't overcame within vray.
Maybe the cooperation on the 2016 new phyisical camera has overcome that issue.
-
Maybe the cooperation on the 2016 new phyisical camera has overcome that issue.
I wouldn't count on it :]
-
Which Vray version is that...? You mention 2.x, that one ?
I am using Vray cameras (3.12 SP1 ) in Corona with all their features and I never noticed such behavior at all. Now I am eager to double check but..
-
oh as far as i knew the newest version... vray 3.10.03 - at least at that time i was rendering that project (early march).
Corona was version 1.00.01 at that time
i also use max 2015 design (working mostly good with my workflow - despite that layer explorer glitches)
I mentioned vray 2.x ... as at that time i discoverd a broken viewport when using tilt/shift at the same time. And regarding chaosgroups answers that time it was a fault on autodesk side... havent paid attention to that detail anymore and lived with the result given in renderoutput. (cropped it in post then)
-
I doublechecked and you are correct !
But my difference is extremely small almost impossible to notice, but there. Which parameter do you say it depends foremost ? Tilting... ?
-
in this particular case i just used a vertical shift -0,23
in the max viewport image, there you can see all the camera settings.
-
Hi all, well - I personally am loving max 2016 (Harrr!!!)) :
- the viewport speed is equal if not faster than that of 2015's
- max creation graph is surely useful for people which understand how to script\program (sadly I'm not among those)
- my favourite feature is the new glowing\neon\cinema4d like object selection outline, imo not only it look far better but it gives much, much better feedback when moving objects which are behind some other objects etc or detecting some detached parts of the mesh or some holes in it - pretty like Geomagic's one in that case, plus is faster (needs confirmation but surely feels so) than the previous one which if not disabled manually or by script always had to show those, sometimes nasty, edges which in case of some highpoly models could be quite slow.
- I still hadn't done any test using the updated x-refs but judging from the new features videos those sure look promising too.
- almost all plugins and scripts - from those which I use, and I use around 50 of those (including Corona) which worked in 2015 do work in 2016 as well, which is surely awesome too - sadly the ones which I hadn't any luck with are Project manager (soon will write the dev. for support for I just simply cannot work without that one), SweepProfile from the same dev. and Ecximer's CoronaLight lister - all 3 of them giving similar .net related errors so probably Autodesk changed something in that regard.
- about the ugly slowness aka scene explorer, well it does seem it is somewhat faster than the one in 2015 but it's quite hard for me to compare cause in 2015 I disabled that slow bastard using this setting http://knowledge.autodesk.com/support/3ds-max/troubleshooting/caas/sfdcarticles/sfdcarticles/3ds-Max-2015-Scene-explorer-find-toolbar-is-extremely-slow.html and it hadn't bothered me since - wonder if that's possible with 2016 ...
Well, all above is strictly imo but I think this time Autodesk did that one can probably call a decent if just a little lazy (as usual) job ))