ANNOUNCEMENT January Update - Patch Notes

Since I am doing an expedition right now I can only comment on the exploration fixes/issues:
  • I can confirm that the stutter seems to happen only in systems with landable planets (though I have seen Paige's post that the cause has already been identified and will be fixed tomorrow)
  • I have NOT seen the new FSS mechanic of "unlikely / likely / very likely" for signals at all. Instead when a body has geo signals the number shows up immediately now. I would speculate that this is related to the stuttering issue. Presumably some calculations are done at the moment as soon I enter a system and by the time I enter FSS the results are available. Not a complaint from my side, just an observation.
  • The signal information in the top right info field of the FSS are now shown with a line break, e.g. "Geological 'line break' (9). I assume the same string is used in the system map since it shows the same line break and the Nav panel which causes the number to not show anymore there. Because as soon as you select the entry in the Nav panel you see the same string with the line break in the description field.
  • The summation of the belts works well, I really love that.
That's it for now, I might edit this if I find anything else.
 
Not sure this is a bug but Guardian Sites are not showing on FSS scan. They are listed on the System Map beside Locations Guardian(4)

That information has been moved to the description area as described in the patch notes. They are actually on your picture highlighted in blue font (very first line).
 
Not sure this is a bug but Guardian Sites are not showing on FSS scan. They are listed on the System Map beside Locations Guardian(4)
I think that's working as intended. They said Human/Guardian/Thargoid sites are considered "Locations" not "Features" and that Locations were moved down to the right side pane. From now on only geological and biological sites will show up on the Features pane.
 
  • I can confirm that the stutter seems to happen only in systems with landable planets (though I have seen Paige's post that the cause has already been identified and will be fixed tomorrow)
  • I have NOT seen the new FSS mechanic of "unlikely / likely / very likely" for signals at all. Instead when a body has geo signals the number shows up immediately now. I would speculate that this is related to the stuttering issue. Presumably some calculations are done at the moment as soon I enter a system and by the time I enter FSS the results are available. Not a complaint from my side, just an observation.
Same here, I haven't seen the Unlikely/Likely bit since the patch. My guess would be that the pre-computation for all landable bodies was not intended, and the fix Paige mentioned is to revert that to the behavior described in the patch notes.
 
Same here, I haven't seen the Unlikely/Likely bit since the patch. My guess would be that the pre-computation for all landable bodies was not intended, and the fix Paige mentioned is to revert that to the behavior described in the patch notes.
Agreed.
I read their explanation why it would take so long originally, but never understood the dependency really. Surely the number of sites (the only info shown in the FSS) is an input parameter and thus available before the rendering of the planet. As such it should be possible to show it "immediately". I could understand that some delay was intended as a gameplay mechanic in the sense that scanning a whole planet for signals does take some time and cannot be instantaneous. I think most players would be willing to accept that in terms of role playing. If they simply would have kept the time in the range of 5-10 seconds I believe this never would have been an issue to begin with.
 
Before it passes underneath the radar, the hilarious Holo-Me bug in VR has been fixed apparently. No more Sleepy Hollow and questionable dreams for me! \o/

The stutters are the only issue left for me, everything else seems fine so far.

O7,
🙃
 
Can you elaborate on that? How did you come to that conclusion.

At first glance this is about data compression, so Elite will need less bandwidth. But Elite hardly needs any anyway. Was this small amount already too much for AWS?

I think Elite's problem come from the fact that networking is hard and the P2P connections aren't very reliable. Would the inclusion of this library really magically fix a lot of that or is it just a "might as well" addition to save some bandwidth?
Networking, when investment and creative tech engineering come together, make beautiful fractal patterns on huge 8K monitors.
It's only hard when you try to do something new, which is what Elite is. P2P, if limited to WIN64 PC is easy.
Try it thru Sony and MS' flower garden paynets, with a frisson of Steam, for instance(s) ;)

Oodle
It's more for FD server side to speed up all the central stuff: Boards, Codex, Map, Logs Missions
Helps those with ISP's who and/or: shape traffic, NAT spoof, low sec DNS, low fi surveillance, poor net design, won't rent enough trunk fibers etc.

Your game makes 1 connect to your ISP. Then to Amazon Web Services, who compete with MIcroSoft for this hot global cloud action.
Some ISPs have lots of AWS connections, some not so much, depending on where you live.
And if they spent for good infrastructure, not corporate salaries.

AWS gateway then makes multiple connections in parallel to FD's front edge servers. My hypothesis of course.
Oodle should only compress what isn't compressed already, like bitmaps and lzn

Gonna try the game now, Going for the Mug
 
I have no idea why Elite is bottlenecking on data loads when the bandwidth monitor lists really small upload and download amounts, but I know that something is wrong there because streaming to discord causes desync/lag, and sometimes so does streaming music. I'm on a fiber optic gigabit connection so I don't think I should be bottlenecking on my end, but it sure acts like it is.
I think they will need some time to get it customised to the live game. Might not even be an Oodle problem
Testing works best live because they cannot really simulate that dynamic load.
Never play on patch day lol.
 
Sorry for the triple. Merge please come back
Am out in the black, and in any system with bodies the game is now stuttering like hell until (seemingly) the bodies are resolved.
Like a library filling for the first time in a cache .... @OldDuck

EDIT no stutter for me, will have to go where no Gully has gone before.
 
Last edited:
Since I am doing an expedition right now I can only comment on the exploration fixes/issues:
  • I can confirm that the stutter seems to happen only in systems with landable planets (though I have seen Paige's post that the cause has already been identified and will be fixed tomorrow)
  • I have NOT seen the new FSS mechanic of "unlikely / likely / very likely" for signals at all. Instead when a body has geo signals the number shows up immediately now. I would speculate that this is related to the stuttering issue. Presumably some calculations are done at the moment as soon I enter a system and by the time I enter FSS the results are available. Not a complaint from my side, just an observation.
  • The signal information in the top right info field of the FSS are now shown with a line break, e.g. "Geological 'line break' (9). I assume the same string is used in the system map since it shows the same line break and the Nav panel which causes the number to not show anymore there. Because as soon as you select the entry in the Nav panel you see the same string with the line break in the description field.
  • The summation of the belts works well, I really love that.
That's it for now, I might edit this if I find anything else.
I saw "likely" and "very likely" several times. Other bodies showed the signals immediately.
 
I can't replicate it. AMD RX580 2g
went to 10 systems with econo, landables gas giants binaries no b-bb-b--bb-baby
Stations screens seem faster
 
Kudos to FD for fixing the bugs first, before introducing the fleet carriers. I think the beta testing was a very positive step to avoid the September Update issues that torqued so many players off. I like the exploration fixes. Actually, I rather like ALL of the fixes. I do not understand the changes to the supply/demand effects on gemstone prices. I guess that means the prices will be a lot more volatile.
 
Still gonna wait - with another post-patch patch coming tomorrow, might as well.
A few good things in here, the rest... haven't had the problems being fixed, so, not much will change for me.

But... a nice Thank You to all of Frontier for your efforts and dedication.

Now, get back to work, you've got actual content to deliver. ;-)
 
Top Bottom