I wanted to check if a 2½ year old description of in-game despawning mechanic is still accurate - anyone know?
I had my ship despawn at a mining station while I was looking for masks a couple of days ago, and went looking for solutions. This Spectrum post from a couple of years ago has what sounds like a fairly well-researched answer: PSA: Ship Despawn Prevention - General - Star Citizen - Spectrum v5.13.2 (robertsspaceindustries.com). But it's obviously from several patches ago, and maybe CIG fixed/changed some of this since?
TL;DR: That article says a 1 hour timer starts when you get your ships out, and before that hour is up, to avoid a despawn, you should take your ship(s) and/or vehicle(s) to a station or landing zone and either:
1. obstruct the landing area and making your ship impounded. Works best with R&R and stations above the planets. Impounding saves the ship state - the vehicles inside the ship, cargo, boxes, the amount of fuel and so on will be saved. You can pay the 500 aUEC fine or wait 10 minutes to get the ship back for free - it doesn't matter. The despawn timer starts again when you press the Retrieve button at the terminal. This is the only way to reset the despawn timer aside from claiming your ship.
2. Apparently, landing normally and waiting to let the ship get stored automatically (when you exceed the alloted time limit) also resets the timer
Storing the ship manually (landing ship at the proper pad and calling another ship to make the original get stored) is NOT the same thing and it does NOT reset the despawn timer.
Apparently, at least back then, little else you do with, near or in your ship has much effect on when it despawns, though being near a ship which has been 'marked for despawn' may delay the despawn until you leave its immediate vicinity, or (possibly) use quantum travel. When you do (when you're not looking?), it will despawn. The OP Tyrtaeus says logging out pauses the timer until you log in again, but that's not much of a solution.
There's lots more detail in the post - worth a read assuming it's still accurate, which I think it could well be.
I have not independently tested this theory in 3.17. I thought it was useful enough to share, to see if anyone here can confirm/contradict.
I had my ship despawn at a mining station while I was looking for masks a couple of days ago, and went looking for solutions. This Spectrum post from a couple of years ago has what sounds like a fairly well-researched answer: PSA: Ship Despawn Prevention - General - Star Citizen - Spectrum v5.13.2 (robertsspaceindustries.com). But it's obviously from several patches ago, and maybe CIG fixed/changed some of this since?
TL;DR: That article says a 1 hour timer starts when you get your ships out, and before that hour is up, to avoid a despawn, you should take your ship(s) and/or vehicle(s) to a station or landing zone and either:
1. obstruct the landing area and making your ship impounded. Works best with R&R and stations above the planets. Impounding saves the ship state - the vehicles inside the ship, cargo, boxes, the amount of fuel and so on will be saved. You can pay the 500 aUEC fine or wait 10 minutes to get the ship back for free - it doesn't matter. The despawn timer starts again when you press the Retrieve button at the terminal. This is the only way to reset the despawn timer aside from claiming your ship.
2. Apparently, landing normally and waiting to let the ship get stored automatically (when you exceed the alloted time limit) also resets the timer
Storing the ship manually (landing ship at the proper pad and calling another ship to make the original get stored) is NOT the same thing and it does NOT reset the despawn timer.
Apparently, at least back then, little else you do with, near or in your ship has much effect on when it despawns, though being near a ship which has been 'marked for despawn' may delay the despawn until you leave its immediate vicinity, or (possibly) use quantum travel. When you do (when you're not looking?), it will despawn. The OP Tyrtaeus says logging out pauses the timer until you log in again, but that's not much of a solution.
There's lots more detail in the post - worth a read assuming it's still accurate, which I think it could well be.
I have not independently tested this theory in 3.17. I thought it was useful enough to share, to see if anyone here can confirm/contradict.