Author Topic: Script Error when starting max2018  (Read 1541 times)

2017-07-12, 10:52:03

SHORT CUTS

  • Active Users
  • **
  • Posts: 69
    • View Profile
    • SHORT CUTS
Since today i get this error when i open 3dsmax2018, Corona 1.6 HF1:

https://prnt.sc/fuo7qs

I checked the script folder and it the scripts are there...i installed the forest pack update yesterday, that was the only change to the system but i doubt that it has something to do with it.


2017-07-12, 17:12:02
Reply #1

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 9057
  • Marcin
    • View Profile
Strange enough we have received similar reports from 2 more users during last ~1 week.
Maybe it has something to do with the new Forest Pack installation? But most probably just 3ds Max freaking out...

The solution for now is unfortunately "refreshing" the ENU folder as instructed here:
https://knowledge.autodesk.com/support/3ds-max-design/troubleshooting/caas/sfdcarticles/sfdcarticles/Resetting-3ds-Max-3ds-Max-Design.html
Note that this will clear all your custom UI settings, keyboard shortcuts, etc. I would also strongly advise renaming the enu folder instead of just removing it, to make sure that you are able to return to the previous version in case of some troubles.

2017-07-13, 10:36:09
Reply #2

SHORT CUTS

  • Active Users
  • **
  • Posts: 69
    • View Profile
    • SHORT CUTS
Reinstalling Corona did the trick for me. No Script Error anymore :)

2017-07-13, 12:03:18
Reply #3

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 9057
  • Marcin
    • View Profile

2017-07-13, 14:43:33
Reply #4

DeadClown

  • Global Moderator
  • Active Users
  • ****
  • Posts: 1439
    • View Profile
    • racoon-artworks
Since the script in question has worked quite well the last couple of years I blame autodesk :D
Any sufficiently advanced bug is indistinguishable from a feature.

2017-07-14, 17:06:32
Reply #5

SHORT CUTS

  • Active Users
  • **
  • Posts: 69
    • View Profile
    • SHORT CUTS
hmm, the fix was only temporary, got the message again today. I will try the "enu-refreshing" solution.