Author Topic: Empty VFB and lightselect elements not updating & Other problems  (Read 14134 times)

2017-04-07, 15:50:23

Jpjapers

  • Active Users
  • **
  • Posts: 1654
    • View Profile
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
« Last Edit: 2017-04-07, 16:04:39 by jpjapers »

2017-04-07, 16:08:33
Reply #1

Jpjapers

  • Active Users
  • **
  • Posts: 1654
    • View Profile
Reverting to an autobackup seems to have resolved all issues

2017-04-07, 16:18:48
Reply #2

Jpjapers

  • Active Users
  • **
  • Posts: 1654
    • View Profile
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.

2017-04-08, 01:55:02
Reply #3

Jpjapers

  • Active Users
  • **
  • Posts: 1654
    • View Profile
lightmix inactivity problems still persisting. wasn't the auto-back that solved the problem it was the max restart.

2017-04-10, 11:09:09
Reply #4

Jpjapers

  • Active Users
  • **
  • Posts: 1654
    • View Profile
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.
« Last Edit: 2017-04-10, 11:12:36 by jpjapers »

2017-04-10, 13:16:16
Reply #5

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
is it happening in RC as well?
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2017-04-10, 14:09:03
Reply #6

Jpjapers

  • Active Users
  • **
  • Posts: 1654
    • View Profile
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?

2017-04-10, 14:12:58
Reply #7

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
ok, try it and let us know
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2017-04-10, 14:19:23
Reply #8

Jpjapers

  • Active Users
  • **
  • Posts: 1654
    • View Profile
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.
« Last Edit: 2017-04-10, 14:33:52 by jpjapers »

2017-04-11, 13:26:00
Reply #9

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
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?
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2017-04-12, 10:42:20
Reply #10

Jpjapers

  • Active Users
  • **
  • Posts: 1654
    • View Profile
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

2017-04-12, 16:54:14
Reply #11

Jpjapers

  • Active Users
  • **
  • Posts: 1654
    • View Profile
Empty VFB happening on RC3 with a completely separate, brand new scene with none of the same elements as the scene i uploaded.

2017-04-12, 19:54:15
Reply #12

fraymond3d

  • Active Users
  • **
  • Posts: 31
    • View Profile
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

2017-04-12, 20:17:01
Reply #13

fraymond3d

  • Active Users
  • **
  • Posts: 31
    • View Profile
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

2017-04-12, 20:18:42
Reply #14

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
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?
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)