I have a bit of an unusual use-case, where I have the player in a VR scene and want to provide them a secondary 'view' of a tileset on a render texture. In short, I wish to use a camera that's not Camera.main for driving Cesium's internal calculations. As it stands right now, it appears that the internal C# -> C++ Interop is hard coded to use Camera.main to simplify the hooks into the unity engine.
Would it be possible to allow for an override so we may pick which camera controls how the tilesets load? Having the ability to chose which camera projection matrix controls the screen-space error of the tilesets is critical for my use-case. Any resources that could help me accomplish this would be most welcome!
kring
commented
8 months ago
I have a bit of an unusual use-case, where I have the player in a VR scene and want to provide them a secondary 'view' of a tileset on a render texture. In short, I wish to use a camera that's not Camera.main for driving Cesium's internal calculations. As it stands right now, it appears that the internal C# -> C++ Interop is hard coded to use Camera.main to simplify the hooks into the unity engine.
Would it be possible to allow for an override so we may pick which camera controls how the tilesets load? Having the ability to chose which camera projection matrix controls the screen-space error of the tilesets is critical for my use-case. Any resources that could help me accomplish this would be most welcome!