Florian Wolf

There really shouldn't be any issues. I only used the pre-release version because I wanted to test out training ArticulationBodies, which are currently only available in the pre-release. But code-wise...

Sure, that sounds like a good feature! There are a few other changes I made but didn't push yet, they will come in the next few weeks. Biggest one is...

> @asmaier is there still no workaround/fix for this problem? Still getting the 405 error I don't think so. Immoscout24 now uses Geecaptcha. I get past the 405 with Selenium,...

I am too interested in something like that and have hit the same wall.

I actually managed to work around these problems. I am fading out a page and then fading the second page in, while both fade-in and fade-out are different animations handled...

I had the same issue. Though no matter what I set my cocoapod generation to in Unity Play Services Resolver, the .xcworkspace wasn't being created. How i fixed it: open...

yup, the Unity iOS pipeline truly is error prone... So many pieces that have to work together, completely unpredictable if any package update breaks anything.

Before Joining: 3 individual Paths, part of 3 different PathCreator components  After Joining: A single path with smooth transitions  The BezierPathJoiner component: