0.17 Discussion thread

Are you launching the game in safe mode?

 

No.

 

I have this issue, after installing new update ?
anyone else?

 

not sure if this has been mentioned but I was in-game with the thing you get when you do ctrl F9 (I was changing the engine audio), I didn't exit that window when I clicked the little red arrow in the bottom left corner to get to the home menu. instead of going there the game crashed. I am not sure if it has anything to do with the Ctrl F9 but it was really weird.

P.S I recreated the problem twice in the safe mode from multiple maps including grid map and west coast USA

 

how do you unlock the additional moddification screen for the gavril blueduck?

 

A few things. Is the 800 Series exhaust note supposed to sound like this?

It's almost sounds like the treble was turned up.
Some of the wired collisions were missed too.

 

There's more

The sawmill no textures go away if you go far enough but the watchtower's logs do the opposite.. Does anyone know the problem?

 

While using the 'cruise control' app i noticed a consistent overshoot of the target speed with different cars and different selected target speeds in a straight line test. It applies to all sort of gearbox and engine combinations.

Watching the throttle bar in the 'pedals' app shows, that the throttle value depletes slowly after the target speed is reached. This leads to an overshoot period of about 3-5 seconds, depending on car and target speed.

E.g. if you selected 50 kph on a base Sunburst 1.8 (M) it will acclerate to ~68 kph before dropping to the target 50 kph.

 

This website (BeamNG.com) is the only safe place to get mods.
Please let your son know to never download mods from 3rd Party sites, they are unsafe and the mods are of a very low level of quality or stolen from this website.

And yes, if you subscribe to a mod via the repository you will receive automatic updates on the mod. Manual installations do not receive automatic updates.

Hope this helps

 

17.0.0.2 Still has some random wood-props about 30~50 meters below the map, underneath the lumber mill. It's significantly lower than it should be. They've been there since the map has been updated. Also, some dead-tree props (with no leaves) might have their object origin (the movement handle) too high, resulting in the spawning too low in the map.
Link for the tree thing to take you to in-game spot.


Sawmill props visible under the terrain from the spawn point, they look almost down towards water level, easy find, no link needed.

There is a tree with it's bottom showing, that needs to be lowered 0.5 ~ 1 meter so that it's not sticking out. Link to position (it's on the far side of the building from the lumber mill spawn point, against the road). You can see where my orange van is as I've driven straight from the spawn point.


Otherwise map is pretty good, hope 17.0.0.2 fixed my CTD's with the Radeon driver (while doing anything).
Didn't Crash for almost ... me and my big mouth... CRASH AGAIN!
Time will tell!

Edit, found another floater (tree in the air), it's between the vehicles right at the corner here.

 

Barstow and Bluebuck RoadSport Vehicles need updated thumbnails to suit new tires

 

Small problem with the Burnside front and rear seats. Rear seats on the Bluebuck are still clipping through the rear wheel well.

 

Just to confirm the 'cruise control' behavior, i noted earlier, is still existing in v0.17.0.2.

 

Tnx devs for the fix!

 

Most hubcabs are still invisible

 

Will do, when i get home i will test it, but i can remember i had the same problem in 0.17.1

 

Changing wheels/lugs/tires with the vehicle customisation tab (CTRL+W) on every vehicle causes the changed thing to become invisible unless you hover with your mouse on the vehicle customisation menu tab; this seems happening only on wheels. It seems to affect all body parts.
Eg. I've chosen the Folk ZT55 as front wheels; I installed them I moved the cursor away from the menu and the tyre is invisible.

After I hovered again on the menu, the tyre reappeared.

This was present in 0.17 and 0.17.1.

 

Well if you are on Windows 10 1903, this July update includes fixes for a bug introduced in the original 1903 release. The bug caused latency spikes in graphics drivers. Since Windows 10 updates are cumulative, you can skip the july update and install the August update or any subsequent update directly.
Older versions of Windows 10 should not be affected. Check which version you are running. Reinstall graphics drivers after these updates and reboot before launching BeamNG. Wait for the desktop and background tasks to be fully loaded before launching BeamNG.

Confirm that you're running the latest Intel drivers (HD 620 drivers; you can look for other drivers with the search box at the top of the page). If you are, check on your computer manufacturer website for specific drivers for your graphics chip. While the industry is moving away from vendor-customized drivers, some products might still require them to work correctly (even if they are much older than the latest Intel driver).

Check that DirectX is in good shape and up to date (this will probably not affect BeamNG, but as sa bonus you might be able to run older games in Win10 after installing this package).

If your computer has another GPU, set it up to use the nVidia/AMD GPU for BeamNG. It can be done in Windows, but you might need to use the nVidia or AMD control panel, or check how to do this with your system manufacturer.

Try leaving your computer unpowered (disconnected from the power grid) for a couple of hours. If you're on a laptop, remember to detach the main battery (if possible).
Try cleaning the heatsink fins with canned compressed air. Be careful not to spin the fans too fast in the process: older fans can become brittle and shatter under stress. Many fast passes are better than insisting on one spot.

More advanced options might include checking that the RAM is running at an officially supported speed, since Intel GPUs use system RAM for graphics. Disable or reduce CPU overclock, especially if you did increment the base frequency (as opposed to the multiplier). You will need to tamper with the BIOS to check and correct these settings. Only do this if you know what you're doing, and do it at your own risk.

There is no iGPU on my system, so I cannot test these solutions directly.
Out of curiosity, are the AMD folk getting this error?
--- Post updated ---

Ghost parts are usually resulting from mod conflicts. If no error shows in the console*, you should guess which mod may be causing the behavior: tanis might have some wheel/rim mod, Alex might have some custom chassis mod for the D15.
If you can't guess the culprit, the quickest way is:

• Disable half your mods.
  • If the problem goes away, reenable half of the mods you disabled.
    • If the problem returns, disable half of the mods you enabled in the previous step.
    • If the problem does not return, enable half of the remaining disabled mods.
  • If the problem does not go away, disable half of the remaining mods.
    • If the problem goes away, reenable half of the mods you disabled.
    • If the problem does not go away, disable half of the remaining mods.

You can iterate this halving process till you find the offending package. Since it's based on power of 2, you only need 10 iterations to manage 1024 mods. While you can enable and disable mods on the fly in BeamNG, for "debugging" purposes it's best to quit the game after making changes in the main menu.

*The console key might be different for some keyboard layouts. On an Italian one, it's the

Code:

ò

key.