matrixreal: you need to do this on your device / phone and this setting depends on your device, so just ask Google how to clear app data from an app on your device.

Hey,

can you provide a screen of your code? I guess it's a performance problem, go check your project in your browser in debug mode and check the cpu-usage. On phones the cpu-usage is around 5-10 times higher (depending on the phone) which can cause lags...

Thanks for the help, I've already solved the problem. I've added the Rotate-Behavior to the Pin and on collisions I set the Pin's rotation speed to the negative wheel's speed for x seconds (depending also on the wheel's speed) and then for the same period of time the negative speed so it gets back to it's normal position. After trying a bit and setting the right times it looks pretty nice now and also performance isn't a problem with that method :)

But maybe your method would have been a bit easier to do.

Thanks!

Hey everyone,

I've made a simple "wheel of fortune" with 8 fields. Spinning the wheel and getting the right rewards works so far. On top of the wheel there is a small "Pin" which shows what you won. Now my question: How can I rotate this little pin when it hits the separaters of the rewards of the wheel while the wheel is rotating?

The wheel rotates with the "Rotation" behavior. I've already tried to make the collision polygon of the wheel like it only has collisions on these separaters. But which behaviors do I have to add to the Pin so that it stays always at the same position but rotating like 20 degrees to the right when it hits the collision polygon of the wheel? Is there any easy way to do this?

Thanks for any help!

Thank you dop2000, just wanted to make sure that there will be no problem by keeping the old events.

For me it seems the easiest and best thing for everyone would be going back to the old system but additionally adding a description so there is less confusion. Because I also think there are more people confused of the new update (because most of the users can't sign anymore) than on the old version.

Is there any chance to add an additional description, so if someone can't build then he just should try to enter the keystore-password in the key-password field or how this actually works?

I have several games and really don't want to change keys for all of my live games if that's even possible.

Atm everything seems to be working by using another signing service, but of course it's more to do so... (exporting, then uploading to another software and signing)

Hey,

I found this from Google:

"Note: Using app signing by Google Play is optional. You can still upload an APK and manage your own keys instead of using an app bundle. However, if you lose your keystore or it becomes compromised, you won’t be able to update your app without publishing a new app with a new package name."

Here the link:

support.google.com/googleplay/android-developer/answer/7384423

So I think it's not possible for everyone to generate a new key. But I don't know how many users will face this issue. Atm. I'm trying to sign the app by another service, but with C3 I can't.

I guess you need to use always the same keystore for google play since it's a live game (already published with the key)...