How do I disable pathtracing on a saved image for non RTX computer?

Development Getting Started & Setup
,
1

Hello, I believe this may be a bug but maybe there is a work around Im not aware of. I created some images of a kitchen on a ray trace enabled PC and those are stored in my images section as path traced images.

When I switch to a non Path-traced computer, of course it will warn you and say path tracing has been disabled because you dont have a ray trace graphics card etc. So I went to duplicate the image but turn path tracing off but the path tracing on/off butting is greyed out and unable to be clicked. I understand that you cant turn path tracing ON but you actually cant even turn it OFF even on a duplicated image.

If you are duplicating images on a computer without path tracing I would love to see them duplicate without Pathtracing on or at least the Pathtracing button on a non RTX computer would only be available to turn OFF rather than not able to be pressed at all.

The only solution I have is to go back to the PC duplicate the images, turn off path tracing and save. Im looking to be able to take care of those issues on the go.

I hope this feedback helps. Y'all do an incredible job with Twinmotion and appreciate all of the updates that are being made!

2

Hello ,

Thanks for sharing this with us. You are correct in that there isn't a way to disable the Path Tracer for images when you're using a device that isn't Path Tracer capable. While not exactly a bug, your use case definitely shows that there is room for improvement to make this more user-friendly.

I'll be bringing this up with the team, but please also submit this feedback on our Public Roadmap here, so you can describe exactly how you'd like this to work in the future. If you have any additional feedback in the future for new features or enhancements, please feel free to submit it on the roadmap, as that's the best place to make sure we hear your requests.

Best,

​​​​​​​Raghib

3

Content removed by moderator.

4

Thank you Raghib, I have submitted to public roadmap. It seems like it may be a simple fix but also nothing is a simple fix right?

Good luck!