v1.30 Bugs Thread

[Steve Walmsley (OP)]

You can research bombardment, autocannon, and air-to-air pods before researching fighter pods. You don't need the fighter pod research in order to put
pods onto your fighters. You can also design size 0 fighter pods. When you design the pods with size 0 they are still counted as 1 MSP.
A size 0 autocannon pod still does damage (mine says 30, not sure if this is base or not). Damage on autocannon pod does not go up with MSP size but
armor pen does, not sure if this is intentional or not. When you put these size 0 pods on a ship the game says that there is "0x fighter pod" in the
ordnance layout (probably working as intended but still weird)

Fixed research pre-requisite. Damage working as intended for AC. With no AP, damage won't matter anyway.

[Doren]

Created this fighter design and it is having the armor rounding issue when clicking "Update Armour".
You can add additional 5tons of components after clicking "Update Armour" but after revisiting the designer the size will return to be too big

Code: [Select]

Pebble class Geological Survey Craft      495 tons       13 Crew       117,9 BP       TCS 10    TH 13    EM 0
1314 km/s      Armour 1-5       Shields 0-0       HTK 2      Sensors 0/0/0/1      DCR 0      PPV 0
Maint Life 0 Years     MSP 0    AFR 98%    IFR 1,4%    1YR 52    5YR 776    Max Repair 100 MSP
Follower    Control Rating 1   
Intended Deployment Time: 4 months    Morale Check Required   

Fighter NT Engine  EP13,50 (1)    Power 13,5    Fuel Use 173,21%    Signature 13,50    Explosion 10%
Fuel Capacity 20 000 Litres    Range 4,2 billion km (37 days at full power)

Geological Survey Sensors (1)   1 Survey Points Per Hour

This design is classed as a Fighter for production, combat and planetary interaction

Also noticed that Fighter Engineering Space gives 14MSP but on some setups this gets bumped up to 15MSP when clicking the "Update Armour"
An example:

Code: [Select]

Pebble class Geological Survey Craft      495 tons       14 Crew       118,6 BP       TCS 10    TH 13    EM 0
1315 km/s      Armour 1-5       Shields 0-0       HTK 2      Sensors 0/0/0/1      DCR 0      PPV 0
Maint Life 1,38 Years     MSP 15    AFR 20%    IFR 0,3%    1YR 9    5YR 128    Max Repair 100 MSP
Follower    Control Rating 1   
Intended Deployment Time: 3 months    Morale Check Required   

Fighter NT Engine  EP13,50 (1)    Power 13,5    Fuel Use 173,21%    Signature 13,50    Explosion 10%
Fuel Capacity 15 000 Litres    Range 3,2 billion km (27 days at full power)

Geological Survey Sensors (1)   1 Survey Points Per Hour

This design is classed as a Fighter for production, combat and planetary interaction


[Steve Walmsley (OP)]

After clicking on the 30 day increment for the sixth time, I got thrown a #1414 error that doesnt go away.   Conventional start, set a civ shipyard to a 10k increase, started TN research, made a couple of ground force units, started building 2 research labs, no other changes I can think of bar ticking auto assign officers

EDIT: Tabbing through the options when starting a game or creating a race skips lines and comes back to them rather than going through every option sequentially in order

What was the error text?

[MarcAFK]

My #1414 was "object reference not set to an instance of an object"

[The_Seeker]

I started a game with Planet X enabled, it generated with a set of moons starting at #26, with the trojan asteroids erroneously having the names "Minera - Moon #1-25".   This is a naming issue only; in the system generation and display screen, the trojan asteroids (named Moon #1-25) are correctly listed as asteroids, not moons.

My #1414 was "object reference not set to an instance of an object"

Was your aurora folder set to read-only?

[nhb1986]

Thanks for the awesome work!

some input:

• Clicking on the header in GU - Unit Class Design leads to #2608 and #1838 Object reference not set to an instance of an object
  
• Clicking the Show Next Tech Button in the Part Design window is a bit sketchy, as it will reset the values chosen initially in the dropdowns.     Makes it difficult to compare 2 parts, I guess the Prototype option makes it obsolete anyway.   

Edit: Also I am too stupid to post pictures inline of the post, so I attached them instead

[MarcAFK]

My #1414 was "object reference not set to an instance of an object"

Was your aurora folder set to read-only?

Why yes it is....
Disabling that doesn't change anything though.
Edit: I Disabled read only but checking the folder again it still says read only.

[insanegame27]

