0.21 Discussion thread | Use Safe Mode before reporting

off topic : my current download speed at HumbleBundle :/


on topic: the tire glitch I mentioned earlier seems to be present at all tires, it's just most obvious on the T-Series.
For the T-Series it occurs 'spot on' 40 km/h, on smaller tires near the 30km/h mark.

 

I just downloaded the hotfix and went on to spawn into the redwood section of West Coast USA, and found that my GPU was pegged at 100% causing my whole computer to freeze which had not happened prior to the hotfix. I tried on two different drives, a 2 year old Samsung 860 Evo 500gb and a brand new Samsung 860 Evo 1TB both in normal and safe mode. I then tried a fresh install of BeamNG and the issue persists. It only happens when I am looking at the area where the redwoods are, even in spectator mode. If I look away the freezes stop. Im not sure what the issue is and I havent crashed due to it, so I have no crash logs to send.

My rig consists of a Ryzen 9 5900x, 32gb of 3600Mhz RAM, and RTX 2070

 

No, it could be done easily,

Spoiler: Manually

browse your game local files "\steamapps\common\BeamNG.drive\content\vehicles\vivace.zip" open it via 7-zip, open the "vivace_differential_F.jbeam" copy the

Code:

    "controller": [
        ["fileName"],
        ["drivingDynamics/actuators/electronicDiffLock" {"name":"lockFront", "differentialName":"differential_F"}]
    ],

, open the "vivace_electric_motor.jbeam" and locate the "vivace_differential_F_electric" section, then paste the code just above "powertrain"
Do the same to the electric rear differential

open the "vivace_differential_R.jbeam" copy the

Code:

    "controller": [
        ["fileName"],
        ["drivingDynamics/actuators/electronicDiffLock" {"name":"lockRear", "differentialName":"differential_R"}]
    ],

, open the "vivace_electric_motor.jbeam" and locate the "vivace_differential_R_electric" section, then paste the code just above "powertrain"
If you do this correctly the jbeam should looks like this

Save your edit, close the window, then play the game your Tograc qE will do the eDiff braking and it will pass the three rollers test.

Alternatively, you can download this mod which I made in 5 minutes. Install the mod then choose the "Open Front Differential w/eDiff" and "Open Rear Differential w/eDiff"

 

Yay, more lighting LOD bugs - this and the lousy FPS, even on top specs, from the eSBR gauge cluster.

 

Watch this, you can also use cruise control set to 40km/h

 

https://www.beamng.com/threads/t-series-experience.71893/page-3#post-1261474
https://www.beamng.com/threads/t-series-experience.71893/page-3#post-1261487

 

i think that is deliberate since the island is abandoned as hecc

 

Posting lighting LOD artifacts until I get a straight answer why they haven't been fixed: day 2

It would seem as though you are using a cube to calculate lighting LOD, and that the cube rotates with the sun. You should be using a sphere or cylinder, or not rotating the cube.

 

Generally with more than one car, or in certain areas of Italy (the towns in particular) or other more intensive maps, the eSBR will cause framerate stuttering - but only when the eSBR gauge cluster is selected. The Cherrier does not do this. Ryzen 9 3900X, GTX 1080TI, 16 GB RAM, the works. Probably has to do with the amount of JavaScript in the gauge cluster.

If it helps, I have 512 px, update rate 3, 250 meter, detail 0.5 dynamic reflections enabled.

 

That is proof that support even can't read all messages of dedicated topic. That's so bad!

 

Modern dashboards for D-Series and Roamer don't have ESC indicators for variants with ESC.

 

No. Also I think we should have some kind of reactions from devs for our replies to understanding of your point of view at less IN THIS topic.

That issue was explained IN THIS topic.

 

Hi! My game makes a glicht when moving the camera around , (0:18 is visible)
My specs:
Intel core i3-7100
16BG Ram
Intel HD 630
------------------------
The problem fix changing the lighting to Low instead of Lowest (thx to Confused_Deer43 for help me)
This didn't happen in the 0.20 ofc

 

Haha, actually did this all the way back when the e-Cherriers were added. Hence understand the effect of the brakes cooking themselves quickly, though was too lazy to add an upper speed limit at which to deactivate the system and a slight but permanently active amount of TCS at the motor side.

The post earlier was in reference to IRL implementation, I think only the manufacturers' chassis/dynamics electronics engineers and OEM suppliers know the exact parameters on eDiff activation thresholds and the like. Can't find particularly detailed specs in owner/technician literature so far, only the basic operating principle and maybe the deactivation speeds.