Can not interact with the game

[ASionville]

Hi there!

I don't know if the problem comes from BeamNG-Py or BeamNG Research, but when I start a scenario (whatever it is), I can not interact at all with the game (mouse / keyboard / controller doing nothing)

Does anyone have this issue too?

[masskro0]

Do you have an AI running? If so, the AI must pass all waypoints until you can control it. You can also add another vehicle without waypoints and control that or remove the waypoints from the AI.

[ASionville]

Here is the script I use, you'll find all your answers in it :

import sys
from time import sleep
import numpy as np
from scipy import interpolate
from beamngpy import BeamNGpy, Scenario, Road, Vehicle, setup_logging

def main():
    setup_logging()

    beamng = BeamNGpy('localhost', 64256, home="../../research/trunk")
    scenario = Scenario('west_coast_usa', 'ai_sine')

    vehicle = Vehicle('ego_vehicle', model='etk800', licence='AI')

    orig = (-769.1, 400.8, 142.8)

    scenario.add_vehicle(vehicle, pos=orig, rot=(0, 0, 180))
    scenario.make(beamng)

    bng = beamng.open(launch=True)
    try:
        bng.load_scenario(scenario)

        bng.start_scenario()

        while True:
            bng.step(60)
    finally:
        bng.close()

if __name__ == '__main__':
    main()```

[masskro0]

I just tried your code and I could control the car manually and look around as well. I tested it in BeamNGpy 1.15 and BeamNG version 1.9 revision 45. Do you get any errors in the BeamNG console?

[ASionville]

I work with BeamngPy 1.16.5 and Beamng.research 1.7.0.0 Where can I find the 1.9?

Also, I found that when I plug/unplug a controller, then I can control the game (if not, even the escape key doesn't do anything)

[masskro0]

I'm using an older version than yours. Version 1.9 gets printed on the Python console but I assume it's research version 1.5 (if I'm not mistaken, pretty confusing). You are using revision 47 while I'm using revision 45. Just some ideas: check if the throttle is assigned to any key (default should be the up arrow), check if any command blocks further computation by debugging, try starting BeamNG manually and load a scenario (without Python). Also, is this your full code? There are many imports which aren't used and since I don't know how the rest of your code looks like I can only make assumptions of the code that you've provided.

[ASionville]

1 - I can't check the keys as I can't do anything, even move the camera or trigger the UI 2 - This is my full code, I don't care of the imports I don't use (was only supposed to be a quick test)

[pascale-commits]

I also tried your code and it worked fine on my machine. Can you paste the log, or preferably send it to me by mail? It's pmaul(a)beamng.gmbh

On the versioning: You are talking about three different versioning types:

1. the internal versioning system depending on the build, which is printed on the console and log
2. the svn versioning, which is the revision number
3. the versioning of the BeamNG.research build, where the latest is 1.7.0.0 which uses revision 47 I think its safe to ignore number 1.

[ASionville]

Hi @pascale-commits ! I'm not currently home, so I can't send you this right now. I will send it sunday afternoon or monday.

Thanks

[ASionville]

Email sent

[pascale-commits]

Hi, excuse the delay.

This might be a bug that can be worked around at the moment by disabling all online features. To do so you can simply delete the BeamNG.research directory in your C:\Users\<yourPCUserName>\Documents folder. When starting up BeamNG through a script you do not need to do anything, but if the first startup is manual, then choose 'No, thanks' in the 'Enable Online Features?' dialogue.

edit: this bug should not appear when using v1.7.0.1, it should be possible to use online features with that build, please reopen the issue if it doesn't