Author Topic: v1.9.3 Bugs Thread  (Read 30611 times)

0 Members and 2 Guests are viewing this topic.

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11743
  • Thanked: 20757 times
Re: v1.9.3 Bugs Thread
« Reply #165 on: May 02, 2020, 01:37:23 PM »
There is something wrong with passive electronic sensors. When designing an electronic sensor with size 0.8 or smaller, there is no range difference when choosing either sensor sensitivity 5 or 6. The range is exactly the same. When choosing sensor size 0.2, there is no difference between sensitivity 5,6, or 8. When choosing size 0.1, all sensor ranges are zero. I suspect it has to do with integer rounding, as all sensors with the same cost have exactly the same range.

Decimal separator is a dot btw.

Passive sensors having integer rounding is working as intended. However, now you have mentioned it I don't remember why I did it :)

Active can be fractional so I have changed passive to be the same.
 
The following users thanked this post: SpikeTheHobbitMage

Offline db48x

  • Commodore
  • **********
  • d
  • Posts: 649
  • Thanked: 202 times
Re: v1.9.3 Bugs Thread
« Reply #166 on: May 02, 2020, 01:41:36 PM »
2) Some (but not all) of the entries in "Aurora Forum Members" are duplicated (such as my own name).
2) You will need to speak to whoever it was that created the list. Happy to re-import.

Steve, you can do this with an SQL query:

Code: [Select]
DELETE
FROM DIM_NamingTheme
WHERE  NameThemeID = 389 AND
       rowid NOT IN
       (SELECT min(rowid)
        FROM  DIM_NamingTheme
        WHERE NameThemeID = 389
        GROUP  BY Name);
« Last Edit: May 02, 2020, 01:46:49 PM by db48x »
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11743
  • Thanked: 20757 times
Re: v1.9.3 Bugs Thread
« Reply #167 on: May 02, 2020, 01:45:54 PM »
When you scrap the last ship in a Task Force, the whole task force is deleted.

That is working as intended. The TF wouldn't be deleted if anything else needed the TF (like SY tasks or movement destination).
 

Offline Inglonias

  • Lieutenant
  • *******
  • I
  • Posts: 170
  • Thanked: 69 times
Re: v1.9.3 Bugs Thread
« Reply #168 on: May 02, 2020, 01:51:10 PM »
Error is "Function #242: Object reference not set to instance of an object"
Screen affected is the class design window.

The error appears to occur when I expand and collapse categories of components in the Race Components tab, but doesn't seem to negatively affect my game (as far as I can tell, anyhow)
s]EDIT: The error began appearing when I marked the "Nautilus Co. 10.4 GW Pressurized Water Reactor" as obsolete from the class design screen (I used the Obso Comp button). Marking it as obsolete from the tech report window also results in this error. I hope that helps.[/s]

EDIT 2: Disregard the above. Error still occurs in class design screen even if that component is not obsolete.

I can't reproduce with your database.

#242 is double-click on component treeview. Does this affect every component when you double-click or only specific components?  If you click on anything but a component the function immediately exits

That explains it. It seems the class design window is treating my double clicking on the categories as clicking on components for some reason. Glad my game isn't screwed up somehow. Thanks for the info.

It doesn't affect every category, but there's no rhyme or reason to the categories that are actually affected.
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11743
  • Thanked: 20757 times
Re: v1.9.3 Bugs Thread
« Reply #169 on: May 02, 2020, 01:51:38 PM »
I have seen this error multiple times in previous versions, both in my own games and here in the various forum bug threads, but I managed to reproduce it consistently. It has to do with relabelling copies of classes as a different class type.

Error Number: #235
Error Message:  Cannot add or insert the item Covenant (P) in more than one place. You must first remove it from its current location or clone it. parameter node: none.
Affected Window: Class design
Steps to reproduce: In the attached DB, choose the Jump Destroyer "Covenant" class. Choose copy class. In the drop down menu in the top, reassign the copy as a destroyer escort.
Other info:
Version: 1.9.3, started in 1.9.0, no mods
Decimal separator: dot
Conventional start, Real stars, 31yr campaign

Using the attached DB, I selected the Jump Destroyer "Covenant" class. I clicked copy class. I selected destroyer escort as a new hull type for the copied class. There were no errors.

There must be something specific to your installation that is causing the problem. In fact, given other reported errors with dropdown and treeviews, I am started to wonder if this is an issue with .NET.

Do you happen to know what version of .NET frameworks in on your PC?
 

