0.30 Discussion Thread

the stambecco's rev limiter doesnt really work on the i6 petrol
the standard engine, with the engine management slot empty, doesn't have "hasRevLimiter":false, inside its engine jbeam, meaning it does still have a rev limiter. similarly, the standard rev limiter doesnt have "hasRevLimiter":true, unlike the adjustable one which does. this means if you add "hasRevLimiter":false, to the base engine jbeam you have to go back and add "hasRevLimiter":true, to the rev limiter jbeam for it to function. yes, i know this is a bit picky but a fix would be appreciated

 

The BNG_LightFlare_1 used for exterior ambient lights on some maps has an occlusionRadius of 0 which means it's visible through vehicles:


Using any value above 0 fixes it.

 

charging stations for electric vehicles do not work on the map of italy, at least in fastello

 

Not sure if this is new in 0.30, but surely a 15 story rowhouse with suburban roof is rather unusual:

 

The fuel consumption sensor does not work correctly on all cars, when the car is stationary, it continues to try to calculate fuel consumption even with the engine turned off. something is wrong with the algorithm

 

A quick trip to Google Earth suggests that while 8+ story residential buildings with sloped, terra cotta roofs aren't super frequent, they're hardly unheard of in SF.

 

Looks like this calculates the average consumption

 

really?) but I thought this was the number of hours before refueling)
«calculates very strangely, in my machines it works differently»

 

I am having trouble with the Vulkan renderer. I have very low frames using it. Using the normal renderer, it works just fine. I can usually run 80 frames with max graphics, but I am only getting around 15 with the Vulkan. I have a GTX 1650 TI, a Ryzen core i7 10700K, and 16GB of ram. I think I might need more memory because it keeps saying that over 80% is being used. Is this an issue on my part or is the Vulkan renderer just not fully optimized yet?

 

i believe this is because (and i could be wrong) there is some current issue with the way vulkan handles when you run out of memory causing massive framerate drops

 

@Leeloo or anyone: Kind of a random question but do you know who came up with the opponent car lists for the AI races at Hirochi Raceway, Industrial Site, and so forth?

 

Question: how should it work? How is it supposed to open if there are plates on both sides? How does the lever go through?

 

I think the little L brackets would realistically have to pivot out of the way, but that would add unnecessary complexity to the jbeam structure.
have a go at jbeaming it yourself, you'll either see why it's so difficult, or you'll be able to prove me (and the vehicle team) wrong

 

Ok)

 

I'm not sure if this is how it's supposed to work, but I've noticed some weird behavior with the clutch in the Barstow. The clutch petal tends to go from fully depressed to fully released repeatedly, and on its own while the car isn't moving. It isn't just visual, though, as it's actually releasing the clutch.

 

In the new video on "Rock Island" you still have grass on the road , so it turns out it's not a bug but an innovation?

 

Will the Bluebuck receive PBR interior materials soon? Adjustable odometers would be cool, as well.