Pages: [1]

Author Topic: why is renderers.current.system_vfbHistoryAutosave now not available?  (Read 1436 times)

2017-05-05, 08:24:30

Christa Noel

  • Active Users
  • **
  • Posts: 911
  • God bless us everyone
    • View Profile
    • dionch.studio
why is renderers.current.system_vfbHistoryAutosave now not available?
hi guys & devs,
renderers.current.system_vfbHistoryAutosave now is not available or.. was it renamed? I cannot find another corona property which do what it does..
Logged
2017-05-08, 21:14:08
Reply #1

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
Re: why is renderers.current.system_vfbHistoryAutosave now not available?
it is now a system-wide property and must be edited via a .conf file in corona directory. We will add maxscript access for 1.7
Logged
Rendering is magic. |  How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)
2017-05-09, 18:49:29
Reply #2

Christa Noel

  • Active Users
  • **
  • Posts: 911
  • God bless us everyone
    • View Profile
    • dionch.studio
Re: why is renderers.current.system_vfbHistoryAutosave now not available?
Huraa! Thanks!! :D
Do i have to create feature request for that?
Logged
2017-05-10, 12:57:28
Reply #3

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
Re: why is renderers.current.system_vfbHistoryAutosave now not available?
we have it logged internally AFAIK so you dont have to ;)
Logged
Rendering is magic. |  How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)
Pages: [1]