Update Speculation thread

they should put an epilepsy warning

 

NOICE! Had the same blur bugs when my water mod had a spec value of above 1 or something like that. Didnt cause the steering wheel offset though lol

 

Reminds me of that tragedy.

 

Tbh, I haven't found the Vivace S 410Q Arsenic to be understeery, even with the same size of tires all around and even with the Clutchex AWD system. If anything, the rear end is drifty enough to make the car turn and feel alive while doing it.
Also, the IRL counterpart also had available carbon-ceramic brakes on its front axle and they were useful when its engine was made of iron - since 2017, it's made of aluminum and these brakes got cut from the options list back then.
Although I don't find any problems with the handling of the Vivace S 410Q Arsenic, I still feel that it needs carbon-ceramic brakes on its front axle because the Inline-5 is capable of serious speeds, especially when tuned. And I hope the BeamTeam, sometime, actually finds a bugless way to make them be lighter than the typical steel brakes, just for the true simulation of trimming a few lbs/kgs from up front (which, in turn, may or may not make the FCV platform's handling a bit more neutral, which, again, has never been a problem for me).

As for the Selecta SportPlus 2R tires, I totally agree with you on the performance front (they're a bit stickier than Sport Tires, after all), but, this time, my context is that of looks: the reverse-staggered set up (265/35s up front, 245/35s at the rear, like you said) would look ace on the fast FCVs and it would be a great way to distinguish the S Arsenic variants (S 310 Arsenic, S 410Q Arsenic) from the normal S ones (S 270, S 350Q), which use the normal 245/35R19 Sport Tires at all 4 corners.

As for the handling of the Ardente, it's definitely gonna be more alive than the other FCVs due to all the things both of us said, but there's something else we must consider with this car: it has an active rear spoiler. That definitely has to account for something, eh?

 

What's interesting to me is that 0.3.0.4 (the Moonhawk update) dropped on 11 September 2013. It's one of only two updates to drop on the 11th of the month - the other is 0.5.3 (the update that added engine thermal simulation), which released 11 March 2016. What's funny is that the Moonhawk was one of the most stressful vehicles for a PC to run when it released, due to its bumpers constantly colliding with itself.

So, the 11th's been home to computer-baking and engine-baking.

Ooh - this makes it the third vehicle to have an active rear spoiler, and it completes the trio of engine placements (rear (SBR), mid (Scintilla), front (Ardente)).

 

“Everything is chrome in the future!”

 

Looks like the same bug that real atmosphere mod has.

 

Yep, we can see the panel seams on the hatch and the folding arms under each side of the spoiler!
And that's an interesting point you made!

 

Try brightening the teaser to see if we can find anything.

 

I think its bright enough

 

I brightened it up a bit.

 

So, according to Stenyak's reply to this Reddit post, 0.39 will probably come out after the 12th of July (which it wouldn't have released on, anyway):

I figured that would be the case.

 

You know, I hope they add planes as a part of the skybox flying overhead. Just the contrails would be a really nice touch to make the world seem alive beyond you.

Also, simplified traffic hopper

 

Whew, I was worried it would come out earlier.

 

Why is that?

Regardless of when it releases, the update would've never dropped on the 12th. It will be funny watching the subreddit implode on that day.

Ooh, that would be a nice touch. However, I feel like the devs won't do that, because then, people will ask when they'll be able to fly planes, and...it took over nine years for water-traversing vehicles to be added (Wydra).

 

Reminds me of when the Vulkan renderer just came out. On my laptop the whole ocean was black boxes lol

 

We already knew it won't be July 12th. Based on recent updates you can pretty accurately find the exact date the update will release, which is obviously

 

Hm? I think you cut out there, did you mean to say it releases on