0.25 Discussion thread

mission failed successfully

 

Oh! That totally makes sense. Thanks for pointing that out! I do have "Start vehicle engines preheated" disabled in my own settings, and I did notice when I was testing in safe mode (where that setting would have been enabled) that the initial redline was higher.

 

I still can't enter traffic with this?

 

The police AI is really having some weird issues, but it seems to me that the whole game just forgets the players position?

I know that it is not intended to have police in the Garage to Garage scenarios, but it did work in 0.24. Also in that scenario I noticed that when the police starts to act weird, traffic stops spawning around the player and the minimap is'nt updating the players position either.

Below is an unfortunately long video for a bug report, but I felt like showing everything from desktop to desktop(also forgot that in safe mode I would lose my keybinds so I really struggled with the default settings...) The bug happens @ 6:57 - you can see that the minimap stops working properly

I did get the support ID for this aswell: 132572
Also the game froze for a second when I pressed ctrl+L (Near the end) and doing that in that situation crashed the game a little later every time.

Also I feel like pointing out the drawbacks of the new bipolar driver camera view aswell;
Just trying to drive in a very relaxed manner is truly horrible with a controller since I can't look both ways fast when stopped and every time I stop when looking back or to the sides the camera snaps back to looking forward. I actually got dizzy from recording this video.

I did drive in a specific manner to exaggerate the wonky camera behaviour. And I do unerstand the idea of sitting in a stopped car and admiring the interior(and pushing buttons in the Scintilla), but I could really use an option to disable the new behaviour.

Beam is still my go to cruising game, simply due to the physics not giving up when driving slowly unlike all(?) other driving games.

 

The barrel knock over in the Field on East Coast is impossible to beat. A gold is 54 points, but there are only 32 barrels and you can only get 20 extra points for the time, leading to a best possible score of 52, less than the 54 needed. It's the one in the field, not around the house or sawmill.

 

You're talking about the forest one right?

There are 34 barrels for me ¯\_(ツ)_/¯

 

Huh that's odd. I'll try it again, maybe something didn't load right.

 

I guess combined with the dashboard fixes and the traffic, there are a bit of fixes, but maybe I'm just not clear on what's a .1 vs a .0.1 - thank you for the help!

 

If you look underneath the black visor, you can see them. IDK how I feel about it.

 

Come on, guys. I'm in a minority, but the new sounds just aren't doing it for me. They need re-balanced. There's so much bass you can't hear the glass breaking or metal scraping.

 

it seems fine to me, realistically crashes seem to mostly comprise of a deep thud, with all the smaller sounds drowned out.

 

I still think that you should be able to adjust every sound within a collision, and not just have one slider titled 'Collision'.

 

The Moonhawk may be in the background of this 0.25 Update but the new rear fascia design and the treatment of the skins/detailing issues the car had since the 0.23 Update really look the part. And the fact that the bumpers and the side stripping can now be colour coordinated makes the car look a bit newer than it is.
Overall, a really nice (and needed) piece of work. I did notice a few misses though:

1. In the vehicle selector, the pictures of the variants that got the treatment weren't updated to depict the changes to these variants and they must be.
2. When the "Powerglow" paint design is applied to the pre-facelifted 1973-75 variant, the Front Fascia and the Front Special Fascia clips seem to be darker in color than the rest of the body. Plus the powerglow light strips don't follow the lines and the sculptures of the 1973-75 Front Fascia and the 1973-75 front Front Special Fascia, as they do with both the rear ones, making the sum seem incomplete.
3. When the "Pinstripes (Body Colored Trim)", "Special & Stripes (Body Colored Trim)", "Special (Body Colored Trim)" and "Stripes (Body Colored Trim)" paint designs are applied to the facelifted 1976-78 variant, the chrome outline of the facelifted rear fascia doesn't get body colored. Only the chrome strip finishing the trunk gets body colored and it makes the rest of the outline seem unfinished/incomplete. On the pre-facelifted 1973-75 rear fascia, the chrome outline gets fully body colored but the chrome trim rings around the taillights are affected.
4. On these four paint designs there also seem to be some slight miscoloring issues on the body details and they depend on what color the stripes are getting. The chrome details on the windows, the outlines of the wheel arches and, finally, both the pre-facelifted 1973-75 and the facelifted 1976-78 front and rear fasciae (plus the circular trim rings of the taillights of the pre-facelifted 1973-75 rear fascia), they're all affected this time.

 

Not sure if this is new to 0.25, but when restarting a mission, parts that were destroyed dont regenerate.

 

Several days into using version 0.25 and I found a few more issues or general observations to point out:

• The game will "preload" the tips right after entering a level. You can see it for a split second at the top before properly loading the tip.

• I noticed that the game tends to use up a few GB of hard drive space during a session. The more detailed a level is, the more space it uses up. In addition, exiting the game will free up whatever space it took away during said session. Maybe it has something to do with some form of cache when the 0.25 update was released, although the temp folder (where the game cache resides) uses up way less space. Take, for instance, loading Grid, Small, Pure with the default D15 V8 4WD. In that session, almost 2 GB of hard drive space was used up while running the game, whereas the temp folder was only a few hundred MB in size. This won't be an issue for most people with plenty of hard drive space, but I'd figure I still mention this anyway.
• Some FPS drops happen from time to time, most notably after 5 to 10 minutes during a session. It's more noticeable on lower-end computers, but not so much on higher-end ones. And speaking of which, some people have reported that their GPUs are not being used by the game for this particular update. I wasn't one of those people affected, since the game is running normally on my end. Updating drivers seem to resolve this, according to a few others. Again, something worth mentioning anyway.

Regardless, I am hoping that I'd receive some answers and/or solutions to any of these

 

0.25.2 has fixed the FFB issues I was experiencing. Great work. Now I can enjoy the Scintilla

 

Is anything being done about the tree shading or lack of SSAO settings?

 

In camera options the slider for driver fov goes up to 150 but fov maxes out at 120, this has been a thing for a while

The H-series should have more transmissions from the D-series (race 6 speed, drag 4 speed etc.) and possibly other parts

Also thanks for the ffb fix