0.19 Discussion thread | Use Safe Mode before reporting

The main problem is minimazing the game

 

Ok

 

Anyone know why my GPU usage is being maxed out at normal settings now? GPU specs, usage, and graphics settings are shown in the screenshot.

Edit: This is with only one car. Any more and it'll just make it worse

 

I think it's a map thing. I remember my 1060 running quite hard on JRI with just one car on normal settings

 

I just tried WCUSA on normal settings and it maxed out my GPU just like ECUSA did. When I set my lighting settings to the lowest, it seemed to drastically reduce the strain on my GPU (from 100%, to ~50%), which is weird because I could run both maps at (full) normal settings at ~90 FPS with only ~50-60% usage on the GPU

 

bug: The #3 siren soundscape is broken and only plays half the siren.

Edit: oops, that's already in the first post..

 

Funny, I just discovered this earlier today, but I forgot to report it. In any case, I can confirm that this is true having replicated it myself. It plays the siren audio file once, but doesn't loop it.

 

yea hope the Intel team helps beam ng to fix this error if they can't oh well I guess, All we can is hope they can solve this issue.

 

Does BeamNG have a LOD system for their maps? My pc is pretty capable of running this game as it runs quite heavy AAA titles, yet it struggles way too much with WCUSA for example.

 

I was going to make an cheap Burnout machine based on the Picolina 110. First thing I did was removing the rear brakes, but when removed the REAR BRAKES the rear wheels keeps receiving brake but the front wheels lost the brakes also no hand brake, if I remove the FRONT BRAKES and keep the REAR BRAKE the rear wheels stop locking when brake is applied, but locks when handbrake is applied.

 

That's probably due to the Piccolina simulating a single piston brake master cylinder.

 

I have 2 bugs and a typo to report. The bugs have only happened since the 0.19 update, with and without installation of any mods.

Bug #1 - force feedback: When switching vehicles, sometimes force feedback stops working. The game still accepts input from my steering wheel, there is just no resistance/force output by the wheel. The problem can be temporarily fixed by entering force feedback settings and changing the strength, then pressing apply. Although the issue will happen again soon after when you switch vehicles. My wheel is a Thrustmaster T300 and it has all of the correct drivers installed. This problem has only been occurring since 0.19

Bug #2 - Fullscreen resolution: When I use alt+enter to enter fullscreen mode, or when I press apply to enter fullscreen in the graphics settings, the game switches to 1280x1024 graphics mode in fullscreen, even if I select another resolution (usually 3840x2160 or 2560x1440). I then have to reopen graphics settings and change the resolution. I have fully updated graphics drivers, and my monitor resolution is 3840x2160. This problem doesn't happen with any other games. This problem has only happened since 0.19. This only seems to happen around 50% of the time I put the game in fullscreen mode. My graphics card is an MSI-built 1060 Ti, with up-to-date drivers.

Little typo: The 1280x1024 resolution is labelled as "1280x1024 (4:3)" when the aspect ratio of that resolution is in fact 5:4

 

A friendly reminder about some dev questions:

Spoiler

 

Hi!
I've found a few minor bugs that I haven't seen mentioned yet.

1. Floating logs around the East Coast sawmill

Spoiler

The log to the left of the roamer is floating. As seen below, the big piles behind him float too

2. Some cars have typos and mistakes in their descriptions. I mainly noticed this with the "preformance class"

Spoiler

The drag Roamer has a lower "preformance class" than the offroad, despite every preformance parameter being better

And here I just don't understand what the description means. This is the Roamer RS, and every other RS (such as the RS LXT models) are also AWD and with a supercharger. So how is it unique?

The K series drift has the lowest "preformance class" of all cars, with 0? The Vivace Arsenic has the same problem.

3. There's a wierd "step" of sorts in the middle of the valley, crossing the italian town which I forgot it's name. I discovered it by complete accident, pun intended..


4. This is not a bug, but just me wondering: the Vivace rally (which is really fun to drive, btw) has a 1.6L engine, despite the Vivace having a 2.0 option. And the Sunburst has a 2.0L in the rally car. So the rules for max engine displacement have changed? or is there some other reason?

5. Floating rocks on Gridmap

 

2. Performance classes are going to be removed (or changed I forget which) according to Nadeox1
5. That's a feature.
Everything else is either a bug or I don't have the proper knowledge to answer (4).

 

Every Gavril has a RoadSport (RS) configuration. The Roamer RoadSport is the only one with AWD.

There is a typo in that description, though. It says "ususual" instead of "usual."

 

The Vivace seems to be a full fledged WRC car, which mandates a 1.6 turbo engine since 2011, while the Sunburst, being much less extreme, may be built to Group A regulations, which were superseded in the WRC in 1993 but still today very common at lower levels

 

A few trees in bad spots on Utah:

These trees kind of block the road


These trees are growing out of a solid rock-face


Here there is a small hole in the terrain. But it is very hard to see it from the road, so IDK if it is really an issue.

Also, I noticed that the replays do not keep the digital gauges (tested on the Sbr and Tograc) and the also the GPS screen. I don't know if it's a bug or just not supported yet.

Mmm, that makes sense.