Open hultonha opened 2 years ago
Note: This ticket also relates to this GHI - https://github.com/o3de/o3de/issues/5339
This is an interesting one, because we try not to document bugs on the website. But because remote desktop is a common configuration for developers (especially right now) we should be considering these as important workflow issues.
I don't think an RFC is appropriate here (it could be moved to the o3de.org repo as a normal issue) but before doing that, it is worth knowing:
Thanks for the feedback @sptramer
Perhaps we could consider creating a page or section specifically to document installing and using O3DE tools online/in the cloud.
Perhaps we could consider creating a page or section specifically to document installing and using O3DE tools online/in the cloud.
+1 to this, I think that's a good idea as there are likely several related 'gotchas' and known issues people should be aware of when using O3DE over remote desktop/in the cloud
Open 3D Engine Documentation / Website RFC Feature Template
Feature - Remote Desktop Documentation for Camera
Currently if working over remote desktop, the camera is extremely difficult to control because internally we 'capture' the mouse cursor (hide it and fix it at a given point). This unfortunately does not play nice with RD (as the client does not currently respect 'set positions' coming from the application).
To work around this, users can disable 'Capture Mouse Cursor' from the settings menu (see below).
This no longer hides the cursor but does make the camera much more usable (this also allows tablets and other devices like this to be used).
It would be very helpful to have an FAQ section about remote desktop (or camera) that could include this information to help surface it to users (currently it's hard to find that this is the solution to the issue).
What is the relevance of this feature?
This will make it much easier to find the solution for using the Editor over remote desktop. There is the possibility of displaying this in the Editor but it's not currently supported and will take longer to implement reliably.
What are the advantages of the feature?
What are the disadvantages of the feature?
Feature design description
Technical considerations
Are there any alternatives to this feature?
Are there any open questions?