Bug Reports - Automobilista 2 (Read the Opening Post)

The same happened to me:
FReiza - Road America
FClassic G3 - Silverstone 75

 

Me too Ramsay happened in a race with V8 Supercars and today with a P4 serious issue when in a organized race. My suggestion is to run lobbies without engine damage.
Don't join ones with it on especially ranked lobbies.

 

Formula Classic Gen 2 Model 3:

In the car selection screen, it is said that the car would have a boost button, but it has not. Was there in former builds, but it has been removed.

 

Silverstone Historic 1975:
Many AI crash when coming out of the garage because of the brickwalls which are placed right and left of the exit.

 

I Know this has been asked numerous times, are Reiza any close to finding out why duplicate liveries are still appearing ? I know this isn't game breaking , but it would be nice to know if they can rectify it.
Many thanks

 

Strange thing: It always happens in championship mode. But in single races, it does not occur in each car class, just in a few. And in some of those, the bug only shows up when custom liveries are in use (Formula V12).

 

Agreed, i think it was either 2 or 3 Formula classes that they are duplicated, haven't seen it in any other classes.

Ok i have found 4 classes that have the duplicate liveries, Hope this helps

Formula Reiza
Formula v10 Gen 2
Formula Ultimate 2019
Formula v12

 

V. 1.3.4.0
Track: Velo Citta
Car Used: P2 - MetalMoro MRX Duratec Turbo
Applicable Settings: 30min + 1lap Multiclass Race P1, P2, P3, P4 with 4 slots weather (heavy cloud + rain + heavy cloud + heavy cloud) - Used this way because in the attempt with a past date (06 Mar 22) and the system does not can find the date.
Report:
A - No weather transition, just heavy cloud throughout the race.
B - Fuel calculation for 30 laps (suggested) yet with 16 laps a refueling stop was necessary, which did not happen in 2 refueling attempts.

Refueling should only be available in allowed categories, in the current version you can do it with Karts and FUltimate for example, which is wrong. Probably other categories have this problem.

 

Track & Layout Used: Any
Car Used: Formula USA all gens
Applicable Settings: Race session with high (50+ C) track temperature
Report: The F-USA tyres are too sensitive to high temperatures.

As soon as the track temp hits 50 C (which happens ALL THE TIME at some US tracks), the tyres overheat to 100 C across the board with no hope of fixing it through setup changes or driving style. The situation is the same with soft or hard tyres, makes no difference. At this point the car becomes undriveable, spins all the time in slow corners, and understeery in fast corners. The AI have no tyre wear or overheating so they will run rings around the player no matter how low you set the AI.

Basically the tyre temperature effects currently make many cars undriveable at high (50+ C) and low (10- C) temperatures, making "real" weather unusable in practice. This is magnified by the exaggerated road surface temperature, where even a cloudy day at 7 a.m. can see 40+ C track temperatures.

 

Track & Layout Used: Any
Car Used: Porsche Carrera Cup
Applicable Settings: Any
Report: Car behaviour over the curbs and bumps; suspension/tyre model after wheel is back on the road produces very oscillatory response with very poor damping and strange rebound which makes car almost jumping.
Steps to reproduce: Drive the car over the curbs and bumbs and observe car jumping like crazy.

This car is a "curb eater" in real life and should not have any of this problems. However currently even taking small amount of curb produces "jumping car".

 

V. 1.3.4.0
Track: NA
Car Used: NA
Applicable Settings: Multiplayer Rating System
Report: I'm aware the rating system is beta but I want to provide feedback. Yesterday is the 3rd time I've had my rating go back to U and experience to Rookie. My stats are still all intact but I no longer can enter certain lobbies. Also, in lobbies other drivers still see me as a S17xx rating but I only see the U1702 and can only enter lobbies U1702 and below. The first 2 times my rating came back and hope it will again.


UPDATE: my S rating all came back yesterday afternoon, and now again today it's lost to U17xx.

 

Track & Layout Used: Any
Car Used: Porsche GT3
Applicable Settings: Any
Report: Car behaviour over the curbs and bumps; suspension/tyre model after wheel is back on the road produces very oscillatory response with very poor damping and strange rebound which makes car almost jumping.
Steps to reproduce: Drive the car over the curbs and bumbs and observe car jumping like crazy. I recommend Nordschleife; this car is barely drivable there. I have issued problems with suspension of this car year and something ago and still not fixed:

 

Just to portray what I meant:

 

F3 301 is still broken, TC and ABS are enabled with values 0-60 and 0-100 ..
Also, Ultima GTR cockpit position is still moved to the right on UW monitor

 

I know it has been reported before but with a bit more testing I can add that when you create a custom championship, no matter what cars or tracks and when you set different times for each session when you run the first race it will run each session at the time you set but for each of the remains rounds every session times defaults to whatever the race time is set at.

 

Track & Layout Used: Monza Historic 1971 10k (no chicane)
Car Used: Lola B2K00 Ford-Cosworth (tried with several other cars without luck)
Applicable Settings: Test Day / Custom Event, Date Type Default Date 25/04/1971, Start Time 14:00, Accellaration 10x , Weather Slots 3, Overcast/Cloudy/Sunny, Wether progression 2x, Livetrack Preset: Default Progressing.
I've tried changing all of these settings, none made it work.

Report: Game hangs on loading, around 10% into the loading bar. The loading bar text still animates, so the game is actually running, but it doesn't continue loading.

Steps to reproduce: Every track, including Monza Historic (with chicane) loads fine, except for this track which hangs on loading. CPU is at 25%, RAM at 26% usage.
I've tried re-installing the game. Installing on a different hard drive. Uninstalling DLC and re-installing. Tried Deleting User folder. Also tested launching the game in Non-VR and VR.

PC Specs:
CPU Intel i7 7700K @ 4.2 Ghz
64GB RAM
GTX 1080 Ti
T300RS (also tried with Xbox One controller, no controllers connected)
Logitech G29 pedals
Oculus Rift CV1

Game Version:
V1.3.4.0

I haven't been able to find anyone else with this issue, I hope you can help.
As stated above, this only happens when trying to load Monza Historic 1971 10k (no chicane) in any mode.

Thanks everyone!

 

I hadn't played AMS2 in a few days, I drove the 2 F-V10s today and every time I use the brakes I get this high pitched sound that's usually associated with ABS even though I'm using authentic aids and those cars don't have ABS. In another forum an user reported the same issue with every car he tried.
Edit: I just tried a few more cars (F-V12, F-Classic G3M2, F3-309), all have the same issue, high pitched noise while braking, authentic aids.

 

Just noticed this today after not using the Formula Classic Gen 1 and 2 for a while:
On Imola 1972, severe shaking or bouncing in car on front and back straights. Like its scraping the ground maybe ( too low)? Default setup.
Tried with Formula Retro with no problem.
Anyone else notice this?

 

Sorry, can not help. Track works fine here on my PC, no issues with loadin

 

OS: Windows 11, latest version. WMR on SteamVR using HP Reverb G2
Version: V1.3.4.0 (any version before this it also happened)
Track & Layout Used: Nurburgring full 2020 observed but probably happens everywhere
Car Used: Cadillac DPI
Applicable Settings: Camera movement g-forces
Report: when setting all camera movement g-forces to 0 I would expect in VR that my body doesn’t move forward if I hit the brakes. Currently when hitting the brakes in this car, I can see my body suit appearing in my view from the inside. I am in helmet cam mode in VR. Re-centering while braking does not solve the problem. Recentering while holding my head as far back as I can and then keeping it forward (a bit unnatural) solves the issue, but should not happen.