1. Trouble with the game?
    Try the troubleshooter!

    Dismiss Notice
  2. Issues with the game?
    Check the Known Issues list before reporting!

    Dismiss Notice
  3. Before reporting issues or bugs, please check the up-to-date Bug Reporting Thread for the current version.
    0.36 Bug Reporting thread
    Solutions and more information may already be available.

Xbox 360 controller dosent work after loading new map

Discussion in 'Troubleshooting: Bugs, Questions and Support' started by NaxNir, Apr 10, 2014.

  1. NaxNir

    NaxNir
    Expand Collapse

    Joined:
    Jan 28, 2014
    Messages:
    618
    I loaded up a map and used my Xbox 360 controller it was working fine and then exited and loaded a new map. The 360 controller did not work. The only way to solve is to quit BeamNG.Drive and load the map again. Is there a simpler way?
     
  2. HadACoolName

    HadACoolName
    Expand Collapse

    Joined:
    Aug 3, 2013
    Messages:
    1,931
    Think yourself lucky mate. I cant even get a controller to work
     
  3. destroyer8769

    destroyer8769
    Expand Collapse

    Joined:
    Dec 9, 2013
    Messages:
    550
    Same here, i have the afterglow controller, tried all the inputmaps.
     
  4. akino_germany

    akino_germany
    Expand Collapse

    Joined:
    Aug 19, 2013
    Messages:
    63
    This is a known bug. Sometimes it works after a map change and sometimes not.
     
  5. n0ah1897

    n0ah1897
    Expand Collapse

    Joined:
    Jan 31, 2013
    Messages:
    625
    Ctrl+m reloads inputs. You can see if that works.
     
  6. jammin2222

    jammin2222
    Expand Collapse

    Joined:
    Sep 15, 2013
    Messages:
    386
    I seem to remember the devs saying this is a tricky bug to fix as its very intermittent.

    I use an xbox360 controller but got a G27 wheel a few days ago and I have been trying to spot a pattern to when it happens but nothing really jumps out as a strong cause.

    For the 360 controller I did notice that its more likely to do it if you have opened the map editor and then changed maps, and CTRL + M will not fix it for me at all. Almost never does it if i don't touch the map editor. Though I would say I open the map editor more often than not. This could be why I notice it more after editing a map. Its the closest thing to a pattern I can spot.

    I haven't had the G27 wheel long enough to make a fair judgment but It seems to stop working 80% of the time when I minimize the game and come back to it. This time CTRL+ M seems to bring it back to life. This is a different bug it would seem as the 360 controller never does this. I haven't used the map editor much since getting the G27 wheel so I haven't noticed it stop working after a map change at all yet.

    I did notice that Shift + M brings up a controller calibration window with some options but I got scared and didn't mess with anything.

    I hope they figure out whats causing it soon.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice