My opinion:
1.Make the animations look smoother (e.g. dog and chicken).
2.Slow the player down and make the controlls harder (so that it is harder to find the right balance).
@slackmoehrle Awesome thanks for the offer. I might have to take you on it
@squares you can search for triangles strip here. I discussed it with bunch of people in the past. As for custom editor basically it’s a small tool to create terrain points and serialized to json for the terrain sections. Sorry can’t show it, but you get the main idea.
yes because the levels arent difficult because of the actual terrain (it is only pressing forward and a few times backwards) but because of the distance.
Look at trials fusion. It takes alot of skill to balance the player on the rather difficult terrain!
@vkreal2 congrats for the release! (if you want, you could test my game Armed Chicks).
My feedback:
I think the game has an important problem with the frame updates.
I can’t see the game fluid, it’s lagged.
The terrain/background, sounds like you cut and paste ‘parts’ of the images, but it looks bad.
And look this video, sometimes i can’t see the background:
(sorry for the bad filming haha, but i repeat: sometimes i don’t see the background. i’m not moving the camera, really, i don’t see the background).
Again, congrats for the release! but fix these bugs, it’s very important for the game play
Definitely not. It’s good this way. Do you use some form of analytics (e.g. Firebase Analytics)? With it, you could see, how often the players start a level and if the reach some points in the game.
SensorLandscape is better, because the player can still rotate the device (if maybe the charger needs to be on the other side). Because the template for cocos is portrait mode, I can’t add SensorLandscape to it, so more (non Android) developer are aware of it.
Can’t wait to test it on my iPhone XS, because most of the developers aren’t aware of the safe area If you do it right and later update to cocos 3.18, it should be also fine on Android 9 (I hope).
You shouldn’t ask me for SDKBox. I don’t like middleware code for such things like Analytics, because it’s a black box. If it’s open source, I’m fine with it, because I see what it does. That’s why I’m also against prebuilt libraries in cocos in general. And Firebase Analytics is offering a C++ library (wrapper for calling the iOS/Android SDK code): https://firebase.google.com/docs/analytics/cpp/start - So you don’t need any (closed source) middleware for that.
But this is only my opinion, if you want to save time, feel free to use SDKBox.
Offtopic: Because of the GDPR (in Europe) you have to do some more work in implementing such tools. Even your ads provider has to be GDPR conform and you have to inform the user about it.