Weird, thats what it always was for me since I first installed the game a couple years ago, I looked for another keybinding that would move the car back to a moved a certain point repeatedly and I couldnt find it. I mean I can still move a respawn point around with F8 like I could before, its just now with F7 its going to a different spawn point than the one I set using F8.
The standard R key bind should do the trick for you, reset function sends you back to the last position you reset at, this position can be changed by using the INSERT key which is the rewind feature, and if you happen to want to go back to the original spot you can save it until you change it with CTRL + HOME and use HOME to return to that spot.
On Utah AI will turn off the lights leaving tunnels at night and won't turn them on again. Same happens on junction near east tunnels but strangely it occurs more random. AI driving on highway from west will turn off lights right before tunnels. Also AI have problems with that same junction. Every AI will take that strange path.
Average consumption (L/100kmh) is not calculated properly, when you drive a longer distance it doesn't average out but keeps jumping around and it drops to 0L/100kmh when you turn of the engine. Also can you add an option for turning on/off driver camera not centering while stationary (the feature that was introduced in 0.25)
Engines on some cars can still be easily damaged due to oil starvation by just doing hot laps. For example: Civetta Bolide (390 GT) Cherrier FCV(more noticeable in Vivace S version,including the Vivace Race one) Hirochi Sunburst(start from trim 2.0 sport and up,really noticeable in 2.0 Sport RS AWD) They will get engine damage during corning and lose a few HP power every a few laps,usually the oil starvation time is very short but just enough to damage the engine,thus they won't trigger the oil starvation message on top of the screen.But you can see the damage by using the Engine Thermal Debug App Please, do a recall to them. For Bolide 390 GT I think it's acceptable because she is old. But for Vivace S and Sunburst RS AWD I think they are modern cars which is suitable for or even designed for track day driving,right? Maybe increase the engine maximum safe G a bit (it's now 1.2G for almost every engine on street car I believe)for those modern CAE'era designed engines will solve this problem.
Well I mean, the Bolide was also designed with competition in mind. It shouldn't oil starve just from hotlapping.
Seriously though can we have the old scoreboard? This is completely useless. I dunno what cars recorded those times, who drove them... the old system was heaps better.
Yeah, I agree on that. Also a fun fact.The 2 cars under Civetta band in the game seems to have a different set of Enigne Maximum Safe G. For every other car this value is the same,1.2G for street version and 1.5G for race version. But on Bolide it's 1.3G for street version and 1.9G for race version. On Scintilla it's 2.0G for street version and 2.5G for race version. And some other sports cars like the ETK-K and SBR4 are at the edge from getting engine damage while doing hot lapping,they will get oil starvation in fast corner but the time is just short enough to not damage the engine.
why does utah not work for me? when I start it, it gives the error 0xc000001b it was back in 0.25.3 and now in 0.25.4 the same thing, I didn't go into the game for two weeks during that time the fix 0.25.3 came out and after it utah doesn't work
What happened?! Even v0.25.1 is not released yet (or atleast is not mentioned in the devblog section) so... how you say you've released the v0.25.4?! What has happened to your Instagram page?!
as I said, the game crashes with the error 0xc00001b when you start, other maps work well, according to the loading menu, the game loads all objects except roads when the game transgresses as loading roads, it writes 0% and the game crashes. --- Post updated --- do you have utah running on game version 0.25.3? or do you have version 0.25.2? --- Post updated --- in version 0.23, in some kind of fix, the same thing happened with the east coast of the USA, with the derby arena, and something else there gave errors 0xc0000409b and 0xc0000001b, it was kind of due to a memory leak, but now it's the same only with Utah
The new hotfix made police chases buggy. It says both "The suspect is under arrest" and "The suspect escaped from you", and is too fast, its like 1 suspect per 10 seconds, and there can be 2 suspects at the same time! and the messages for the suspects is glitched. Video (look at end):
Can you maybe give a bit more information about this? Are you running in safe mode? Did you try to re-install the game? It seems to be either a problem on your side, or maybe caused by something specific that I didn't experience. I personally didn't notice any issue on Utah when I play.
25.3 tested in Safe Mode. Now I tested it in 25.4 but now paths are working correctly. However AI is still turning off lights here.
With what? Police chase? Then just go in a police car and drive around (with traffic cars/ai cars). In the chat it says "Suspect fleeing" or something like that.