Problem with opening Maya

Anonymous

Problem with opening Maya

Anonymous
Not applicable

Good afternoon, everybody.

 

I have a problem opening Maya. Long story - short, I had the software (2015) running perfectly until December. I had some university tasks to do in it and since it was holydays, I haven't used it for a while. In the beggining of the month I decided to open it up and continue working but in the opening window it showed the following: 2.PNG3.PNG

 

During the time that I haven't open it, the only thing that I could think of that could have made a difference is the GPU drivers update. I am using two GPUs - Intel Graphics HD 4000 and AMD Radeon HD 8750 (The second one is the discrete GPU if I am not mistaken). I tried changing the environmental variables, downgrading the AMD's drivers, reinstalling Maya, checked the Temp folder permissions, even made an administrative account and nothing that I found on the web helped. I'll be really thankful if anyone has a suggestion or an advice for this issue. Thank you in advance!

0 Likes
Reply
436 Views
3 Replies
Replies (3)

Anonymous
Not applicable

5.PNG

0 Likes

Anonymous
Not applicable

A little update. I reinstalled the graphics drivers with a previous stable version (since obviously I had a beta version) and it opens up. But then when I installed Houdini and opened it, it crashes. Tried opening Maya - same problem. Tried opening RealFlow - crashes while loading (Connecting UI signals...). I guessed it was the graphics drivers, evidently now it's something else causing the same Maya problem and most likely having something to do with Houdini's and RealFlow's opening crash. I also can not open Premier Pro. That's what I get: 1.PNG

 

I've read somewhere that the Python may cause some problems in Maya but I have no idea what exactly it is.
I would really be thankful for an opinion or an advice.

0 Likes

Anonymous
Not applicable

After a long time of updating anything basically, the thing that worked was a fix that was additionally made by AMD (16.1). Turns out, the graphics card's drivers were the problem after all. If anyone has this kind of a problem, make sure that you have the latest stable drivers and the latest fix if it's available. I'll leave the post just so it might help someone.

0 Likes