Unfamiliar error transferring commodities to Fleet Carrier

Never seen this before myself, just checking if it's familiar to and logged by others (so I can either upvote or log a new).
Colonisation efforts have dramatically increased my activities transferring commodities to Fleet Carriers. I am occasionally, maybe every tenth transfer or so (further testing required to confirm) encountering a $ error and the transfer fails.
Pretty unpredictable problem and a subsequent repeat of the same transfer attempt succeeds.

Just me?
1743356457170.png
 
Never seen yours before, but I have on occasion managed to overflow a transfer from carrier to Cutter (i.e. 785/784) which I always undo. Could be a lag/desync issue.
 
It's the servers, I've seen this. Your ship is "docked" but it's not really docked yet. So you rush to the inventory screen and try to transfer cargo and get this error. Then sometime later your ship ACTUALLY docks, and things work as normally.
 
It's the servers, I've seen this. Your ship is "docked" but it's not really docked yet. So you rush to the inventory screen and try to transfer cargo and get this error. Then sometime later your ship ACTUALLY docks, and things work as normally.
You're bang on the money Commander!
I noticed today that there can be a kinda grey area where you're docked on the FC, but not quite. During this period the option to transfer cargo is available, but attempting to transfer will result in the
1743773212373.jpeg
Sometimes the completion of the extended docking activity can be witnessed as a significant (delayed) clunking lockdown.

Workaround, as in so many walks of life, is a to have a little patience :cool:
 
It's the servers, I've seen this. Your ship is "docked" but it's not really docked yet. So you rush to the inventory screen and try to transfer cargo and get this error. Then sometime later your ship ACTUALLY docks, and things work as normally.
:unsure: I am not quite sure. Yesterday, while suffering the problem, I could make some transfers (every 1T transfers I tried worked), but most of them didn't work resulting in the $ error. It was an intermittent error.

If it was a "docking" problem, I shouldn't be able to make any transfer from the beginning until I was actually docked, and then all transfers should work. It was not the case.
 
:unsure: I am not quite sure. Yesterday, while suffering the problem, I could make some transfers (every 1T transfers I tried worked), but most of them didn't work resulting in the $ error. It was an intermittent error.

If it was a "docking" problem, I shouldn't be able to make any transfer from the beginning until I was actually docked, and then all transfers should work. It was not the case.
Just when you think it's 'some progress made'. 😢

Please add your experience (which appears to contradict mine) to the ticket if you can spare the time, ta.
 
We're definitely at home to Mr. $ Error today, popping up reliably on first cargo transfer attempt.
Does seem to coincide with glitchy game performance, whether that be due to network, server load or an unhelpful prevailing wind direction :cry:
 
Perhaps a good new: In Trailblazers Update 3 (Guatamaya Corsair Update) that will be released tomorrow, it is announced this bug fix:
  • Fixed issues with cargo instancing
Cross your fingers!
 
Bad news then... :rolleyes:

I haven't tried yet as I am fighting in the current CG. When finished I will try, but surely I will get the same as you.
 
I have returned to mining for the last CG.

And I have confirmed the $ problem is still here :(

Most of the related reported issues in the Issue Tracker have expired before Frontier has taken any action to solve it.

But many other related issues have been opened. I have just signed for a new one with the most number of reports: The error is "$" when transferring cargo from the hold of a fleet carrier to the hold of a ship

I don't know why people open new issues instead of signing for just one to be noticeable for Frontier... :oops:
 
Back
Top Bottom