Duplicate Stellaris - Offspring Corvettes can't use Ion Thruster - Offspring Destroyers can upgrade/build them normally

[calmon]

Description
Offspring Corvettes can't use Ion Thruster - Offspring Destroyers can upgrade/build them normally

Game Version
v3.4.2 (7836)

What version do you use?
Steam

What expansions do you have installed?


Do you have mods enabled?
No

Please explain your issue is in as much detail as possible.
I just developed Ion Thrusters and while I'm able to use them in Corvettes and Destroyers I can't use them in my Origin Ship: Offspring Corvette (it's not in the list, just the starter thruster). I CAN use them in Offspring Destroyers.

Steps to reproduce the issue.
Develope Ion Thrusters -> try to upgrade/or build new Offspring Corvetter

Upload Attachment
File(s) attached

 

[XIIOlympia]

Description
Offspring Corvettes can't use Ion Thruster - Offspring Destroyers can upgrade/build them normally

Game Version
v3.4.2 (7836)

What version do you use?
Steam

What expansions do you have installed?


Do you have mods enabled?
No

Please explain your issue is in as much detail as possible.
I just developed Ion Thrusters and while I'm able to use them in Corvettes and Destroyers I can't use them in my Origin Ship: Offspring Corvette (it's not in the list, just the starter thruster). I CAN use them in Offspring Destroyers.

Steps to reproduce the issue.
Develope Ion Thrusters -> try to upgrade/or build new Offspring Corvetter

Upload Attachment
File(s) attached

I experienced the same thing. Cruisers are also bugged, can't confirm but battleships probably will be too. Some of the components just aren't available. Cruisers can use the tier 2 thrusters but not the tier 3 while the destroyers are able too. I want to say hyperdrive or sensors were the other one I noticed but without the game Infront of me I can't confirm.

 

[Uhlume]

Same here, it appears that the offspring ships have some issue where they can't access the whole module library.

 

[Tremnei]

Hello!

Thank you for the report!

We are aware of the issue, it has already been added to our bug database.