You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I'm trying to disable collision between vehicles via beamngpy.
In BeamNG the setting is Options->Gameplay->Simplified collision physics.
When changing this setting, the settings.json file in the user folder gets the new line ""disableDynamicCollision":"true""
Using the settings.change("disableDynamicCollision", "true") method works, as long as the disableDynamicCollision value is not already in the settings.json file.
If the value exists and is set to false, the method changes the setting in the json file, but in game the collisions are still enabled
(On further testing, this is not the deciding factor wether it works or not, as just now it failed to apply the settings even after deleting the line before starting)
In the in game settings menu, the simplified physics option is not selected, it does however show the warning below the setting, that normally only shows up when the setting is enabled.
This is my testing script, it has so far always reproduced the error on the second launch:
Hello,
I'm trying to disable collision between vehicles via beamngpy.
In BeamNG the setting is Options->Gameplay->Simplified collision physics.
When changing this setting, the settings.json file in the user folder gets the new line ""disableDynamicCollision":"true""
Using the settings.change("disableDynamicCollision", "true") method works, as long as the disableDynamicCollision value is not already in the settings.json file.
If the value exists and is set to false, the method changes the setting in the json file, but in game the collisions are still enabled
(On further testing, this is not the deciding factor wether it works or not, as just now it failed to apply the settings even after deleting the line before starting)
In the in game settings menu, the simplified physics option is not selected, it does however show the warning below the setting, that normally only shows up when the setting is enabled.
This is my testing script, it has so far always reproduced the error on the second launch:
The text was updated successfully, but these errors were encountered: