Please consider removing the Dropping animation

We all have those 5 seconds of nothing when you try to enter/drop out of supercruise. 5 seconds isn't much, but it's 5 seconds I could spend doing something else. Not to mention it is slightly off putting in a non-explanitary way.

What I think is happening now is the player (computer) is contacting the ED servers to check or prepare the instance for arrival. This would take time to spawn in the ships in the instance.

Instead, go off the code for "If in supercruise and J key is pressed, drop out into normal space" and as soon as J is pressed it drops you out. The instancing is done whilst you drop out. The sensors simple need to "update" to hide this. Set a 3-5 second period when the sensor can do a full sweep of the area (it's logical in a way) before displaying ships as they spawn in. If jumping to a station, here's a solution for it not appearing straight away:

When within 1mm and travelling under 1000km/s, people drop out as a safe disengage. Most people do this as soon as possible, up to about 300km away. You won't be able to see the station from 3 km away, right? Whilst the instancing is loading, instead if that horrible blue slipstream effect, just play the dropping out noise and decelerate

This is more logical than the system of "You're going at 600km/s aaaaaand now 300 m/s". Simply drop out but still travel quite fast as the ship slows down, then 5 seconds later, when you will be able to see the station, the instance will have loaded. Much more immersive.

Support would be nice :D
 
.. What I think is happening now is the player (computer) is contacting the ED servers to check or prepare the instance for arrival. ... The instancing is done whilst you drop out...

Yeah, the network connection for this is peer-to-peer not via severs (I believe), hence the delay...

Edit: I think even for NPCs it's a P2P instancing thang.
 
Last edited:
Yeah, the network connection for this is peer-to-peer not via severs (I believe), hence the delay...


My suggestion would still work, though wouldn't it? Assuming there's enough time to load the instance whilst you decelerate towards the Safe Disengage locarion
 
Last edited:
My suggestion would still work, though wouldn't it? Assuming there's enough time to load the instance whilst you decelerate towards the Safe Disengage locarion

The game doesn't know where you will disengage until you actually do so. Just because you're heading for a station doesn't mean you'll drop there. So it's pointless and wasteful to pre-load an instance you may not drop into.
 
Or the client could load the data from the server 10 seconds earlier as you approach a station or RES. If you have a destination locked, and are 10 Mm away, the client should request the data for the destination.
 
Well sometimes - particularly if I have had a glass of sherry or 2, I miss my exit window and have to do a loop. Load it 10 seconds earlier and well I muck up the instance for other players.

In computing terms - the annoying thing about concurrent events is you have to order them - to avoid race conditions. Look up the Philosophers Dinner - and consider the ownership of NPCs, including say the station.

Simon
 
Back
Top Bottom