Empty VFB and lightselect elements not updating & Other problems

Daily build Apr 3rd
I changed my render elements but the VFB still shows all of the old elements and none of the new in the lightselect tab despite having deleted all the old lightselect elements. Also i click render and the vfb occasionally remains empty and greyed out (see attachment)

DR Is being used (i managed to get 3 renders out without a hitch) the render nodes are running the same build but are running legacy due to not supporting SSE 4.1

Also noted that lightselect settings arent being saved with the file, Corona is reporting DR mismatch on some render nodes despite using the same installer on all nodes and having used the nodes for a few renders successfully

Reverting to an autobackup seems to have resolved all issues

Problem seems to occur after stopping a render.
After i click stop none of my lightmix works. i cant turn things on and off and i cant change intensities or colour. Well i can, it just does nothing.
I can dump out a cxr and use it in image editor absolutely fine.

lightmix inactivity problems still persisting. wasn’t the auto-back that solved the problem it was the max restart.

Anybody interested?
Ive attached some images showing me turning off the various lightselects and nothing happens.
As i say this is fine in the standalone image editor. Its just in the max VFB after stopping any render.



is it happening in RC as well?

Ah, theres an RC! ill try this again. Its strange though it seems to be only with that one file which was created in an earlier daily. Perhaps thats the reason?

ok, try it and let us know

The lightmix inactivity is still happening with RC1.
Ive uploaded the scene to your uploader, its called 1491827363_IODV2.max just incase you want to have a look.

I cannot reproduce it in your scene. Does it happen always for you? Would you be willing to try running it in assert (debugging) build of Corona?

Yes it seems to always happen but strangely only in that scene. I wonder if i merge it into a new scene itll fix it?
I can try a debugging build sure.
What do i need to do?

Thanks

Empty VFB happening on RC3 with a completely separate, brand new scene with none of the same elements as the scene i uploaded.

Hi,

Just post the same bug but I found it… Just need to import in a brand new scene… and all bugs are gone!! something with the upgrade vs old versions scenes…

Hope it help!

Frank Raymond

Ok… Did more tests, its caused by the DR, no problem at all until you thick enable DR…:S waiting from corona users to awnser something about it…

Thx

is it happening ONLY with DR, or can it happen without it? Does it start happening during render (I mean, at the beginning of render it works, then in the middle it stops without cancelling the render)? Or does it start happening only after one render ends?

Could you please try RC4? Let me know if it solves the problem.

will try in the morning.

@Ondra both scenes ive tried hve used dr and it starts at the beginning of the render, none of the stats appear they stay as "— — — " but the dr nodes are rendering for sure.

What you have to do it open the scene, render it, then stop the render and cancel denoising. Then next time you render it will stay blank. The only fix seems to be a max restart.

Is this still happening in RC4?

No to the empty frame buffer but getting an issue whereby the render wont stop when DR is enabled. It stops the current pass but the time continues and you cant get out of the render mode so the only way to stop the render is to crash out max.

What does DR tab say in this state? Is 3ds Max still locked, or just Corona VFB? Can you start new render using buttons from Scene rollout?