Did something with Max2013 change in the last 24 hrs or so?

punchface

Yesterday, everything was fine.

Today, I'm getting crashes like crazy.

I swear on my grandma's grave that I have not visited any dubious porn sites today nor have I indulged in any thievery of anyone's intellectual property that would have caused me to go to dodgy Russian or Persian or Chinese or Indian hosting services that might have inflicted a virus upon me.

I swear I've not anything like this recently.

Max crashes...sometimes it crashes right when it opens. Sometimes it crashes when I try to open a file...sometimes it crashes after I have a file open and have done some work on it...and not much work either, at most, I get 5-10 minutes of work in and then the program soils its diaper.

Photoshop works fine.

Firefox works fine.

Windows Media Player works fine.

I've tried working on three different files...same horrid instability.

There is only ONE thing that I've done today that has changed my system from yesterday...I installed the RC1 update to the Topogun 2.0 beta. I haven't used it yet. I opened it to update my license stuff, closed it, and that was it. I can't imagine that the most Topogun update is culprit.

Has anybody noticed really bad performance from Max 2013 today besides me? I'm really at a loss here as to what the deal is.

pf

Neox

try making a backup of the 3dsmax ini and all ui/config files and deleting them, it will screw up your ui and stuff but max did that every now and then to me

Ace-Angel

Reset everything, and try a reinstall, get the latest patches, etc.

But yeah, after 2012, this is not an uncommon issue.

punchface

Sp1 installed.
Product Update 4 installed.

So...

Just so I don't anything stupid, lemme make sure I understand what you are saying, Neox...

If I make a copy of my config files (there aren't any really, I just roll with the software more or less out of the box) and a copy of the INI file (and do something like move that copy to my desktop before deleting the INI file that's in my top Max directory, then Max should write itself a new (and presumably un-corrupted) INI file by itself the next time I try and fire up the program? Is that right?

pf

Neox

yep it should

often enough i had it destroy either my ini or the quadmenu config files which lead to max freezing

SPYFF

Some solution, i fix sweep modifier crash with this metod: Make bankup from your cutosm startup plugins and everything custom stuff from 3dsMax root folder (where the 3dsmax.exe and many dll-s). If done, delete everything from this root folder, and navigate your 3dsMax install disk: "x64\max\Autodesk\3ds Max 2013", select every file, and copy the emprty root folder. Working fine for me, i hope help.

shaderfx

It could also be that you received a windows update or driver update that made things unstable on your machine?

punchface

Deleted max.ini and let the program write a new one on subsequent boot.

No good.

Repaired install.

No good.

Deleted install and REinstalled (did that literally hours ago)

No good.

Considering rolling back to the 2012 version which would be horrible because most all of the stuff I've been working on for the last month and a half has been in 2013.

Neox,

What/where are the quad menu config files?

MH

animax

Usually when this happens, i rename the following folder.
C:\Users\[USER NAME]\AppData\Local\Autodesk\3dsMax\2013 - 64bit

Then start 3dsmax 2013, it will create another settings folder.All your settings,custom scripts will go.

punchface

I've done a complete reinstall twice.

I can't even get a fucking file to open before the miserable piece of shit crashes.

I'm going to roll back to 2012.

pf

punchface

uninstalling the drivers and software for my Wacom tablet appears to have fixed the problem.

It may be that I'm speaking too quickly but, well, before, as soon as I would touch a menu button, Max would crash, after the Wacom uninstall, Max did not crash and I was able to work normally.

A couple of nights ago, I got about two hours of good work out of Max before it started crashing again when I changed my viewport settings from Nitrous to OpenGL. Brief euphoria and happiness ensued to be replaced by rage the next morning when the crashes started again.

Now, I'm getting results...will the crashes start again after a few hundred more mouse-clicks? I'll have to wait and see.

I can totally live without a Wacom tablet when I wanna use Max. But....but I bought this damn tablet for a reason and if I can't use it with Photoshop and Zbrush because having the drivers on my computer messes up Max, I'm going to be exceedingly pissed off....

...but if all I have to do is to remember to unplug the USB cable for my tablet to keep my Max from shitting its diaper, I'm totally okay with that.

sigh...

pf

punchface

Okay, so it's my tablet. So far, the solutions to the problem I've explored just wind up disabling the tablet entirely which I'm not down with at all. My tablet is not a paperweight, it's a tablet. I want to use it with Photoshop and Zbrush and I can't allow my solution for not screwing over studio Max deprive me of its use.

I'm going look for Wacom threads here in technical talk and see what I can find but given that i know now that this issue is not exactly a Studio Max issue, I think I can safely call this thread done and over.

I really appreciate the responses I received even though ultimately what the problem turned out to be was something totally different than Max's configuration. Thanks for taking the time guys, really.

pf

monster

Maybe you can just stop the Wacom Services from the Task Manager.

punchface

Monster,

It's what I'm doing now sir. When I wanna work in Max, I fire up services.exe and disable the tablet. When I'm done, I go back in there and turn it back on.

It's a solution and it'll work for now, but it's lame and it's ghetto and it's not really fixing the problem.

If for no other reason, I wanna fix the problem because by pride and irritation refuse to allow a crappy bunch of software products get the better of me.

pf