Aurora 4x
C# Aurora => C# Bug Reports => Topic started by: IanD on May 03, 2020, 05:30:54 AM
-
Not a game breaker just annoying. I was updating and enlarging an existing design. First I copied the existing design, enlarged it by 5000 tons, then renamed it and went to change the class designation from cruiser to heavy cruiser. I then got:-
Function #235: Cannot add or insert the item 'Hawk Mk2' in more than one place. You must first remove it from its current location or clone it. Parameter name: node.
The new design was then deleted
But I had cloned it and renamed it. I get the same result if I don't rename it but just clone it (copy design) with or without design changes. Most importantly I was not trying to move Hawk Mk2 but a renamed clone.
Game version 1.9.3
-
I've always done Copy Design=>Change Class->Rename->Modify without problems, so it might be an order of operations issue.
-
After the next turn increment I got a Function #1420 An object reference not set to the instance of an object.
All three new designs I had attempted to move then turned up in the correct location. Not a clue what was going on or why. The only other action was the discovery of a new system (Gliese 1), but I doubt that had anything to do with it.
Edit
I tried copy then change class but got the same result.
Edit 2
I tried moving one of the designs from Heavy Cruiser to Strike cruiser and got the Function #235 again. After a turn increment The moved design appeared in the new class. This time no other Function appeared.
-
I had a similar bug in 1.8.0 but Steve couldn't reproduce it.
I had some trouble getting the exact circumstances to reproduce it, then when Steve asked for more information it showed up with a different class.
I had a hunch that it was because I was using a non-standard hull type.
If you refresh the class list by ticking or unticking either of the checkboxes at the bottom then the ship should re-appear.
-
It specifically has to do with changing the designation of a class that already existed. It goes like this:
-Open class designer.
-Make new class.
-Close and re-open designer.
-Change designation of the new class.
-Error ensues.
The class is actually still there, if you reload the designer again then you will see it.
I reported it a couple times already but its been ignored so far (to be fair its pretty minor, it doesn't actually delete the class).
The other thing is the error will refer to the preceding class (whichever is directly above it in the list), rather than the one you are actually modifying.