Star (Dust) Wars

[gyagyagyerek]

Originally Posted by nujack

I have some slowdowns in first Level which makes it impossible to navigate the ship any longer. Ship is destroyed shortly after. That wasn't the case with the first Demo. BTW I tested the game on my A4000 with 060/PPC.

I have Updated the download link with a possible fix (in ShipMovement/Timing). Please try again!

[gyagyagyerek]

Originally Posted by spudje

I can't get the game to work (in WinUAE emulated CD32, preparing update for my CD32 HDD image). I can't do anything on the title screen. Starfield moves, but I can't move the mousepointer

The game was tested on real A500, A500+,A600 A1200 with kick1.3-4.0, on floppy and HDD with multiple chip-ast ram config.
It was also tested in UAE with multiple config. It should work, but if You can send me an UAE-config file, maybe we can get closer to a solution (possible joy port switch..) ? :S

I read here (http://www.indieretronews.com/2018/1...d-of-year.html) that it only have problems with write floppy write protection..

[spudje]

OK, I'll hope to provide the info later this week. Maybe I'll try some other WinUAE config as well.

[Steril707]

nice game!

[gyagyagyerek]

V1.3D (2019.01.10.)
http://www.electricblacksheep.com/do...sw_game_v1.zip
- check out the OPTIONS menu for 3D mode..

[spudje]

Nope, tried many configs now, all same behaviour. It loads to start screen, star field moves, pointer not. Tried swappng mouse/joystick to no avail. Same behaviour with your latest 1.3.

I have the game on HDD, delete the s, devs & libs folder (as I have my main ones on DH0), made sure though I copied the required libs to the main libs folder.

The 3d version does work though.

[DamienD]

Originally Posted by gyagyagyerek

V1.3D (2019.01.10.)
http://www.electricblacksheep.com/do...sw_game_v1.zip
- check out the OPTIONS menu for 3D mode..

Thank you for all the updates gyagyagyerek; keep up the good work

One small thing though; 3D mode is horribly slow and unplayable on an Amiga 500 (1MB Chip RAM, OCS / ECS).

Fine on an A1200 though; lucky that I emulate

...but when using an AGA chipset your bullets sometimes get "stuck" on screen for a few seconds; not a big deal, just an observation.

[amiman99]

Very well made, thanks for the effort to make the game.

[nujack]

Originally Posted by gyagyagyerek

I have Updated the download link with a possible fix (in ShipMovement/Timing). Please try again!

Thank you for the update that fix the problem. Latest version is playable again and has no longer slowdowns.

[gyagyagyerek]

Originally Posted by spudje

Nope, tried many configs now, all same behaviour. It loads to start screen, star field moves, pointer not. Tried swappng mouse/joystick to no avail. Same behaviour with your latest 1.3.

I have the game on HDD, delete the s, devs & libs folder (as I have my main ones on DH0), made sure though I copied the required libs to the main libs folder.

The 3d version does work though.

If you don't need it necessery, please turn off the "install virttual mouse driver" in UAE Settings/Host/Game ports menu.

In the next update the pointer will movable with joystick as well.

[gyagyagyerek]

I've updated the DOWNLOAD link again.

fix:
- The pointer arrow is movable with joystick.
- 3D versions are a bit faster..

mod:
Becouse of (1mb) chipram and ADF limitations the 3d vector version(s) of the game has been moved to separate ADFs. Each of them has it's own source code within.

So there is a:
- sw_game_20190113_2D.adf is the "original" Star (Dust)Wars game.
- sw_game_20190113_3D_Color.adf is a 3D vector version based on the same game.
- sw_game_20190113_3D_BW.adf the same as the previous, but slightly faster becouse it has no colors.
- sw_game_20190113_3D_Anaglyph.adf is a stereoscopic versoin. It is playable through Anaglyph (red/blue or red/green) glasses.

Unforunately for playing the 3d versions you still need at least an AGA machine.

[DamienD]

Thanks gyagyagyerek

...though personally I'll probably just stick with the original 2D version.

[NeoHippie2016]

@gyagyagyerek: wow, so many Versions! Can't wait to try them all...

[zzbylu]

Gameplay:
[ Show youtube player ]

[spudje]

Thanks a lot. it works now! The reason I have that virtual mouse is because I tend to work have my WinUAE running on a PC in my "mancave" but do some wotrk on it on my laptop in de living room via VNC. So I guess in the end it would have worked when I transferred the CF to my real CD32.

On minor thing: Name entering for high score cannot not be filled/skipped without a keyboard. So CD32 people have to reset here everytime.

[gyagyagyerek]

Just a video from the 3D Anaglyph version:
[ Show youtube player ]

and the 3D Vector version:
[ Show youtube player ]

It is created purely because of curiosity!
It is terrible slow on almost every Hardwere, but there is a possibility to make such things..
Unfortunately Amos is not a 3D engine and Amos3D is a nightmare (for me), specially for modelling..

[gyagyagyerek]

Originally Posted by spudje

Thanks a lot. it works now! The reason I have that virtual mouse is because I tend to work have my WinUAE running on a PC in my "mancave" but do some wotrk on it on my laptop in de living room via VNC. So I guess in the end it would have worked when I transferred the CF to my real CD32.

On minor thing: Name entering for high score cannot not be filled/skipped without a keyboard. So CD32 people have to reset here everytime.

I don't know how to check write protection in AMOS without running into some trouble with some popup windows or necessary keyboard interaction.
..so if it is an acceptable solution there is also a CD32 version in the zip file that put your points to the highscore under the name "Player" but not save/write it to the disk.

[saimon69]

I know you have used the sample in the background due to short memory but in case someone comes with a music how much RAM you have?

[gyagyagyerek]

Yes, it's a repetitive sample in the battle.mod file you find on the ADF. It is 46322 byte 4 channel SoundTracker file. Simply overwrite it if you want to change it.
From Chip ram perspective the mod has to be 50000-100000 bytes if it is an Amiga with 1MB ChipRam. If it has 2MB ChipRam, than offcourse the module can be bigger than 1MB.
From disk space perspectiveIf you don't need it, you can delete the .Amos file to free up some space on the floppy, but if you copy it to a hdd than it can be bigger.