Jump to content

Gold_Firing_Noob

Players
  • Content Сount

    19
  • Joined

  • Last visited

  • Battles

    2936
  • Clan

    [HOG]

About Gold_Firing_Noob

Recent Profile Visitors

156 profile views
  1. Gold_Firing_Noob

    suprise suprise i dont even play wow

    The hits keep coming...GG WG. An excellent way to piss off players even more....
  2. Gold_Firing_Noob

    Godawfully slow and laggy port

    Port is laggy as [edited]and managing clan page or enabling flags/consumables or in fact anything that tries to recall data is broken slow.
  3. Gold_Firing_Noob

    Updated Operations

    Thanks mate... I'll keep an eye on this.. it was making me scratch my head a bit.
  4. Gold_Firing_Noob

    Updated Operations

    Most operations I spend my time alight no matter the ship I go out in... worst one last night was ten fires on me over the course of the operation... on average I get set alight six fires which in cruisers mean I have to burn through repairs just to stay afloat let alone be in good enough health to deal with the suicide dd. By comparison I managed to set between 1 and 3 fires per operation. Another curiosity.. last night when we had three enemy visible only for both myself and another player both had indication that all three where targeting each of us at the same time...WG your AI buff cheat is a little too obvious.... try to turn the difficulty up by a smidgen and not just try to screw your player base.....not all of us are unicum legends, some like me are just average potato types wanting to spend time in the company of others who enjoy playing ship combat games.
  5. Gold_Firing_Noob

    New Unsporting conduct system needs to be fixed

    same issue happening to multiple clan members who play together.
  6. Gold_Firing_Noob

    randomly not being able to get into a game

    same cross multiple members of our clan
  7. Gold_Firing_Noob

    penalised for server drop

    Our clan sees a lot of cases where three of us will be div'd and one will not enter the battle but the other two do. It is random who does not join but by simple observation it is most often the leader of that Div. Even setting the leader as the person with best ping does not clear the problem. Often closing the client and then trying to re-open in order to join the battle results in the client not even opening the port; the only guaranteed way to get into the battle is shut client and the [edited]WG game center and then re-open the game client. I would assume this is working as intended based on the regularity with which it impact members in or clan. for all the fanboyz: I7 8GB Ram Nvidia 4GB Graphics OS and graphic on latest stable drivers and patches No Mods
  8. Gold_Firing_Noob

    Bug Reports

    Last update has decimated graphic performance..... three of us play together a lot and all experience the same issues. 1) graphics stuttering and frames dropping severely when there is a lot going on in battle. 2) randomly being dropped totally to desktop when entering battle and then having to wait two to three minutes to logon and get back into battle. 3) having random cases where the LMB refuses to fire weapons for a few seconds at a time. 4) not seeing results screen and being unable to select any tab or the division in order to ready up for next battle. 5) ctd and disconnects in battle 6)) eventhough running 4GB graphic cards we are being forced to turn all graphic settings down to minimum in order to prevent frame rates dropping into unplayable territory. We are located UK, East Europe and Africa. OS win 7 / 8.1 / 10 Two play with mods and one does not. display cards are nvidia / nvidia / amd. problems are independent of who leads the division / OS/ display card/ ISP / Mods... i.e....WG.. you need to employ better coders and QC staff.
  9. Gold_Firing_Noob

    Bug Reports

    to add to the other sterling work done by the last group of %^$%^ that compiled the game code for this incarnation of hell: when you die and try to cycle to another allied ship using LMB or RMB the game hangs..... well done, please give me another reason to take my money elsewhere.
  10. Gold_Firing_Noob

    Excessive draw on Graphics card when in port.

    maxing out the temp on graphics cards not really a problem.... +1
  11. Gold_Firing_Noob

    Bug Reports

    CTD when entering Battle and excessive GPU load when in port: System Drivers and OS: OS is patched to latest with all hotfixes (both Technet and public). Graphics card is Nvidia family with 4GB memory and running latest stable driver sourced directly from NVIDIA. Running latest MSSE and have done additional system scans using other security products. Problem Observed: When in game the GPU load is 30-40% and card runs at under 40 deg C When I return to port after battle or start the game in port then the GPU load shoots up to 100% and card runs at 70 deg C This issue is particular to Wargaming WOWs and no other software on my machine creates the same GPU load and temp spike. Attempts to isolate observed spike in GPU load and temp: ALT-TAB to another window results in immediate drop in GPU load and corresponding drop in card temp indicating that the GPU load is related to the window being focused (i.e.WOWS) Leaving the focus on the WOWs game and just letting it idle does not see a reduction in GPU load or temp over observed periods of 45 to 60 min. Checking with other more graphic demanding games like Metro 2033 and ultra HD modded C.O.P. does not result in 100% GPU loads on idle or even in game. Selecting battle in WOWS sees an immediate drop in GPU load and corresponding drop in card temp. Observations: The WOWs process is using the GPU inefficiently in port and indicates either poor code or worse that the GPU is being used for non game related work when in port. CTD happen often when going from port to Battle and this corresponds with the drop in GPU load and stopping of whatever inefficient process is being run by WOWS on the GPU in port. Coupled with the GPU load in port is associated low level network traffic, I have run a network capture on that traffic and still need to decode it into something meaningful. Thoughts: The GPU load and temp spike on the card is a direct result of WOWS when in port and should be resolved by Wargaming. (be it inefficient code or otherwise) The only other family of application that I can think of that runs a GPU at 100% are BIT Miners and data crunchers... but neither of those should be run by wargaming on my hardware.
  12. Gold_Firing_Noob

    Excessive draw on Graphics card when in port.

    Just to save time: OS is patched to latest with all hotfixes (both Technet and public). Graphics card is Nvidia family with 4GB memory and running latest stable driver sourced directly from NVIDIA. Running latest MSSE and have done additional system scans using other security products. Problem Observed: When in game the GPU load is 30-40% and card runs at under 40 deg C When I return to port after battle or start the game in port then the GPU load shoots up to 100% and card runs at 70 deg C This issue is particular to Wargaming WOWs and no other software on my machine creates the same GPU load and temp spike. Attempts to isolate observed spike in GPU load and temp: ALT-TAB to another window results in immediate drop in GPU load and corresponding drop in card temp indicating that the GPU load is related to the window being focused (i.e.WOWS) Leaving the focus on the WOWs game and just letting it idle does not see a reduction in GPU load or temp over observed periods of 45 to 60 min. Checking with other more graphic demanding games like Metro 2033 and ultra HD modded C.O.P. does not result in 100% GPU loads on idle or even in game. Selecting battle in WOWS sees an immediate drop in GPU load and corresponding drop in card temp. Observations: The WOWs process is using the GPU inefficiently in port and indicates either poor code or worse that the GPU is being used for non game related work when in port. CTD happen often when going from port to Battle and this corresponds with the drop in GPU load and stopping of whatever inefficient process is being run by WOWS on the GPU in port. Coupled with the GPU load in port is associated low level network traffic, I have run a network capture on that traffic and still need to decode it into something meaningful. Thoughts: The GPU load and temp spike on the card is a direct result of WOWS when in port and should be resolved by Wargaming. (be it inefficient code or otherwise) The only other family of application that I can think of that runs a GPU at 100% are BIT Miners and data crunchers... but neither of those should be run by wargaming on my hardware.
  13. Gold_Firing_Noob

    Holiday Lottery - Try your luck!

    Congrats to all winners and also to the OP for running this giveaway. Hope the visit to the hospital was not serious.
  14. Gold_Firing_Noob

    Holiday Lottery - Try your luck!

    Hi there, I would definitely like to join and participate in the raffle... a truly grand idea!
  15. Gold_Firing_Noob

    Bugs

    Identical issue.
×