Posts: 1
Threads: 1
Joined: May 2026
I checked the Curvy asset with Project Auditor 2.0 and found that there is a lot of obsolete code. This was tested in 6.3LTS
It would be great if these could be updated in 6.3+ versions. This should be automatic when you upload from this version, and otherwise the UNITY_6300_OR_NEWER could be perfect.
To check:
- Install unity 6.3
- Install project auditor 2.0
- Run analysis
Posts: 2,221
Threads: 103
Joined: Jun 2017
Hi,
I will run the analysis later today. Will keep you updated.
Posts: 2,221
Threads: 103
Joined: Jun 2017
Here's a rewrite in my own words:
Hi,
Thanks for the heads-up!
I ran the Project Auditor, and the obsolete code it flagged are all false positives. None of them relate to deprecated Unity APIs — they're actually parts of Curvy Splines' own API that I've intentionally marked as obsolete myself.
Here's my reasoning: when I decide to remove something from the API (for simplification or clarity, for instance), I don't delete it immediately. Instead, I keep it in the asset and only remove it with the next major release. This is in line with semantic versioning, which reserves breaking changes — including the removal of obsolete API members — for major version updates.
On top of that, all the flagged obsolete API calls are wrapped in a `#pragma warning disable 618` block, so they don't produce any console warnings at compile time. In my view, the Project Auditor should respect these pragma blocks, just as the compiler does.
For all these reasons, I am planning to remove the obsolete API members only when Curvy Splines 9.0.0 is released.
Did this answer your request?
Have a nice day