Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
A jam submission

Orbit Salvager (CGA graphics)View game page

A game for Windows, Linux and DOS. Survive while salvaging cloth dryers and making fuel out of asteroids!
Submitted by raphnet (@raphnetlabs) — 4 days, 19 hours before the deadline
Add to collection

Play game

Orbit Salvager (CGA graphics)'s itch.io page

Is your game for DOS or inspired by a game from the DOS-era of PC gaming?
It is a game made for DOS, coded in x86 assembly and using CGA graphics.

Leave a comment

Log in with itch.io to leave a comment.

Comments

Submitted

The fire effect when crashing is quite convincing, good job!

Also, the artwork / animation of the little person in the spaceship looks really good. Wonder which tune they are rocking to? (obligatory "please add adlib music" nag)

Is the planet surrounded by a solid sphere? I bounce off the "top" of the screen as if there was such a thing.

The hitbox for the asteroids is quite small. Couldn't the little person salvage cloth dryers and build a kind of "shield" out of the salvaged ones, so that hitting an asteroid reduces the shield? (e.g. 1 shield added per clothes dryer salvaged, 1 shield removed per asteroid hitting the ship).

Also, my newfangled VGA card is heavly unused by this, hope there will be a mission disk that adds VGA support, a speech pack and adlib music ;)

Submitted

At least in DOSBox, I noticed that after exiting the game, the keyboard isn't working anymore. Could it be that the keyboard interrupt hooking isn't properly reversed at exit? Also, when launching from a small launcher program, the games never properly returns (could it be that there are other interrupts that are hooked by the game, thereby potentially messing up the caller's stack)? Other games work fine with the launcher (using DOS int 0x10, 0x4b). When running in DOSBox Debugger and launching from my launcher, after exiting something like this is printed:

...
CPU:Illegal/Unhandled opcode 0F00
CPU:Illegal Unhandled Interrupt Called 6
CPU:Illegal/Unhandled opcode 0F00
CPU:Illegal Unhandled Interrupt Called 6
...

In case of not using a launcher (running ORBSALV.EXE directly from DOSBox), I don't see these, but the keyboard stops working.