Hi, and thank you. 🙂

On your feedback:

1. - Nothing to support that yet (UI wise for sure), but the newnew UI which is work in progress might eventually allow that.

2. - Factions don't really mean anything apart the color of the system currently.

3. - The whole trading is heavily in need of a rebalance for sure.

Maybe you could report that crash on our Github page, so we can track it. I'll check anyway, but I'm on the art side of things, so I can't really fix anything sadly, but the actually knowledgeable guys might spot the problem right away.

Edit: I tried jumping Altair, nothing happened.

I just went back to Altair and it crashed again. Is it possible it has something to do with my own computer? Did you try landing anywhere? I was about 1.6 AU from one of the space stations when it crashed.

I wasn't able to crash it with traveling to a station there either. Tried it right now, I even kept time accel on the highest for a month or so after docking. Also tried it both on an orbital and a ground station.

If you next time experience the crash, could you post the output.txt and openGL.txt from the Pioneer directory either in your Home directory (Linux) or In your Documents (win)?

Will do. Thanks.

Also, were there any missions active at the time you experienced the crash?

Factions don't have much impact yet (although we would love to change that in the future) - except for crime.

Sometimes there was a mission, sometimes not. Sgould I just copy and paste the text of those files here?

Pasting them to pastebin.com would make it less cluttered in my opinion.

Interesting tool. Here are the files from the las time I tried to travel to Ioho system. I have Windows 10, by the way.

opengl.txt: http://pastebin.com/0sD5e1Gc

output.txt:  http://pastebin.com/uLn3fz5U

Hope this helps.

output.txt doesn't look complete, since it ends on half a word.

Do you have any modules/modds downloaded? Could be they crash your system due to stale code. Check your pioneer config folder. Consult FAQ on our wiki for how to do that.

Well, that is the file I get, maybe that is part of the problem? No, I don't have any modules/mods downloaded.

Here is a new one, same system. It also ends in the middle of a phrase.

output.txt: http://pastebin.com/fqc0qMrN

opengl.txt:  http://pastebin.com/eDn8sYzV

A truncated "output.txt" usually just means that it's hard crashed before it could flush the file access.

I'll have a quick look a those systems to see if there's anything common too them.

Aside from a couple of these being very big systems I cannot see what else they have in common. Some of them are small/normal sized, they don't all have the same stars, or number of stars. It's very strange.

Could it have to do with my own OS? Im on Windows 10, 64 bit. I installed the latest build just a week ago.

I don't think it's your OS. I'm on the same OS and build myself.

I'm trying out the downloaded version right now, rather than building it myself, but so far I'm not getting any crashes.

I just tried unistalling an reinstalling from the start and tried some systems that had previously failed and one of them now did not crash, but two others did.

Hmm, I remember there was an issue about the tradeships.lua crashing the game if a ship had too short hyperjump distance and some odd other circumstance. Can't remember how it turned up in the output.txt. It might worth a try deleting it from the data/modules directory and check if it happens without it.

I just tried that. Keeps crashing. I even tried it starting a game at Earth and then beginning at New Hope and had the same result. 

I still can't reproduce in Altair. Neither when I jump to Altair or the brown dwarf, then traveling to said town. I'll try it a number of times just to make sure. 

@PabloSanchezGrobet: maybe you could jot down the system names where you encounter this to give a bigger pool to try on?

I tried Walterar's suggestion, to see if it made a difference and it crashed both ways. But there was a difference: when I selected Altair A as hyperspace jump target, it crashed almost immediately after the jump; then I selected Altair f as target and then tried to navigate to Mruk town and it let me travel some distance before crashing, I was about 2 AU from target when it crashed, I don't know if that means anything. 

I just found out something. It only crashes when I'm at normal view (F1). I jumped to Atair A, after the jump, I selected autopilot to vicinity of Mruk town, about 120 AU distance, and then quickly went to maps view (F2) and kept it the whole journey and it didn't crash. Then I had to go back to internal view again to tell the autopilot to dock with Mruk Town, again quickly went back to orbital view and everything was allright. But after the docking, it crashed immediately after I pressed F1 to go to normal view again.

Ah now that is more interesting, ok then my advice is to start the game, go to the Options, and reduce the planet detail settings to lowest then give it another go.

Maybe create a save game somewhere close to where the game crashes so that it's quicker for you to repeat in the future?

Also how much RAM do you have and how much is the GPU allowed to use?

On a side note, if you're 120 AU out, then you've targeted the wrong star. Which leads to quite tedious game play.

I tried that, nothing worked. I even reduced all other graphics options to the lowest and deactivated other options like speed lines, compact scanner, star field density, tried different resolutions, and it still crashed. I have 4 GB RAM, and NVIDIA GeForce 630M graphics card.