"Yokosuka Barrier" port broken after restarting the game.

[DJ Daemonix]

Greetings,

I'm encountering a bug where selecting the "Yokosuka Barrier" port in-game will work as intended in the scope of this running instance of WOWS, but after restarting the game, the port will revert back to "Philippines".

 

- Trying to select "Yokosuka Barrier" port again is impossible, as it appears already activated, just like "Philippines". So two enabled ports, somehow.

- Selecting another random port is possible, but current selected Port will read "Yokosuka Barrier".

- Selecting another port then selecting "Yokosuka Barrier" again is impossible, and will yield same result as 1st bullet point. ^

The only way to clear the bug is to restart the game once more. Only then is "Yokosuka Barrier" selectable again, and usable, but next restart will yield the same result, if selected.

Regards,
DJ Daemonix

Aslains_WoWs_Logs.zip

Edited July 5, 2019 by DJ Daemonix
Obligatory Logs attached, sorry for the omission.

[DJ Daemonix]

A bit more on the topic, Yokosuka Barrier's skybox is completely broken : 

 

[Manacetamol]

1./ Before exit the game, u must switch back to Official ports, any of them

 

2./ If u forget and it will stuck with Official ports << WG's fault, I reported it but they didnt fix.

to fix it >> open "preferences.xml" find the Green tags and change the current (port_preset & port_preset_custom) like Orange tags,

follow this >>

Quote

<lobby_values>
            <port_preset>    ocean    </port_preset>
            <port_preset_custom />
            <i_dont_like_premium_port>    false    </i_dont_like_premium_port>
            <i_dont_like_twitch_port>    false    </i_dont_like_twitch_port>
            <i_dont_like_azurlane_port>    true    </i_dont_like_azurlane_port>
            <i_dont_like_arc_port>    true    </i_dont_like_arc_port>
            <game_type>    PVEBattle    </game_type>
            <ship>    4286527472    </ship>
            <shipBattleHistory>    4184749872,1561265148,4183701456,1561265623    </shipBattleHistory>
 </lobby_values>

[FuneraVirtus]

Quote

<port_preset_custom />

 

You sure that / is in the right place, mate?
Generally / means ignore or end the following, which means the > would be ignored, resulting in port_preset_custom not being recognised. I have no experience with this API whatsoever, so this could be a completely idiotic misassociation made in ignorance of the preference.xml syntax, in which case I apologise.

 

[Manacetamol]

13 hours ago, FuneraVirtus said:

 

You sure that / is in the right place, mate?
 

 

it will remove Custom port and return to official one

[DJ Daemonix]

23 hours ago, FuneraVirtus said:

 

You sure that / is in the right place, mate?
Generally / means ignore or end the following, which means the > would be ignored, resulting in port_preset_custom not being recognised. I have no experience with this API whatsoever, so this could be a completely idiotic misassociation made in ignorance of the preference.xml syntax, in which case I apologise.

 

My thoughts exactly.

As i work with XAML frequently, i'm very used to that sort of syntax. To clarify, a / in an orphan tag is used as an escape character, to specify its orphancy. Reason why HTML has <br/> tags to end line.
So perhaps something broke withing the preferences.xml file upon install of the modpack, but there is no way to know without confirmation from Aslain himself. I'd be glad to attach my preferences.xml file for reference, had it not contained my connection strings and tokens used for logging into my account.

Still, the problem can't just be worked around. We need a fix on this.

[Manacetamol]

6 minutes ago, DJ Daemonix said:

So perhaps something broke withing the preferences.xml file upon install of the modpack, but there is no way to know without confirmation from Aslain himself. I'd be glad to attach my preferences.xml file for reference, had it not contained my connection strings and tokens used for logging into my account.

Still, the problem can't just be worked around. We need a fix on this. 

Modpack is fine

Port mod is OK

just because WG didnt fix it since 0.8.4

[FuneraVirtus]

21 hours ago, MixCore said:

it will remove Custom port and return to official one

Thank you for the clarification; I have changed it as you said. 
However, under the /Bin64 folder, I found another  preferences.xml file, with different  information, including this :
 

<lobby_values>
            <port_preset>    ocean    </port_preset>
            <port_preset_custom />
            <i_dont_like_premium_port>    true    </i_dont_like_premium_port>
            <i_dont_like_twitch_port>    false    </i_dont_like_twitch_port>
            <i_dont_like_azurlane_port>    true    </i_dont_like_azurlane_port>
            <i_dont_like_arc_port>    false    </i_dont_like_arc_port>
            <port_preset_custom>    Black_Hole    </port_preset_custom>

 

My question is:  Should I remove   <port_preset_custom>  Black_Hole  </port_preset_custom>  from that file, or is your orphan tag solution designed only to empty  the value of port_preset_custom before  the client tries to set it to the user's port choice?
The reason I ask is that I'm wondering whether I need to search my computers for any other prefrences.xml files tied to WoWS installations (Public Test, for example) and remove the custom port line from them all.

Edited July 9, 2019 by FuneraVirtus
grammar

[Manacetamol]

1 hour ago, FuneraVirtus said:

Thank you for the clarification; I have changed it as you said. 
However, under the /Bin64 folder, I found another  preferences.xml file, with different  information, including this :
 

 

My question is:  Should I remove   <port_preset_custom>  Black_Hole  </port_preset_custom>  from that file, or is your orphan tag solution designed only to empty  the value of port_preset_custom before  the client tries to set it to the user's port choice?
The reason I ask is that I'm wondering whether I need to search my computers for any other prefrences.xml files tied to WoWS installations (Public Test, for example) and remove the custom port line from them all.

"<port_preset_custom>  Black_Hole  </port_preset_custom>"

yes, remove "Black_Hole" then it should be back to normal