3ds max issue.

[Legacy_Jedijax]

               I've been using 3ds max 7 for some time now to alter nwn models in lots of wonderful ways (My thanks go to Lord of Worms and Estelindis for their patient guidance!). However, I recently chamged my ailing ATI 3870 for a MSI Nvidia Twin Frozer GTS 250, and 3ds max has not worked properly ever since. Sure, the app starts normally, and works right... for about a minute; after that time, the program freezes, and I can't do anything short of opening the task manager and shutting it out manually.

This didn't happen before the new videocard came along, so it stands to reason the issue lies with its drivers or configuration. However, I've tried to make a profile for 3ds max through the nvidia control panel, and the thing won't recognize the app as a 3d one, and won't let me add it. I also tried turning all default graphic options to their lowest capabilities, and, you know, the usual troubleshooting tweaks, won't do a thing to solve the issue; adding xp compatibility and administrator priviliges won't either.

I hope someone has experienced such thing and found a solution you may share with me.

Also, I've been reading some of the threads here, and it seems higher versions of 3ds max work with the nwn max scripts, so I would like to know up to which version do the nwn max script works just as fine as in version 7. Perhaps the issue could be solved merely by updating to a higher version?

Thanks in advance! I know I ask a lot and may be annoying, but there's nowhere else to go.
               
               

               
            

[Legacy_BigfootNZ]

               I had an unusually similar issue about 6 months back... for me (Max8) worked fine but suddenyl it would the moment I would try and save a file and the save window opened it would hang the machine and id have to hard restart. The thing is it turned out for me to be a GPU issue also... or at least I believe it was since after much hair pulling i enabled the  ATi catalyst process to run and it has a GPU crash restore option. It would pop up and say your GPU has crashed restarting GPU and it would no longer hang the machine, the thing is it still would occasionaly cause a hang (I used to disable the ATI catalyst startup process since its quite a ram hog)... the only thing I found that stoped it completely (so far) was to set Max back to using software rather than hardware for its view ports, apart from taht work around I havent been able to get the problem sortted (One day ill reinstall windows which might fix it)

Interestingly for me the issue all started when while having Max open and NWN2 toolset loading, AVG and Comodo poped up and told me the NWN2 toolset was infected and attempting something it shouldnt... which is bizzare since I had no viruses (im very regular with things like that) and the NWN2 Toolset has on some occasions had similar 'false positives' (I get it once in a blue moon when opening some of the larger Data.zips, why i have no clue)... this caused max and the toolset to crash and the issue started from there, even with a complete reinstall of Max (everything removed registry entries the lot) and the NWN2 toolset... i didnt reinstall windows since I didnt want to have to go through all the hassle.

So somewhere along the lines something was permanently fubar'd for me... while my experience was with NWN2 yours sounds similar.

Definitely try setting Maxs viewport drivers to run with Software rather than hardware and see if you get around it that way. There isnt to much difference between the two options really, and you wont be missing out on anything in particular. Max (or teh older versions) arent all that good at huge polygon counts anyway, and any large polycounts you might need can be easily handled by most CPU's (Ive gone up to 100,000 polys fairly easily and had no issues)
               
               

               

                     Modifié par BigfootNZ, 03 décembre 2010 - 09:55 .
                     
                  

            

[Legacy_Xenovant]

               go to customize>preferentes and in the "viewports" tab change the "display driver" (directx, opengl, sofware,..)

EDIT: Hey bigfootnz, you posted while I was writing xD
               
               

               

                     Modifié par Xenovant, 03 décembre 2010 - 09:56 .
                     
                  

            

[Legacy_Jedijax]

               Thanks, guys, though the driver was set to software from the very beggining... Should I change it to either OpenGL or Direct X?
               
               

               
            

[Legacy_Xenovant]

               try experimenting with both of them. I  use opengl but it doesn't mean that it will work fine for you



 By the way... what happens between you and the graphical cards? You insulted them or what? You are always having problems with them xD (just a joke '>)
               
               

               
            

[Legacy_Jedijax]

               I tried them both but the issue persists! It seems it may be something else. Any other fix you could advise? Also, what about the other question? Bigfoot uses 3ds Max 9, but what about you? Do the nwn max scripts work above 9?



I know, I know... You are disturbed by how many problems I have with old/new cards... sniff... just imagine what it means to be me...
               
               

               
            

[Legacy_Xenovant]

               I use 3dsmax 8.



I'm not disturbed. I don't mind at all, as I said, it's just a joke  '>



 I don't know what to say now... if you said that tried the typical troubleshootings tweaks... Try updating your 3dsmax to a newer version
               
               

               
            

[Legacy_Jedijax]

               I know it was a joke, Xeno, though I would certainly be disturbed/worried/scared if I were you. It was a joke too! Well... except for the part where it sucks to be me... that's pretty serious...



I'll download a newer version. Say, does it work with 10? Or is 9 as far as one may go?
               
               

               
            

[Legacy_Michael DarkAngel]

               

Jedijax wrote...
I'll download a newer version. Say, does it work with 10? Or is 9 as far as one may go?

There has been no testing with anything past 9 that I am aware of.


  MDA
               
               

               
            

[Legacy_Jedijax]

               Bu it is a fact NWN Max works with 9, right? Good enough for me! I'll upgrade, and let you guys know how it went. Hopefully, the issue will be fixed!
               
               

               
            

[Legacy_Jedijax]

               Err... the NWMax files uploaded in the vault say they go up to version 8, not 9. People using 3ds Max 9 can work with the "6 to 8" scripts?

               
               

               
            

[Legacy_BigfootNZ]

               Umm I dont have 9, I use 8...



Pitty nothing worked so far, I only suggested my idea because it sounded similar to what happened to me, both dealing with GPU's and suddenly happening where before it was fine.



Hope you get up and running again.
               
               

               
            

[Legacy_Michael DarkAngel]

               Yes, versions 6 through 8.  Or, you could always use my Plus version and give me some critical feedback.


  MDA
               
               

               
            

[Legacy_Jedijax]

               Oh, you're the guy who made the plus? Tell you what, once I have downloaded/installed the whole thing and hopefuly the issue is fixed, the first thing I'll do is check your plus version!
               
               

               
            

[Legacy_Jedijax]

               Victory! We have victory! Whatever happened to my 3ds Max version 7 is anyone's guess; however, updating to version 9 seems to have solved the issue. I just made fixes to a pair of tileset models and everything was A-Ok. Hope it lasts! Thanks everyone, for your assistance. Now, to check those Plus scripts...