what costs more Resources

Hello

what costs more Resources Floating tyres visible or not visible?

If you want to maximize perfomance, disable the floating tires by setting Enabled to false under the Decoration part of the config.

Ok thanks.  

So that would not help?
"Dynamic": true,

Setting them to dynamic actually requires that the plugin do some work to toggle them on and off when entering/leaving water.

Here is a more detailed explanation of the performance consequences.

When the decorative inner tubes are enabled, regardless of whether they are dynamic, they are always spawned and networked to clients. That means there's a greater networking cost when a heli is started or stopped since that is when helis enter/exit global broadcast mode. For example, if someone starts a heli engine across the map, if it was outside network distance, it gets networked to me at that time, requiring that the inner tubes also be networked (i.e., network packets are sent to my client for each inner tube entity). There is a small cost to networking entities to clients (on create, update, and destroy) but Rust normally sends an enormous quantity of network messages per second on populated servers, so I estimate the true impact of the inner tubes to be negligible.

When then inner tubes are set to dynamic, even though they are still networked to clients, they are invisible because of a flag. When the plugin wants to show or hide the inner tubes, it simply sends a flag update to clients, which is a relatively small network message, much smaller than a full entity message. The plugin was designed this way in order to minimize the time spent hiding and showing the inner tubes.

Overall, the decoration aspect of this plugin, or even the plugin as a whole isn't a performance bottleneck that I'm aware of. Do you have any data or anecdotes suggesting this plugin is causing significant performance loss?

Hey, thanks for the detailed explanation. 
So if I understand correctly, tyres that only show up in the water are better than seeing them all the time. 

No, no problems, everything is ok. I just wanted to know what you think would be the best setting. 

Showing inner tubes only some of the time is currently better for client performance but worse for server performance, but only marginally worse because hiding and showing is fast.

I should add a disclaimer that this is subject to change. I could make the logic "lazy" by only creating the inner tubes on the server side the first time the heli touches water. That is a good idea. If I do that, dynamic inner tubes would be better for server performance in many cases (though not all, as it depends on a few things).

My advice is to keep them dynamic, purely for player experience, since people probably don't want to see inner tubes on their helis all the time, though I could be wrong about that.

Vielen Dank für Ihre Hilfe. Ich werde sie dynamisch gestalten, da ich persönlich es schöner finde, wenn man sie nur auf dem Wasser sieht. Vielen Dank. 

Changed Status from Pending to Closed