ExpandCollapse

Staff Member

Its just way more comfortable on WASD and free camera thru Shift+C
[...]
I hope i explained that well. Please help us

Click to expand...

Hi, welcome to the forums!
Please help me understand better, so we can devise a solution that can make everyone happy: how is that choice of bindings not problematic in free camera too?
After all, both the shift+c free camera AND the vehicle will move if you have chosen WASD controls for both.

ExpandCollapse

Hi, welcome to the forums!
Please help me understand better, so we can devise a solution that can make everyone happy: how is that choice of bindings not problematic in free camera too?
After all, both the shift+c free camera AND the vehicle will move if you have chosen WASD controls for both.

Click to expand...

Hi, as long as i can remember i was using this control scheme, WASD one.
And it is very fast, comfortable and efficient.
Driving is normal - "WASD"
Binds to open car selection menus is near.
I use "X" and "Z" as gear Up and Down. Shift is near to hold clutch.
"Ctrl" for node grabber is perfectly positioned so i can use camera control and mouse while trying to connect nodes or something.

When i use free camera i have to turn off the car, so its not gonna roll away. It was "V" i think. Or just pause physics with "J". It would be perfect to have a toggle so when you use free camera, car controls wont be activated. But its ok. I don't make any cinematic videos, so i i'm not really affected by Car moving when i move a camera.

I had perfect control scheme for myself, but i cant use it now in "driver" camera
So, in short, i can use all binds efficiently with one hand not moving it to "arrows" to control a car

Adding new bind option for "Move seat camera forward/backward" would be awesome

ExpandCollapse

Staff Member

Thank you. It seems you enabled the Options > Camera > Collision option. This unannounced feature is experimental, not generally usable yet, and will probably be removed in the next hotfix. In the meantime, simply disable the feature

ExpandCollapse

ExpandCollapse

So it's just the loading screen not appearing, right? It does not block you from playing the game still?
Can you please replicate the issue and PM me a Support ID? ( include a link to your post, so I can connect the two things )

ExpandCollapse

By default pieces are slightly curved inward. At the moment it's not possible to change that, but we took note

That option slipped in. It's highly 'WIP' , not all corner cases have been tested yet.

The local Forestry-Commission has been notified

Hello, please note the blue text in the first post.
This is an issue coming from the AMD drivers itself, at the moment there's not much we can do about it.
Some users suggested that installing the Latest Optional drivers + Clearing the cache fixed it for him.
If it doesn't for you, please contact the AMD Support about it (so that they can acknowledge this issue), and as temporary solution you can either go back to an older driver (pre-July 2018) or disable grass (Options > Graphics > Custom Quality > Grass Density)

First post contains some mods that have been reported to break the game at the moment, give it a look

