Jump to content

hangglide42

Members
  • Content count

    954
  • Joined

  • Last visited

  • Battles

    13462
  • Clan

    [PROJX]

Community Reputation

361 Excellent

About hangglide42

  • Rank
    Ensign
  • Insignia

Profile Information

  • Gender
    Male
  • Location
    West Coast US
  • Interests
    History, Geopolitics, Military History & Technology, Techno-Geek, Astrophysics & Cosmology, Flying, Mathematical & Business Models

2 Followers

Recent Profile Visitors

2,210 profile views
  1. Hindy has pretty good AA - AFT may not be a bad choice -
  2. Come on WG really 0.7.5/0.7.6?

    The reason I believe May 23rd is the drop date for 7.5 is because the PT announcement has contained a PT pt 1 & 2 statement in the announcements for the PT in the past if there are 2 PT periods. The 7.5 announcement contained no indication of the 2 pt test format and the 23rd is consistent w/ a 4 wk drop schedule that WG has announced, so I believe this is the single PT period for 7.5 (WG’s 2 pt PT cycle would actually have pt 2 starting this week w/ pt 1 running the prior week which didn’t happen). The “rounds” they are referring to may be the split in tests for CAs+Cleveland in 7.5 & the PT for 7.6 which includes the rest of the new CL line. This is also consistent w/ how the ships were released to the testers & CCs (i.e. they got the 7.5 ships to review first, then they were removed and they were given the 7.6 ships). The “new” ship introduction in terms of new models is 1 (w/ 4 reparameterizations.) for 7.5 vs 4 entirely new models for 7.6. Because most of the ship portion of 7.5 requires primarily retiering parameter changes, WG may have shortened the PT period since they have gotten much of their feedback on the rebalanced tiers from their tester/CC testing feedback on the retiered ships that 2 PT cycles may not have been deemed necessary. I stand by the original prediction that 7.5 should drop on the 23rd.
  3. Come on WG really 0.7.5/0.7.6?

    The drop schedules shouldn’t be as far out as you’re fearing - 7.5 (CAs+Cleve move) should drop on May 23 & 7.6 (CLs) should be on June 20 if WG sticks to its release pattern. Not that much longer.
  4. Usually, the suggestion to send a commander to reserve applies mainly to the situation where you don’t want your commander to be moved according to WG’s split mechanics. This ensures the Commander stays w/ a particular ship irrespective of tier moves or other changes. The Gneisnau013 link is very detailed wrt what will happen for this split regarding the Commanders so it should allow us to evaluate whether we like the Commander moves (it appears to be a “stay w/ Tier” algorithm) & take the appropriate action.
  5. Tangential, but....Sovereigndawg is referring to states which have a insurance model known as “No-Fault”. In this model, your insurance pays for damage on your vehicle even tho you didn’t cause the accident.
  6. The recent Waterline video series stated that the compensation for the USN Cruiser Split will follow along the lines of the last VM DD line split. If so, this is what should happen: WOWS Enjoyment - When Lines Split... WG has a very Player-friendly policy when a Tech Tree Line splits. Players are generously compensated new ships depending on what ships they have in port at the time of the split. This article explains the mechanics of what happens as of the 1st 2 line splits that occurred and what is anticipated for the 2018 USN Cruiser Line split in specific detail. If you want to know what ships to have in your port to net some free ships w/o the grind, this post is for you. (This post will be kept current re: WG Policy as to what happens.) In your case, this means: Your Pensa will move to T6 (with it's downgraded parameters for T6) The new T7 New Orleans will also be in your port (ship that replaced the Pensa in its old slot). Your Cleveland will move to T8 in the new CL line (with upgraded parameters for T8). Having both the Cleve & Pensa will also earn you some silver since you would've gotten a compensation ship, but you already have the ship in the slot the compensation ship would've occupied.
  7. Kronstadt - FXP Ship?

    Just some info to add to landedkiller’s summary here - A WG rep stated a while back that “the next Free XP ship would not be a BB for a change”. This seems to suggest that the Kronshtadt would likely be the Free XP ship. There have also been previous hints by WG that you will be able to earn the Stalingrad by other means than as a Clan Battle reward. This info coupled w/ the recent Waterline videos suggest that the new “coal” & “steel” currency mechanisms are going to be the likely vehicles for earning this ship.
  8. What’s kinda interesting is that the Commander’s skills seem tailored for a BB skipper...Is this just portending the release of the Stalingrad/Kronstadt...or a possible Russian BB line?
  9. New spectator mode?

    If you’re allowed to see the unconcealed movements of both teams, it provides sufficient info for players to deploy to counteract enemy moves. This is why casted competitive streams use delayed feeds to try to use the time delays to date the usefulness of team deployments & positions to minimize the impact of this reveal (I.e. the teams have discovered most of the info thru the game before the stream view is an unfair advantage minimizing the usefulness of sniping). Some clans have gone so far as to attribute their difficulties to their streamers and have implemented rules to require the stream delays (along w/ some more controversial actions taken by a particular clan). There are a couple of levels of spectator issues that can be used by players to gain an unfair advantage. The first paragraph describes the “arena e-sport” view issue. The second paragraph refers to info from a particular streamer player view that can be misused. Streamers have typically used either stream delays or various artifacts such as their webcam to block the minimap view. For the OPs reason for wanting to learn from following a particular player, the minimap would be key to understanding why a player may be moving to a certain location or executing a certain strategy. You currently can already do a version of what you’re suggesting w/ your own team once you die - you can cycle to any ship still alive on your own team and experience what they’re doing as they play. Edited 13 hours ago by hangglide42 Hi Clutch - I did and owe you an apology because I negected to describe a 3rd category of potential issue that is a technical issue that may come into play wrt the concept of a random spectator observer (I put the full thread in so folks get the gist of the total discussion). Firstly, don't get me wrong - I would love to see a Spectator mode if you can address the issues I outlined and provide a technical solution that would be scalable & performant. Currently, the client-server structure of the game involves information transfer that represents a player client and the info that gets transfered as we move out ships, fire our weapons etc. This is coupled w/ ship characteristic info that is tied to a release (why your replays stop working after a minor release version update - the characteristic files don't match the message/position capture replay files to reproduce your replay properly). This structure is reflected in the replay files - when playing a replay, it's essentially replaying the message transfer as if you are a player client and sufficient info re: enemy ship positions and movement are captured by the file to recreate a already played battle (w/ the exception of a few replay artifact bugs like the behavior of torp aim indicators as an example). If a number of random additional players are added to the game even in an observer mode, this increases the amount of server messaging traffic required to effectively support a particular game. The current 12x12 starting player format currently already shows some cracks w/ being able to keep up w/ the necessary traffic in scenarios such as: Players w/ connection bandwidth issues, internet node response issue or slower PCs tend to experience greater lag or frequency of DCs. An extreme example is during a CC event where they tried to play a 12x12 CV match - the response time/lag issues wrt controlling any of their air wings was hilarious due to the messaging increase the plane squadrons added to the server response load over a surface ship only game. This isn't an internet or PC performance issues as all the CCs had performant HW w/ what in many cases were streaming capable internet services - it does reflect some technical limits to the game architecture. The "randomizing of a game & allowing a observer to watch a particular player idea" I actually am all for - it'll be interesting if WG can implement this in a way that doesn't impact the game for the actual players in a match.
  10. New spectator mode?

    If you’re allowed to see the unconcealed movements of both teams, it provides sufficient info for players to deploy to counteract enemy moves. This is why casted competitive streams use delayed feeds to try to use the time delays to date the usefulness of team deployments & positions to minimize the impact of this reveal (I.e. the teams have discovered most of the info thru the game before the stream view is an unfair advantage minimizing the usefulness of sniping). Some clans have gone so far as to attribute their difficulties to their streamers and have implemented rules to require the stream delays (along w/ some more controversial actions taken by a particular clan). There are a couple of levels of spectator issues that can be used by players to gain an unfair advantage. The first paragraph describes the “arena e-sport” view issue. The second paragraph refers to info from a particular streamer player view that can be misused. Streamers have typically used either stream delays or various artifacts such as their webcam to block the minimap view. For the OPs reason for wanting to learn from following a particular player, the minimap would be key to understanding why a player may be moving to a certain location or executing a certain strategy. You currently can already do a version of what you’re suggesting w/ your own team once you die - you can cycle to any ship still alive on your own team and experience what they’re doing as they play.
  11. New spectator mode?

    It’s unfortunate that a fun & reasonable enhancement falls victim to the darker implulses of human nature. I too wish this were available but the following happens: The game currently allows for a free floating camera for ships on your own team and what’s visible to your team. When a full spectator mode is permitted, the following happens: Those who have popular twitch streams often insert delays in their streams because there are those who will “snipe” the streams to get unfair intelligence on the strategies employed by the enemy forces. An in-game spectator mode will present the same problem. Unfortunately, too many players will make use of the feature to view the entire playing field & pass the info along to those still alive on their team, giving an unfair advantage to teams w/ the ethically challenged players.
  12. WG indicated that the USN Cruiser split promos will span a couple of releases; akin to what they did w/ the French BBs. Since WG went to a 4-wk release cycle a couple of releases ago, this would make the 7.5 target date May 23and 7.6 date June 20. The USN Cruisers have not shown up on a PT yet which should happen prior to the actual release. Based on this, it’s likely that the Halsey commander mission or collection may be in the 1st release, with the actual split happening in the following release (June 20). If they do a similar thing to the French BBs, they may offer early access to the ships, but there is no indication yet that this will happen. The PT cycle info for 7.5 should be out shortly - that should give you a good read of how the rollout will be structured - not long to wait!
  13. I can see in a early game scenario where a Asashio can spot a Gearing for a concentrated bunch of teammates that can concentrate their fire; a Gearing may be reluctant to engage a Asashio. That would be attributable to the fear of spotting for the team rather than fear of the DD itself. In a later game scenario w/ no or spotty support, the Gearing should be able to at least chase an Asashio from the cap & if the Asashio gets overly bold (given equal player skills), the Gearing’s ROF, HP & slight speed advantage should be able to easily take it down. I haven’t seen many competent Gearing Captains running from Asashio with the exception of being reluctant to engage due to enemy team focus fire.
  14. Given this datapoint, it would suggest the calculation was done using US dollars. The USD exchange equivalent for your purchase is in the upper-$20 range which would be consistent w/ your suspicion - the website describing the offer also described it in dollar terms so they most likely did the simpler thing & did a currency conversion equivalent.
  15. First time ever (for me anyways)

    Congrats on the Solo Warrior! Toughest achievement - well done!
×