do the high scores reset every day? i had 2 high scores over 20k yesterday.
Log in with itch.io to leave a comment.
The iconic GALAGA, another OUTSTANDING port from ARLASOFT! Check out my sample of the game play, and please subscribe to my channel if you feel so inclined! Thanks! :)
Just the best Galaga clone I saw on the Commodore 64. Period!
Is this version (v1.05) going to be the final version?
I hope and guess not. V1.05 still has some smaller problems that should be fixed, like for example the annoying autofire-problem.
I will hopefully get some time before Xmas and New Year to sort out a final update. I wanted to make some improvements to enemy movements but ended up breaking the whole game so had to revert back to v105.
Nice, sounds good. One question - did you read what I wrote a bit further down, when I mentioned "Phoenix (Atari VCS-2600)" and the one with "Tiny Galaga" on the Amiga-500 and it's color scheme, among other things?
So nice! So well done!
Great version. We play this game in the C64 HISCORE challenge this month :)
There seems to be a bug in two player though. Very cool otherwise, great unofficial port.
There are three ships shown and when one of the player ships gets hit, one of those three ships get removed, even though each player has three ships. A bit confusing.
Do you mean the lives count? You share three lives, although only the losing player can lose the final life.
Will there be a V1.06, that fixes the last remaining bugs? That would be great. Especially the thing with the Autofire, that goes on shooting by it's own, is a little bit strange sometimes in gameplay. Overall it's definately a good game, only a few teething problems should still be eliminated.
Yeah, with Galaxian being released in the next few minutes (spoiler), I'll hopefully have some time to tweak a few things on Galaga.
Can you try Galaxian and see if the auto fire is fixed on that? If so I can put that fix into Galaga too.
I tried your new Galaxian game and there this problem does not occur. I've tried it with two joysticks, both of which contain "rapidfire as long as the player holds the firebutton down" and whenever I leave the button in "Galaxian DX", the rapidfire stops immediately, like it should be. So there it works.
By the way - there in "Galaxian DX" a rapidfire (autofire) doesn't help much anyway, because a maximum of only one shot of the player can appear on the screen at the same time. But with "Galaga" it often helps, because more shots on the screen are possible there and you can shoot several enemies one after the other in Galaga with rapidfire. :-)
Your new "Galaxian DX" is really good, the next great C64 port of a classical Arcade-shooter. WOW!! You know what. If you don't know, what to port next to the C64, then I have a suggestion. The Atari VCS-2600 version of "Phoenix" is fantastic. A little different from the Arcade original of this game (because the VCS2600 couldn't implement it technically back then, i guess), but the Atari-2600 version of "Phoenix" has it's own charm and plays really great. My number-one game on this system since my childhood. To have this Atari-2600 version 1-to-1 on the C64 too, would be awesome! Nothing needs to be changed, "Phoenix" on the Atari-2600 is awesome as it is and exactly like this it should be ported. Maybe you will find time for that at some point in the future, that would be great!!!
Could you have a look at this thing in the meantime, now that it's clear since some weeks, that in "Galaxian DX" this problem with the Autofire don't occure? Then this could be fixed in Galaga too, like you mentioned.
And one question more. Somewhere here in the entries you wrote, that, when less colors would be used for the attacking enemies, technically more possibilities would be there, for improving other things to make Galaga, which is already good, even more closer to the Arcade version. And you also wrote, that you decided against it, because you wanted the sprites to have more colors. Just one question to this - how about a second version and then a selection-function for the player, in the beginning of the game, where he could choose, which version of the game he wanted to play. And then a second version would be created, with a similar look, when it comes to the colors, than for example the game "Tiny Galaga", that came out last year for the Amiga? Only two colors, but nevertheless, it looks and plays really good. Looks like a LCD game on older game&watch handhelds, when it comes to the colors. Everything could be the same like now in your C64 Galaga, just with less colors (two or three) but therefore with some improved other things? What do you think? Player then could choose everytime in the game-menue, which version to play and this version then reloads.
well, I have been waiting for this since forever, but you are not completely there yet... compared to the nes version graphics are gross. the music is not completely like the arcade one. and you cannot fire while being captured. A potential great game, but graphics and sound should improve.
The C64's hardware limitations make it impossible to improve the graphics in any meaningful way. You can either have hi-res characters, meaning you can define every pixel in a 8x8 character block or 24x21 sprite, but they can only be one colour, or you can have multi-colour meaning you can only define pairs of pixels but have three colours, two of which must be shared across all chars/sprites. I chose to go for more accurate colour over sharper sprites that are all one colour.
Contrast this with the NES that can have hi-res sprites with any three colours from a palette of 54.
Unfortunately some compromises are inevitable, if it was easy it would have been done in the 80s.
Same with the sound, it's as close I can get without the benefit of dedicated sound hardware built specifically to make Galaga's sounds that the arcade has.
I see that you can 'fire' when being captured on the arcade but this doesn't really add anything to the game, the bullets just fire off in random directions and I've never seen one hit anything. Because I'm drawing player bullets with characters, changing their X position in flight would take probably a couple of days to code, for very little benefit.
A potential great post but spelling and punctuation should improve.
I am reviewing this game right now for Zzap!, italian version (www.zzapmagazine.it). I know that the hardware (ie: commodore 64) has its own limitations. But Galencia is doing a better job graphics-wise.
Firing when captured is a plus: you can shoot enemies while being captured, and you could even free yourself (killing the capturer) if you are playing your last life. :-)
I appreciate what you are doing, don't get me wrong. I love that game too.
and please, forgive me when I type using my phone: I make many mistakes using a virtual keyboard. I guess you see my point, anyway.
It's a good game, but it could improve and it could become a great one!
Galencia's sprites are much bigger, so you can obviously add more detail. The smallest sprite in Galaga is half the size of a Galencia sprite.
But at that point they take up so much room compared to the overall dimensions of the screen it's no longer Galaga. In Galencia the swarm is virtually on top of you, it might look more like a zoomed-in Galaga, but it can't possibly play like it.
There are also less sprites so they don't need to use chars, and they have the advantage of not having to look like anything that came before so can be designed with double-wide pixels and the available colours in mind.
As I say, I'm no artist but I can't really see how you can make Galaga on the C64 look significantly better without compromising on gameplay.
If I were making a brand new IP like Galencia, built specifically for a 320 x 200 landscape screen as opposed to 224 x 288 portrait one, absolutely the graphics wouldn't be good enough. And I agree there are definitely elements from the arcade gameplay that I haven't quite captured yet. That's why for Galaxian I am porting directly the arcade code.
The choice is really down to chunky, less detailed sprites or no game at all. And there's no way I'm doing hi-res single colour enemies, this isn't a Spectrum ;)
contact me and I will provide you the review when the magazine has been printed (contatti at zzapmagazine dot it or davide at davidecorrado dot eu). As I said, good work, being galaga one of my favorites, I am very picky with it. if you could, add fire while being captured :-)
Finally I had some time to test this version (1.05). It looks and feels awesome, but I encountered two bugs: the first was already stated before. When I use a joystick with auto fire, that requires me to hold the button down for firing, it continues to fire even when I stop pressing the button or disable the auto fire altogether. It stops however, when I press the button without using auto fire (tested with competition pro and QuickShot QS-137F). The second bug is, that the datasette, that is usually plugged in, turns on when I start the game (I hear the motor). That's a little annoying. Maybe you find some time to look into these problems.
The routines SaveKernalZP and SaveGameZP both write to $00 and $01 (STA $02,x writes to $01 if x=$FF). I think this is not intended but switches the datasette motor on and might cause other side effects.
Yeah you're right, there's another bug where I copy what ever is in GameZP to the actual ZP upon launch, when I intended to just back up the Kernal ZP at that point. It just happens it doesn't crash this game but it did the next project. Will fix!
Lovely version of the game. Nice job!
If you are still interested in fixing bugs, I have a couple for you for v1.05:
1. After shooting the enemy that had previously captured my ship, the ship doesn't fall down but instead behaves like the enemy alien that captured it (including swooping down to attack).
2. As I lose a life but before I respaw,n an enemy ship comes down to try and capture it in its beam. When I do respawn the enemy ship reappears as if it actually did capture my ship.
I have video footage of these if you're interested.
Thanks! No 1 is not a bug, if you shoot the boss in formation, your ship flies out of the level and rejoins as the last enemy in the next normal level. This happens in the arcade too.
Number 2 sounds like it might be though, video would be great.
Today i found another strange thing in the game while playing.
It was the first time today, that i played the game with a joystick, that has Rapidfire. And normally on this controller, the Rapidfire only shoots faster, when i hold one of the firebuttons, this controller don't has a real Autofire, which you turn on and then it shoots by itself until you turn it off again.
But while playing Galaga for a while and when i took my finger off the firebutton, i recognized, that the rapidfire suddenly continues to shoot quickly by itself. How can this be? It was then, as if this joystick had a real Autofire, a fire, that shoots quickly by itself, which this controller does not have. And this is reproducable also in the game, at least in the emulators it is, i will try this also on my real C64 tomorrow, but i guess, that this will happen there too.
I then tried this joystick with other games, if i can reproduce this behaviour, but i can't. Only in Galaga this happens.
I had the same issue with my setup (real C64 and two different joysticks). When I use a joystick with "real" auto fire however, I don't have any problems, even when I turn auto fire off.
Fantastic! One of my retro-dreams come true! Finally I'm able to enjoy Galaga in my favorite computer of all time! It runs flawlessly on my Ultimate 64 Elite, I noticed only a small glitch in the score table when adding my initials, garbled characters appear when I move the joystick up/down, but it seems to fix itself. Congratulations!
Had you seen my feedback about the FC3 fix, because in v1.05 this problem is still there?
And i wanted to mention another thing, that i recognized. When i get a new d64-File, i usually look into this file with the d64-editor first, before using it. And since two versions of Galaga, this tool always reports me a "Galaga is crosslinked with galage at blocks nr..." message, when i open the Galaga.d64 file. Also the tool shows not completely deleted files on this disk, which are still visible as scratched "scr" files and here seems to be the reason for this crosslinked-message.
Seems like you used a d64, on which an older version of the game was saved and this version was not fully deleted. The reason, why i mention this is, that this crosslinked blocks possibly could cause problems, for example with the score-saver and so on. Not a must, but could be. Better would be, to completely delete older versions of the game on this disk, or to use an empty and fresh d64, when a new version appears.
I only got to talk to the Freaky Fish dev this afternoon. He worked out that there is a bug in Final Cart 3, when it saves files it switches the C64 to VIC bank 0, then doesn't switch it back to what it was. Therefore the game is still technically functioning but displaying graphics from the wrong area of memory.
I've uploaded a new v105 that should fix this and is also a brand new .d64.
The FC3 problem is fixed in the newer v1.05, good work, thanks for that. Yes, i also reported this bug in the "Freaky Fish DX" comments yesterday and it was solved there too now. But you've already saw my comment below here, with the "extended zeropage to default..." answer, how to fix this problem, right? I guess, it's a similar way or maybe the same way, to fix this problem?
The thing that "czayas" reported above, about the garbled characters while typing in the name for the highscore-list, i also had several times today in the newer v1.05. Wanted to report it, but then saw, that another person already did this. One time today, and this was very strange, even the score of the first place in the highscore-list, changed to a much higher-score and this, while i typed in my name and moved the joystick. LOL Seems like the controller-movements caused this, but i am not sure.
just noticed that if I let my last fighter get captured, I get a free fighter? I don’t think that happened in the original! I thought it would just go straight to game over after being captured…
Also I seem to keep hearing extra lives sounds without actually getting one.
Which version are you playing? That bug should be fixed.
And I think the sound you're referring might be the 'transform alert' when an enemy is about to spawn three transform enemies. It does sound similar to the extra life effect.
It's the latest 1.04. I guess the bug isn't totally fixed. When I have no lives in the tank, I shouldn't be getting a free life!
Using WinVice got to Stage 10, and it seemed to get stuck there once the enemies were defeated? I Used v103
I've uploaded V1.04 which fixes this issue, apologies!
Gameplay is good now in V1.04, but i found a little hardware compatibility problem. Alot of users have a FC3 modul on their C64, especially in combination with a SD2IEC this works great because of the modul-fastloader that also works with the SD2IEC.
I found out, when Galaga is played while a FC3 is activ and then the player makes a score, that is enough for the highscore-table, then there is a graphic-problem, after the highscore is saved. The graphics are destroyed then and the player must make a reset, before he can play again.
The only thing to prevent this problem when a FC3 is plugged on the C64 is, that the player uses the "kill" command in the BASIC screen to turn the FC3 off, before starting the game. Bad thing is, that then the game can not be loaded directly over the filebrowser on the SD2IEC, but must be loaded from BASIC instead.
Maybe this incompatibility of the score-saving to the FC3 modul can be fixed? This thing is a known problem, because Galaga is not the first game i had, that has this problem with the score-saving when a FC3 is activ. I can remember that the game "Freaky Fish DX" had a similar problem in the original version. The FC3 is a part of the problem here, but i also know, that this can be fixed. So if you can not locate this problem, i would know, which person i could ask, that knows this problem and how to fix it without much effort. Then i could give this information to you, if you want.
Would be great if you could find that out, one of my testers had the same issue but I don't have that hardware to test with so have no idea where to start. I'll put a note for now that people with the Final Cartridge 3 need to disable it.
I ask this person, how to fix this and then come back to you. By the way, if you have no real FC3, you can also recreate this in one of the known C64 emulators, by inserting an FC3 image there. Then the same problem occurs.
Okay, i have the answer now, how to fix this FC3-incompatibility. He wrote, it should actually be quite simple. The saver routine in the FC3 modul causes this error here in the game. To fix it, you have to set the save-address in the extended zeropage to default.
The code can be anywhere in the game, but it must be before JSR$FFD8.
That's all he wrote. To check, whether the fix works, you don't need a real FC3. You can also take an emulator and insert an image of the FC3 there, the behaviour will be the same. That's a good way to check, even if you don't own a real fc3 yourself.
Apologies for the bugs everyone, we thought we had done thorough testing but obviously not! I hope it hasn't spoiled your enjoyment of the game too much.
And just like that 2021 is super slick! legendary!
Thank you for adding 2 player, my kid and me, there's no stopping, now the best game ever, just got even better, I only have praise to say for this game, making it more addicting than ever
Thanks, yeah I put that in so I could play with my little one. Brought up on touch or mouse control she really can't her head around the joystick though!
Amazing conversion. Love how you have coaxed the SID to output very arcade accurate effects.
Happy to purchase when you guys fix that bug on level 13. ;)
Thank you, my wife and I love that we can play Co-op.
The game plays very well on the MiSTer FPGA C64 core.
Awesome. I need to get into c64 development 4sure