[1.25HF1] Problem purchasing new shields after plot encourages it

[Sparky Sparkycorp]

In DeVries, after killing some Reavers, we are told about some spare Terran shield generators we are welcome to use. After following the plot beacon, I arrive at the shield-setting NPC. I can afford one of the new shields (Behemoth Mk 2) but not the other (Swift Mk 2) but it won’t let me buy the Behemoth.

Since the trade interface shows I have two default shields, I sell one on a hunch that maybe I can only fit two to my ship at once. I am still unable to but the Behemoth so I check my ship info again and it says that it is compatible with both of the new shields on sale. On a second hunch, I sell my second default shield in case I cannot mix types but I still cannot buy either new shield (since I now have enough cash for either). Finally, I try closing and reopening the conversation in case the trade window needs to refresh my ship status but that didn’t help either.

Fix: Not sure. Since I was directed to the NPC by the plot and my ship says it can use both of the new shields, there must be something going wrong somewhere.

Suggestion: Make it clear in our ship description how many shield generators we can use at once and ideally, whether we can use different types at once or not since that is unclear too.

[Sparky Sparkycorp]

Edit: Sorry, there was a mistake.

"Swift Mk 2" should have read "Dashing Shield Mk2".

[YorrickVander]

Having reached that point in the story with better shields already bought, I know that up to 1.25 you dont actually have to buy them - simply taking the convo option highlighted with a dot on the radial is enough to continue on. At least mk2 shields is useful though for later missions (sorry mini spoiler ) so that might be good time to stall and go make some extra cash to upgrade

[sandalle]

Be sure that you have enough money, some of those are in the millions of credits (e.g 3,250k)?

[Sparky Sparkycorp]

Thanks for the replies.

I checked the old save and I did have enough money for them both.

It looks like Egosoft fixed this in the patch notes for 1.30 RC3 beta yesterday

(I wasn't able to go back and confirm yet)