Two more questions from me,
Which sound engine do you use?
Do you use CocosLive for highscore service, how do you display it? as UI elements are kinda problematic with cocos2d
Occurro! is out!
(45 posts) (12 voices)-
Thanks Zemm. Have you upgraded to version 1.1 of Occurro!? The first version crashed right where you mentioned under certain network conditions. I haven't heard of any crashes there with 1.1.
Occurro! uses a version of Apple's SoundEngine.cpp that I fixed bugs in. I may move to something else if I can find anything that lets you set sound positions in 3d space.
I'll write more tonight...I only have my iPhone now.
-Bryan
Posted 2 years ago # -
-
@Zemm - Hmmm, that's a new one on me then. Is there any chance you'd send me the crash logs (via Xcode's Organizer)? If you email them to support at acceleroto dot com that'd help me a ton.
@RedshirtRich-
>Got any more in depth insight into the joystick implementation?My post above (http://www.cocos2d-iphone.org/forum/topic/601#post-6774) gives a rough outline of my touch logic. Sorry, but I'm not going to share any of my actual code of that. I don't mean to be inconsiderate, but that's some prized code of mine.
In general though, the answer really depends on what type of control you're trying to make. If you want a fixed D-pad controller, then you'd look for touches in specific zones of the screen. Once you detected a new, moved, or ended touch in each zone, you need to write the code that moves your specific object based on that input.
The easiest way for me to figure out code structure is to draw flow charts by hand of what I want it to do. Here's a flow chart I just drew up of the ccTouchesBegan method for a d-pad controller: http://acceleroto.com/share/dpad_flow_chart.pdf
In that controller, the ccTouchesMoved method could be the same as the ccTouchesBegan method. You'd need to figure out logic for ccTouchesEnded & ccTouchesCancelled to set "command.x" and "command.y" to zero if there wasn't any input detected. Once you have the command (it would work as a CGPoint) programmed, you need to write code in your main game loop to do actions on your player's character based on those inputs.
That's just an example of a simple controller...it may not be the best for your game. Also, please forgive my scribbling in the pdf. :)
It's also definitely worth playing lots of other games and learning from what others did. You'll find things you like & things you don't like in most games. One important thing to note though is things you like may not be things your audience likes. Read forums & reviews of other apps. There's tons you can learn out there.
For Occurro!, most "gamers" & game reviewers love the controls. Many non-gamers find them difficult to learn. You should also think about how the different people in your audience will learn your controls.
-Bryan
Posted 2 years ago # -
I just redrew the flow chart & uploaded a more legible pdf. If you got a hand-drawn version, please download the new version here: http://acceleroto.com/share/dpad_flow_chart.pdf
(This doesn't answer all the questions...it's just a starting point.)
Also, PJ Cabrera's book on game programming with Cocos2D iPhone is here: http://bit.ly/4B0E7g
...and the coolest game ever is here: http://bit.ly/occurro ;)
-Bryan
Posted 2 years ago # -
-
Thanks Dave. Riq & all the contributors here were instrumental in getting Occurro! done - I'm honored to give back whatever I can.
I really need to implement the fixed d-pad logic I flowed out in my earlier post into Occurro! My day job and another coding project are eating all my time for the next couple weeks. I'll get that added to the game ASAP.
Posted 2 years ago # -
Gonna look into PJ Cabrera's book, though I think there are only a few small sections on cocos2d.
Looks like he has a NEW book hitting in December! Anybody got any info on that?Posted 2 years ago #
Reply
You must log in to post.