Things related to Scout+
Are savegames update-safe so they survive newer versions of the game?
No, unfortunately. That's the price we pay for progress. I go to a start up position then start a new game. I recreate my ship, money, equipment and statistics by using the technique at the bottom of this page.
It's almost like continuing your game. 😉
The bug hunter strikes again! This time I docked at a ground station. I saved the game then continued. I went to the bulletin board and accepted a delivery mission, clicked 'hang up' then clicked on what I thought was another delivery mission to the same place. It wasn't. I think the mission wasn't deleted from the board. When I clicked on it again I got this message;
[attachment=2591:Screenshot from 2014-05-09 2049 cropped.png]
OK = CTD
@Marcel It is an "old" bug of UI of Pioneer engine, already reported. Check this out: https://github.com/pioneerspacesim/pioneer/issues/2732
By now you must be careful not to accept any mission with activated pause.
Walterar, thank you for answering all of my inane questions.
And thanks again for Scout+.
Marcel, thanks to you, many of these questions help me to make a better game for all, your keep asking.
Ok, here's another one. I was on autopilot and on the final path entering into a hoop station. I got a warning that there was a ship nearby, then a ship exited the station and collided with me. The game stopped with this message;
[attachment=2593:Screenshot from 2014-05-14 1937.png]
OK = CTD
The point is that I had landing clearance, so the ship should not have launched until after I docked.
If I approach while a ship is departing I should get a message like,
"Clearance Denied. Ship departing. Move away from the waypoint."
Yes, that's a mistake. Tomorrow I'll post the fix pack. Thanks Marcel!
I have an idea of the origin of this, they are several. I just download your last zips and I will see them.
OK, I hope it helps. A small update; I loaded the saved game without the postal mission at NN 3140. I proceeded to Yuan Orbiter, docked and saved the game and it worked.
I could send you my saved games so you could examine them for signs of corruption. 😉 I don't know if that pun survived its journey through Google translate. I could also send you the contents of my mods folder so you could use the saved games. That would only be if you want to pursue this further. I have another possibility. I was in the bad habit of saving the game, then pressing Alt-F4 to quit. I would get a message from Ubuntu giving me the option to force quit, then after a few seconds the message disappeared. I wonder if that could corrupt the last game I saved. I'll exit the game and quit using the buttons from now on, and if I see this happen in the next version I'll let you know.
Bug report for G18; I've noticed that when I take an exploration mission to an uninhabited system, jump to the system, then look at the system views the game crashes. When I go to the same system without taking the mission I can look at the system views without a crash. I've tried it with two uninhabited systems that had exploration missions on the bulletin board and the result is the same for both. I think I see the line in output.txt that describes it.
pioneersp: SystemInfoView.cpp virtual void SystemInfoView Assertion `NeedsRefresh() == REFRESH_NONE' failed.
Here's the output file for one of them.
The other one was at Zeta Tucanae i.
Here's something odd. I got back from Zeta Tucanae. I completed the mission by not looking at the system view. There was another mapping mission on the board. This one was to Gliese 831 A,B d4. I took it, jumped, and after a fight, saved then looked at the system view and it worked fine. I was able to set my navigation target and had no crashes. I don't know if this is related to the issue you mentioned. There are no star ports in these systems. Do you think it may be caused by my spawning a ship with console.lua before I first took off?
@Marcel: On which star systems did that happen (including sector coordinates please, names are not unique)? Did you activate the system info view for another system (or the same system) before (if so which one)?
I don't think that whether there was an exploration mission for this system should make any difference for this assertion. But, which systems were shown directly before the assertion might be relevant.
The systems were Zeta Tucanae (0,-2,-4) and NN 3517 (2,2,-1). They were both on the same bulletin board in the savegame. That may be a clue. The first time I went to Zeta Tucanae I searched for the system and viewed it. Subsequently, while testing, I just went to the system. If I accepted the mission, the game would CTD when I tried to access the system view. If I just went there without accepting the mission I could access the system views without a crash. NN 3517 displayed the same behavior. I loaded a stock pioneer-20140508-linux64, started from Earth and did not experience a crash at Zeta Tucanae.
I'm really enjoying G18. There are two minor issues I've seen. The first is the rotation dampers are often off when I start a saved game, but they were on when I saved the game. It's a minor thing and I've learned to check the status of my ship before continuing.
The second concerns the skybox. The mods by Vuzz and pebblegarden seem to be incompatible in G18. I can only use one or the other. I tried renaming them to see if the alphabetical sorting had changed but to no avail. I could use them both together in G17. Vuzz's skybox for Sol would overwrite pebblegarden's.
I don't know if either of these issues are related to Scout+, just FYI.
? this skybox is, in fact, not a work for pioneer or Scout +, but a project for Genesia ...
Exactly, in the current resolution it is not compatible with Pioneer Scout Plus