Copyright © 2026 Unity Technologies
The cause of this issue is the VFXManager.asset file, whenever kCurrentRuntimeDataVersion is incremented when runtime data changes, it expected to automatically being upgraded in user project which is not the correct behaviour and the VFX graph team has plans to to take this out for 6.5. The fix for 6.5 for this issue will be included in this refactor
The cause of this issue is the VFXManager.asset file, whenever kCurrentRuntimeDataVersion is incremented when runtime data changes, it expected to automatically being upgraded in user project which is not the correct behaviour and the VFX graph team has plans to to take this out for 6.5. The fix for 6.5 for this issue will be included in this refactor
The cause of this issue is the VFXManager.asset file, whenever kCurrentRuntimeDataVersion is incremented when runtime data changes, it expected to automatically being upgraded in user project which is not the correct behaviour and the VFX graph team has plans to to take this out for 6.5. The fix for 6.5 for this issue will be included in this refactor
Steps to reproduce:
Actual results: "Asset Database is set to Read Only, but it has found out-of-date assets. This should not happen!" and "Refresh completed but there are assets queued up for importing. Check for code that modifies assets which gets called after OnPostProcessAllAssets." errors are thrown in Virtual Player's Console
Expected results: No errors are thrown when Virtual Player is started
Reproducible with versions: 6000.3.0a2(1.6.1), 6000.3.0f1 (2.0.1), 6000.4.0a5(2.0.0), 6000.5.a2(2.0.1)
Not reproducible with versions: 6000.0.63f1 (1.6.1), 6000.2.14f1 (1.6.1), 6000.3.0a1(1.6.1)
Tested on (OS): macOS 26.1
Notes:
Issues you vote on will appear here