Yes, it looks like I can add the stack traces without error now.
I can't really provide a simple repro case directly. The general steps of what happens to trigger this error:
1. Prefab is loaded via addressables
2. This prefab has a CurvyGenerator on it, don't know how much these screenshots will help show the setup
![[Image: mVhHVJE.png]](https://i.imgur.com/mVhHVJE.png)
![[Image: Z4IQAHH.png]](https://i.imgur.com/Z4IQAHH.png)
3. When instantiated the error happens immediately with the provided callstacks. Before any of our custom code runs that actually specifies where the control points should be.
The generator doesn't really have anything unusual on it so far as I can think. The only thing I've changed from the default settings really are the materials and I have disabled pooling on the splines as the generators are being pooled by us.
I can't really provide a simple repro case directly. The general steps of what happens to trigger this error:
1. Prefab is loaded via addressables
2. This prefab has a CurvyGenerator on it, don't know how much these screenshots will help show the setup
3. When instantiated the error happens immediately with the provided callstacks. Before any of our custom code runs that actually specifies where the control points should be.
The generator doesn't really have anything unusual on it so far as I can think. The only thing I've changed from the default settings really are the materials and I have disabled pooling on the splines as the generators are being pooled by us.