Author Topic: v1.8.0 Bugs Thread  (Read 53765 times)

0 Members and 1 Guest are viewing this topic.

Offline DFNewb

  • Captain
  • **********
  • D
  • Posts: 508
  • Thanked: 103 times
Re: v1.8.0 Bugs Thread Game Creation bug
« Reply #465 on: April 27, 2020, 12:15:53 PM »
Game Creation bug:

1) Click new game . . . 
2) set "earth Mineral Deposits) to any other number above 100.
3) check minerals on earth

-> its the same no matter what is set (didnt test below 100)

Current fix: space master mod to set them manually :(

Sincerely

What is the actual error and how do you know the minerals are not being generated correctly?

They should be different each game and it would be hard to tell if 80 or 120 are making a difference without checking a lot of samples.


I just set it to 1000 to test and got normal numbers.

 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11729
  • Thanked: 20681 times
Re: v1.8.0 Bugs Thread
« Reply #466 on: April 27, 2020, 12:24:27 PM »
The function number:
when loading up: #1170
once game has opened: #3060, appears 4 times
The complete error text:
1170: object cannot be converted from dbnull to other types
3060 (all 4 windows): object reference not set to an instance of an object


actual error: a whole bloody system disappeared, no bodies remain except the star
also, all of my ground units disappeared
had to reset windows for the Events window not to have the 'white screen' error anymore


The window affected: -
What you were doing at the time: opened aurora and loaded saved game
Conventional or TN start: TN
Random or Real Stars: Real Stars
Is your decimal separator a comma?: changed to period
Is the bug is easy to reproduce, intermittent or a one-off?: just look at the DB ;)
If this is a long campaign - say 75 years or longer - let me know the length of the campaign as well: ~125 years

This was another game with nulls replacing some doubles in the database.

Did you change to period for the decimal separator before you started the game?
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11729
  • Thanked: 20681 times
Re: v1.8.0 Bugs Thread
« Reply #467 on: April 27, 2020, 12:33:29 PM »
The function number - #407
The complete error text - Object reference not set to an instance of an object.
The window affected - Main window.
What you were doing at the time - Clicking 30 days.
Conventional or TN start - Conventional.
Random or Real Stars - Random.
Is your decimal separator a comma? - No a .
Is the bug is easy to reproduce, intermittent or a one-off? - Seems pretty random.
If this is a long campaign - say 75 years or longer - let me know the length of the campaign as well - 71 Years

Db attached, click 30 days and you should get the error.

Fixed. It was related to a CAG being promoted. Thanks for the db.
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11729
  • Thanked: 20681 times
Re: v1.8.0 Bugs Thread
« Reply #468 on: April 27, 2020, 12:35:58 PM »
Quote from: Steve Walmsley link=topic=10990. msg128511#msg128511 date=1587994767
Quote from: RedDagger link=topic=10990. msg128509#msg128509 date=1587994010
I took a gander at DIM_PlanetaryTerrain in the database, I think I spotted a typo.

Not sure what you are looking at, but that isn't the table from the normal Aurora. db.  Do you have some type of mod running?

I extracted the data from DIM_PlanetaryTerrain and put in a spreadsheet to see it more easily.  Here a print of the table.

Yes, understood now and fixed. Thanks.
 
The following users thanked this post: RedDagger

Offline db48x

  • Commodore
  • **********
  • d
  • Posts: 648
  • Thanked: 202 times
Re: v1.8.0 Bugs Thread
« Reply #469 on: April 27, 2020, 12:36:26 PM »
I gave an order to stabilzie a lagrange point on a planet.
Then I cancelled all orders for that fleet.

Afterwards I was unable to give the stabilize lagrange point order on that same body again.
Option simply didn't appear.

That's some very good QA testing.
 

Offline Kelewan

  • Warrant Officer, Class 2
  • ****
  • K
  • Posts: 74
  • Thanked: 18 times
Re: v1.8.0 Bugs Thread
« Reply #470 on: April 27, 2020, 12:37:16 PM »
The function number:
when loading up: #1170
once game has opened: #3060, appears 4 times
The complete error text:
1170: object cannot be converted from dbnull to other types
3060 (all 4 windows): object reference not set to an instance of an object


