Compilation Errors: Unity 6.3 + ARCore Extensions + Geospatial Creator (CS0592 & CS0246)

Hello Cesium and ARCore Community,

I am encountering blocking compilation errors while trying to set up ARCore Extensions with Geospatial Creator in Unity 6.3.

Despite having the packages installed, the GeospatialCreatorCesiumAdapter script (provided by Google ARCore Extensions) is failing to recognize the Cesium namespace, and there is also a C# attribute error in the ARCore source code.

Environment:

  • Unity Version: 6.3

  • **ARCore Extensions Version:**arcore-unity-extensions-1.52.0-arf6

  • Cesium for Unity Version: 1.21

The Issues:

I am facing two distinct types of errors preventing the project from building:

1. Syntax Error in ARCore Extensions (CS0592): The compiler rejects the [field: SerializeField] attribute in the Google script, which seems to be an issue with the C# version compatibility in Unity 6.

Library\PackageCache\...\ARGeospatialCreatorOrigin.cs(87,10): error CS0592: Attribute 'SerializeField' is not valid on this declaration type. It is only valid on 'field' declarations.

2. Missing Namespace / Reference Errors (CS0246): Even though I am setting up the Geospatial Creator, the adapter scripts cannot find the Cesium library references.

GeospatialCreatorCesiumAdapter.cs(26,11): error CS0246: The type or namespace name 'CesiumForUnity' could not be found GeospatialCreatorCesiumAdapter.cs(65,25): error CS0246: The type or namespace name 'Cesium3DTileset' could not be found (And multiple similar errors regarding CesiumGeoreference)

Context: I expected these libraries to work out-of-the-box as standard dependencies. The #if ARCORE_INTERNAL_USE_CESIUM directive seems to be active, but the references are broken.

Has anyone successfully configured Geospatial Creator in Unity 6.3? Is there a specific branch of ARCore Extensions or a workaround for the SerializeField error in this Unity version?

Any guidance would be appreciated.

Thanks.

Hi @Oscar_Rojas, welcome to the community!

We don’t have any insight into the workings of Google ARCore extensions and Geospatial Creator, but perhaps your errors can be resolved by using different versions of Cesium for Unity.

Could you try downgrading to Cesium for Unity v1.19.0? We made some architecture changes in v1.20 and v1.21, so it’s possible that the bug comes from there. Let us know if that helps!

for posterity, I did downgrade to cesium v1.19 and it compiles, so do that if facing this issue
I hadn’t tried 1.20 yet