logi_9
By utilizing the OSC interface of the dolly system, it is now possible to indirectly obtain and set the camera position from external systems.
If external tools could automatically control the camera, users would be able to implement complex features beyond the capabilities of the standard dolly system. However, the currently available API still presents some barriers, such as requiring JSON files for data exchange and the need to manually set waypoints to retrieve parameters.
If the current camera parameters (position, rotation, zoom, etc.) could be read and written via OSC, these issues would be resolved. Given that importing and exporting paths is already possible, I believe the technical challenges would not be too significant. Could you consider implementing this functionality?
Below are some examples of features that could be achieved with this improvement:
Example 1: Advanced Camera Control
It would enable advanced camera automation beyond simple "Look-at-me" functions, such as dynamically switching controls based on the player's position, similar to how Cinemachine works.
This would allow users to utilize functionalities like those provided by VRCPrismStudio (by harunadev) without requiring other community-made camera extension assets.
Example 2: Integration with Community-Made Camera Assets
Currently, the VRChat user community offers various camera extension assets for high-quality video recording.
If the standard camera's position and other parameters could be accessed, external cameras could be aligned accordingly, enabling features like dolly movements and audio source switching in combination with the standard system.
(For this use case, allowing camera information to be retrieved as avatar parameters would further improve convenience by eliminating the need for external tools.)