Author Topic: [feedback] BackBurner  (Read 2907 times)

2016-11-21, 18:04:06

kahein

  • Active Users
  • **
  • Posts: 181
    • View Profile
Hello,
D'ont why this happen but I have a window script wich open when I launch rendering via backburner.
« Last Edit: 2017-04-24, 18:08:01 by Ondra »
Asus Z10PE-D16 WS / Dual Xeon E5-2690 v4 @ 2.60GHz / RAM 64 Go - GTX 970
Win 10 / Max 2017 / Corona 1.4

2016-12-06, 14:13:19
Reply #1

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 12768
  • Marcin
    • View Profile
Have you tried removing CoronaRenderer_InitScripts.ms from C:\Program Files\Autodesk\3ds Max 2017\scripts\Startup, and then re-installing Corona?
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2017-04-24, 18:07:52
Reply #2

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
Hi, is this still an issue? Does it go away if you manually remove the script as Marcin suggested and then reinstall 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-05-04, 17:34:51
Reply #3

slava1516

  • Active Users
  • **
  • Posts: 7
    • View Profile
i have the same problem
when i remove the file from the startup folder, the problem disappears, when reinstall corona - problem appeared again
is it a critical file?
what can be wrong when i remove the file from the folder

i would have say that the problem appeared after i install soulburn script pack and the error appears on 3ds max startup.


« Last Edit: 2017-05-04, 17:42:42 by slava1516 »

2017-05-04, 17:40:54
Reply #4

slava1516

  • Active Users
  • **
  • Posts: 7
    • View Profile
the following stroke appears before the error



« Last Edit: 2017-05-04, 17:46:02 by slava1516 »

2017-05-04, 18:10:03
Reply #5

slava1516

  • Active Users
  • **
  • Posts: 7
    • View Profile
just deleted soulburn script, problem still be the same

2017-05-04, 20:57:04
Reply #6

slava1516

  • Active Users
  • **
  • Posts: 7
    • View Profile
updating to 3ds max 2017.1 and installing sp2 and sp3 resolved the problem