BeamNG.drive (284160) #1237
Comments
kisak-valve
added
the
Game compatibility - Unofficial
kisak-valve
changed the title
|
Beam NG installed from Steam, not working for Steam. just run command from place with game
test it, have fun. 😄 Tested on Hardware & Software: confirmed it also on the website where is list of tested games by Steam Beta users Inside this website (... docs.google ...) you have |
|
Just tested for myself and can confirm that via proton version 3.7-6 it black screens and crashes, using wine staging from winehq it works fine |
|
@tele1 The crash seems to be due to wine-mono/gecko being missing. Following this: https://www.reddit.com/r/wine_gaming/comments/8r6low/guide_how_to_install_net_45_on_64bit_prefixes/ makes it work but when launching via steam it seems to remove any custom additions to the prefix. |
|
As of the new update last week beamng is unable to launch anymore with Wine 3.14+ and DXVK. I get this in the console. Seems like some Nvidia API being used despite having an AMD GPU.
|
|
It doesn't work for me. Error 0x00000001 |
|
Game runs now with 3.16-5. I am however unable to change controls properly. Whatever changes I make do not register and then upon the next loading of some sort of resources (reload car, load a map, restart the game) only the last change I've made gets saved. I have to repeat this process for every button I want to change. |
|
It also crashes quite frequently, after loading maybe 5-7 different cars, not at the same time but in total over one session. Seemingly takes fewer cars to crash the game on bigger maps. |
|
With Proton version 3.16-5 I can load and play the game but it is horribly slow no matter what graphic setting I choose. I'm using a I5-6500k and 960gtx. When running natively within Windows I can almost max everything and stay above 60fps. I have no idea what the issue is or what is bogging down but my GPU usage hovers at around 30% and my Quad core has all cores at about 70%. Any help would be appreciated, or if you have any settings I would be able to change for a performance increase I would be interested. |
|
So my problem was I had to uncheck limit FPS, if I had it set to 60fps I would get around 20FPS. I also noticed that certain custom vehicles would cause the fps to crash pretty hard. Other than that things seem about normal for playing a game inside of wine instead of natively. Thanks for the hard work! |
|
I'm using a Logitech Momo racing wheel and force feedback only works under certain (bizarre) conditions. I have to be driving a non-power-steering variant of the Gavril Vanster (no other car works for this, power steering or not), and if at any point I drive a different vehicle, force feedback stops working until I restart the game. This means that to get it working in the first place, I had to open the Garage, load the "Drift Missile" or "Off-Road" Vanster, save it as the default vehicle, then quit and relaunch the game and play free roam. The only clue I have to help explain this is that with any other vehicle, I also get frequent crashes, usually when loading levels or vehicles. It seems like larger maps (Italy and San Francisco, especially) crash on load the first few attempts but then start working (possibly something to do with caching? Clearing the game's cache makes the maps crash again) @echoz28 I found that I could change multiple settings at a time, then immediately quit and relaunch the game and they'd all be saved (even though some of the changes didn't show up while I was changing them). |
|
Hello @daprice, please copy your system information from steam ( |
|
@kisak-valve Steam System Information: https://gist.github.com/daprice/2ae2906d58f4e753554ab80d8e869640 Uncompressed, the proton log is 464MB! To get it small enough to upload I had to compress it with .tar.xz, then again with .zip so GitHub would take it (sorry!). Prior to this session, I cleared the game's cache. The log is of opening the game, choosing Play -> Free Roam -> Italy -> Default spawn, then the game shows its loading screen for a while, when it finishes loading it displays a few frames with a lot of missing scenery then crashes. Edit: Sorry, forgot to mention this is with Proton 3.16-6 beta |
|
Here's a separate log from testing the steering wheel force feedback issue (same System Information as my previous comment). For this log, I opened the game, chose Play -> Free Roam -> Grid, Small, Pure map -> Default spawn with the Off Road Vanster as default vehicle, the game loads, when it's finished loading I move the wheel back and forth to test force feedback (it's working), then I switch to a different vehicle, the Ibishu Covet Beater, and move the wheel again (now force feedback is no longer working but wheel input still works), then I exit from the game. (thankfully this one only needed zip compression) |
|
Seems to get stuck on a black screen for me, too. Tried launching through a terminal but there was no interesting output. I hear the little sound that you'd normally hear when you get to the main menu but the image remains completely black. Steam overlay works fine and shows that it's rendering the black screen at 1000+ FPS. |
|
The black screen issue is more of a general issue, the workaround by the devs fixed it for me. |
|
The black screen issue has been fixed in the most recent update for the game. |
kisak-valve
changed the title
To clarify, fixed as in they disabled the multi threaded renderer by default |
|
The game instantly crashes upon hitting "play game" under BeamNG.drive's launcher after the 0.17 update. I've tried launching the game with esync off, but it did not yield different results. It's worth noting that the previous version of the game worked flawlessly on my system.
|
|
I am having the same problem after the update to 0.17. The game launches then instantly crashes. Previous Versions worked perfectly.
|
|
version 0.17 needs this patch https://source.winehq.org/git/wine.git/commit/a20295ce3ddde224f9d958f6a4e5d117528e9279 |
Unfortunately it seems that is not enough. I tried launching BeamNG through WINE Staging 4.14 (which is supposed to have the patch) and this is what I ended up with from the moment I pressed "Launch game" up until the crash reporter appeared: Proton log snippet
The (probably) relevant line: It seems like _o_floor is a stub: https://source.winehq.org/git/wine.git/blob/a20295ce3ddde224f9d958f6a4e5d117528e9279:/dlls/api-ms-win-crt-private-l1-1-0/api-ms-win-crt-private-l1-1-0.spec#l955 |
|
Seems like them (beamng) switching to a newer sdk has caused this mess.
Edit 1: Patches for it are on the way Edit 2: with these patches applied, it now hits Edit 3: When using the patches from "Edit 1" and this hack patch i have created here https://bugs.winehq.org/attachment.cgi?id=65072&action=diff the game works again |
|
It works now on 4.11-2 after the first 0.17 hotfix. |
|
Crashing Everytime i respawn a car Issue transferred from #3223. My beam.ng Game keeps crashing every-time i re-spawn a car in a big map, i think its my |
|
Hello @Headscientist, please add |
|
|
|
BeamNG recently came out with a new VR mode, but sadly it doesn't work properly via Proton, other OpenXR VR games I've tried do work properly. It breaks in 2 different ways, depending on the order.
For the second one it seems like it tries to start, but fails the negotiation with wineopenxr64 with error -6. Proton version: 8.0-4 |
|
When running Beammp on 8.0, Experimental or GE with prime-run I get the following error: It works fine on 7.0 A friend of mine has a desktop with an nvidia gpu, and it works fine for him on newer versions, so this issue might be exclusive to laptops. Similarly if I run beammp on my amd iGPU it works just fine. Not sure if this is an issue with Proton or Nvidia Drivers. |
|
I have played the game extensively on proton, over 30 hours. Everything works (even beammp and mods), controllers and wheels, not sure on steamvr because on the pc i can access that has it, there were difficulties running steamvr in the first place (it's really bad on linux it seems) The only aesthetic issue was some textures turning black (there are some fixes for this but nothing worked 100% for me yet, but i did manage to fix it so only very few textures are black) The main issue with playing the game is major FPS drops. When I load into a fresh map, usually i have ~140fps, it's great, i play, i crash some cars, everything's fine. But seemingly at complete random, sometimes i will get massive fps drops and go down to sub-30 fps out of nowhere, and i don't just mean like a lag spike but more like this is just my framerate now for no discernible reason. Occasionally it gets even worse and i go down to sub-20fps, which renders the game entirely unplayable. Alt-tabbing sometimes fixes the fps drops, sometimes not. |
Here's some additional insight provided by one of the developers of the game (source): [Previous post includes a log file]
|
Hi all. It seems that the problem is more with the latest versions of Proton/Wine than with the game, as it seems that nobody complains on Windows. |
|
BeamNG.Drive keybinder broken when under Proton Issue transferred from #8113. Compatibility Report
System Information
I confirm:
SymptomsCannot set custom key bindings, shows up as Reproduction
WorkaroundEdit the config JSON files, however this can get VERY annoying as the config resets every time you update the game |
|
Additional datapoint: I cannot repro the keybinding issue on my machine, so it must be something more specific going on. Specs: GPU: 3080 (Laptop version) I tried both the normal and the Vulkan mode of the game; and tried binding both alphabetical keys and symbol keys, all seem to work for me. Running Linux Mint with Mate DE. And additional datapoint; can't repro on my Steam Deck either. |
Note I am on Fedora |
|
@TiagoTiago also note that I can repro the issue, as it happens no matter what I do. |
|
Also also also note there is no difference under experimental. |
|
Btw, dunno if it might be helpful, but I checked just now and the game writes some stuff to it's own log file immediately after you apply a change to the control bindings; so it might be useful to look at the last lines of |
|
@TiagoTiago no errors related to bindings, possibly pointing at Proton's Wine Keyboard |
Are you using some less common keyboard layout/language by any chance? |
|
English (Australia), basically the same as american layout |
|
Logitech G923 XBOX Force Feedback doesn't work properly on BeamNG.drive Issue transferred from #8440. Compatibility Report
System Information
I confirm:
SymptomsI boot up BeamNG and I use a Logitech G923 XBOX Version to try and drive in the game. The game runs fine but the wheel itself is having terrible issues with regards to force feedback. Other games like ETS2 or Assetto Corsa run fine but the force feedback in BeamNG does not respond the way it should at all. I tried changing the settings in the Force Feedback tab, set update type to 'Full (slow fallback)', it made the behavior a bit more responsive but just a tiny bit and the wheel still went as crazy as usual. Tried using the ffbwrap command to see if it fixes anything but the issue still persists. Can't upload the Proton Log since it's pretty big. Reproduction
|
|
Just in case, double-check if the problem doesn't get fixed if you set Force-Feedback to inverted in the game. |
I have done that as well but it didn't change anything unfortunately. The wheel still goes as wild as it did before. |
@narcester what are "Update rate limit" and "update type" set to in the ffb settings (all the way at the bottom)? |
Update rate limit is "Automatic" and Update type is set to "Fast" currently but I switched it to "Full" before and the force feedback hasn't really improved much. |
|
Try setting "update rate limit" lower, like 750Hz. Does that change anything? I had an issue for a while where the auto detection wasn't working for certain devices. But it stopped happening for me a while back. Maybe this wheel is unique somehow. Anyway worth a try. EDIT: I would probably restart the game after that change. I'm not sure it works right away. |
The wheel is much more responsive now but it still has some hiccups. If I drive straight and give it a little left turn, it tries to self steer back into place but it fails to do so and it keeps going left and right over and over. |
|
Oscillation (the back and forth overshoot you are describing) is not uncommon in force feedback systems. Some games handle it better than others. Setting damping in the driver can help, along with just lowering the gain a bit. However if changing update rate limit had an impact on your problem I would say what's most likely happening is the game is sending more FFB data to the wheel or driver than it can process. I had this issue with my OpenFFBoard wheel and it appeared in the kernel log like this when playing BeamNG with high update rates (>1000Hz). Lowering the update rate limit to 750Hz worked for me, and at some point the dynamic rate setting (automatic) also started working, but it's possible your hardware/drivers need it to be even lower than that. No FFB system will ever be completely free of oscillation but it's usually possible to tune it so it's not noticeable. It gets a lot worse with higher gain, and especially if your wheel is clipping, which is to say that the game is requesting more torque than the wheel can produce, so all detail is lost above the max torque the wheel can output. |
|
Also, try other USB ports; I remember reading some wheels work better on USB 2 and others on 3; and make sure there aren't too many USB devices connected (some computers got some internal USB hubs resulting in some ports having more bandwidth left than others depending on which devices are plugged in which ports, and IIRC, some wheels can have a little trouble if they don't get enough bandwidth (there are some apps that will let you see what the topology of the USB connections is on your system and some other details; I have USBView, lots of details, but I'm not 100% sure how to figure out how saturated each hub actually is since it doesn't show "live" data, just what I assume are the standard specs; dunno if it that specific app is available in all distros, but you probably can find some alternative if you can't get that specific one for yours)). |
Yeah, I've read in a GitHub repo that contained info about supported wheels on Linux that it's because of the way the hid-logitech-hidpp driver is written that it sends commands to the wheel at the same rate the game is sending them, so it is as you said. The "Automatic" option in "Update rate limit" needs to be fixed. I set it to 1250 Hz for now. Thank you so much for helping me out on this and I hope this issue gets fixed soon for the G923.
Bandwidth is not an issue in my case but thank you regardless for the help. I've also downloaded the package in case I need help with something. |
and others
It launches fine, switches to full screen at which point its black.... Then it crashes and the BeamNG crash reporter comes up: https://gist.github.com/JamesHealdUK/2497ce5b2c5c123d4ad5878ed1042e67
Steam generates a huge ass log file for it too (16mb big!) https://gist.github.com/JamesHealdUK/478e3dc53c14a2168a05ba5a0755d729
Tried with both esync enabled and disabled to no avail.
The text was updated successfully, but these errors were encountered: