Author Topic: 3ds Max 2018 Update 4 overwriting files bug?  (Read 3582 times)

2018-05-17, 07:17:54

Dan Rodgers

  • Active Users
  • **
  • Posts: 55
    • View Profile
We are getting a really weird bug across the studio at the minute, pretty sure it has only just started this past couple of weeks...

Basically, if you click to close max, the dialogue box comes up asking whether you would like to save the file, click 'Don't Save...'  and max saves the file anyway.  Is anyone else having this issue or know any fixes for it?

We are constantly jumping in and out of each other's files to take assets/textures etc. and with this current bug, it's pretty easy to overwrite each other's work.

Cheers


2018-05-18, 02:14:01
Reply #2

Dan Rodgers

  • Active Users
  • **
  • Posts: 55
    • View Profile
I would read these articles and would check if 3ds max scenes in question got infected by a virus.

https://knowledge.autodesk.com/support/3ds-max/troubleshooting/caas/sfdcarticles/sfdcarticles/Scene-file-crashes-corrupts-scene-data-gives-Script-Controller-error-or-no-longer-uses-the-Undo-function.html?st=alc
https://knowledge.autodesk.com/support/3ds-max/troubleshooting/caas/sfdcarticles/sfdcarticles/Potential-issues-with-third-party-MAXScript-CRP-switching-to-different-viewport-scene-lights-disappear-or-seem-deleted.html

Cheers for the reply and links.  Looks like we have the ACL script problem across a few of our machines and now in loads of files across the network.  Anyone know of a proper solution to this? Autodesk just recommends rolling back older save files but we have no idea which files are infected and rolling back could mean 10+ people loosing more than a weeks worth of work.

tried a few things we found on this website http://www.fangdede.com/thread-72883-1-1.html  but that didnt seem to make any difference.

I'll post back if we find a solution

2018-05-18, 09:47:28
Reply #3

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 8856
  • Let's move this topic, shall we?
    • View Profile
    • My Models
Obviously rolling back to older save files is not a realistic solution at all. You can try prune scene script. In latest version it has batch repair option, so it might be ideal in your situation: https://forum.corona-renderer.com/index.php?topic=19797.msg126360#msg126360
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2018-05-18, 10:32:21
Reply #4

Dan Rodgers

  • Active Users
  • **
  • Posts: 55
    • View Profile
Obviously rolling back to older save files is not a realistic solution at all. You can try prune scene script. In latest version it has batch repair option, so it might be ideal in your situation: https://forum.corona-renderer.com/index.php?topic=19797.msg126360#msg126360

Cheers man, I'll give that a go on Monday

2018-05-23, 09:30:03
Reply #5

Dan Rodgers

  • Active Users
  • **
  • Posts: 55
    • View Profile
Obviously rolling back to older save files is not a realistic solution at all. You can try prune scene script. In latest version it has batch repair option, so it might be ideal in your situation: https://forum.corona-renderer.com/index.php?topic=19797.msg126360#msg126360

An update on all this...

So the Prune Scene script that Romullus recommended works pretty well.  It's not perfect but it is definitely the best option that I can find at the minute for sorting out the problem.

2018-05-26, 04:13:25
Reply #6

arqrenderz

  • Active Users
  • **
  • Posts: 996
  • https://www.behance.net/Arqrenderz1
    • View Profile
    • arqrenderz
we found the virus on our office, but cant batch prune scene to clean all the mess, so its no a real soultion, any news on this?

2018-05-28, 12:00:49
Reply #7

Dan Rodgers

  • Active Users
  • **
  • Posts: 55
    • View Profile
we found the virus on our office, but cant batch prune scene to clean all the mess, so its no a real soultion, any news on this?

From what I can tell Autodesk are working on some sort of solution, but who knows how long that is going to take.  Best of solution for now is install the prune script on all machines and then save a new ‘clean’ iteration of the infected files.

The script seems pretty good and should hopefully be able protect from any similar problems in the future.