After clicking on the 30 day increment for the sixth time, I got thrown a #1414 error that doesnt go away.    Conventional start, set a civ shipyard to a 10k increase, started TN research, made a couple of ground force units, started building 2 research labs, no other changes I can think of bar ticking auto assign officers

EDIT: Tabbing through the options when starting a game or creating a race skips lines and comes back to them rather than going through every option sequentially in order

What was the error text?

Function #1414: Object reference not set to an instance of an object

[The_Seeker]

My #1414 was "object reference not set to an instance of an object"

Was your aurora folder set to read-only?

Why yes it is.   .   .   .   
Disabling that doesn't change anything though.   
Edit: I Disabled read only but checking the folder again it still says read only.   

Did you play on versions 1. 0, 1. 1, or 1. 2 before extracting 1. 3 and overwriting the exe and db?  If so, make a new, clean 1. 0 folder and apply the 1. 3 patch, and see if that works.  I suspect it might be caused by the presence of the save backup files being a different version than the primary db.  I have not received any #1414 errors since applying the 1. 3 patch directly to a clean install of 1. 0. 

[Vivalas]

Man, spent forever setting a game up but I guess it's all premature right now:

Attatched a DB file, whenever the fleet that is currently at my homeworld (Imperial Fleet 01) tries to go anywhere, it starts throwing about 30 or so "Function #713: Reference not set to instance of an object" errors. This is a random stars SM start. Before this happened I was messing about with fighters and sub fleets and what not and might have broken something.


EDIT: My current game is over an old 1.00 install as well that had games on it.

[insanegame27]

My #1414 was "object reference not set to an instance of an object"

Was your aurora folder set to read-only?

Why yes it is.    .    .    .   
Disabling that doesn't change anything though.   
Edit: I Disabled read only but checking the folder again it still says read only.   

Did you play on versions 1.  0, 1.  1, or 1.  2 before extracting 1.  3 and overwriting the exe and db?  If so, make a new, clean 1.  0 folder and apply the 1.  3 patch, and see if that works.   I suspect it might be caused by the presence of the save backup files being a different version than the primary db.   I have not received any #1414 errors since applying the 1.  3 patch directly to a clean install of 1.  0. 

My 1414 was straight from 1. 0 to 1. 3, I didn't even know about the other two patches

[Toobah]

Hi!

Conditions:
Conventional start as well as new start.
Same issue both on day 0 and a couple of months in.
Have tried changing the numbers, checkboxes on the Minerals window - no difference.

Issue:
Clicked the "Open mineral survey window".
This opens the Minerals window with no rows showing in the main section.
Clicked "Search".
Popup appears notifying me: Function #2026: input string was not in a correct format. "
Nothing else seems to happen.

[The_Seeker]

My #1414 was "object reference not set to an instance of an object"

Was your aurora folder set to read-only?

Why yes it is.     .     .     .     
Disabling that doesn't change anything though.     
Edit: I Disabled read only but checking the folder again it still says read only.     

Did you play on versions 1.   0, 1.   1, or 1.   2 before extracting 1.   3 and overwriting the exe and db?  If so, make a new, clean 1.   0 folder and apply the 1.   3 patch, and see if that works.    I suspect it might be caused by the presence of the save backup files being a different version than the primary db.    I have not received any #1414 errors since applying the 1.   3 patch directly to a clean install of 1.   0.   

My 1414 was straight from 1.  0 to 1.  3, I didn't even know about the other two patches

But did you play at all or even start the game before applying the patch?

[insanegame27]

My #1414 was "object reference not set to an instance of an object"

Was your aurora folder set to read-only?

Why yes it is.      .      .      .     
Disabling that doesn't change anything though.     
Edit: I Disabled read only but checking the folder again it still says read only.     

Did you play on versions 1.    0, 1.    1, or 1.    2 before extracting 1.    3 and overwriting the exe and db?  If so, make a new, clean 1.    0 folder and apply the 1.    3 patch, and see if that works.     I suspect it might be caused by the presence of the save backup files being a different version than the primary db.     I have not received any #1414 errors since applying the 1.    3 patch directly to a clean install of 1.    0.   

My 1414 was straight from 1.   0 to 1.   3, I didn't even know about the other two patches

But did you play at all or even start the game before applying the patch?

I did start a game, yes.

[db48x]

I think controls on the right-hand edge of some windows can get cut off or wrapped to the next line if they don't fit, rendering them invisible or inaccessible. For example, the number of instant research points on the research screen:



or the exact size of a class on the class design screen: