Connection lost without internet drop or instability

Discussion in 'Bug Reports' started by Matheus Machado, Feb 15, 2020.

  1. Matheus Machado

    Matheus Machado Registered

    Joined:
    May 4, 2017
    Messages:
    62
    Likes Received:
    30
    It happened during the last bmw m2 qualifiers. Both times this line was the first message related to anything regarding the connection in the trace file, which are included below.

    6606.01s JNILog.cpp 33: New Message received: Connection lost
     
  2. Matheus Machado

    Matheus Machado Registered

    Joined:
    May 4, 2017
    Messages:
    62
    Likes Received:
    30
    adding to this topic. Had the same in VEC servers while practicing today. Trace showed the same messages it was in the logs posted above.
     
  3. Kevin van Dooren

    Kevin van Dooren Registered

    Joined:
    Sep 21, 2017
    Messages:
    107
    Likes Received:
    74
    These are the last lines in every trace you posted as far as I can see, and they actually say that you might have a controller driver issue:

    2432.75s hwinput.cpp 1753: Unacquiring device "Logitech G27 Racing Wheel USB" (if this is the last line in your trace.txt, your controller driver is probably buggy)
    2432.75s hwinput.cpp 1761: Now releasing same device (if this is the last line in your trace.txt, your controller driver is probably buggy)
    2432.79s hwinput.cpp 1763: Device successfully uninitialized
    2432.79s hwinput.cpp 1753: Unacquiring device "Controller (XBOX 360 For Windows)" (if this is the last line in your trace.txt, your controller driver is probably buggy)
    2432.79s hwinput.cpp 1761: Now releasing same device (if this is the last line in your trace.txt, your controller driver is probably buggy)
    2432.79s hwinput.cpp 1763: Device successfully uninitialized
    2432.79s hwinput.cpp 1753: Unacquiring device "Controller (XBOX 360 For Windows)" (if this is the last line in your trace.txt, your controller driver is probably buggy)
    2432.79s hwinput.cpp 1761: Now releasing same device (if this is the last line in your trace.txt, your controller driver is probably buggy)
    2432.79s hwinput.cpp 1763: Device successfully uninitialized
    2432.79s hwinput.cpp 1753: Unacquiring device "T500 RS Gear Shift" (if this is the last line in your trace.txt, your controller driver is probably buggy)
    2432.79s hwinput.cpp 1757: Device release skipped as part of workaround ...
    2432.79s dynman.cpp 2994: Entered DynMan::Exit()
     
  4. Matheus Machado

    Matheus Machado Registered

    Joined:
    May 4, 2017
    Messages:
    62
    Likes Received:
    30
    These lines also pop up when exiting a server normally and the way I read it it should be the absolute last line, which is not the case as there are 6 lines below it every time. I have however looked at these lines before and reinstalled drivers to be sure and it didn't change a thing. Maybe some s397 dev can clarify it though.
     
  5. Matheus Machado

    Matheus Machado Registered

    Joined:
    May 4, 2017
    Messages:
    62
    Likes Received:
    30
    Happened today during the practice session of the bmw m2 cup as well, here is the trace log, realtime log and steam plugin log which was also generated this time.

    Connection to teamspeak server and discord was normal at the time, no drops.
     
    Last edited: Jun 20, 2020
  6. D Nichols

    D Nichols Registered

    Joined:
    Jun 18, 2019
    Messages:
    32
    Likes Received:
    16
    Happened to one of our cars in todays D1 VEC race, twice. I've linked them here.
     
    Matheus Machado likes this.
  7. Matheus Machado

    Matheus Machado Registered

    Joined:
    May 4, 2017
    Messages:
    62
    Likes Received:
    30
    Another race day another drop. BMW M2 cup practice again this time. TS kept normal with not even packet loss reported. Steam plugin.log generated this time as well, renamed due to forum not allowing upload of .log files.
     
  8. Matheus Machado

    Matheus Machado Registered

    Joined:
    May 4, 2017
    Messages:
    62
    Likes Received:
    30
    When I joined the session standings were certainly not correct as well. It persisted after the rejoin.
     

    Attached Files:

Share This Page