When I try to build for visionOS as platform, Iam keep getting into this error, CesiumForUnity namspace not Found, can any one help me with this please! Even though I have the CesiumForUnity package
I am able to run the and get the 3D map tiles in unity’s player but I am unable to build i for visionPro, If I try building for other platforms like ios it successfully builds without the namespace error, but I am getting into this error when I do it only for VisionOS
/Users/saikapil/Documents/MathCo/Practice_Unity/GithubRepo/ProjectSpirare-for-Unity-1.5.0/packages/jp.co.hololab.spirare.cesium/UI/Scripts/CesiumCreditText.cs(1,7): error CS0246: The type or namespace name ‘CesiumForUnity’ could not be found (are you missing a using directive or an assembly reference?)
/Users/saikapil/Documents/MathCo/Practice_Unity/GithubRepo/ProjectSpirare-for-Unity-1.5.0/packages/jp.co.hololab.spirare.cesium/UI/Scripts/CesiumCreditText.cs(16,17): error CS0246: The type or namespace name ‘CesiumCreditSystemStringConverter’ could not be found (are you missing a using directive or an assembly reference?)
There are other threads on the forum as well. I’m not sure how many of them have arrived at working solutions, but there may be some bits of build advice:
Is there an active discussion about the potential support for Cesium in RealityKit in the future? While I’ve managed to get it working with Unity, I’d much prefer to use SwiftUI and native Swift libraries instead of relying on Unity for Cesium integration.
At present, combining SwiftUI elements with Unity-managed content in a single volumetric window isn’t supported. It would be amazing to see RealityKit adopt support for Cesium, especially as more developers focus on building solutions natively in Swift. Additionally, managing multiple frameworks feels cumbersome. A seamless integration with RealityKit would greatly simplify the workflow when working with native SwiftUI and libraries.