Jump to content

Gardner2

Distinguished Civilian
  • Posts

    1,111
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by Gardner2

  1. On 11/14/2018 at 8:28 AM, C. Wilson 1st MRB said:

    Not sure why you posted a ban report, when he was only banned for a week. I have changed it to a ban request and upgraded his ban from 1 week to 1 month.

     

    Signed,

     

    C. Wilson, Military Police Deputy Chief.

    In the past I received a demerit for not posting one, so I always do now. 

  2. Ive run the verify game files on my side (install was fresh 3 weeks ago due to this being a brand new system. 

     

    Not getting error codes in console now, but still getting lag spikes on stock maps on the public server.   I see someone else has also reported lag spikes on the pub now as well. 

     

     

  3. I'm averaging around 270fps in game, this appears to be mainly stock maps only on our server (pub, have not been on the custom to see if it does the same). We played on a custom the other day and I do not remember seeing any lag during it. 

    And as mentioned when on other servers like the one gun game one I frequent which is all custom maps/levels I do not experience any lag. 

     

     

  4. 18 hours ago, Yamagata 1st MRB said:

    Hmm, I think it was determined that the steadycam error was related to Video Drivers, might be worth looking for driver updates.  Have the newest Nvidia drivers install, and literally less then a month old brand new laptop, all drivers up to date and current. 

     

    Have you noticed when exactly you experience these lag spikes?  If what I found before is true, it might be an unoptimized custom map... But if you're getting those errors on maps like Donner or something, then there is a bigger issue.  All stock maps on the pub server, seems to be totally random, sometimes I'm running, sometimes I shooting (really sucks as I'm usually being shot back at and cant move lol), sometimes callings for medic, sometimes just standing still in a room all alone.

     

    I wonder if someone has that wood_creak1.wav available for download, it might need to be put on the FastDL server to speed up the server-to-client communication.  The odd thing is, you should be getting all the necessary files as soon as the server initiates a map change or when you connect.  Ultimately, there is an issue between you and the server caching sounds, which is causing your lag.

     

    Any ideas, Medical Supply Staff?

     

  5. fixed most of the errors, but still getting random lag spikes on the server. 

     

    Got this error this morning: 

    2555.105049 BlockingGetDataPointer:  Async I/O Force ambient\materials\wood_creak1.wav ( 2071.81 msec /  2192.38 msec total )
    Error reading weapon data file for: weapon_ifm_steadycam
     

     

  6. Name: K. Gardner

    Rank: Sgt.

    Type of issue: (Software, Hardware, Steam, Not sure) Software

    Brief Description of Issue:  Only happens on our pub server, no issues on other servers so far, keep getting random lag spikes.

    Get the following errors in console:

    1443.481109 BlockingGetDataPointer:  Async I/O Force weapons\mp40_shoot.wav ( 1826.49 msec /  2175.78 msec total )
    1504.581986 BlockingGetDataPointer:  Async I/O Force physics\glass\glass_impact_soft2.wav ( 2047.31 msec /  2170.41 msec total )
    Error reading weapon data file for: weapon_ifm_steadycam
    MP3 initialized with no sound cache, this may cause janking. [ bandage\bandage.mp3 ]
    Failed to create decoder for MP3 [ bandage\bandage.mp3 ]
    MP3 initialized with no sound cache, this may cause janking. [ bandage\bandage.mp3 ]
    Failed to create decoder for MP3 [ bandage\bandage.mp3 ]
    *** Invalid sample rate (0) for sound 'bandage\bandage.mp3'.
    Attemped to precache unknown particle system "blood_impact_red_01"!
    Attemped to precache unknown particle system "blood_impact_green_01"!
    Attemped to precache unknown particle system "blood_impact_yellow_01"!
    Attemped to precache unknown particle system "slime_splash_01"!
    Attemped to precache unknown particle system "slime_splash_02"!
    Attemped to precache unknown particle system "slime_splash_03"!
    The server is using sv_pure 0.  (Enforcing consistency for select files only)
    #Game_connected

    803.560335 BlockingGetDataPointer:  Async I/O Force player\damage\female\minorpain2.wav (  181.68 msec /   303.89 msec total )
    810.330735 BlockingGetDataPointer:  Async I/O Force physics\plastic\plastic_box_impact_soft2.wav (  116.10 msec /   287.17 msec total )

     

     

    ***Medical Supply Staff ONLY Below this line***

    Current Status: Resolved

     

    Main Technician: Yama

    Supporting Technician: J. Candy

  7. Name:H40 MADN3SS

    SteamID:  [U:1:150720583]

    Reason: Multiple TK's, very disrespectful in voice chat (typical 12year old kid spewing that he's a god crap).

    Duration: 1 week

    Demo: no

     

    Responded to a pm from Harding regarding multiple tkers, gave everyone who was tking a kick and rewarned, this kid kept going thought he was untouchable. 

     

  8. Name: LsK   BZS

    STEAMID:  [U:1:7805609]     

     

    Reason: trolling and tk/tw.  Bruce Lee had warned him several times verbally, I gave him a verbal warning when he intentionally started trying to get in front of me while sniping at which point he turned around and headshot me.  

    [SM] ✦ LsK   BZS made a headshot
    ✦ LsK   BZS killed Sgt. K. Gardner [1st MRB|MP] with p38.
     

    Ban Duration: gave him a 1 day ban, if an officer would like to increase I have no issues with that as he will probably repeat. 

     

    Demo?: No. 

     

     

  9. Name: 3shaggy

    SteamID: did not grab before hitting ban sorry, will try to find (I suck at finding IP's when I forget to do a status first)

     

    Reason: Came back from being afk, found people complaining about tks and saw 3shaggy TK a player in spawn in front of me, warned to not do it again 3shaggy argued they were not (was sitting at -2 on score board) I kicked them for arguing with an admin.  Came back and immediately tk'd again and argued that they were not, at this point I found out another admin had recently muted them for trolling/mic spam and kicked once before already.  

     

    Duration: 1 week. 

     

    Demo: No. 

     

     

×
×
  • Create New...