Thanks for the info!
(To be expected, that mod modified the game's core files)

Screenshots are now saved in folders (one per month). Open that one and your screenshot should be there.
If not, replicate and give a Support ID: (via PM possibly, include a link to your post, so it doesn't get lost here)

So it's just the loading screen not appearing, right? It does not block you from playing the game still?
Can you please replicate the issue and PM me a Support ID? ( include a link to your post, so I can connect the two things )

No, the old camera has been replaced with this one that has more features and is more reliable all around (still some rough edges, but we are working on that)
May we know what you don't like, so we can improve it instead?

It uses the same bindings as for the free camera. Modify them and it will modify the seat stuff too.

ExpandCollapse

Note that only 'Driver' camera FOV is saved, and not 'onboard' nor 'relative' nor any other cam.
Even then, the seat and fov adjustments are saved only one second after you stopped tweaking them, to prevent hitting disk I/O too often. If beamng.drive is unable to run correctly in real time, it's possible that the timing is off and it takes more than 1 second. Judging by your video, maybe 10 or more seconds. Not sure. Try testing it without steering wheel (or whatever fixes the abnormal framerate).

Click to expand...

Issue was when adjusting camera while having 60fps, however it can be that as it was 3fps earlier, that might make things bit 'off'.

It seems escape velocity indeed is far greater than bus tires can handle, maybe I need to craft skis, yes skis would be a solution
Who needs Kerbals, when you can have horribly green planet made in BeamNG

ExpandCollapse

Great update, as always! I'm really happy for some of the small fixes, especially the "smart" e-brake one (thanks!), but also some other small skin changes like the rusty pickup, and the t-series dumptruck becoming 2-tone.

I've located some small bug- you can select non-lightglow cars for the lightglow mode. I'm actually not to sure if it is actually a bug, but since you can't access the lightglow cars on a normal map, it'll make sense that you can't select the normal cars on lightmode. Doing it is simple- you just don't double-click in the selection menu, but single-click.

ExpandCollapse

ExpandCollapse

Unsure if its been reported yet but sometimes loading screens don't appear when selecting maps in free roam/light runner time trails. All that can be seen is a laggy main menu screen.

This happens not only for me but on my brothers computer too, and he only has 5 mods installed so I don't think its mod related (although I don't know for sure). We both have fairly decent computers with high quality parts. (my PC specs are in my profile, my brothers is similar)

ExpandCollapse

BeamNG.Support

Staff Member

Can you please create a new bind for "Move seat camera forward/backward"
We currently cant use "W" and "S" in firstperson camera if "move free camera" and "Throttle/Brake" are binded to it
Its just way more comfortable on WASD and free camera thru Shift+C then WASD than moving your hand all over keyboard or not able to use a mouse.

Great update, as always! I'm really happy for some of the small fixes, especially the "smart" e-brake one (thanks!), but also some other small skin changes like the rusty pickup, and the t-series dumptruck becoming 2-tone.

I've located some small bug- you can select non-lightglow cars for the lightglow mode. I'm actually not to sure if it is actually a bug, but since you can't access the lightglow cars on a normal map, it'll make sense that you can't select the normal cars on lightmode. Doing it is simple- you just don't double-click in the selection menu, but single-click.View attachment 483614View attachment 483615

Click to expand...

Not a bug, but meant. We did not want to limit the vehicle selection there. In the LightRunner mode the 'powerglow' vehicles are visible just because there's the search term pre-inserted

ExpandCollapse

Very interesting. I have all mods disabled, nothing in /beam/documents/vehicles, yet when I have default vehicle spawn (default d15 as I just few days ago did clean reinstall) I hit ctlr e then double click cannon and it says fatal vehicle exception with stuff in console.

I did then move all mods (15) away in addition to have them disabled, cleared vehicle cache folder and still it does the same.

After launching game, spawning D15 and a cannon, I then had these to appear in my cache folder, does my cannon thinks having autobello wheels or something? View attachment 483621

Do you have Autobello installed or cached? Could that be reason it works for you, I have really no other idea right now.

///////

Another bug is with this, I guess node group/flexbody group needs adjusting so that mesh does not do that:

Does this error shows up before the game's launcher shows up, or after you press 'Launch game' from the launcher?
Does this occur if you start the game directly from the Bin64/BeamNG.drive.x64.exe file?
(you can find this in the game's installation directory. You can access it by going to Steam > Library > Right-Click the game > Properties > Local Files tab > Browse Local Files button)

ExpandCollapse

By default pieces are slightly curved inward. At the moment it's not possible to change that, but we took note

That option slipped in. It's highly 'WIP' , not all corner cases have been tested yet.

The local Forestry-Commission has been notified

Hello, please note the blue text in the first post.
This is an issue coming from the AMD drivers itself, at the moment there's not much we can do about it.
Some users suggested that installing the Latest Optional drivers + Clearing the cache fixed it for him.
If it doesn't for you, please contact the AMD Support about it (so that they can acknowledge this issue), and as temporary solution you can either go back to an older driver (pre-July 2018) or disable grass (Options > Graphics > Custom Quality > Grass Density)

First post contains some mods that have been reported to break the game at the moment, give it a look

Thanks for the info!
(To be expected, that mod modified the game's core files)

Screenshots are now saved in folders (one per month). Open that one and your screenshot should be there.
If not, replicate and give a Support ID: (via PM possibly, include a link to your post, so it doesn't get lost here)

So it's just the loading screen not appearing, right? It does not block you from playing the game still?
Can you please replicate the issue and PM me a Support ID? ( include a link to your post, so I can connect the two things )

No, the old camera has been replaced with this one that has more features and is more reliable all around (still some rough edges, but we are working on that)
May we know what you don't like, so we can improve it instead?

It uses the same bindings as for the free camera. Modify them and it will modify the seat stuff too.

ExpandCollapse

Driver camera, UI elements that are marked to be hidden in driver camera view appears when you go to options menu, when closing menu they stay there, but sometime later they vanish, it's bit random when they vanish, changing gear etc. can make them to go hidden as they should be.

CTRL-R works of course to hide them or ALT-U, but something is not set when closing menu, if they should even appear when going to options menu?

ExpandCollapse

To those having this same issue ( 0xC0000417 - STATUS_INVALID_CRUNTIME_PARAMETER ), please feel free to contribute. It would help a lot

Does this error shows up before the game's launcher shows up, or after you press 'Launch game' from the launcher?
Does this occur if you start the game directly from the Bin64/BeamNG.drive.x64.exe file?
(you can find this in the game's installation directory. You can access it by going to Steam > Library > Right-Click the game > Properties > Local Files tab > Browse Local Files button)

ExpandCollapse

To those having this same issue ( 0xC0000417 - STATUS_INVALID_CRUNTIME_PARAMETER ), please feel free to contribute. It would help a lot

Does this error shows up before the game's launcher shows up, or after you press 'Launch game' from the launcher?
Does this occur if you start the game directly from the Bin64/BeamNG.drive.x64.exe file?
(you can find this in the game's installation directory. You can access it by going to Steam > Library > Right-Click the game > Properties > Local Files tab > Browse Local Files button)