Development Sneak Peek #7 & Update v0.15.0.6

14 March 2019

Hello everyone,

As usual, we’re diligently working on adding new features, more content and doing various amounts of internal research.

Since that work typically doesn’t get visibility until it finally gets released in a major update, today we’re showing part of it. Today’s sneak peek is focused on the Italy map.

As we mentioned back when this map was first released, that initial version of Italy doesn’t include everything we had in mind. In a future update, you’ll be seeing more towns and official buildings, additional offroad trails, expanded seaport facilities and more, as shown below:

Italy – Work in progress:

In parallel to the regular development process for major updates, we never forget about possible issues that the community brings to our attention. Today we’re bundling a small selection of the resulting bugfixes. The idea is to solve only the most important issues, risking overall stability as little as possible.

This fifth update for version 0.15 includes the following changes:

Bugfixes

  • Fixed repository not working when manifest cannot be parsed
  • Fixed crash when static render manager tries to render 30000+ instances in one draw call
An up to date list of known issues can be found in the dedicated Feedback & Bug Reporting Thread here.
Instructions on how to update the game here.

That’s all for now!

Fourth hotfix for 0.15

27 February 2019

Some more fixes and improvements.

Bugfixes

  • Added guard for missing default.pc
  • Fixed crashdump being saved to default userpath even after changing it
  • Fixed default userpath being incorrect if Windows Defender “ransomware protection” is enabled
  • Fixed crash on render related to shadow materials
  • Fixed missing GPU meters on the performace UI
An up to date list of known issues can be found in the dedicated Feedback & Bug Reporting Thread here.
Instructions on how to update the game here.

Deprecation of DirectX10 support

30 January 2019

The relentless march of technology brings with it many improvements but also requires us to make difficult decisions.

Adapting our rendering technology to utilise the maximum potential of modern DirectX libraries means that supporting older DirectX versions has become increasingly difficult and introduces instabilities into the game for all users. DirectX10 was first introduced with Microsoft Vista back in 2007, 11 years ago, and both Nvidia and AMD stopped supporting DirectX10 in their driver development several years ago

Though it has been possible to run BeamNG.drive on DirectX10 graphics cards, this did not meet our minimum system requirements, which have called for DirectX11 for some time. The developer resources required to maintain functionality on DirectX10 graphics cards has reached the point where continued support is not sustainable. It is for this reason that we have had to make the decision to cease ongoing support of DirectX10 in the same way we had to stop supporting the now 17 years old DirectX9.

We have made available a branch of the DX10 game client in Steam. This branch will not be updated beyond this point.
You can find instruction on how to use it here.

Third hotfix for 0.15

29 January 2019

Third round of fixes and improvements.

Bugfixes

  • Fixed crash when rendering shapes with invalid details numbers
  • Fixed initial window size of scriptAIManager
  • Fixed autobello thumbnails
  • Fixed custom groundmodel not being loaded
  • Fixed Some utility function using default userpath instead of actual defined userpath (may have fixed issues inside the torque3D editor)
  • Launcher: Fixed open dialog failing to open on some specific configuration
An up to date list of known issues can be found in the dedicated Feedback & Bug Reporting Thread here.
Instructions on how to update the game here.

Older Posts »