I’m almost sure it’s FPP 6.2.x with an animated camera, referenced in a forest object (@Rowan: see ticket #184420).
To test:
switch to a one viewport layout, move away from the scene - looking into the sky for example
remove the camera reference from all FPP objects
delete all keys of the animated camera
delete all FPP objects
update to a newer FPP version (which one do you use Jens?), I could not repro this with 6.3.1 (which we currently use) any more
If IR stops restarting in any of the above cases, it’s the FPP bounding box issue: As soon as the mouse hovers over the bounding box of a FPP object, IR restarts. Maybe you could check this.
Well I never even installed ForestPack Pro (Trialled it once time ago) yet I encounter this issue from time to time as well. Just hovering mouse outside of VFB :- ).
Now that animated timeline was mentioned… that’s something I will look for association next time it happens.
Interesting. I almost never have a non-animated timeline but encountered this only in conjunction with FP. But at the same time, I do not own a similar demanding display gadget accumulation like you :]
I have also uploaded a new file as I now get crashes on render. This is after I tried to roll back from the nightly vray5 and phoenix + corona 7 builds to the “stable” official releases (I need to send this project to a cloud render service later). I have then tried to uninstall corona, vray and phoenix first + deleted ENU folder, restart and then install the stable releases. Main issue here seems to be the displacement of the phoenix ocean tex. It crashes the scene every time even though I made new maps and deleted the old. It works okay solo in a fresh scene, but there’s some old setting somewhere that makes it crash.
update: it is something in the render settings that triggers this. I have tried merging stuff from the old scene in to a new scene and if I include the “render settings”, the crash on render starts. So I have uploaded two small test scenes. One WITH the merged in “render settings” that crashes and one WITHOUT that merged “render settings” that works fine.
Hi
When I rolled from Corona 7 DBs back to Corona 6 it was enough to reset Corona render settings in scenes saved under Corona 7, after that Corona 6 worked fine for me. Otherwise Max crashed when I tried to render those scenes without resetting.
I think the file name was this one: “Vindoe_environmnt_oktagon_v51-local.v06” I’m uploading a new scene, this time in max 2021 and with corona v6 that also has the IR refresh bug.
I tried switching to max 2021 instead of my current 2020, as max kept bugging out (keyboard shortcuts didn’t work and couldn’t click max’ menus). So not able to save or anything, but could navigate and use viewports and the command panel. So weird. If I try and close the max window it does so immediately, no prompt asking for saving, no max crash report etc. But 3dsmax.exe keeps running in the background. I’m not getting this bug with the scene in max 2021, but now there IR bug is back! Argh, this project is cursed! I do think it could be tied to vray5/phoenix as all these bugs came after installing and using those.
update in case anyone else had his bug the bug with not being able to click menus and keyboard shortcuts not working only happens when I open the material editor (slate). Then it activates the same second. There’s a phoenix ocean tex and foam tex amongst a couple of corona maps and materials in there. It happens with the newest “stable” vray version: vray_adv_51001_max2020_x64. If I install 51000 instead, bug is still there. BUT if i go back to 50005, the bug is no longer there.
There might a list of features with some similar “attributes” that cause excessive refresh. I.E:
Physical camera with Target and something else going on
ForestPack with Physical camera animated
etc..
When this happens to me, it’s usually in larger scenes already and it’s really hard to diagnose (Also at that point of project I no longer have enough life energy to do diagnosing).
But it’s almost always tied to behavior with camera I don’t think I ever had this issue in rendering IR from viewport.
is there a way you guys can add a feature to Coron Multimap where you can add a self illumination or lighting enabled map so that some random elements in a model can be lit?
DB 22-03-2021 - updated PhysicalMaterial is great! Clear coat now works exactly as I want it to work - thank you guys!
Could you, please, give some information about Edge color - does it just tint reflection on the surface at a glancing angles of viewing or it does something more?
Also would like to know, is it enough simply invert glossiness map to get roughness map with the same visual representation of material, or some other adjustments have to be done in order to convert glossiness map to roughness map properly?
I managed to do something not physically correct in the physically correct material! Or am I doing something wrong?
Shadows are black and white with colored material. And when the Directionality in the light source changes, the light in the refractive material turns black. Its black outline is visible but its luminous properties are lost, I assume this contradicts the physics of light.
Cheers Bormax, I was planning to post a notification today about it here. Regarding edge colour I am going to quote some answers:
“In normal use, the Physical material works like the real world, where reflections are always white, with very slight color variation at the grazing angles. To maintain this, there is no longer any “Reflection Color” slot in the material, unlike in the Legacy Material, and the Physical material correctly calculates color curves for metals based on the Edge color.”
About glossiness to roughness map, that is indeed correct a simple inversion would work most of the time granted that the glossiness map is actually properly fitting for the model (as far as I’ve seen there are cases were 3d humanoid models were made to have different glossiness and roughness maps). Most Quixel bridge assets though are imported to Corona Renderer as inverted roughness maps, due to pre-CoronaPhysicalMtl setup and it works equally great.
we are just interested in the question of how we should define this edge color for physically correct materials? should we select it according to the reference image or are there any rules for this?
The proper way to approach this for CoronaPhysicalMtl would be to either enable “Thin Shell” and apply the colored checker mask in “Thin Absorption”, or in a more physically correct manner without the use of Thin Shell but with Volumetric Scattering (in a form of tinted glass), or even with a colored coated translucent paint through ClearCoats Absorption layer. The result of your example is expected as refraction rays are not colored, only diffuse reflection is (base layer). Please see attached.
Regarding the second issue can you please offer some reproduction steps I can’t seem to be able to do it. Thanks!
Hi Frood, sorry for not getting back to you on this. I got the IR refresh bug again, and came back to this thread to read through what you said. You are right!! If I disable them but the forest pack icon is still visible, nothing changes. But if I hide them completely in the forest lister, the IR bug goes away. That’s it.
It’s 100% tied to the camera. If I remove the “limit to visibility” under the Forestobject’s “camera” roll down menu, the IR bug goes away.
update: Just saw this on the forum. Guess I’ll try with that update
Forest Pack 7.0.8
Fixed continuous updating of Interactive Render when using Camera->“Limit to Visibility”.
This bug would also affect general performance when camera clipping is enabled on viewport.
Yep, the worst issue however has been that it happened even when using a perspective viewport - not even looking through a (referenced) camera. Now they seem to have fixed even camera view? Interesting and thanks for the info.
Downloaded and installed the latest daily yesterday (22 March, I think?).
This isn’t a bug per se, but suddenly I see this blocky progression happening in my renders (most noticeably only when it first starts but the progressive nature of the render also looks different than it used to). Note: a remove region render is responsible for the obvious shape in this screenshot.
What’s changed to suddenly start this different behavior? Is it expected?