actual error: a whole bloody system disappeared, no bodies remain except the star
also, all of my ground units disappeared
had to reset windows for the Events window not to have the 'white screen' error anymore


The window affected: -
What you were doing at the time: opened aurora and loaded saved game
Conventional or TN start: TN
Random or Real Stars: Real Stars
Is your decimal separator a comma?: changed to period
Is the bug is easy to reproduce, intermittent or a one-off?: just look at the DB ;)
If this is a long campaign - say 75 years or longer - let me know the length of the campaign as well: ~125 years

This was another game with nulls replacing some doubles in the database.

Did you change to period for the decimal separator before you started the game?

AFAIK you can override the decimal separator, or check that it is set correct.
https://docs.microsoft.com/en-us/dotnet/api/system.globalization.numberformatinfo.numberdecimalseparator?view=netcore-3.1
Just so that you don't need to chase know issues
 
 

Offline Cobaia

  • Warrant Officer, Class 1
  • *****
  • C
  • Posts: 88
  • Thanked: 16 times
Re: v1.8.0 Bugs Thread
« Reply #471 on: April 27, 2020, 12:39:05 PM »
The function number: #917
The complete error text: Value too big or too small for Int32
The window affected: Main game window
What you were doing at the time: Refueling ships and setting Join Fleet Order
Conventional or TN start: Conventional
Random or Real Stars: Random
Is your decimal separator a comma?: Yes
Is the bug is easy to reproduce, intermittent or a one-off?: Constant
If this is a long campaign - say 75 years or longer - let me know the length of the campaign as well: 160 years long

I was able to save the game and remove the orders.  Error stopped.

 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11729
  • Thanked: 20681 times
Re: v1.8.0 Bugs Thread
« Reply #472 on: April 27, 2020, 12:47:00 PM »
Getting a lot of error messages with "Function #858: Attempted to divide by zero" when passing time on the tactical map.  Happens again when I save and restart the game.
1. 8 Random stars, TN start with 1 NPR, 10 years into the game
Using UK windows settings

DB attached

Running without problems - I think this might be have been related to a bug I fixed when you try to refuel ships without fuel capacity.
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11729
  • Thanked: 20681 times
Re: v1.8.0 Bugs Thread
« Reply #473 on: April 27, 2020, 12:55:36 PM »
AFAIK you can override the decimal separator, or check that it is set correct.
https://docs.microsoft.com/en-us/dotnet/api/system.globalization.numberformatinfo.numberdecimalseparator?view=netcore-3.1
Just so that you don't need to chase know issues
 

At the moment, the game is using the local separator, which works most of the time but fails when I populate fields that include decimal points. I also tried to interpret the content of a text field and decide which to use based on user intention, but that fails for non-decimal because the thousand separator looks like a decimal point. Finally, I could populate fields based on the local separator but that might cause confusion for people who do enter the periods even when their system is set to comma.

The problem is confusion between the two. I think the simplest thing is to force the game to use periods and inform the user when their separator is set to comma that it will cause problems in the game.
 
The following users thanked this post: VimWabbit

Offline db48x

  • Commodore
  • **********
  • d
  • Posts: 648
  • Thanked: 202 times
Re: v1.8.0 Bugs Thread
« Reply #474 on: April 27, 2020, 01:21:04 PM »
AFAIK you can override the decimal separator, or check that it is set correct.
https://docs.microsoft.com/en-us/dotnet/api/system.globalization.numberformatinfo.numberdecimalseparator?view=netcore-3.1
Just so that you don't need to chase know issues
 

At the moment, the game is using the local separator, which works most of the time but fails when I populate fields that include decimal points. I also tried to interpret the content of a text field and decide which to use based on user intention, but that fails for non-decimal because the thousand separator looks like a decimal point. Finally, I could populate fields based on the local separator but that might cause confusion for people who do enter the periods even when their system is set to comma.

The problem is confusion between the two. I think the simplest thing is to force the game to use periods and inform the user when their separator is set to comma that it will cause problems in the game.

