Automobilista 2 V1.6, IMSA Track Pack, Endurance Pt2 & Lamborghini DLCs RELEASED (V1.6.3.6 Live Now)

This is a legacy bug that has been there since forever and impacts mostly auto-rolling starts in some car / track combos from certain position. Fixing it requires rewriting rolling start logic which is on the taskboard but that is not an overnight job and not a particularly high priority for the time being. You should be able to largely mitigate the chances of it happening on the tracks where it does happen by simply running manual rolling starts

As per above - the changelog clearly refers to the issue being mitigated, not fixed. A sample size of one isn´t going to be very representative, especially if it is around issues of AI multiclass racing on a track that has segments allowing for many cars to run 4-5 wide abreast funneling into where only 1-2 will fit. It tends to be an issue with real racing too.even if not quite to the current extent of the game.

By now you should all be very aware of what AMS2 is and isn´t folks - it is a game with lots of content, lots of options and lots of features and that sort of design means it is always under constant maintenance, inevitably with some longer standing issues along with some that never gets resolved as an inherent result of the very ample territory it provides - it´s the "price of fredom" as far as this particular game is concerned.

You can set yourself up for frustration by insiting on running a certain combo of car / track / settings that you already know currently has some issues; you can work with the software as it is and instead use any of the vast amount of permutations that do work rather well until the current issues are resolved or further improved on, or you can move on to whatever game does offer what you are looking for if this one isn´t it. By all means take the path your heart leads you on but please give the constant forum moaning and departure annoucements a rest as they aren´t really going to move the needle in any direction.

 

I don´t think we ever had a "release when ready" approach, not least as one man´s "ready" is another´s "unfinished mess" With AMS2 it is always been about the overall value, both of the game generally as well as the updates we deliver for it. Sometimes the value needs to be big in volume and spread, sometimes it´s good enough to be incremental but if we aim too high neither the game not its updates would ever see the light of day.

We are well aware IMSA and the Daytona 24h is a especially premium content in the sim and that is one of the reasons we pushed to fast-track this update as we could see the issues were beyond allowing that particular race to be an enjoyable experience in v1.6.3.5; unfortunately just wanting to fix certain issues doesn´t mean we can in any arbitrary timeframe.

The next best thing is to at least mitigate some of these on the shortest term possible, so that´s what we did - I personally ran several test runs over the weeend while performing these adjustments and had the AI run through the initial couple of laps relatively unscathed in many of them, while also having two 24h races scaled to 48min where the AI pitstop strategy was fairly competitive. Naturally I also had runs with lots of carnage into T1 or the Bus Stop and those remain issues to be further improved on, and that is what we will continue pushing for.

So it goes back to the point of my previous post - as premium as the IMSA content is and as important as we all find for it to be working as well as it possibly can be made to work on every scenario, it doesn´t change the fact it is one combo out of literally thousands - as with any product one needs to take its good with its not-so-good at least until we manage to make it better; everyone is obviously very welcome to continue reporting on the persisting issues and we are certainly chasing to serve the segments of the userbase that aren´t quite seeing the glass half-full, but ramping up the intensity or the volume of the complaints isn´t going to move the needle wrt to how fast we can make the progress they want to see.

 

Did read it many many times and it´s one of those egregious issues we have been eager to get on top of for the longest time. There is a recent lead on what´s at the root of it that one of the devs is already chasing but until it leads to a fix there is little we can say that is going to be of actual value.