"I can´t run Automobilista" - Official troubleshooting topic

I recently purchased the bundle of Automobilista 1 Ultimate Edition + Automobilista 2, but when I try to run Automobilista 1 or Automobilista 1 Beta it does not run. It says that my system is below requirements, but bizarrely enough, It runs perfectly Automobilista 2, which requires more processing and graphical power.

I have a Razer Blade Stealth 13
I-7 10th gen 1065G7
NVIDIA GeForce GTX 1650 with Max-Q Design

Please advise, I am about to request a reimbursement because of all the headache it has already given me.

 

Thanks I searched the forum and found a 'solution' to downgrade to a previous beta build of the game. Now it works again. Hopefully the devs will fix this so that I can also enjoy the latest hotfixes of the game, like probably many other players with a thrustmaster/fanatec combo.

 

Why does 1.5.25 lead to a lower framerate? I use that version.

 

Nobody from the studio is willing to help me with this issue? the exact message I have is:
"your computer is below the minimum requirements to run automobilista. Press continue to try playing anyway." I have tried selecting advanced settings and/or enabling DynHUD. My CPU is currently processing at 3.21GHz. So, the processor should not be an issue. my computer specs are:

Razer Blade Stealth 13
I-7 10th gen 1065G7
NVIDIA GeForce GTX 1650 with Max-Q Design 4gb dedicated ram





Does anybody know any other form of contact with them?

 

Thank you for the reply @CrimsonEminence. Pressing continue does do anything, it gives me an error sound, and the game crashes. I've tried different combinations of selecting advanced settings and enabling DynHUB.

In Nvidia Control Panel, I have also forced the GTX1650 to be the preferred CPU, but it does not get to the point where the game even starts to use the video card. I believe the problem is with the i7 processor that is 1.30-1.50GHz in nature, but on turbo settings, it gets to 3.50GHz, but the game doesn't even try to run because of that (that's my guess).

 

Thanks for the reply @Domagoj Lovric. I suspected the DirectX 9 was not installed and got the installer earlier from Microsoft, but just to make sure I hadn't got the wrong one, I followed your suggestion and installed it from the support folder in the game.

I also forced the "ams.exe" and "ams config.exe" to run on the GeForce GTX CPU on Nvidia control panel (picture attached) and disabled the intel iris graphic card on device manager, but nothing worked. The game also never opens to even use the graphics card. I attached a picture, which you can see the graphics card activity window and it shows the AMS2 in use when I am playing it, which is never shown for AMS1 or beta versions.

My guess is that the game is recognizing the i7 Intel processor as not compatible because in the original configuration it is 1.30-1.50GHz, but on turbo settings, it gets up to 3.50GHz. Is there any way to override the processor?

Thank you.

 

Thanks @Domagoj Lovric. When I select advanced settings and press continue, the game simply crashes. Attached is the trace file I generated. I also tested the +highprio and -fullproct commands and they did not work.

However, I tried a lot of different things, and to be honest, I don't know what really made it work. Among the things I tried, I turned off the processor turbo, forced the game to play on the intel graphics card instead of the GeForce. In the end, I was able to run the game for the first time and got the setup v2.0 screen, which allowed me to select the Nvidia graphics card and populate my "config.ini" file.

Before the config file had the following configurations:
MasterPlayerFile=
CPURating=1
SystemRAM=0
VideoRAM=0
ObjDetail=1
TexDetail=1
VideoGUID=

After I got it to run for the first time it became like this:
MasterPlayerFile=
CPURating=4
SystemRAM=2044
VideoRAM=4064
ObjDetail=1
TexDetail=1
VideoGUID=D7B71E3E-5CD1-11CF-216E-0F301BC2D635

Now, I can play the game, but I still cannot open the Configuration tool that would allow me to test different graphics settings (it crashes in the same way that the game file crashed before).

I have a Beta version for the game as well, which I was not able to make it work through the steps I took before. The only way I was able to make it work was by copying the config.ini CPU and Video configurations from the normal version of the game that I made work. However on this version, I also cannot open the configuration tool and if you could think of something I can do to try to resolve this issue, I would appreciate we continue to work on it.

Also, how do I turn off the trace=2 command? It is tracing files every time I play the sim.

Thank you

 

Hallo everybody, i have the same issue explained in the post i quoted but the problem is that, previously, everythinghs worked flawlessly with the same configuration. I've been out of my sim rig for almost 2 and 1/2 yrs and this week i was able to mount againg my rig with my usual pc, but this time automobilista has shown this exact problem. I've tried the steps suggested before but without luck ( +highprio - fullproc, tried to close all programs like msi and other things, reinstalled everything) i'll try to post a trace when i'm going back home

My specs are :
i7 4770k @4.2
gtx 1070 @2050

 

ok here i got the trace file and a screenshot similiar to what the other user got

 

With Win10 Pro x64 20H2(or 2004), the game doesn't receive mouse input on main menu. Not only click also cursor doesn't focus anywhere. So that can't choose any session, setting, series, even can't quit from game. To quit game needs to kill the prosess from task manager.
This issue doesn't apeere on Win10 1909. It comes out only with win10 update to 20H2 or 2004, without any other changes.

 

So is there a solution for this problem?
I can't run AMS since a few month because CTD when changing from menu to track or sometimes when coming back from race track to menu (ESC).

I tried different thing installed d3d from the folder support and from MS. I also disabled a lot of the injected DLLs tried also some of the beta version. But nothing and I would really try the VR version.
Attached a few trace files.