There have been several suggestions which would be better than that alternative. If you don't want to fix it properly, you can simply set the decimal separator to whatever you want, and then you don't have to rely on the user to set it up correctly.
 

Offline Hastermain

  • Petty Officer
  • **
  • H
  • Posts: 24
Re: v1.8.0 Bugs Thread
« Reply #475 on: April 27, 2020, 01:24:00 PM »
The function number:
when loading up: #1170
once game has opened: #3060, appears 4 times
The complete error text:
1170: object cannot be converted from dbnull to other types
3060 (all 4 windows): object reference not set to an instance of an object


actual error: a whole bloody system disappeared, no bodies remain except the star
also, all of my ground units disappeared
had to reset windows for the Events window not to have the 'white screen' error anymore


The window affected: -
What you were doing at the time: opened aurora and loaded saved game
Conventional or TN start: TN
Random or Real Stars: Real Stars
Is your decimal separator a comma?: changed to period
Is the bug is easy to reproduce, intermittent or a one-off?: just look at the DB ;)
If this is a long campaign - say 75 years or longer - let me know the length of the campaign as well: ~125 years

This was another game with nulls replacing some doubles in the database.

Did you change to period for the decimal separator before you started the game?

Ever since previous versions yes, but I just realised the 10^3^x separator (you know, the 10 , 000 , 000 , 000) was set as a period, not a comma. Sorry for the waste of time! dumb mistake of mine
 

Offline Guridan

  • Leading Rate
  • *
  • G
  • Posts: 8
Re: v1.8.0 Bugs Thread
« Reply #476 on: April 27, 2020, 01:47:40 PM »
Quote from: Steve Walmsley link=topic=10990. msg128611#msg128611 date=1588009620
Quote from: Guridan link=topic=10990. msg128501#msg128501 date=1587991483
Getting a lot of error messages with "Function #858: Attempted to divide by zero" when passing time on the tactical map.   Happens again when I save and restart the game. 
1.  8 Random stars, TN start with 1 NPR, 10 years into the game
Using UK windows settings

DB attached

Running without problems - I think this might be have been related to a bug I fixed when you try to refuel ships without fuel capacity.

That could very well be, I did have some tugs moving some of my terraformers and they had a refuel scheduled on the way to their destination.
 

Offline swarm_sadist

  • Lt. Commander
  • ********
  • s
  • Posts: 263
  • Thanked: 21 times
Re: v1.8.0 Bugs Thread
« Reply #477 on: April 27, 2020, 01:55:03 PM »
If spaceports do not stack, why does more than one spaceport on a planet take more than 1 million workers?
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11729
  • Thanked: 20681 times
Re: v1.8.0 Bugs Thread
« Reply #478 on: April 27, 2020, 01:57:56 PM »
The function number: #917
The complete error text: Value too big or too small for Int32
The window affected: Main game window
What you were doing at the time: Refueling ships and setting Join Fleet Order
Conventional or TN start: Conventional
Random or Real Stars: Random
Is your decimal separator a comma?: Yes
Is the bug is easy to reproduce, intermittent or a one-off?: Constant
If this is a long campaign - say 75 years or longer - let me know the length of the campaign as well: 160 years long

I was able to save the game and remove the orders.  Error stopped.

I think it was related to movement toward a very distant target. I've changed the value I think was the problem from an integer to a double.
 
The following users thanked this post: Cobaia

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11729
  • Thanked: 20681 times
Re: v1.8.0 Bugs Thread
« Reply #479 on: April 27, 2020, 01:59:08 PM »
At the moment, the game is using the local separator, which works most of the time but fails when I populate fields that include decimal points. I also tried to interpret the content of a text field and decide which to use based on user intention, but that fails for non-decimal because the thousand separator looks like a decimal point. Finally, I could populate fields based on the local separator but that might cause confusion for people who do enter the periods even when their system is set to comma.

The problem is confusion between the two. I think the simplest thing is to force the game to use periods and inform the user when their separator is set to comma that it will cause problems in the game.

There have been several suggestions which would be better than that alternative. If you don't want to fix it properly, you can simply set the decimal separator to whatever you want, and then you don't have to rely on the user to set it up correctly.

Assuming the user types in the correct format when required, which is the biggest issue.