PS4 Hotfix (25/07/17)

Status
Thread Closed: Not open for further replies.
Distance readout wonkified

Downloaded update 1.05. Now, when targeting jump locations the distance read out is reading distances with more comas than I feel like figuring out. Tried restarting my game session. Issue persists. Any ideas?
 
"You must spread some Reputation around before giving it to Old Duck again."

Sorry pal,,, I must be sending you too much love,,, lol

That might have been fate... It looks like I did speak too soon after all. Tonight I was all excited when hyperspace was taking extra long, since I'm in the Pleiades sector, I thought, "This is it! I'm going to meet my first Thargoid!" Nope, I met a crash screen instead.
 
Last edited:
Horizons sharing

On the one hand, im glad they fixed the issue with Horizons not being accessable to secondary accounts, but on the other hand, im sad because i didnt want to wait for a someday patch, so i bought Horizons for myself so i could play in wing with my bro without missing out. so it was kinda worth it, but still sucks i didnt need to now and it was 30$ mostly wasted, coulda bought me and him bobble head letters or something
 
I've had no connection issues with ED since launch but following the 1.05 update came across a few issues.

1. When I'm jumping from system to system, the jump itself before you come face to face with the star lasts around 5-seconds or so, but after the 1.05 update I was getting jumps of 3-4 minutes!!! Began to panic thinking I'd simply have to restart the PS4 but they did eventually drop out - but why so long?

2. Also when logging into the station services it took 1 minute or so to log in, rather than the 10-seconds.

Might be Coincidence - but in the end I gave up last night, will try again tonight.
 
Last edited:
It didn't seem as bad after the downtime for a server restart but if it continues with anymore drop outs tonight I'd say it's made it worse :(

I had more disconnects and hard lock ups last night than I have previously had since launch! :/
 
Still being dropped for matchmaking server issues, but at least I can load stuff straight back in instead of having to wait a minute or two.
 
Still no Cobra mk iv.. Come on FD release it!!

seriously FDev not giving us an overweight, slow, and not so good cobra is a blessing. imagine how many commanders will complain when they finally get the cobra mk4 because its to slow or a waste of money. i for one feel FDev are doing the right thing, spending time fixing problems rather than adding a completely naff ship to the game. so thank you FDev for making the repairs rather than glossing over it with an ugly ship that is useless as anything except a garden ornament
 

stormyuk

Volunteer Moderator
seriously FDev not giving us an overweight, slow, and not so good cobra is a blessing. imagine how many commanders will complain when they finally get the cobra mk4 because its to slow or a waste of money. i for one feel FDev are doing the right thing, spending time fixing problems rather than adding a completely naff ship to the game. so thank you FDev for making the repairs rather than glossing over it with an ugly ship that is useless as anything except a garden ornament

To be honest it won't be a lot of work adding it, its already done as its on the PC and Xbox. The assets for the graphics and all that jazz are probably already there (in fact I have killed some at RES sites, so they are in the game, just not available for players to buy). Still I won't lose massive sleep over it not being in but its supposed to be not bad engineered and has more slots than the Mk3.
 
Ooops, looks like the "speculative fix" for the server issues didn't work, that or the servers were super busy last night because I gave up in the end due to the constant server disconnects and I'd applied their suggested fix from the FAQ.

Fingers crossed the devs can get this fixed soon but I'm sure can't be easy with all the different routers and ISP's to figure out the root cause.
 
Ooops, looks like the "speculative fix" for the server issues didn't work, that or the servers were super busy last night because I gave up in the end due to the constant server disconnects and I'd applied their suggested fix from the FAQ.

Fingers crossed the devs can get this fixed soon but I'm sure can't be easy with all the different routers and ISP's to figure out the root cause.

Dav mentioned there was another issue last night affecting all platforms, so last night was a bit of a write off with regards to checking the effectiveness of the hotfix.
 
Makes sense as after the half hour or so downtime I didn't have any disconnects so hopefully it was unrelated to the patch.
 
As posted in the disconnection thread, have been playing for about 4h this morning solo at the GC battle. Not a single disconnect by now, but need to move back to my homebase later today 20+ jumps and start mining. Then we talk.
 

stormyuk

Volunteer Moderator
As posted in the disconnection thread, have been playing for about 4h this morning solo at the GC battle. Not a single disconnect by now, but need to move back to my homebase later today 20+ jumps and start mining. Then we talk.

To be honest I very rarely run into problems in Solo, my problems all start in Open and usually when its trying to instance or match make.
 
I've had no connection issues with ED since launch but following the 1.05 update came across a few issues.

1. When I'm jumping from system to system, the jump itself before you come face to face with the star lasts around 5-seconds or so, but after the 1.05 update I was getting jumps of 3-4 minutes!!! Began to panic thinking I'd simply have to restart the PS4 but they did eventually drop out - but why so long?

2. Also when logging into the station services it took 1 minute or so to log in, rather than the 10-seconds.

Might be Coincidence - but in the end I gave up last night, will try again tonight.

This is the buggiest game I have ever played. Period.

I finally got to the Felicia Farseer mission. After hyper-jumping to Deciat, it immediately became obvious that her station was behind another planet. I used that planet to break my hyper-jump, then set course for her station.

No option to escape the planet's orbital cruise was available, stating that super-cruise would take over 50 minutes. I was forced to set course for a nearby station to break my ship free of the planet.

These little annoyances are become problematic. No one should expect that a game they paid $60 for only performs as expected 80% of the time.
 
Last edited:

stormyuk

Volunteer Moderator
This is the buggiest game I have ever played. Period.

No option to escape the planet's orbital cruise was available, stating that super-cruise would take over 50 minutes. I was forced to set course for a nearby station to break my ship free of the planet.

As willow says this is not a bug, you just need to plan your entry into orbit a little bit better so your distance to the planetary base is smaller, with practice it will become easier. I try and position myself so that I don't enter the planetary area (the blue circle around the planet) until I can get a good trajectory on the target base and then enter orbital cruise and glide modes much closer to the target.

You can always take a wide arc while in normal SC around the planet if required if the base you want is on the far side of the planet.

You also don't need to set course to another target to get out of a planetary atmosphere, just head away from the planet until you build up speed and break orbit. Target the planet and make it a hollow dot on your compass if that helps.
 
Last edited:
Funny that the game's one of the greatest features are orbits, mass locks, gravity and that kind of amazing details and some of people think that these are a bug. No sir, these make this game a unique and heavenly space-sim.

Some of people should keep playing NMS on PS4
 
Last edited:
To be honest I very rarely run into problems in Solo, my problems all start in Open and usually when its trying to instance or match make.

See, and since I dont have PS4 gold I only play solo and all my disconnects were happening in solo only. if you are interested, its all documented in the other major thread. Having said that, the MTU and DNS change reduced disconnetcs from one every 5 to 10 Minutes to one every 1-2 hours.
The fix of today - even though I understand other users seem to have increased trouble - for me has sorted this problem even more. Haven't had a single disconnect since. Now I was jumping since this morning probably 100 J and I haven't had a disconnect. Before I couldnt jump more than 10-15 J without disconnect.

But the hardest test to follow. Once I am back at my main base I will go for a mining run.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom