Muddyfunster

Thanks KarlG, been a short pause on this while i've been travelling this last week but thanks for the feedback.

This is looking good Kev, such an unusual concept for a game.

diagonal shots would be good, also is it intentional that I can walk over my wall and knock it down?

neat, kinda reminded me of the Xevious proto, I like how it can speed up and even go backwards. nice shadow on the sprite too. Not sure i'm keen on the movement though

This is a bit more gentle, i tried to get a sound like when you pass something like a whoosh / doppler effect. However sound is one of my skills that's still very much "developing". I'd be interested to see which folks prefer, the more muted woosh or the "abused duck" Cheers

*that* made me chuckle. It's a good point, i'll look into it

Thanks for the feedback guys, it's appreciated and helps me to add features and tune the game.

Thanks Arenafoot, kinda surprised but really pleased!

Thanks Kev, JetRush1 did the music and he did a great job, All I had to do was shoe-horn it into the code, which took a few hours but it was well worth it as it's a great track. Props to mksmith to for figuring out how to get TIA Tracker tunes playing via bB, that in itself is a gamechanger I think,

It's something I'm going to have a look at, not sure if how successful I'll be as the game already has a lot of stuff going on and I'm always wary of the cycle count, but i'm certainly going to try but for now this is the "final" version. RushJet1 has also put together some fantastic music for Dare Devil.

let there be music!

Ok, here is a title tune integrated with title screen kernel, TIA Tracker player and Tyre Trax. Great job on the notes by RushJet1 @mksmith, again, nice job on figuring this out

I've updated the first post with a short vid of the revised final version complete with kicking title tune. Huge credit to RushJet1 for his superb music that he provided for Tyre Trax and to mksmith for figuring out how to get TIA Tracker to work in bB,

Thanks! Must admit, I'm pretty stoked to be nominated along side some of the names and games on that list.

Kev, That's a good question and one that probably has hundreds of answers I guess it really depends on your game. In tyre trax, I used the timer to drive the difficulty, so it was indirect, the player had to play better to get a gold cup. secondly, on the "free play" modes, I set the difficulty switches to control the type of obstacles (doubles and triples, instead of singles) and the view distance (make the obstacles appear closer to the player to reduce reaction time). In Dare Devil, the difficulty is the amount of movement in the obstacles from level to level and then in the level, each screen becomes progressively faster. Other variations could be faster moving enemies, enemies that attack more frequently (shooter games) You could tie it to the score, level, screen, timer, amount of enemies dead/alive or combinations of those. Mostly it will depend on your game as to what works and what doesn't.

I got Nena in my thread, I'm happy

Yep, it's kind of limited to bank 6 I think, from the ground up, when starting a project, that's totally fine. Right now, I'm playing code tetris to get things to fit to be honest, its a good excuse for me to optimise my code at the same time so it's a good problem for me to work through.

Also, great job figuring this out and sharing it MKSmith, really cool

New test build available, V180 with functioning bonus balloons.

new public test build added to 1st post.

ok I think I've cracked it Huge code move around needed though.

glad to hear it's working with titlescreen kernel, I was thinking I'd have to write a separate titlescreen as a trade off. did you keep everything in the same bank? must be a tight squeeze

I've tried the standalone example code, that works great with my tia tracker file once the proper changes are made for the variables etc. As a quick test, I tried to integrate the code into an existing program. I usually use bank 2 for title screens, so I've stripped out the title screen code in Bank 2 I added the variables required in to bB - compiles, no issues. When I add the code to initialise and call the tracker it refuses to compile with an unresolved symbol list, oddly pointing at the title setup label. rem ***************************************************** bank 2 rem ***************************************************** title_setup rem initialise tiatracker gosub tiatrackerinit title_loop drawscreen gosub tiatrackerplay goto title_loop asm include "tiatracker/tiatracker.asm" end This is the compiler output --- Unresolved Symbol List 27.title_setup 0000 ???? (R ) 28.title_setup 0000 ???? (R ) free ram: 0 DPC free RAM= 603 35 bytes of ROM space left in bank 1 Music player size: $e9 Track size: $4bd 851 bytes of ROM space left in bank 2 302 bytes of ROM space left in bank 3 585 bytes of ROM space left in bank 4 1909 bytes of ROM space left in bank 5 35 bytes of ROM space left in bank 6 1310 bytes of ROM space left in graphics bank If I move the code to the end of bank 2, then every other label gets flagged as unresolved. Probably something I'm doing wrong, need to play with it some more. [edit] forgot to add, I have other code also sharing bank2 but there is enough space as you can see from the compile output.

Jesus Mary and Joseph! I can't wait to see this!

I was referring to RT's note on how to activate breakpoints for overcycling, not any issue logging with Stella I spent about an hour trying to find that post