Announcements

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

DX11 Tessellation Crashing Maya

Anonymous

DX11 Tessellation Crashing Maya

Anonymous
Not applicable

I was hoping to use DX11 tessellation to display displacement in the viewport, but my Maya always crashes with a fatal error shortly after applying the displacement. To test this I used blank scene and applied a displacement texture onto a sphere and I get a crash either instantly or within a few seconds. I tried using both Shaderfx and the dx11shader. My viewport renderer is set to DirectX, not OpenGL. The dx11shader plug-in is loaded. My GPU is Nvidia GTX-770 and my graphics card drivers are up to date. My Maya is 2018.2, but I have experienced this issue in 2018 and 2017 as well. Is there any way I can get rid of the crashing?

0 Likes
Reply
1,302 Views
12 Replies
Replies (12)

sean.heasley
Alumni
Alumni

Hi @Anonymous and welcome to the community

 

While we don't officially support the gtx 770, our certified driver with that card is 388.43. So if you can uninstall you're current driver and install that one it should solve your issue!

Nvidia have an article with steps on how to uninstall drivers that can be found here!

 

Once you have completed the steps above download the Maya 2018 certified driver 388.43, install it, then check the version number.

Here is how you can check your GTX 770 driver version number:

 

  1. Open your Start Menu and type Device Manager
  2. Under the 'Display Adapters' tab right click your gpu and select 'Properties'
  3. Under the Details tab you will see Driver Version.

 

 

Please let me know if this resolved the issue, if not I’ll be happy to keep working with you.

 

 

If one or more of these posts helped answer your question, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

 

 

 

Kudos are greatly appreciated. Everyone likes a thumbs up!

 

0 Likes

trubb1
Contributor
Contributor
Been having the same frustrating issue on 2 different workstations w/ no. one w/ a gtx1080 & the other w/ titan x. this only started w/ maya2018 & is still stable in maya2017.

will try rolling back to the suggested driver & respond.
0 Likes

trubb1
Contributor
Contributor

No luck on the workstation w/ the gtx1080 & the autodesk "TESTED" 388.43 desktop win10 64bit driver....

IMG_8692.jpg

w/ maya default prefs and DirectX11 set for render engine, I making a pretty simple scenario....

 

file -f -new;
polySphere -r 10.0 -sx 8 -sy 8 -ax 0 1 0 -cuv 2 -ch 1;
shadingNode -asShader dx11Shader;
sets -renderable true -noSurfaceShader true -empty -name dx11Shader1SG;
setAttr -type "string" dx11Shader1.shader "AutodeskUberShader.fxo";
connectAttr -f dx11Shader1.outColor dx11Shader1SG.surfaceShader;
select -r "pSphere1";
sets -e -forceElement dx11Shader1SG;

setAttr -type "string" dx11Shader1.technique "TessellationON";

 

After activating hardware texturing, then either panning/zooming/dollying or transforming the object a 

few times and KABOOM!

 

IMG_8693.jpg

I'm not even smooth shading, nor activating displacement mapping on the shader.

 

0 Likes

Anonymous
Not applicable

Hi, I'm afraid it is the same for me. I rolled back my driver, used the MEL script posted above by trubb1 and get a fatal error.wmgdgg

0 Likes

trubb1
Contributor
Contributor

Update-

 

Tested same scenario on a certified Quadro p5000 w/ the certified driver(385.08) and latest driver(390.77) and same result.

 

0 Likes

sean.heasley
Alumni
Alumni

Hi @trubb1 and @Anonymous

 

Thank you for the reproducible steps!

 

I was able to get a crash so I'm going to do some more testing then log it with our dev team for a fix to be worked on!

trubb1
Contributor
Contributor
Thanks a bunch Sean!

-Omar
0 Likes

Anonymous
Not applicable

Hi, any update on this issue? Seems like it wasn't fixed in 2018.3 update. I tried with both 388.43 drivers and latest, crash occurred both times (used the same MEL script as posted above)

0 Likes

sean.heasley
Alumni
Alumni

Hi @Anonymous

 

I can confirm that this was not fixed in 2018.3 however I can't say what update/version we plan to implement a fix.

 

The dev team is working on it however and as soon as I get the ok to let you guys know when it is fixed I will!

 

 

0 Likes

Anonymous
Not applicable

im guess this was never fixed???

0 Likes

trubb1
Contributor
Contributor
Actually I think it may have been fixed with update 4. Didn't test thoroughly, but seemed to work a few days ago on a file using dx11 tessellation.
0 Likes

Anonymous
Not applicable

Link?

0 Likes