Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

59 Excellent

1 Follower

About Armastadt

  • Rank
    Potato Aim

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Armastadt

    Ping, Latency, Jitter, Loss

    Takes that long to fact check. Great post by the way.
  2. Also, evidence? What evidence did you submit? Did you report on a section of replay that shows him allegedly ESP tracking players? Head shot through walls? Did you capture your conversation and gameplay and submit that? A lot of the results depend on the evidence. If he's as blatant as you say, he'll get caught eventually. You can't use ESP and not have it affect your game play, like staring, checking, and tracking non-visible players. It's human nature to pay attention to cues in your visual field.
  3. @PUBG_Sheepy So does this tell you all you need to know with respect to the bug?
  4. Sure. But before I go to all that trouble, let me just recap that this issue wasn't present up until update #10 then has been constantly present until update #17 which seemed to address it as a known issue, then immediately regressed in update #18. The error that gets thrown in the crash files is the following: <ErrorMessage> LowLevelFatalError [File:D:\wk\tsl-client-branch\build\UnrealEngine\Engine\Source\Runtime\CoreUObject\Private\Serialization\AsyncLoading.cpp] [Line: 1375] No outstanding IO, no nodes in the queue, yet we still have 'PackagesWithNodes' in the graph. </ErrorMessage> This error has been present since at least 3/27/18, as that is the earliest crash file I've kept around just to document the occurrence of this issue. Judging by forum search results, it looks like it probably started round 3/17/18: There's basically a 14 pages dedicated to this issue in this thread: It happens on Intel and AMD. It may happen more with over clocked AMD chips, but the AMD overclocking crash seems to be a separate issue based on other forum threads. It happens on all all versions of Windows. It happens whether you uninstall and reinstall the game. It happens whether you turn HPET (High Performance Event Timer) on or off, though some report success with turning off. It happens whether or not you update graphics drivers, or change graphics cards. It happens regardless of Windows updates. It happens when you have the latest BIOS updates. It happens whether you start Steam as an admin or not. It happens whether you've verified the program files in Steam or not. BattleEye starts correctly, the service is running. You can see the extent that some people have gone to try and troubleshoot this issue: Now for what I've tried with respect to your basic troubleshooting guide: 1. Try turning it off and back on again Seriously? Yes. 2. Remove all launch options There are no launch options to remove, I launch it from Steam. However Steam launches the game is how it starts from the day in purchased and installed the game until now. 3. Verify the integrity of the game files Done that, multiple times. Both as administrator and not. 4. Manually remove configuration settings Done that. 5. Update Windows Of course. 6. Update your graphics card drivers Yes, of course. Including using different video cards. 7. Run Steam as Admin Yes. 8. Launch the game from Steam Always. 9. Check that BattlEye is running correctly Yes. Service is there, and starts correctly. 10. Add exception rules to your anti-virus and firewalls Exceptions are already present, for Production, Test and Experimental. 11. Connect directly to your router/modem No. Impractical and not related to firewall or modem, since clearly reducing the number of active CPUs to one solves the problem. It's a threading issue. 12. Enable Port Forwarding for PUBG No. Not necessary as it's not related to a port issue. Since clearly reducing the number of active CPUs to one solves the problem. It's a threading issue. 13. Attempt tethering to a mobile device No. Impractical and not related to the way I connect to the Internet or my ISP, since clearly reducing the number of active CPUs to one solves the problem. It's a threading issue. 14. Uninstall/reinstall PUBG Yes. Multiple times. Which of the three crashing issues you are experiencing: 1. When launching the game 3. When leaving a match Your IGN: Armastadt Operating System: Windows 8.1 Enterprise 64-bit (6.3, Build 9600) (9600.winblue_ltsb_escrow.180718-1800) Language: English (Regional Setting: English) System Manufacturer: Gigabyte Technology Co., Ltd. System Model: To be filled by O.E.M. BIOS: F8 Processor: AMD A10-7870K Radeon R7, 12 Compute Cores 4C+8G (4 CPUs), ~3.9GHz Memory: 8192MB RAM Available OS Memory: 8136MB RAM Page File: 4844MB used, 6491MB available DirectX Version: DirectX 11 Card name: NVIDIA GeForce GTX 1080 Ti Manufacturer: NVIDIA Chip type: GeForce GTX 1080 Ti DAC type: Integrated RAMDAC Device Type: Full Device Device Key: Enum\PCI\VEN_10DE&DEV_1B06&SUBSYS_374C1458&REV_A1 Display Memory: 15188 MB Dedicated Memory: 11120 MB Shared Memory: 4067 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) Monitor Name: Generic PnP Monitor Attached is a crash on startup, just after the credits/copyright screen. UE4CC-Windows-56E2500E453B4A9BCE244CB0FECD7C86_0000.zip
  5. Just need faster reflexes man. (Also, just to be clear, I was trying to be funny with the remove single fire comment.)
  6. Armastadt

    A "thank you" deserved.

    My guess is that we will never see a stand alone, offline training mode. I think the server implementation is too tightly tied to cloud services and would take too much effort to refactor to make it stand alone.
  7. They should get rid of single fire on weapons capable of auto, that's gotten me, and probably many others, killed more than being on burst instead of auto.
  8. Update #20 and still no fix for crashing during loading credits and after game when re-entering the lobby. 5 1/2 months, 10 updates, no permanent fix.
  9. There is no reason to ban harmless stream snipers, and unfortunately impossible to conclusively prove actual malicious stream sniping (using Twitch to gain advantage) unless there is some sort of Twitch/PUBG integration for detection and easily denied. ("But I didn't know _____ was in my game.").
  10. Armastadt

    FREEZING in LOBBY after the new patch

    Seems that way. Add me to the list of those experiencing this.
  11. Armastadt

    re: It’s Time To FIX PUBG.

    Fired it up to test things out. 1) Still suffering from a crash after the credits on game start up, which has a work around of messing with CPU affinity. This has been present for 5 months. 2) Now, seems that a lobby hang, bug is present. After entering game lobby doesn't completely load, UI becomes unresponsive, with PUBG theme playing in background. I would say it's time to fix PUBG, for sure.
  12. And.....Update #19 still has no fix for crashing during credits. Whatever you did on Update #17 fixed it--so go back and figure it out. Oh, great, and you've added a lobby hang bug too. Fan-freaking-tastic. 5 Months, 9 updates, no (permanent) fix, with more bugs added as a cherry on top.
  13. Armastadt

    What is the idea?

    Give him a break, he just came from ballet practice.
  14. Armastadt

    reasons why gunplay is not fair

    What @DeadlyEggXoP said. And, in this engagement, there is basically one bullet difference in the outcome here. Had the camper landed one more shot, the pusher would be dead instead. I'd write that off to reaction time and latency as described above.