Empty VFB and lightselect elements not updating & Other problems

[Jpjapers]

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

[Jpjapers]

Reverting to an autobackup seems to have resolved all issues

[Jpjapers]

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.

[Jpjapers]

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

[Jpjapers]

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.

[Ondra]

is it happening in RC as well?

[Jpjapers]

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?

[Ondra]

ok, try it and let us know

[Jpjapers]

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.

[Ondra]

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?

[Jpjapers]

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

[Jpjapers]

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

[fraymond3d]

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

[fraymond3d]

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

[Ondra]

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?

[sevecek]

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

[Jpjapers]

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.

[Ondra]

Is this still happening in RC4?

[Jpjapers]

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.

[sevecek]

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?

[Jpjapers]

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?

Ill check the DR tab next time i render (shouldnt be very long) , 3ds max itself isnt locked, just corona. But because corona is still rendering, i cant actually do anything to the scene apart from save it thankfully. I cant start a new render no, its as if its still rendering but the passes doesnt increase yet the time keeps going.

[sevecek]

Ill check the DR tab next time i render (shouldnt be very long) , 3ds max itself isnt locked, just corona. But because corona is still rendering, i cant actually do anything to the scene apart from save it thankfully. I cant start a new render no, its as if its still rendering but the passes doesnt increase yet the time keeps going.

I see. Could you also create a minidump next time it happens? That would be extremely helpful.

[Jpjapers]

Ill check the DR tab next time i render (shouldnt be very long) , 3ds max itself isnt locked, just corona. But because corona is still rendering, i cant actually do anything to the scene apart from save it thankfully. I cant start a new render no, its as if its still rendering but the passes doesnt increase yet the time keeps going.

I see. Could you also create a minidump next time it happens? That would be extremely helpful.

Sure thing

EDIT: Ill send you the minidump, ill point out that my nodes are still using an older daily build and ill update them now and see if the problem persists after sending the dump.

[Ondra]

is it still happening in RC5? If yes, do you have a minidump for us? ;)

[Jpjapers]

is it still happening in RC5? If yes, do you have a minidump for us? ;)

Im unable to test until Tuesday (Easter holidays here in UK)

[fraymond3d]

Only after ONE render with Dr activated...

[fraymond3d]

I cant install RC5 for the moment, we have 30 slaves and I dont have time right now to do it... need some production :S

[Ryuu]

Hi guys, could you please test the latest RCs to see if the problem is still present?

If this issue happens again, please send us a minidump and a screenshot of the VFB DR tab. Thanks!

[Jpjapers]

Hi guys, could you please test the latest RCs to see if the problem is still present?

If this issue happens again, please send us a minidump and a screenshot of the VFB DR tab. Thanks!

No problem with this anymore however ive had repeated crashes with RC6, at least 4 times with different scenes in Max 2017 and always when rendering.
Attached minidump to this post. I can make a new thread if necessary.
Just installed RC8 and will see if it happens anymore today.

[Ryuu]

Just to be clear, you're saying that RC7 does not crash in situation where RC6 does, right? :)

[Ondra]

Hi guys, could you please test the latest RCs to see if the problem is still present?

If this issue happens again, please send us a minidump and a screenshot of the VFB DR tab. Thanks!

No problem with this anymore however ive had repeated crashes with RC6, at least 4 times with different scenes in Max 2017 and always when rendering.
Attached minidump to this post. I can make a new thread if necessary.
Just installed RC8 and will see if it happens anymore today.

I cannot read the minidump - can you upgrade 3dsmax? You have old version of 2017 for which Autodesk does not provide symbols

[Jpjapers]

Just to be clear, you're saying that RC7 does not crash in situation where RC6 does, right? :)

Im not sure i havent installed RC7 i jumped to RC8 as i saw it was in the folder this morning. I havent had RC8 crash yet but RC6 did a few times yes. It wasnt every time, it was intermittent. Ill know by the end of the day if its still happening as i have a fair few renders to do today.

[Jpjapers]

Hi guys, could you please test the latest RCs to see if the problem is still present?

If this issue happens again, please send us a minidump and a screenshot of the VFB DR tab. Thanks!

No problem with this anymore however ive had repeated crashes with RC6, at least 4 times with different scenes in Max 2017 and always when rendering.
Attached minidump to this post. I can make a new thread if necessary.
Just installed RC8 and will see if it happens anymore today.

I cannot read the minidump - can you upgrade 3dsmax? You have old version of 2017 for which Autodesk does not provide symbols

Didnt realise there was an update. Ill do that now and if it crashes again with RC8 ill upload a minidump.

EDIT: No max updates are available in the updater for me

[Ondra]

weird, you have version 19.50.something, I have 19.51.something. Autodesk keeps only latest version of PDBs on their server, which means that as soon as any update rolls out, all old minidumps become worthless. Same with minidumps from people who did not update.

[Jpjapers]

weird, you have version 19.50.something, I have 19.51.something. Autodesk keeps only latest version of PDBs on their server, which means that as soon as any update rolls out, all old minidumps become worthless. Same with minidumps from people who did not update.

According to my about box im on v19.0.
Ill install SP3 from the autodesk site and see if that changes anything.

EDIT: Ill also update my nodes as i forgot they are still on RC5

For some reason the max update installers dont do anything. They open, configure and then just dont run :/

[Jpjapers]

Yup @ondra, none of the available max updates including security patches change my version number to 19.51..... Its still 19.50.....

[Ondra]

see attached - apparently the number in UI is not updated. What matters is file properties info for 3dsmax.exe executable

[Jpjapers]

see attached - apparently the number in UI is not updated. What matters is file properties info for 3dsmax.exe executable

The number in the exe is still 19.50.....
I ran a wrapper around the updaters to make sure they were doing stuff and the log they generated was all fine so they seem to be installing.
Just a side note, when you install max service packs is there any dialog that appears or does the msp just extract the files it needs to without any UI?