Rendering environment fails

[Anonymous]

Hi everybody,

With last update of Fusion 360 I'm having problems with the rendering environment.

Same with images HDRi from web and also using the Fusion 360 ones.

When I try to render everything disappears.

See video.

Thanks

[lance.carocci]

Hi @Anonymous, sorry that you're experiencing this! Can you confirm your Operating System? I may need additional details later, but if this is on macOS then it might be a known issue we are currently developing a fix for.

[Anonymous]

Hi,

Thanks for the replay.
I’m working with MAC, Mojave.
The version of Fusion is, May update.

Regards

[lance.carocci]

Thanks @Anonymous. We deployed a hotfix last night to version 2.0.5811. Give this a try, as it should contain the fix to Mac rendering that I think may be impacting your workflow. Let me know either way.

[Anonymous]

Thanks. 

I have discovered that the issue only affects the render when you select in the 3D cube one of the views. For example right, left, top, etc... 

If you move the object, for example, using the orbit tool everything works fine.

Only if that could help. 

Regards

[lance.carocci]

@Anonymous is this to say that yesterday's update did not fix the behavior?

[Anonymous]

Hi,

If you refer to 2.0.5811 it didn’t solve my problem.
The situation happens as I mention above.
Render only fails when you select one view from 3D cube.
If you move the object then works fine.

I didn’t see any other update besides 2.0.5811.

[lance.carocci]

I'm sorry you're still experiencing this after the update! The fact that it's only one view cube angle is very interesting. Would it be possible to record this behavior? Or if I missed it in the initial recording, please let me know the timestamp.

Side note:

I'm assuming you used macOS's built in screen recorder - which is great! - but I also wanted to make you aware of Autodesk Screencast as an option. Not because it's an Autodesk product, but because it's specifically designed to look for supported apps to capture command and input meta data and overlay it on the recording once it's uploaded to the Autodesk servers, which in turn can be handy in understanding the timing and exact commands you're using to produce this error. This step is optional; I just wanted to make sure you were aware of it.