Steam Tags tell you everything you need to know about this game

[Anonymous Helper]

http://steamcommunity.com/sharedfiles/filedetails/?id=1274274394

[Red Eagle LXIX]

Well, at least this game directed me to discover the Open source Pioneer ( https://pioneerspacesim.net/ ). Another game added to my collection I'll never have time to play.

Strangely Pioneer had near daily development in the time this had none. I have to wonder what kind of sham this was to be thrown on Steam in Early Access, and to not even update while they had access to essentially free development. The "release" has caused me to remove this title from my Wishlist as well as add the dev to my list of less than trusted developers (that's the nice name, I have a local name that is far more harsh and not polite enough for the forums).

Even worse and the reason these developers should never recover: They have failed to comply with the license that allowed them access to the sources they used to produce this title. This title is "released" but the current source files are not available (their last Github commit was June 21, 2016 with Alpha 12.2 ( https://github.com/MeteoricGames/pioneer )).

[STORM]

I played Pioneer....and the Elite games Pioneer derives from. They are fantastic games with solid underlying features that Jumpdrive was building on, while fast-forwarding playability to be more high-level to what most people are used to today (mainly the [transit] feature). I'm of the camp that assumptions lead to errors, but with Meteoric seems to be a dishonest set (or single set) of people.

[Dwarden]

irony of life is that most of the bugs Jumpdrive has
exists because it uses 2-4 years old code from Pioneer

and most of issues were fixed already , so just code merge could do wonders

[STORM]

Seems an old joke applies here:

==Software Development Cycle==

Programmer produces code he believes is bug-free.
Product is tested. 20 bugs are found.
Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs.
Testing department finds that five of the fixes didn't work and discovers 15 new bugs.
Repeat three times steps 3 and 4.
Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
Users find 137 new bugs.
Original programmer, having cashed his royalty check, is nowhere to be found.
Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.
Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
New CEO is brought in by board of directors. He hires a programmer to redo program from scratch.
Programmer produces code he believes is bug-free...