Offline Inglonias

  • Lieutenant
  • *******
  • I
  • Posts: 170
  • Thanked: 69 times
Re: v1.9.3 Bugs Thread
« Reply #170 on: May 02, 2020, 01:55:34 PM »
I have seen this error multiple times in previous versions, both in my own games and here in the various forum bug threads, but I managed to reproduce it consistently. It has to do with relabelling copies of classes as a different class type.

Error Number: #235
Error Message:  Cannot add or insert the item Covenant (P) in more than one place. You must first remove it from its current location or clone it. parameter node: none.
Affected Window: Class design
Steps to reproduce: In the attached DB, choose the Jump Destroyer "Covenant" class. Choose copy class. In the drop down menu in the top, reassign the copy as a destroyer escort.
Other info:
Version: 1.9.3, started in 1.9.0, no mods
Decimal separator: dot
Conventional start, Real stars, 31yr campaign

Using the attached DB, I selected the Jump Destroyer "Covenant" class. I clicked copy class. I selected destroyer escort as a new hull type for the copied class. There were no errors.

There must be something specific to your installation that is causing the problem. In fact, given other reported errors with dropdown and treeviews, I am started to wonder if this is an issue with .NET.

Do you happen to know what version of .NET frameworks in on your PC?

If RegEdit is to be believed, 4.8.03752.

I retrieved this info from the registry (press Win + R, type "regedit.exe") at the following location: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\1033\Version
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11743
  • Thanked: 20757 times
Re: v1.9.3 Bugs Thread
« Reply #171 on: May 02, 2020, 01:59:35 PM »
I have seen this error multiple times in previous versions, both in my own games and here in the various forum bug threads, but I managed to reproduce it consistently. It has to do with relabelling copies of classes as a different class type.

Error Number: #235
Error Message:  Cannot add or insert the item Covenant (P) in more than one place. You must first remove it from its current location or clone it. parameter node: none.
Affected Window: Class design
Steps to reproduce: In the attached DB, choose the Jump Destroyer "Covenant" class. Choose copy class. In the drop down menu in the top, reassign the copy as a destroyer escort.
Other info:
Version: 1.9.3, started in 1.9.0, no mods
Decimal separator: dot
Conventional start, Real stars, 31yr campaign

Using the attached DB, I selected the Jump Destroyer "Covenant" class. I clicked copy class. I selected destroyer escort as a new hull type for the copied class. There were no errors.

There must be something specific to your installation that is causing the problem. In fact, given other reported errors with dropdown and treeviews, I am started to wonder if this is an issue with .NET.

Do you happen to know what version of .NET frameworks in on your PC?

If RegEdit is to be believed, 4.8.03752.

I retrieved this info from the registry (press Win + R, type "regedit.exe") at the following location: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\1033\Version

What other versions are installed - I just made a new thread on this topic
 

Offline Haji

  • Captain
  • **********
  • Posts: 442
  • Thanked: 53 times
Re: v1.9.3 Bugs Thread
« Reply #172 on: May 02, 2020, 02:07:10 PM »
Sometimes when I switch to another race with SM mode on in the tactical screen I get errors "Function #2947: The given key was no present in the dictionary". The reason I'm not attaching the DB is that the problem is solved if I save, leave and re-start the game and I cannot notice any problems with the game, such as missing stuff. Right now more annoying than game breaking.
The only other thing I can add it usually happens when I've played for a while and from what I can remember it is always a different race that is affected by the errors.
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11743
  • Thanked: 20757 times
Re: v1.9.3 Bugs Thread
« Reply #173 on: May 02, 2020, 02:08:20 PM »
I am getting no log entry for a fuel ship when it has low fuel. Only got a warning when it reached 0. Maybe some kind of check that sends a warning if the distance it has to take would lead to fuel depletion... .

I'll add a low fuel warning for tankers when they fall below 20% minimum fuel rather than the 20% of total fuel for non-tankers
 
The following users thanked this post: SpikeTheHobbitMage

Offline ChubbyPitbull

  • Gold Supporter
  • Sub-Lieutenant
  • *****
  • C
  • Posts: 143
  • Thanked: 32 times
  • 2023 Supporter 2023 Supporter : Supporter of the forum in 2023
    2024 Supporter 2024 Supporter : Supporter of the forum for 2024
