Separate names with a comma.
Apple separated the operating system for iPhones (iOS) and iPads (iPadOS) since their different so much now.
Aside from peripheral support, most likely not. BeamNG, a windows application (.exe), would not be compatible on iPadOS. Even if it would run, the...
[ATTACH]
I think it's just Synsol following the car, as the camera movements seem pretty manual. Having "natural" barriers (such as construction) seems...
It's in Devolopment Screenshots.
Holy crap, that looks amazing. DoullPepper is doing such a good job revamping, it looks like a completely new map.
Crash Hard 01's maps may work for you. They have a lot of off road tracks and jumps
Most maps should run well on 8 GBs of RAM, and most maps do support dynamic time of day. Maps that are larger than 2048x2048 (1.5 sq miles) may...
You can change the time, just go to Esc>Environment>Time Of Day. To which you can move the slider to change the time. You can enable Play which...
Dry Rock Island was not very performance friendly compared to the other maps at the time IIRC. Jungle Rock Island is what replaced it. You can...
I think he's referring to me, @Jetpackturtle. You should still get ≥30 fps with that clock speed on Medium and High settings.
More ram can improve your overall system performance, but it won't affect the game's FPS.
Yes, it is.
You can probably run it >30 FPS on Medium and High settings. You can also disable SSAO or Dynamic reflections if the FPS isn't adequate.
BeamNG is a very hardware-demanding game, so it would not be able to perform well on Macs, and would not run on any mobile device at all. There...
Your specs look more than enough to be able to run BeamNG.Drive, but can you also state your RAM just to be sure?
Okay, if you know that, what was exactly the point of the post? Was it meant to speak everyone's mind?
Well, you're going to have to wait for that. The devs might be working on it in the background, but there's no way to be sure as of now.
I am having the same exact issue. I have no mods except UCP enabled, cleared the cache, and the problem still persists, with the exact same log...
