Netcode fix almost here!

6 posts / 0 new
Last post
DynamicX's picture
Offline
Last seen: 4 years 7 months ago
InvestedPlatypus #2
Joined: 15/03/2014 - 13:40
Netcode fix almost here!
Quote:

PATCH DAY
Today we will patch both server and client on the CTE for the fifth time! This will mean some server downtime. You will also have to update your CTE client in Origin to join servers once they are up again.

 

 

 

PATCH CONTENTS
This patch includes:

  • Jet rear-view camera on separate button (Free look)
  • Russian Stealth jet ECM visual effect fix
  • Uniform Soldier Aiming improvements (Based on CTE player feedback)

 

WHAT ARE WE TESTING?
The contents of this patch includes fixes based on your feedback through the forums in the CTE. We would like you all to test these items to make sure we adressed them correctly (in your opinion)!

 

 

 

 

END OF INITIATIVE?

This patch concludes the first initiative on the CTE. The end of an initiative will not necessarily mean we won’t be working on additional fixes and tweaks in this area – it will just not be the focus of the full team.

For instance, we are working on automating the client side High frequency update option (and removing the option), as well as other tweaks and fixes to the netcode in general.

 

 

In the coming days we will switch to the natural follow up to network/”netcode” issues – Core Gameplay. More information about next initiative will be posted soon!

 

 

 

 

 

PATCH – NEXT RELEASE

The next release in the retail game will include a bulk of the changes and fixes made on the CTE. We think this collection of changes to the game, which were tested through the CTE is significant enough to warrant its own release as early as possible.

 

 

 

 

INCLUDED FEATURES

The upcoming release will contain the following features and fixes (PC, see coming patch notes for detailed list per platform):

  • Fix for explosion packs not being shootable sometimes
  • Fix for reducing damage mismatch between client/server
  • Fix for third person player orientation mismatch
  • Character collision improvements
  • Improvements for client side packet loss
  • Various server performance improvements
  • High Frequency Bubble
    Server to client “tickrate” improvements for damage, position, rotation, projectiles and stance (infantry/vehicle)
  • High Frequency Bubble: Added client option to set frequency of server to client update rate (OFF/LOW/MED/HIGH, default: OFF)
  • High Frequency Bubble: Added server kill switches to disable feature for rest of round based on low server performance
  • Dampened explosive camera shake
  • Reduced FrameHistoryTime by 33% (less time for a client to inflict damage to enemy during packet loss)
  • Various server side network improvements and fixes

 

 

FUTURE FEATURES

The following fixes and improvements did not make this release – and will continue to be tested on the CTE for upcoming releases.

 

Not all fixes and improvements are guaranteed a release however – some will not meet our quality demands or are simply tests for the CTE environment.

 

  • Possible fix for PC chat delay (unconfirmed)
  • Hainan Resort: Under-terrain exploit fix
  • Deathshield fix (already live, CTE integration)
  • Obliteration Competitive mode
  • Operation Metro 2014 exploit fix (partial)
  • PC-Client stability improvement
  • High Altitude Jet fix (Released separately very soon)
  • Changed the way FOV slider option works – the UI now correctly displays vertical FOV
  • Improved the Uniform Soldier aiming based on CTE player feedback
  • Added Jet 3P rear view camera
  • Implemented FOV slider for vehicle 3P chase camera (option)
  • Visual fix for weapon sticking out of ragdoll and rotating weirdly
  • Fix for Hardcore killcard not showing up properly

 

 

FEEDBACK
To give your feedback – please visit the forums and post your opinions in the appropriate section!



Audio is love, audio is life.

Courage isn't the absence of fear, It's doing what must be done despite the fear.

"An apology is worthless if you do not learn from your mistake." - Me

 

XPT700's picture
Offline
Last seen: 6 years 6 months ago
InvestedClan MemberPlatypus #2
Joined: 22/04/2012 - 11:48
I don't understand this one: 

I don't understand this one: 

  • High Frequency Bubble: Added client option to set frequency of server to client update rate (OFF/LOW/MED/HIGH, default: OFF)

So you can set your tickrate [in a vague way] manually? Seems rather strange, surely its fairer if everyone has the same!

 

Anyway, I welcome this patch, and I hope it can restore some faith in what was a screwed up game 

DynamicX's picture
Offline
Last seen: 4 years 7 months ago
InvestedPlatypus #2
Joined: 15/03/2014 - 13:40
you can only change how YOU

you can only change how YOU see the world, so updated at 10hz or 30hz or in between. It does not change how much date you send TOWARDS the server so that will remain 30hz ensuring everyone has the same experience.

I believe they have done this because of the console rules that a certain connection may not be discluded from the game which led to the 10hz tickrate/netcode back in Bad Company.

And about the game being screwed, it is not! I know, maybe im stubborn but I believe you make your own fun in a game Smile



Audio is love, audio is life.

Courage isn't the absence of fear, It's doing what must be done despite the fear.

"An apology is worthless if you do not learn from your mistake." - Me

 

Kiwi's picture
Offline
Last seen: 9 months 3 weeks ago
InvestedClan MemberWebwizardPlatypus #1
Joined: 28/05/2013 - 11:53
They said that they used the

They said that they used the 10Hz tickrate for the beginning of FrostBite because the consoles were not powerful enough (the engine was not optimized yet). Also, it seemed to be fast enough back in the days (Bad Company 1&2). In Battlefield 3 they started to see that it wasn't fast enough anymore, but people didn't complain about it (that much). With Battlefield 4 they had done some optimizations, and though that it would work well again, but they soon realised it didn't, but at that point fixing the bugs had a higher priority than changing the (hardcoded) tickrate (which would cause loads of new bugs).

It works great with the new tickrate slider, but I don't think they should put this on off by default, because 90% of the people will not see that option/understand it.


"MICHAEL! Zuig m'n nepel... Ehrrr... Tipple!" - Exhibition (2017)

DynamicX's picture
Offline
Last seen: 4 years 7 months ago
InvestedPlatypus #2
Joined: 15/03/2014 - 13:40
It wouldnt matter if it set

It wouldnt matter if it set to off by default. since you still send information towards the server at a rate of 30hz. that option only affects what he recieves



Audio is love, audio is life.

Courage isn't the absence of fear, It's doing what must be done despite the fear.

"An apology is worthless if you do not learn from your mistake." - Me

 

Kiwi's picture
Offline
Last seen: 9 months 3 weeks ago
InvestedClan MemberWebwizardPlatypus #1
Joined: 28/05/2013 - 11:53
Yes, but if the option will

Yes, but if the option will be turned off by default, people will still not have a better experience, and they wouldn't know how/that they can make it better.


"MICHAEL! Zuig m'n nepel... Ehrrr... Tipple!" - Exhibition (2017)