0.23 Discussion thread

why does this happen everytime i wanna play and yes thats is safe mode and its on every map on every car that happens in different colors aswell

 

The Wigeon's Darter variant spawns in with a regular front tire instead of the race front tire.



If you equip the 1.3L inline 4 in the Wigeon, the driveshaft is not quite in the correct spot.

 

It is weekend, but Humble Bundle has no new version, this is quite odd, I hope that I will not miss 23.2 as I try to collect them all

 

I am getting the GPU is not responding fatal error, even with a fresh install and no mods. Graphics drivers are up to date, and it seems to only happen on detailed maps and not very often on grid map

 

Bump to add that Bus Routes and campaign don't work either. Not sure what changed from 0.23.1 to 0.23.2, but whatever it was seemed to break everything outside of freeroam that used the "Start" button.
EDIT TO ADD: Safe Mode, vanilla scenarios fully load normally.

 

BeamNG Update Version 0.23.2.0.x: i am experiencing VERY long load times with unpacked mods since this update has dropped. what used to load to main menu in 10 seconds has now taken me 10 minutes.

 

For the humble bundle people here, I doubt the 0.23.2 is gonna be up as 0.23.3 is probably being worked on and idk, might be uploaded?. Not sure.. though it should fix the UI issues imo

 

Bumping this as I found a solution on my end!
When booting the game, instead of launching go to "Manage User Folder" and open it in Explorer. Then go to the mods folder and delete the "Unpacked" folder. There's a BeamMP folder in there so there might be something in there that conflicts with the current build. Personally I haven't launched BeamMP since 0.23.1.
This might not be the fix of scenarios, bus stop, and campaign for everyone, but it's a solution I found after starting in Safe Mode.

 

All the KissMP people are probably sitting there like "there was an issue for you? hm. welp, I guess we know who chose better..."

Spoiler

PLEASE DO NOT MISINTERPRET THIS as me saying that BeamMP devs don't know what they're doing, or that BeamMP is awful, or that KissMP users are stuck-up, or whatever else. I have clearly stated my opinion on the matter in other threads, this is only a joke, not meant to hurt or insult anyone. Thank you.

 

yes. that is true. the configs i made saved instantly instead of freezing the laptop for a few minutes.. buut the UI lagging doenst help. lol

 

This dark chrome is clearly unintentional and really bugging me

 

ngl, i thought that was a real life photo.

 

Thanks to PBR, BeamNG is now able to properly render white vehicles... unfortunately most of the white colors aren't quite able to take advantage of this, so I made my own

 

i noticed that the Moonhawk has a "LOW OIL" light, and I hit the oil pan and it said "oil critically low" but the light didnt light up.
i also hit the engine and it said "Engine Damaged" yet the "CHECK ENGINE" light didnt light up either.

edit: all lights came on (other than HIGH BEAMS and PARKING BRAKE) when the engine was broken, hydrolocked or locked up

 

(Safe Mode enabled) The campaigns' some parts are broken, Suspension Bridge episode from Senseless Destruction for example:

After you finish you can not pass to the next episode, also sometimes shows you the dropping cutscene, even you are safe on the bridge.
Edit: Canyon Trial episode from A Rocky Start campaign is broken too:

Edit2: Stunt 2: Jump from Hustle Bustle campaign also broken:

Edit3: I don't think that i'm a bad driver, but it's impossible to get a full score from 9th episode from Driver Training campaign:

After drift episode it gives same broken page too:

 

The level of detail and pop-in of props in West Coast USA is about half as detailed compared to other maps, I can visibly see the change from green blob to modelled tree. This doesn't seem to happen in interior cam, only in orbit.

 

Default D15 pickup truck's 3rd brake light turns half on before main brake lights, when you apply 1% of brake.

With gamepad I get 1% of braking if I don't set deadzone and that kinda amuses me every time when I lift of throttle.

Also all the stutters and hiccups disappears pretty much completely in Vulkan and DX11 if I set graphics like this:
Vsync on (Windows refresh rate 144Hz, G-sync on from monitor)
FPS limiter to 60 (want to save electricity)
Windowed mode

So when turning camera, sometimes you usually get those tiny drops in fps to 40 or even below 20fps, especially with Vulkan this happens a lot if you are not using high performance power profile or set CPU and GPU clocks to locked to certain value.

However with above settings I can use pretty much any power profile and there are no hiccups.

I did test this with
Ryzen R9 5900X
GTX1050Ti (I know, makes perfect sense)
Driver version was 45X.XX from no apparent reason.

Without doing those settings as frequency jumps, there is hiccup to 20 or 30 or 40 fps range.

Edit: Btw, don't bother with those settings in Windows 10, it works only in Windows 8.1 it seems, in Win 10 only way is to have 144Hz refresh rate and G-sync on, with that there is not much noticeable hiccups even in Vulkan, except when Win 10 loads which is a feature of Win 10 I guess, but it is kinda annoying to listen the fans as result of poor little GPU trying to push 144fps in this game.

 

Finally got around to play with the new update, Great job as always! I love the new Gridmap, it's off-road area is really well-done, the map loads really well, and the modular way it's built, I believe, would enable us modders to make scenarios with plenty of stuff in the .prefab files, essentially using existing obstacle models to make brand new obstacles! and the Italy garage delivery scenario is really nice, I'd love to mess around with the files and modify it into new scenarios, as soon as I have some free time!

Speaking of which, I've found a few issues with it (and with Italy in general), should be an easy fix:

Spoiler: Italy and garage scenario issues

Navigation error


Misplaced trigger



AI + nav issue into one-way road. Actually, it's an ETK, so maybe the AI is supposed to mimic real ETK driver's behaviors so it might pretty accurate...

As for gridmap, I've found some things which might not be bugs, but could be improved regardless IMO:

Spoiler: Gridmap bugs and suggestions

I'm really not sure what this is meant to be, but it looks as though the decalroads are slightly misplaced? I mean, the yellow line makes no sense as far as I can see, but maybe it's supposed to be like this. IDK.


I really like these ball shaped obstacles. They look a bit like something you might encounter on an off-road trail, and are more challenging than some other obstacles since they require careful tire positioning as well as throttle control.


However, I think that they could be better implemented on Off-Road Tower. Here, they are too ball-like, if it was a real structure they would most likely roll aside and be arranged differently. Also, there's really only one path here, since they are too spaced out and the gaps between them are too big and even really big tires can't get out of. And there's a super-deep hole on the left side of the picture...


Which walk-mode dude can fall into and get trapped under the whole tower, and can't get out.

Here's a quick edit which I think really improves this part and makes it is a bit more like the ground-level version of the obstacle (notice another block at the bottom which closes the hole, and more/bigger balls so that there are multiple possible paths which still aren't easy, but at least you have a bit of room for error and re-trying a different approach)
Before


After

Bug with the Wigeon Canopy having some sort of vibration. IDK what caused it so I posted the whole driving session during which it happened. It happened multiple times while going down this track (which is not even really possible with this car, but that's irrelevant...) so it's not some physics simulation one-time issue, but I haven't tried other roads. My guess is it getting hit with the vegetation?


Bug in the mattress scenario. you can "play as the gates". Also, there seems to be a timer issue after resetting. maybe the van's timer doesn't reset upon restarting? Or some other thing is registering as a time-based failure while there was no timer failure? I never managed to finish this scenario because of that, since every time I'd get with the van towards the port's exit the scenario would fail. But I only tried it 2-3 times so I'm not 100% sure on this one.

(Disclaimer: All these were found with every single one of my mods disabled, however it was not in Safe Mode.)