New player experience
So a buddy of mine has a new comp and when we got to deciding what game to play he said SC. He has not tried it since 2.0.
I had not logged in 3.5 live patch, I did do the ptu, so said sure.
We had 40 mins of bad. He stepped off the platform at oli and got the EVA bug. Ghat was simple to fix. He spawned his 300i and we get in to show him, door killed us both. I spawned a Cutlass and the back ramp killed us both, which happened in the Connie I spawned only it was the elevator.
I loaned him an Arrow and he had no HUD. So he mucks around with the 300i until he got on and the doorway didn't kill him.
We go to yela and I showed him how to land on the moon. Next we tried a pve mission in the belt which worked good but the first engagement took so much work to kill the Npc we both ran out of ballistics.
We then limped back oli because he had crashed into an asteroid.
We tried to explore a HH but it killed us just trying to walk around it so much we called time.
When we closed out SC I said to him I think I'll make it a point to play it a bit before we both try next patch because that was not awesome. He said yeah it looks great but not really worth logging in because you can't even do anything when walking or entering ships kills you with such a high rate.
Posted May 27, 2019, 9:54 PM UTC
I certainly won't defend 3.5.0, but that sounds like an extra level of bad luck chief. It's nowhere near that bad usually at least for me. Maybe you were on a bad server...did you try to log off and see if you could get on a different one?
No might try that, like I said I was surprised as u did play a fair bit of the ptu, was my comments about it that led him to saying let's fire it up and kill some people... I mean do some courier missions.
When lock in, first check if the stores have inventory. If the stores are empty, the server might be in late stages of degradation (which can lead to all kinds of oddities like for example the physics grids freaking out breaking legs left and right) and I would immediately switch to a different server instance.
For now wait for 3.5.1 which will contain bugfixes and server optimisations for many of the problem that were introduced with 3.5.0 (presumably through the additional server load that ArcCorp added as many of the current problems are related to degrading background services).
careful, experience and knowing how to avoid or work through bugs can make it seem like they are not there...