UseNextGenSteamNetworking: bandwidth is lower than stated? about fizzysteamworks

[Chykary]

Hello,

the MaxPacketSize is just the size for a single packet. It was faulty previously and would have caused a disconnect.

[NikitaNikita1]

Hello,

the MaxPacketSize is just the size for a single packet. It was faulty previously and would have caused a disconnect.

That is, the maximum packet size is larger than the maximum channel bandwidth? Is it possible to somehow find out the actual maximum bandwidth not on practical tests? Or are there no constants for this?

[Chykary]

Hello, there's a Steam config value that one can use to clamp the bandwidth: k_ESteamNetworkingConfig_SendRateMax. However, it is 0 by default, which means no limit.

So I am currently not sure what could limit your bandwidth.

[joecons97]

@NikitaNikita1 Did you ever fix this? This seems to have started out of nowhere for me recently

[NikitaNikita1]

@NikitaNikita1 Did you ever fix this? This seems to have started out of nowhere for me recently

No. What I noticed after a lot of testing is that it looks like using the newer version of the (direct) connection of Steamworks has a 1 megabit limit, while the old (p2p) version allowed 1 megabyte to be transferred. I researched this in early summer but it doesn't seem to have changed.

[joecons97]

@NikitaNikita1 Did you ever fix this? This seems to have started out of nowhere for me recently

No. What I noticed after a lot of testing is that it looks like using the newer version of the (direct) connection of Steamworks has a 1 megabit limit, while the old (p2p) version allowed 1 megabyte to be transferred. I researched this in early summer but it doesn't seem to have changed.

I've switched back to the legacy solution for now. I guess this would be more of a question of Steam support then.

Thanks for replying :)

[Chykary]

The topic seems to be related to Steam API features/limitations and isn't something impacted by the transport. :-)