Jump to content

41.76 UNSTABLE Released

nasKo

By nasKo
in PZ Updates

 Share

Recommended Posts

nasKo

nasKo

Posted
Posted

We skipped public testing for 41.75.

The TL;DR of the changes from 41.74 to 41.76 is that the Steam Networking API implementation was improved; Linux crashes should be fixed and overall networking performance has been improved alongside connection stability in internal tests.
In essence the game will now also use direct communication with dedicated servers, instead of going entirely through Steam’s own networking API, improving performance and stability for dedicated servers.

 

 

MP

 

- Improved Steam Networking API implementation.
- Selected game data is no longer transmitted through the Steam P2P API but through UDP instead.


- Adjusted Anti-Cheat Types 21-24 to result in fewer false positives.

A note that if you do not run a public server (i.e. a server exclusively for you and your family & friends without the worry of griefing and cheating), you can entirely circumvent any sort of frustration with false positives by disabling all AntiCheat protections in the servers .ini file.

 

- Split the large ConnectionDetails packet into several smaller packets with one of the ConnectionDetailsPacket.State enum values indicating which data is requested.
- Improved algorithm for the transmission of large files while playing.

- Loading screen now shows the download status of large files when connecting to a server.


- ZNet library was rebuilt on all platforms.
 

- Fixed ObjectModData packets not being sent while the server was in the FastForward state.
- Fixed bug in world dictionary when an item in a different module but with a similar name as an vanilla item was removed.
- Fixed a new stubble Beard getting added to remote players after each appearance change, which resulted in receivePlayerZombieDescriptors errors.

Link to comment
Share on other sites
  • nasKo pinned this topic
Ralms

Ralms

Posted
Posted
1 hour ago, nasKo said:

(...)
- Adjusted Anti-Cheat Types 21-24 to result in fewer false positives.

A note that if you do not run a public server (i.e. a server exclusively for you and your family & friends without the worry of griefing and cheating), you can entirely circumvent any sort of frustration with false positives by disabling all AntiCheat protections in the servers .ini file.

 

- Split the large ConnectionDetails packet into several smaller packets with one of the ConnectionDetailsPacket.State enum values indicating which data is requested.
- Improved algorithm for the transmission of large files while playing.

- Loading screen now shows the download status of large files when connecting to a server.
(...)

 

Thanks for the update.

I have some questions regarding these topics: 

  1. Can we have a quick description of what each Anti-Cheat type is checking in the server config file? The way its now, its completely generic and hard to decide the impact it would be turning each one on or off and hard to tune multipliers (type 2, 3, 4, 9, 15, 20, 23 so far). 
  2. Regarding large files downloads, from hosting a server for over 9 months now, I noticed that the Game client won't retry to download anything. If a file fails to download for any reason (several packets lost, network interruption blip, etc) it just forces the player to quit, not even return to main menu. 
    Can we add retry logic and allow the player to return to the main menu if something goes wrong connecting to a server? 

Thanks. 

Link to comment
Share on other sites
nasKo

nasKo

Posted
  • Author
Posted
16 minutes ago, Ralms said:
  1. Can we have a quick description of what each Anti-Cheat type is checking in the server config file? The way its now, its completely generic and hard to decide the impact it would be turning each one on or off and hard to tune multipliers (type 2, 3, 4, 9, 15, 20, 23 so far). 
  2. Regarding large files downloads, from hosting a server for over 9 months now, I noticed that the Game client won't retry to download anything. If a file fails to download for any reason (several packets lost, network interruption blip, etc) it just forces the player to quit, not even return to main menu. 
    Can we add retry logic and allow the player to return to the main menu if something goes wrong connecting to a server? 

Thanks. 


Good points. We'll add a Main Menu button and have a retry looked into again.

Link to comment
Share on other sites
Ralms

Ralms

Posted
Posted
6 hours ago, nasKo said:


Good points. We'll add a Main Menu button and have a retry looked into again.

Thank you for acknowledging it. 

To provide more details, the situation which has highest occurrence where a large amount of data is transmitted and would benefit from a retry logic is the map download. 

On high populated servers, the "Failed to download map", because 1 chunk didn't arrive is very common. 
 

Link to comment
Share on other sites
Manwer

Manwer

Posted
Posted
On 9/10/2022 at 11:44 AM, SalSevenSix said:

Any news on using an existing map from 41.73 on 41.76 ? Or do we need to start a fresh map?
Going to be an interesting day if a fresh map is required when 41.76 is pushed to stable!

Would like to know too, we are waiting for the release to do the wipe :unsure:

Link to comment
Share on other sites
Mr_Space

Mr_Space

Posted
Posted
On 9/10/2022 at 1:44 PM, SalSevenSix said:

Any news on using an existing map from 41.73 on 41.76 ? Or do we need to start a fresh map?
Going to be an interesting day if a fresh map is required when 41.76 is pushed to stable!

 

On 9/13/2022 at 9:24 PM, Manwer said:

Would like to know too, we are waiting for the release to do the wipe :unsure:

It doesn't reset the map, but i believe it does reset the loot and possibly the Z's. I did the switch after 24h of being live, not sure if it was a bug but it removed player buildings also.

 

Link to comment
Share on other sites
  • 2 weeks later...
  • nasKo unpinned this topic
  • 1 year later...
rosiewilsonnsjh

rosiewilsonnsjh

Posted
Posted
On 9/8/2022 at 7:25 PM, nasKo said:

We skipped public testing for 41.75.

The TL;DR of the changes from 41.74 to 41.76 is that the Steam Networking API implementation was improved; Linux crashes should be fixed and overall networking performance has been improved alongside connection stability in internal tests.
In essence the game will now also use direct communication with dedicated servers, instead of going entirely through Steam’s own networking API, improving performance and stability for dedicated servers.

 

 

MP 

 

- Improved Steam Networking API connections game implementation.
- Selected game data is no longer transmitted through the Steam P2P API but through UDP instead.


- Adjusted Anti-Cheat Types 21-24 to result in fewer false positives.

A note that if you do not run a public server (i.e. a server exclusively for you and your family & friends without the worry of griefing and cheating), you can entirely circumvent any sort of frustration with false positives by disabling all AntiCheat protections in the servers .ini file.

 

- Split the large ConnectionDetails packet into several smaller packets with one of the ConnectionDetailsPacket.State enum values indicating which data is requested.
- Improved algorithm for the transmission of large files while playing.

- Loading screen now shows the download status of large files when connecting to a server.


- ZNet library was rebuilt on all platforms.
 

- Fixed ObjectModData packets not being sent while the server was in the FastForward state.
- Fixed bug in world dictionary when an item in a different module but with a similar name as an vanilla item was removed.
- Fixed a new stubble Beard getting added to remote players after each appearance change, which resulted in receivePlayerZombieDescriptors errors.

The loading screen now shows the download status of large files when connecting to a server.

Link to comment
Share on other sites
  • 11 months later...
  • Kirrus locked this topic
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...