#2939 is a small function for calculating the orbits of companion stars. This function runs fairly often, so looks like an intermittent bug. The only objects referenced are the Star Type and the Parent Star, so perhaps the function is running when the latter doesn't exist - maybe for the primary. I'll add a check for that.Thank you for investigating!
BTW I've just generated about 50 systems in a random stars game without the bug appearing, so it does seem fairly rare. Hard to fix though unless I can reproduce it. I'll keep trying.
I just created 90 systems without issue, using the "Create System" button, so I'd agree it's relatively rare.
It seems decidedly less rare when using "Create Habitable", occurring in an average of 4-5 created systems, up to a maximum in my testing of 12 - I assume this is due to a large number of systems being created and discarded behind the scenes to find viable habitable targets.
#2939 is a small function for calculating the orbits of companion stars. This function runs fairly often, so looks like an intermittent bug. The only objects referenced are the Star Type and the Parent Star, so perhaps the function is running when the latter doesn't exist - maybe for the primary. I'll add a check for that.Thank you for investigating!
BTW I've just generated about 50 systems in a random stars game without the bug appearing, so it does seem fairly rare. Hard to fix though unless I can reproduce it. I'll keep trying.
First chance to play with 2.2.1, decided to test out the new "Create Habitable" feature.
After generating a number of systems, I'd say 10 or so, I clicked "Create Habitable" as usual and received the following error:
2.2.1 Function #2939: Object reference not set to an instance of an object.
This error message disappeared after clicking "Ok", but resulted in Aurora freezing, requiring me to force close it.
This occurred without any modifications or alterations to anything, using a newly created, non-real stars game. Just activated SM and started clicking "Create Habitable".
I then attempted to replicate the issue. Upon relaunching Aurora, it recurred on the second habitable system created, with the same symptoms as before. Replication is simple: launch the game, start a new game with Known Stars turned OFF, turn on SM, start clicking the appropriate button until it happens.
EDIT 1: To reflect the fact that this issue happened in a newly created, non-real stars game.
EDIT 2: I just had the same error (Function #2939) occur when attempting to create a new game on a freshly unzipped, clean 2.2.0 database. The only setting altered was to deselect "Known Stars"
EDIT 3: It also occurs when turning on SM and clicking "Create System". Not every time a system is created, but eventually. I suspect this is related to the similar bug that was discovered in the previously released version involving non-Known Stars game and system creation, it's just too similar.
Should the ground forces window update itself after next time increment?
I had the Ground Force window opened to monitor the replacement process. I done 1 day increments 12 times and saw now changes in my formations. Once I closed the Ground Force window and open it again. I noticed than replacement took its place already.
I do not see any events in the log about replacement take place. Is it ok?
Bit of an issue with 2.2.1:
GU Copy + Upgrade creates multiple copies of identical items. I have a company HQ that I use in all my company sized formations. Using the copy + upgrade button on each company sized formation created 7 copies of that HQ, all identical.
Perhaps there could be a check to see if something with that exact design already exists? If so, don't duplicate?
EDIT:
To complicate matters further, it creates a new series for each item it duplicates, regardless of the fact that I already had series for each GU.
SJW: Fixed for v.2.2.2
Hi Steve, I am asking just to understand the deadlines as I am playing a little bit as everyone else but not playing any major campaign.
Are you going to release the 2.2.2 soon (today or in the weekend for example) or will it be a long term update (months) and will it contain the fixes that require the database update?
Thank you
Dani
