PC Q Not Acknowledging Sifa Still On Dostos

Discussion in 'Troubleshooting' started by mattwild55, Oct 5, 2021.

  1. mattwild55

    mattwild55 Well-Known Member

    Joined:
    Mar 19, 2019
    Messages:
    687
    Likes Received:
    2,711
    Er, pretty much as the thread title suggests - surprised this wasn't patched. Does anyone know of any workarounds?
     
  2. GuitarMan

    GuitarMan Well-Known Member

    Joined:
    Aug 15, 2020
    Messages:
    583
    Likes Received:
    781
    Which route is this happening on?
     
  3. mattwild55

    mattwild55 Well-Known Member

    Joined:
    Mar 19, 2019
    Messages:
    687
    Likes Received:
    2,711
    Dresden.
     
  4. GuitarMan

    GuitarMan Well-Known Member

    Joined:
    Aug 15, 2020
    Messages:
    583
    Likes Received:
    781
    I haven’t come across this one, will try again tonight.
     
  5. Michael Newbury

    Michael Newbury Well-Known Member

    Joined:
    Dec 11, 2016
    Messages:
    4,024
    Likes Received:
    3,260
    Ran a service with the Dosto tonight to Miessen and had no issues with the Q key to acknowledge SIFA.
     
  6. mattwild55

    mattwild55 Well-Known Member

    Joined:
    Mar 19, 2019
    Messages:
    687
    Likes Received:
    2,711
    Strange, I wonder what's going on with my system then? I noticed it was fine in the stream the other night but didn't know if Matt was using a different control method.
     
  7. Kobebeef

    Kobebeef Active Member

    Joined:
    Oct 13, 2020
    Messages:
    217
    Likes Received:
    207
    If the q key don't work then restart service, should temp fix it
     
  8. Michael Newbury

    Michael Newbury Well-Known Member

    Joined:
    Dec 11, 2016
    Messages:
    4,024
    Likes Received:
    3,260
    When Matt plays on PC he generally uses a Xbox controller.
     
  9. sequencer2k16

    sequencer2k16 Well-Known Member

    Joined:
    Jun 20, 2020
    Messages:
    833
    Likes Received:
    1,078
    You took over the Dosto from an AI right?

    Helped someone a few days ago who had exactly the same problem.
    In the end it turned out that the bug only occurs with Dostos that were taken over from AI.

    Workaround: Do not take over AI Dostos. ;)
     
  10. Jinoss17

    Jinoss17 Well-Known Member

    Joined:
    Aug 21, 2020
    Messages:
    495
    Likes Received:
    1,109
    I have the exact same issue but I had it with the BR146 taken from AI: I think it's a general issue, not just related to Dostos.
     
  11. phillip.good

    phillip.good Well-Known Member

    Joined:
    Sep 23, 2020
    Messages:
    346
    Likes Received:
    526
    I am getting the same issue on PS5 but not every dosto service
     
  12. mattwild55

    mattwild55 Well-Known Member

    Joined:
    Mar 19, 2019
    Messages:
    687
    Likes Received:
    2,711
    Many thanks! It's a pain because I normally play the game by spawning on foot and then taking over a service but I guess I'll adapt until it's patched.
     
  13. Mr.Drew

    Mr.Drew Member

    Joined:
    Jul 26, 2018
    Messages:
    57
    Likes Received:
    36
    I have the same or a similar problem on XBOX ONE X - also happens when not using AI services btw.

    When you hit the B button (similar to Q button on PC) on Xbox, it does not acknowledge PZB or Sifa. So nothing happens. You would have to flick the button in the cab by using the control stick, but this takes too much time while driving. This happens on the new BR143, the new DoSto Controllcar for Dresden and as well on the BR 146.2. It not only happens on Riesa-Dresden, but also when you select the new BR143 on MSB for example, the B button still does not acknowledge SIFA or PZB.
     
  14. phillip.good

    phillip.good Well-Known Member

    Joined:
    Sep 23, 2020
    Messages:
    346
    Likes Received:
    526
    Unfortunately it’s not just taking over an AI dosto; that’s what I had originally thought. It appears to be a random issue that may only be one of the 3 dosto type services…. I just haven’t worked out which one as yet

    either way it’s still a bug!
     

Share This Page