0.16 Discussion Thread

the 'enlightenment sounds' as they have been dubbed seem to occur only when you are going through thick bushes while revving your engine.
they freaked me out when i first heard them

 

The gate prop (in both configs) is really badly wobbly when spawned and in general the jbeam feels like it lacks stiffness imo

 

I would just like to say the devs have done a great job with optimization. Back in 0.14, the performance tester put me at ~78 MBeam/s and 8 realtime vehicles. I just decided to fire it up and I'm now at 104 MBeam/s and 11 realtime vehicles. The optimizations really are helping, keep it up!

 

Hey, this is just more of an rant, rather than bug report/constructive commentary, but...

... if you take the Dxx/Hxx/GrandMarshal V8 (the 5.5) up to its paces with tier 3 performance addons, it overheats. Not after a while, but after several seconds. Using N2O is basically two 1/4 mile runs and engine goes ... engine goes.

... yeah I know that an engine that makes 1000+ Nm is probably going to overheat, as some point, but if you add "high"performance radiator you are sort of awaiting ... high performance from it?

... why don't I use mods you say? Well because of my frequency of being able to enjoy BeamNG - when I started it up last time, it got updated; and now all the saved configurations (and most of the mods that did something) are non-functional and the one that had some sort of invincible radiator does not worky worky anymore. So to save me some headache and time, I just decided to remove them all (mods&personal configs) and simply go with "jeu de vanille".

So what would I like to suggest?

Well! Why not add an official "cheating radiator" to all water cooled petrol V8's? Am I out of my mind? Of course not. With it would be also nice to add an "lead foot driver" achievement so everyone gets to know you simply ... drive over the edge and fuel consumption is something you really do not care about, so you had to reach for "cheating radiator" to keep things cool enough to not blow.

P.S. : Calm your pitchforks and torches ... it's just an rant.

 

After a recent hotfix (not sure if it was .1 or .2) main menu has been very laggy. This doesn't apply to the level or vehicle selector, just the main menu and the menu where you can select freeroam and stuff. but it's still pretty annoying
Recorded it, it wasnt affected that much by OBS so it's pretty much what it's like without it being recorded

 

Turn on GPU accelerated UI from graphics options as that was turned off because some AMD GPUs and alike had issues with it.

 

Thanks, thought I turned it on after .2 but apparently I didn't

 

@Diamondback is it intended behaviour for the torque converter to unlock upon braking? Normally with the tc locked that can help with engine braking, especially on the bus.. when the tc unlocks, engine braking falls a bit..

 

With cars that is a custom I believe, with TC on, braking might be bit less controllable so TC usually is unlocked when braking for safety reasons.

However with heavy vehicles using some other than D mode may hold TC lockup more as there are lower gear settings which are for descending.

 

You don't want the TC to stay lockup when you braking if the wheel lockup the engine will stall. And vehicles with ABS will not stall but the moment-of-intertia of your engine will interfere ABS operation,resulting a longer brake distance. Some experienced drivers recommend clutch-in when moderately or heavily braking in an MT vehicle.

AFAIK in BeamNG the shiftlogic is not affected by brake value. The TC will unlock(but not downshift) if your RPM get slightly lower than the TCC lockup RPM, then if you are coasting downhill it'll not lock up even if the speed is higher than the TCC lock up speed, unless you apply throttle slightly. This feels like it affected by braking.

 

I just wanted to report that the glowmap of the front lights of the Autobello is still wrong. After breaking them there's still light.

 

Bugs:
Bin sounds like a bush (Italy)
UI doesn't disappear quick enough for steam screenshots (still)

 

I'm finding out that some Automation vehicles of mine are no longer accelerating properly when going straight, only when cornering:


Same happens with 4WD disconnected, not sure if it is only my Automation vehicles, there was one other high performance Automation vehicle not made by me which did the same, there just is some straight or almost straight position in steering where Acceleration is cut, not sure if it is TC or ESC or what, but clicking ESC button stops that from happening.

 

After I got the Windows 1809 update, I suffered a massive performance loss. I downloaded the 0.16 update when I had version 1803 and it ran beautifully, getting above 110 fps with high settings on Matrix Freeway with 3 cars spawned. When I got 1809, it was dropping to 70 fps. I updated my GeForce drivers to 430.64 to see if it'll fix the problem and it showed a little improvement but still hovering around 90 fps, not what it used to be. Is there anything that could be causing this?

I am running a GTX 1060 3gb with an i5 8400.

 

BeamNG keeps doing optimizations while Micro$oft keeps doing the opposite.

 

It angers me since I was refraining from getting the 1809 update due to many terrible issues being reported about it and Windows forced me to do the update, so in that moment I had no choice but to restart my computer and let the update happen.

 

Windows 10 force update cannot be turned off easily, including device drivers, effectively converting our computer to Microsoft's guinea pig. They do this to save testing effort and electricity in their HQ.
Even worse, I often find my computer consume lots of electric power and the CPU fan is running like there's no tomorrow when I'm away from keyboard, it quiets down when I move the mouse a bit. Seems like Windows is making my pc doing distributed computing(botnet or something?)secretly. They USE OUR PC TO TEST THEIR SOFTWARE IN BACKGROUD. So I always shut down my computer before I left.

 

When you spawn the default Moonhawk (the red one) it still spawns with body-colored trim. That issue has been in Beam for a long time IIRC...