Ability to choose skin in multiplayer.

[Home Fries]

Syncing Liveries would be a huge bandwidth problem unless everyone already had them on their Harddisk.

 

Most of the Aircraft DO have a Single Decal Layer, the issue is, not all Liveries are simply decals...

What about this:

 

IF (otherUser.HasChangedSkinNameOnHarddisk == true)

Show the changed skin

ELSE

Show the default skin of this plane (like it is when I join a plane in Multiplayer and I don't have the skin)

 

:smartass:

 

My thoughts on this.

[kylekatarn720]

+1

[FalconPlot16]

why poll for this ? this is must be implemended already

[Roblex]

The usual stated reason for not allowing everyone to decide what skin they want to wear is that if there are 40 players in the server and each player has a personal skin then every player will need to download 40 skins when they enter the server.

 

I like the idea of putting in a logic test to say 'If Player X has a skin that is not on my hard drive then just display the default skin for this server.' This way a squadron can have their own skins so they can all recognise each other and that just need to ensure that everyone in the squadron has downloaded the skins. The same can be done if another squadron that yours often flies with also has its own skins.

 

One issue that has not been addressed yet though is squadron codes. In your own missions it is possible to set a squadron code that will appear on the fuselage, eg 56 RAF squadron uses 'US' followed by another letter, and have that letter automatically incremented for subsequent aircraft so if the first is 'US A' then the second is 'US B' etc but as far as I am aware, the squadron codes are set by the mission designer and an online player will not be able to alter that. We can get round this by having a custom skin with 'US A' written on the base skin and another with 'US B' etc but then the codes shown in the lobby would not match the codes on the aircraft(eg the list of aircraft I can jump into might show a spitfire 'AK J' is available but if I then change the skin to one showing 'US R' then anyone seeing US R will not know who is in the plane because the list will not show any planes with a US R code. Is there a more elegant way?

Edited June 13, 2017 by Roblex

[Home Fries]

One issue that has not been addressed yet though is squadron codes. In your own missions it is possible to set a squadron code that will appear on the fuselage, eg 56 RAF squadron uses 'US' followed by another letter, and have that letter automatically incremented for subsequent aircraft so if the first is 'US A' then the second is 'US B' etc but as far as I am aware, the squadron codes are set by the mission designer and an online player will not be able to alter that. We can get round this by having a custom skin with 'US A' written on the base skin and another with 'US B' etc but then the codes shown in the lobby would not match the codes on the aircraft(eg the list of aircraft I can jump into might show a spitfire 'AK J' is available but if I then change the skin to one showing 'US R' then anyone seeing US R will not know who is in the plane because the list will not show any planes with a US R code. Is there a more elegant way?

 

Either the mission designer would need to implement the dynamic numbering scheme based on your squadron's participation, or for the static skins, ensure the number in the ME (which shows up on the multiplayer screen) matches the static number on the skin. Either way, this is not out of the question for organized exercises, but probably too much for something like Blue Flag. Of course, if you all jump in the same aircraft type and replace the default skin with your own skins with static numbers, every member of the squadron will see the numbers as you like them.

[Frederf]

Be careful what you wish for: some skins approach 80Mb. :cry:

 

You misunderstand. "Sync" in this case means to synchronize skin identities between clients. The only data this involves is telling other clients what skin identity is being used, not the skin data itself.

 

Currently you can change skins in 2.1 MP but the identity does not change for other users. If it was synced then all clients would know to use that skin's local data. No actual texture data would be transmitted.

[SkateZilla]

You misunderstand. "Sync" in this case means to synchronize skin identities between clients. The only data this involves is telling other clients what skin identity is being used, not the skin data itself.

 

Currently you can change skins in 2.1 MP but the identity does not change for other users. If it was synced then all clients would know to use that skin's local data. No actual texture data would be transmitted.

 

This was reported already and acknowledged by devs.

[Isegrim]

I voted NO

 

Because the biggest CONTRA on this point is that the usage of this restricts Modules to be only used on one Coalition side on PvP servers.

 

As an example.

 

If i use the KA-50 on both Coalition sides and a blue Client changes its skin to the one which is used on the red side it would be very Hard to identify it by visual as an actual enemy.

 

This counts for all Modules.

[Home Fries]

Isegrim,

You make a great point, but I don't think it's necessary to kill the entire feature. A few server-side options could fix the problem.

 

You can already restrict a skin to a set of nations in description.lua, though that doesn't prevent people from creating an identical skin and removing these restrictions. However, allowing a server to restrict specific skins to a specified list (i.e. whitelisting skins), blacklisting skins, or allowing a server to require default skins, or even disabling skin change for the server altogether could work around this very easily.

Edited June 18, 2017 by Home Fries

[MikeMikeJuliet]

Todays changelog for 2.1. : Ability to change liveries in the rearm & refuel menu...

 

This should work in MP, no?

[Chizh]

Todays changelog for 2.1. : Ability to change liveries in the rearm & refuel menu...

 

This should work in MP, no?

 

Yes, it does.

[Alwandy]

Confirmed, it does.

[MikeMikeJuliet]

Case closed, I guess...

[Dingo_Bob]

is it a local change or across the server haven't had a chance to get online yet?

[Roblex]

That one puzzles me because we were able to change liveries in the re-arm menu before the update.

 

I have been flying in MP servers with Pierre Clostermans spit livery for the last week though I think I was the only one able to see it. The official liveries that came with the server (Burning Skies has three different Spit squadron liveries) could also be selected and I think those ones get loaded to everyones disks and so are visible to all, Does this change mean that now other people can see custom liveries?