As said yesterday, there's a little update now live!

-The intro story have been reworked.
-Chapter 1 have been partially reworked.

I'm currently developing interface features so everything I need is ready for future gameplay. The story should advance soon and be available when the first chapter is over or close to be.

I announce that I will share my game up to the chapter 2 so when I'll fully finish my game you'll have plenty of story to discover and choices to make! And of course I will keep you updated on the development of Luali: A Quest for Wings even passed the chapter 2!

And as always, thank you all for your support and for following me in my first project!

This Game is going a bit bonkers from vinicity's funky back ground to Daves music mixing function to shooting ships ufo's and floppy disc looking boss's im going to press on and see it through.Plus iv learnt alot from this project.
iv now added in a shield instead of lives for better recovery
need to sort the boss so he's out on his holidays atm.
il reshare later with these updates.
to do;
finish the boss get him in
add big shot which will be deploy able at a cost of 100 points will wipe out all the ships
add pulse shot which will slow the ships back down at a cost of 300 points
and better enemy logicmovement

@vinicity very neat ✨, it just makes you wanna play it immediately.

@Martin the first level is shared but not the updated version just a couple more things to add to the 2nd level hopefully later today ...:)

@Retrocade_media Thank you. Your "Sanitization Unit Fuzeion" logo looked good too. I would like to make a title like that for my next game's title screen 😊

@toxibunny said in First project:

Is that a thing that’s going to stay? It would make my level creation a lot easier if so...

I'm not aware of any plans to change the current behavior

I was only thinking about this earlier. I'm hopefully going to get back to it at the beginning of the week for a day or two. I've got some things lined up and ready to go in my head, it's just getting the time now.

Very good indeed!

Thanks for the comments, guys. Actually finding was not too hard, but fiddling when to start stop the playback, to get them loud and clear (well as good as you can).

Woah! I've always wanted to do something like this on fuze but 3d is way beyond me at the moment... Hopefully you can succeed!

Love it! really nice effect

My first stab at the ball bouncing (which in my defense I did really, really late at night) was taking the result of the collideSprites() function, which returns, among other things, a vector called resolution_a (described as "Vector - How sprite A was pushed during the collision { x, y }"). So I just multiplied that vector with a constant and set that as the new speed for the sprite.

That kind of worked, but it was very inconsistent. Sometimes the balls would just pass through the viruses, and sometimes they would fly away super fast. It looked kind of bad, to be honest.

So I decided to fix this. I still wanted to use the c.resolution_a, since that seemed easier than having to calculate angles and stuff myself. So what I did was taking the returned vector, normalizing it using the normalize() function, and then multiplying it with the speed the ball had before the collision.This worked perfectly, and the bounces feels really good now. Very satisfying!

@Mechanical if you download the ‘improved joycon test’ program from the big share thread, it’ll show you what is happening with the numbers when you twist the joycon around. The numbers go from -1 to 1 just like the analogue sticks, and can probably be used similarly in your case (atan2 to get an angle maybe?) Be aware though, that proper recalibration only seems to be possible by docking/undocking or disconnecting/reconnecting the joycon. I think you’ll be able to get some sort of usable aiming working though if you try a few things out..

@xevdev they should have or would be good to have links on this site for them

Use the time() command. Have variables called starttime, currenttime, and elapsedtime. Put a starttime = time() right at the beginning before your main loop, put a currenttime = time() inside your main loop, and then just remember that elapsedtime = currenttime-starttime. Making starttime=currenttime will reset the counter (don’t do that every loop though, obviously), and if you just want seconds, then secondscounter = elapsedtime%60

The % means ‘modulo’ , btw. Google it, it’s very useful!