Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Problems compiling after pulling down project from source control
#2
Hi

Yes, Curvy Splines can be part of of any source control repository. I use it that way, and I have plenty of customers that use it that way, with no issue.

The assembly definitions generated by Curvy should be enough. If there is any issue with them, I am not aware of it and no customer reported that to me.

Sometimes Unity does some weird things. Try removing the sln file of your project, and make unity generate a new one.

Try comparing (using WinMerge for example) the two project folders you have, the working one (not using source control) and the not working one (using source control). Maybe there are some missing files in the not working one?

Try including little by little Curvy and its dependencies in your project until you reach the point where it does not build. Start by including DevTools, then LibTessDotNet, then Curvy, then Curvy Examples

Try using another unity version

I hope this helped
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.
Reply


Messages In This Thread
RE: Problems compiling after pulling down project from source control - by _Aka_ - 01-16-2022, 11:53 AM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Get position of all control points for a spline gekido 1 6 03-28-2024, 10:08 PM
Last Post: _Aka_
  Avoiding runtime GC allocations on control point position change Ell223 8 18 02-24-2024, 10:43 AM
Last Post: _Aka_
  Connection "next' control point jh092 3 15 11-22-2023, 11:47 AM
Last Post: _Aka_
  Custom Control Nodes Lupos 3 15 05-27-2023, 09:05 PM
Last Post: _Aka_

Forum Jump: