In view editor and HUD elements not displaying correctly maya 2019 student

[Anonymous]

 After upgrading my GPU to the Nvidia RTX 2080, I have run into an issue with maya 2019 student where the In View editor will appear as a thin line with no options displayed. When I try to resize the menu, it will automatically stretch across the entire screen and still not display any options. I can open the drop down menu from within the editor and click reset size, but nothing changes.

My HUD elements will not display either, whenever I turn on a HUD element, I get the warning " Warning: Panel size cannot accommodate all requested Heads Up Display elements." I have three monitors, two connected to displayports on my graphics card and one connected with dvi to my motherboards integrated graphics card. All of them are set to 1920x1080 resolution. 

I have reset my preferences and even uninstalled and reinstalled the program and I am still having this issue.I have also checked the hardware compatibility here and my graphics card is said to be supported for 2019.1 . My driver version is 430.86. Any help is appreciated.

I made a post about this a while ago about maya 2018 and I assumed that it was just a compatibility issue, however I think that it is something else now that I have upgraded to maya 2019 and the issue persists 

[sean.heasley]

Hi @Anonymous 

Thanks for the detailed post! Normally I would jump to this being a GPU issue but you clearly have the supported card/driver so it is most likely not that.

If you go to Windows->Settings/Preferences->Preferences->Display can you try changing the rendering engine settings and see if that affects this at all?

[Anonymous]

@sean.heasley 

Thanks for the reply! I changed the viewport 2.0 rendering engine to OpenGL(strict), OpenGL(Compatibility), OpenGL(Legacy) and DirectX 11 and there was no change

[sean.heasley]

Hi @Anonymous 

Hmm ok. Does this happen with other tools like extrude or smooth etc or is it just the bevel tool?

One thing you can try is using the legacy viewport.

Steps to do this:

1. Documents > Maya > VERSION (2018, for example)
2. Open the Maya.env file in Notepad (by default, it is empty)
3. Paste the following text into the document: 
   • MAYA_ENABLE_LEGACY_VIEWPORT=1
4. Resave the document
5. Relaunch Maya. The option to use Legacy Renderer in the Viewport is available, and have access to the Performance Settings window.

[Anonymous]

@sean.heasley 

Its doing it with all tools that have an inview menu, however each one shows up a little different and legacy viewer isnt making a difference

[sean.heasley]

Hi @Anonymous 

Can you possibly download 2018 and see if the same issue occurs?

I'd like to narrow this down to as few possibilities as possible as this may be a new problem with 2000 series GPUs that would need to be logged with our development team.

[Anonymous]

@sean.heasley 

I had this problem with maya 2018 as well and I made a post about it then here and I accepted the solution that it was just unsupported hardware at the time. I had also changed quite a few things with my computer at the time preceding this issue including upgrading power supply, upgrading hard disks and cloning one disk to another and upgrading from windows 7 to windows 10. Maya 2019 was not on my computer when all of this happened however. Maya 2018 isn't currently on my computer, but I can redownload it if there are some tests you want me to run.

I am also attaching a DXdiag file in this post in case you need more hardware and computer information as this seems pretty unique to me

[sean.heasley]

Hi @Anonymous 

Ah ok thanks for that!

One other test, if it's possible, do you have a multiple monitor set up and/or another monitor you can use? I doubt it is a monitor issue but it's worth testing if possible so we can rule it out. Also yes if you wouldn't mind downloading and testing 2018 again even though the 2080 isn't officially supported for it that would be very helpful.

Reproducing something like this can be extremely difficult so I'm trying to gather as much info as possible if I do indeed need to log this with development for a fix.