Re: v1.9.3 Bugs Thread
« Reply #174 on: May 02, 2020, 02:11:13 PM »
I've been geo surveying a multi star system that had previously been grav surveyed. I was using the Bolzano-class Exploration Cruiser "Tigre" who had Primary Standing order "Survey Next Five System Bodies" and Secondary Standing Order "Survey Next Three System Locations." The Tigre finished geo surveying the planets and asteroids around Aachen-A and returned to Earth to refuel and overhaul. I sent the Tigre back to the Aachen system after overhaul was complete as the planets around Aachen-B and Aachen-C still needed Geo surveying. However, after jumping through the jump point, the Tigre constantly reports. "CX Tigre is unable to carry out its primary standing order (Survey Next Five System Bodies) or its secondary standing order (Sruvey Next Three System Locations)."

I thought this may be due to potential range concerns; at early game my Bolzano-class explorers only have 30.1b km range, and the orbital period of Aachen-B is 13.8b km. Conditional orders would send the Tigre back to refuel. Is the game looking ahead and refusing to attempt surveys because of fuel concerns?

Save attached. 

Screnshots:
Off-Topic: show

Ship status:


Aachen System Map


Aachen-A Detail:


Aachen-B Detail:

 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11743
  • Thanked: 20757 times
Re: v1.9.3 Bugs Thread
« Reply #175 on: May 02, 2020, 02:11:42 PM »
Sometimes when I switch to another race with SM mode on in the tactical screen I get errors "Function #2947: The given key was no present in the dictionary". The reason I'm not attaching the DB is that the problem is solved if I save, leave and re-start the game and I cannot notice any problems with the game, such as missing stuff. Right now more annoying than game breaking.
The only other thing I can add it usually happens when I've played for a while and from what I can remember it is always a different race that is affected by the errors.

That is the function that returns the name of a star. The only key involved is the system ID. I've added code to return error text instead of star name when this happens.
 
The following users thanked this post: Haji

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11743
  • Thanked: 20757 times
Re: v1.9.3 Bugs Thread
« Reply #176 on: May 02, 2020, 02:13:56 PM »
I've been geo surveying a multi star system that had previously been grav surveyed. I was using the Bolzano-class Exploration Cruiser "Tigre" who had Primary Standing order "Survey Next Five System Bodies" and Secondary Standing Order "Survey Next Three System Locations." The Tigre finished geo surveying the planets and asteroids around Aachen-A and returned to Earth to refuel and overhaul. I sent the Tigre back to the Aachen system after overhaul was complete as the planets around Aachen-B and Aachen-C still needed Geo surveying. However, after jumping through the jump point, the Tigre constantly reports. "CX Tigre is unable to carry out its primary standing order (Survey Next Five System Bodies) or its secondary standing order (Sruvey Next Three System Locations)."

I thought this may be due to potential range concerns; at early game my Bolzano-class explorers only have 30.1b km range, and the orbital period of Aachen-B is 13.8b km. Conditional orders would send the Tigre back to refuel. Is the game looking ahead and refusing to attempt surveys because of fuel concerns?

There is a max ten billion range on that order type. Try ordering the ship to travel to the distant secondary component, then the standing order will work.
 

Offline Suxxor

  • Petty Officer
  • **
  • S
  • Posts: 25
  • Thanked: 1 times
Re: v1.9.3 Bugs Thread
« Reply #177 on: May 02, 2020, 02:14:41 PM »
My PC lost power while save was in progress. All scientists and research progress are lost. I suggest saving creates new file instead of rewriting existing one. Replace/delete files after the save completes.
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11743
  • Thanked: 20757 times
Re: v1.9.3 Bugs Thread
« Reply #178 on: May 02, 2020, 02:15:53 PM »
V 1.9.3, just using the Federated Nations game as a springboard for my own efforts.

No error text, I just noticed the retirement of Commander Georg Baumgarten, despite having a presumably rather important assignment in command of a survey ship. I was surprised as I didn't think that officers who were currently assigned were supposed to be able to retire. Was I just unlucky?

DB attached.

That is WAI. C# has a different set of rules for commander careers.
http://aurora2.pentarch.org/index.php?topic=8495.msg104038#msg104038
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11743
  • Thanked: 20757 times
Re: v1.9.3 Bugs Thread
« Reply #179 on: May 02, 2020, 02:16:54 PM »
My PC lost power while save was in progress. All scientists and research progress are lost. I suggest saving creates new file instead of rewriting existing one. Replace/delete files after the save completes.

It does create a new file. See this stickied topic.

http://aurora2.pentarch.org/index.php?topic=11078.0