Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
On my one off teapot test, yes it does fix it. I had the same test project that i could instantly break my system with (teapot in Action, HWAA on, rotate in Y). This now works as it should on both 4X & 8X HWAA. As to whether it fixes the issue outright and for real world use, can't say, but something that was definitely broken now isn't.
Hopefully now I can get Resolve running, which was simply impossible on 10.9.3.
Still broken for me. Two ways around it. Firstly, and most obviously, deselect hwaa until you want to render or move on from Action. Secondly, and less obviously, create a node upstream from Action and use that as a context view. Then you can alter Action parameters but look at the effect 'through' that upstream context view and thus not have Smoke crash the system.
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")