Assetto Corsa Competizione: New Hotfix Releases Deployed

[Paul Jeffrey]

Kunos Simulazioni have deployed a couple of hotfix releases for Assetto Corsa Competizione, including some very welcome VR performance advice...

Well, let us be honest here, these are some pretty sizeable update notes considering the "hotfix" tag, so don't be fooled into thinking they are just quick and simple new build releases aimed at single areas of focus - most sim racing game developers don't have release notes this large for main build updates!

Alongside the new fixes, Kunos have also offered some advice to players looking for more performance from VR devices, of which you can see the details below:

ACC Hotfix Update Notes:

v0.6.2

• Fixed wrong first lap time when start-finish line is crossed before the green light.
• Fixed AI erratic speeds during formation lap.- Added lumirank update in the replay.
• Enabled detailed animations in onboard cameras.
• Added session over message for qualifying/practice.
• Improved AI pace at Monza and Nurburgring.
• Added intermediate solution to run the formation sequence in Multiplayer. Overtakes may happen, but enables the controlled formation sequence.
• Fixed protocol mismatch on the rating backend, resulting in wrong data.
• Fixed SA Rating working in Multiplayer.
• Fixed RC Rating preventing data being stored in Multiplayer.
• NOTE: Due to incompatibilities with the data, the Rating Profiles will be reset again.
• Fixed end-sequence in Multiplayer: spotter announcement, checkered flags and so on will now be correctly triggered.
• Fixed formation sequence not starting when the leader is in the pits.
• Fixed rare crash in the Multiplayer server, possibly also crashing connected clients.
• Fixed races not showing time gaps in Multiplayer races.
• Fixed tyres not being correctly selected based on dynamic weather conditions along with the setup.
• Added “Official Test Server” opened for experimental features and testing. See the official support forum.
• Fixed search and password text input issues in VR.

v0.6.1

• Added rear-view camera display in Lamborghini Huracán GT3.
• Consistent mirror resolution in all cars.
• Fixed ghost car not working in some instances.
• Ghost car now has a more stable render.
• Fixed replay highlights increasing with longer sessions.
• Fix to mirror resolution default. – NOTE: defaults to intended default resolution (MID) without changing anything. The EPIC setting is now eliminated. No action required from the user.
• Added precision timer to MP.
• Fix to false-positive DQ resulting from teleporting to pits.
• Fixed standings widget not updating total player count.
• Fixed driving camera resetting after entering and leaving the pause menu.
• Fixed both Nissan’s’ setup ECU values, now start from 1.
• Fixed potential issue with road effects settings not loading properly.
• Race communication durations edited for important messages.
• Race results now show gaps to the leader.
• AI skill and aggressiveness sliders remember last set values across game modes. NOTE: AI values will reset after initial launch so pay attention when playing for the first time.
• Informative help snippets added when selecting each graphics setting.

Assetto Corsa Competizione is currently at release 6 status.

Check out the Assetto Corsa Competizione sub forum here at RaceDepartment to stay in touch with the latest news, community discussions and fan engagement regarding this well developing racing simulation.

Like what we do at RaceDepartment? Follow us on Social Media!

 

 

[mrbungle83]

Since this build, its the most satisfying sim i have ever driven the FFB is so communicative i am seriously starting to get excited.

 

[Toonces]

Well if you want to simulate a series where gear ratios are fixed, you don't allow adjustments...

You have a point, but this works only if the ratios are well chosen. In ACC, they're too far apart for my liking.

 

[Peter Kerényi]

You have a point, but this works only if the ratios are well chosen. In ACC, they're too far apart for my liking.

Rules are rules. If you have to use homologated gearing, you have to learn to drive around it or adapt to it. As Kimi would say, it's the same for everybody.

 

[AJ McDaddy]

Decided to fire the game up and run a few laps. Got to say visuals are great as is FFB fo me. I am though getting the 100% CPU warning in the top left with a field full of AI, but only getting the occasional frames drop. GPU a GTX 1080, CPU i5 4690K).

Having seen a few vids of online issues I'm sticking to offline for now. Having said that, this has to be the best AI I've ever raced against - kudos to Kunos there.

 

[miky90]

I have read that the framedrops in gaming in these days have been caused even by a bad windows 10 update.

 

[Fernando Deutsch]

You missed one, Loading times are excellent!

This is something that puzzles me. How on earth they can load the track and cars so fast with the level of detail on both of them.

 

[Alex Townsend]

Decided to fire the game up and run a few laps. Got to say visuals are great as is FFB fo me. I am though getting the 100% CPU warning in the top left with a field full of AI, but only getting the occasional frames drop. GPU a GTX 1080, CPU i5 4690K).

