EDIT: It turned out, the issue wasn't deleted. It was a GitHub quirks hiding my account.
Binary aborts immediately after "New game" (#335)
lwho commented 12 days ago wrote: Self-compiled binary from master (6cdec84) on Ubuntu 12.04.4 LTS 64 bits.
Startup sequence runs properly, but 1 second after "New game" it aborts (saw airport buildings for a very short time).
Never happened with Pioneer, so probably not an upstream bug.
[backtrace, stderr.txt, opengl.txt stripped]
lwho commented 3 days ago wrote: And now it's not even compiling anymore:
[compiler errors stripped]
Half-Shot commented 14 hours ago wrote: I'm getting exactly the same issue with Alpha4 from a build from the devs.
Bug Report:
http://forum.paragongame.com/index.php? ... -new-game/
lwho commented 4 hours ago wrote: Thanks for the notice. Seems the devs are ignoring their bug tracker.
lwho commented 4 hours ago wrote: Looking at your gists, that doesn't look like the same issue. I'm getting a GL_STACK_UNDERFLOW directly after game start. Your log seems to indicate, that the game ran for some time.
You seem to have AMD graphics hardware (proprietary or open source drivers?), I'm using an Nvidia graphics card with their proprietary drivers (see my opengl.txt above).
Salwan commented 4 hours ago wrote: Hi, I'm almost done syncing latest pioneer changes with our changes in sync branch. Did you run into these issues when testing the binary paragon alpha 4 release (the one from the website) or directly compiling from source? Keep in mind that since alpha4 paragon depends on a different set of assets that are not part of the opensource repository so compiling and running it on pioneer's assets may lead to crashing on new game though I'm curious what would cause it. I did however notice the GL_STACK_OVERFLOW assert when running in debug and will investigate it when I have time.
lwho commented 3 hours ago wrote: As I said 6cdec84 self-compiled. 6cdec84 should be the same as Alpha 4, as far as I can tell.
What do you mean by this? I cloned MeteoricGames/pioneer including the data folder. I did not mix with any pioneerspacesim/pioneer files.Keep in mind that since alpha4 paragon depends on a different set of assets that are not part of the opensource repository so compiling and running it on pioneer's assets may lead to crashing on new game though I'm curious what would cause it.
Half-Shot commented 3 hours ago wrote: I used the binary provided by humble bundle (Alpha 4).
lwho commented 3 hours ago wrote: I just also tried with the alpha4_rc branch (so commit 698536e). Same issue.
Salwan commented 2 hours ago wrote: Aha ok to clarify Paragon's art assets (most of /data folder) are not under an opensource license anymore hence they are not part of this repository. The data folder in this repository is from an obselete release.
If you bought paragon you can simply use the data folder from our latest release (currently at alpha5) to run a freshly compiled version but we didn't merge the latest changes with master yet so use the sync branch to build an alpha 5 binary.
lwho commented 2 hours ago wrote:Just to make that clear:Aha ok to clarify Paragon's art assets (most of /data folder) are not under an opensource license anymore
[...]
If you bought paragon [...]
You take the Pioneer source code without paying us (the Pioneer authors). Then you add some artwork. And finally you want us to pay for work which was partly done by us.
vs.
We trade free development work (source code) against free artist work (Paragon's art assets). After all, that's what open source development is about: You give your competence in one area and spend your free time and in exchange you get the competence of others in other area and benefit from the time they spent.
Now which deal sounds fair for you, and which doesn't?
About two hours later, there is no sign of issue #335 anymore. It seems, they don't want to hear anything about the fairness of their business model.