Having seen a few vids of online issues I'm sticking to offline for now. Having said that, this has to be the best AI I've ever raced against - kudos to Kunos there.

I got the CPU warning too on a i7 3770k at 4.2
Lowered the number of cars competing by 2 and didn't see it again.

 

[AJ McDaddy]

I got the CPU warning too on a i7 3770k at 4.2
Lowered the number of cars competing by 2 and didn't see it again.

Yes, I reduced mine last night and haven't had it since

 

[DrRob]

Interesting. I had the warning constantly flashing at the top left corner although I had steady FPS in the 70s-80s, no stutters. IIRC I raced a field of 20 cars (i5-6600k)

 

[Alex Townsend]

Interesting. I had the warning constantly flashing at the top left corner although I had steady FPS in the 70s-80s, no stutters. IIRC I raced a field of 20 cars (i5-6600k)

I think the update also increased number of cars as iirc I had about 26 or 24 selected yet didn't increase them myself.

 

[Jorge Villar]

On each track the number of cars you can select for offline racing is different, I think it depends on the number of pitboxes. I could be wrong though.

 

[Gergo Panker]

Interesting. I had the warning constantly flashing at the top left corner although I had steady FPS in the 70s-80s, no stutters. IIRC I raced a field of 20 cars (i5-6600k)

The warning has nothing to do with fps. It pops up when the physics thread of the CPU can't keep up with image being rendered, thus constantly being late (see the L counter in the fps app). No matter how playable your fps is, your gameplay will suffer and you should lower the amount of opponent cars until you don't get the popup anymore.

 

[DrRob]

The warning has nothing to do with fps. It pops up when the physics thread of the CPU can't keep up with image being rendered, thus constantly being late (see the L counter in the fps app). No matter how playable your fps is, your gameplay will suffer and you should lower the amount of opponent cars until you don't get the popup anymore.

Cheers for the pointers. Will do. But what exactly will I be experiencing with the cpu warning on? Didn't notice anything.
I suppose with v0.6 some serious change was implemented, since I never experienced this prob with the previous versions and same number of opponents?

 

[AJ McDaddy]

As previously reported here, the CPU warning was introduced in the latest hotfixes and the recommendation from Kunos is to reduce the number of AI. Lord Kunos has also stated:
"the fight is not over yet.. we finally steered ACC in the right direction with 0.6 regarding the stability of the software which frees up some time to look into performance optimizations."
So we can expect some CPU (and GPU) performance related improvements.

 

[Jorge Villar]

As previously reported here, the CPU warning was introduced in the latest hotfixes and the recommendation from Kunos is to reduce the number of AI. Lord Kunos has also stated:
"the fight is not over yet.. we finally steered ACC in the right direction with 0.6 regarding the stability of the software which frees up some time to look into performance optimizations."
So we can expect some CPU (and GPU) performance related improvements.

This is one of those "I told you" moments. Dedicated to all the complainers.

Also, nice to see Lord Kunos active again in the forums. I guess he has been basically chained to his programmer chair until the release of 0.6.

 

[Emery]

S3. Despite all odds (and previous inclusions) now we're stuck with the default gear ratios as if we were all racing Austin-Healey 100s.

Know what you're playing! GT3 rules do not allow different alternate gear ratios. AC was incorrectly generous in that regard.

 

[Alex Townsend]

Just tried a wet race, medium rain at 7pm with 29 opponents. CPU usage warning was flickering in the top left hand corner.
I previously had it set to 25 and didn't get the warnings. But that was in the dry. Would the weather have any effect on this?

 

[Daggerman]

I have a problem with my G27 and ACC.

If I try and map controls it just continuously tries to map an action to G27 button 10. So you click on an action like “look left” and then in a split second it’s applked button 10 to that action. Any ideas?

 

[Alex Townsend]

Also, just to advise, I'm having to turn down an awful lot of things to get it running at 60fps in the wet and dark. I'm sure it's better than it has been before but still, a GTX1070 really being brought to it's knees to get acceptable frames...
I figured I'd throw the worst case scenario at my system and set it for that, then I can go into any game mode with any weather or time settings and should be ok.
I wish there were graphics profiles that you could set during the game. Then you could set one for dry/day, wet/day, dry/night, wet/night etc.

 

[Timberwind]

Any ideas?

Make sure the stick shifter is not pressed, wheel is straight and all buttons are not mapped to a keyboard stroke. Check whether your G27 is false-recognized as a Driving Force GT by opening the profiler. If so, you need to fix that first. I had the issue you described as well, but fixed it and could freely map all buttons. But I do not quite remember what I did exactly.