Troubleshooting FAQ

[Killrob]

Game Crashes on Launch?

This could be due to several things, here are some of them:

Corrupted Install. Try to verify your game files. To do so you just have to right-click the game in your Steam Library, choose properties, go to the Local Files tab and click the Verify Integrity of Game Files option. It will notify you after it is done if anything was broken.

Didn't Get Redistributables. It seems Steam has removed the folder that seems to harbor the redistributable files that come with the first game install. If you accidentially said no to installing these, the game might not function correctly. These are the files you need:
https://wiki.automationgame.com/index.php?title=Install_Redistributables

Plugin OnlineSubsystemNull Failed to Load. This happens due to left over game files from a previous version that did not get cleaned out. The solution is to manually delete the entire Automation Steam folder \Steam\steamapps\common\Automation
and then verify the files to get a fresh download with no left-overs from previous version. Note that uninstalling and redownloading via Steam does not fix the issue!

Windows N & Media Pack. Players running Windows N can run into the issue of the media pack not being installed or uninstalling itself. This needs to be installed for the game to run, you can get it here:
https://www.microsoft.com/en-us/software-download/mediafeaturepack

Antivirus Blocking The Game. We’ve had tons of reported issues from people using Bit Defender, blocking the launch of the game making it just crash. What a bully! Add an exception for Automation and try to run it again. Also add an exception for the savegame folder Documents\My Games\Automation
Recently there have been a few reports of Windows Defender blocking the location as well, in that case you need to add an exception for that.

Low Graphics VRAM. Your graphics card or chip may have too little memory to stomach the default launch options of Automation, try to launch it via the Safemode button option either in the startup options picker or in the launcher.

Crashes Before Launcher. In most cases that is due to your system not having an up-to-date or corrupted install of the required .Net Framework. This can be solved by updating your .Net Framework install to Version 4.5.2[www.microsoft.com] or higher.

Crashes Before Launcher Despite 4.5.2. Well, that is unfortunate! You can launch the game directly via the executable files. You find the appropriate one for your system here: \Steam\steamapps\common\Automation\UE424\AutomationGame\Binaries

Your DirectX Install is Old / Broken. The game needs DirectX 11 to run, and some people had issues of the game claiming that some files were missing but a verify didn’t fix it. In that case try to download and install the latest DirectX 11 version.
Note that for running the Kee Engine Version (old Lite Campaign) you need to have the latest DirectX 9 version installed.

Outdated Graphics Drivers. The standard tech support goto answer, but sometimes this actually is what keeps the game from even starting. Find your latest stable-version graphics card drivers and install them. You can do so for instance here (NVIDIA)[www.geforce.com], or here (AMD)[support.amd.com], or here (Intel)[downloadcenter.intel.com]. The 2016/2017 Intel graphics default drivers don't seem to be compatible to UE4.21 anymore, you need to update them if you run an Intel chipset. Note to Intel graphics users: you need to download those drivers linked and install them, doing it via your system driver update does not work.

Weird Driver Conflict.In 2019, a Windows Creators update broke Automation for some people with integrated Intel Graphics unless you have the latest Intel Drivers installed. You need to download the latest Intel Graphics Drivers[downloadcenter.intel.com].

Messed Up Config Files. Also, for some reason, the game could be erroring on startup because of broken or outdated configuration files. In order to fix that, use the Clear Cache button in the game launcher, or manually delete the contents of %localappdata%\AutomationGame\
To do so manually, paste the link into the windows explorer path bar and hit Enter, then delete all that is in there.

Very Low Game Framerate on Good System

There is an issue with low FPS that is caused by having an XBOX controller or other controllers connected to your PC while playing Automation. This can also move your mouse cursor when you seemingly don't give it any mouse input. Make sure to disconnect your controller.

Another cause can be your anti-virus kicking into overdrive for some reason, make sure to whitelist Automation.

Yet another cause can be messed up configuration files. To remedy that use the Clear Cache button in the game's launcher.

Game Doesn’t Save Cars / Settings / Can't Build Anything!

This most likely is due to your anti-virus selectively blocking the game folders. The important one for engines and cars is: Documents\My Games\Automation
The important one for saving your units is: %localappdata%\AutomationGame\Saved
You can paste that with the % into your Windows Explorer path bar and hit Enter.
Another weird one could be that you have installed the game on an external drive, we had a few reports of that causing issues.

Where to Find The Log Files / Car Files?

They are in: %localappdata%\AutomationGame\Saved\Logs
There is a Game Log button in the Automation launcher taking you there.
If you are running into issues playing the game or have startup issues we will need your latest log file from there. You can paste that with the % into your Windows Explorer path bar and hit Enter in case the launcher doesn't work for some reason.
If you need to send a specific car that is causing issues, select it in the car manager and hit the Save For Sharing button, it will display where it put the small .car file.
You can send the files to [e-mail] and link your support thread.

Getting Tech Support

Saying that the Game Crashes is as good as telling your doctor that it hurts and expecting them to stop it from hurting. What is 'it'? When/what causes 'it' to hurt? Just like a Doctor we need information to solve your problem. When making a post, please try and provide as much information from the list below that you can! We can't help you, unless we know what is wrong.

0. Make sure you've read the Troubleshooting FAQ
That makes you special already, and really helps us helping you.

1. Describe your problem precisely!
How did you trigger it, what were the previous choices you did, etc.

2. Pictures can say more than 1000 words
If you have a problem describing your problem, make a video or take a screenshot. Sometimes that's easier

3. Include the game logs
Some other errors leave a hint in the logs. Hit the Game Log button in the game's launcher and send us your AutomationGame.log file.

Those things will ensure we can quickly address the issue and get you playing.
Cheers!

[rhodesman]

I am having an issue where the game crashes every time I play. The crashing seems to happen at random times but looking at the logs it seems like an issue with the graphics?

I could use some advice, I have updated my display drivers, tried changing graphics settings in the game and nothing seems to help.

[2022.05.04-23.48.45:458][572]LogD3D11RHI: Display: Temp texture streaming buffer not large enough, needed 16777216 bytes
[2022.05.04-23.48.45:685][586]LogD3D11RHI: Display: Temp texture streaming buffer not large enough, needed 8388608 bytes
[2022.05.04-23.48.45:783][592]LogPakFile: New pak file ../../../AutomationGame/Content/Paks/pakchunk7optional-WindowsNoEditor.pak added to pak precacher.
[2022.05.04-23.48.45:818][594]LogD3D11RHI: Display: Temp texture streaming buffer not large enough, needed 16777216 bytes
[2022.05.04-23.48.46:024][606]LogD3D11RHI: Display: Temp texture streaming buffer not large enough, needed 8388608 bytes
[2022.05.04-23.49.30:192][251]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 0 AsyncPackages
[2022.05.04-23.53.39:669][190]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 0 AsyncPackages
[2022.05.04-23.55.01:401][ 87]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 0 AsyncPackages
[2022.05.04-23.57.22:017][510]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 0 AsyncPackages
[2022.05.04-23.57.33:126][176]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 0 AsyncPackages
[2022.05.04-23.57.51:548][268]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 0 AsyncPackages
[2022.05.04-23.58.06:556][139]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 0 AsyncPackages
[2022.05.04-23.59.02:506][492]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 0 AsyncPackages
[2022.05.05-00.00.11:830][645]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 0 AsyncPackages
[2022.05.05-00.00.45:044][629]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 0 AsyncPackages
[2022.05.05-00.01.23:191][916]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 0 AsyncPackages
[2022.05.05-00.01.30:517][324]LogThreadingWindows: Error: Runnable thread TaskGraphThreadNP 1 crashed.
[2022.05.05-00.01.30:517][324]LogWindows: Error: === Critical error: ===
[2022.05.05-00.01.30:517][324]LogWindows: Error: 
[2022.05.05-00.01.30:517][324]LogWindows: Error: Fatal error!
[2022.05.05-00.01.30:517][324]LogWindows: Error: 
[2022.05.05-00.01.30:517][324]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000028
[2022.05.05-00.01.30:517][324]LogWindows: Error: 
[2022.05.05-00.01.30:517][324]LogWindows: Error: [Callstack] 0x00007ff795997941 AutomationGame-Win64-Shipping.exe!FMeshDrawShaderBindings::SetOnCommandList() [D:\workspace\UE-Local\Engine\Source\Runtime\Renderer\Private\MeshPassProcessor.cpp:911]
[2022.05.05-00.01.30:517][324]LogWindows: Error: [Callstack] 0x00007ff7959cf19b AutomationGame-Win64-Shipping.exe!FMeshDrawCommand::SubmitDraw() [D:\workspace\UE-Local\Engine\Source\Runtime\Renderer\Private\MeshPassProcessor.cpp:1166]
[2022.05.05-00.01.30:517][324]LogWindows: Error: [Callstack] 0x00007ff7959cf4d4 AutomationGame-Win64-Shipping.exe!SubmitMeshDrawCommandsRange() [D:\workspace\UE-Local\Engine\Source\Runtime\Renderer\Private\MeshPassProcessor.cpp:1253]
[2022.05.05-00.01.30:517][324]LogWindows: Error: [Callstack] 0x00007ff795964167 AutomationGame-Win64-Shipping.exe!TGraphTask<FDrawVisibleMeshCommandsAnyThreadTask>::ExecuteTask() [D:\workspace\UE-Local\Engine\Source\Runtime\Core\Public\Async\TaskGraphInterfaces.h:886]
[2022.05.05-00.01.30:517][324]LogWindows: Error: [Callstack] 0x00007ff795108b61 AutomationGame-Win64-Shipping.exe!FTaskThreadAnyThread::ProcessTasksUntilQuit() [D:\workspace\UE-Local\Engine\Source\Runtime\Core\Private\Async\TaskGraph.cpp:888]
[2022.05.05-00.01.30:517][324]LogWindows: Error: [Callstack] 0x00007ff79510af2c AutomationGame-Win64-Shipping.exe!FTaskThreadBase::Run() [D:\workspace\UE-Local\Engine\Source\Runtime\Core\Private\Async\TaskGraph.cpp:542]
[2022.05.05-00.01.30:517][324]LogWindows: Error: [Callstack] 0x00007ff795266177 AutomationGame-Win64-Shipping.exe!FRunnableThreadWin::Run() [D:\workspace\UE-Local\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:86]
[2022.05.05-00.01.30:517][324]LogWindows: Error: [Callstack] 0x00007ff79525fca1 AutomationGame-Win64-Shipping.exe!FRunnableThreadWin::GuardedRun() [D:\workspace\UE-Local\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:35]
[2022.05.05-00.01.30:517][324]LogWindows: Error: [Callstack] 0x00007ff848a27034 KERNEL32.DLL!UnknownFunction []
[2022.05.05-00.01.30:517][324]LogWindows: Error: [Callstack] 0x00007ff84a322651 ntdll.dll!UnknownFunction []
[2022.05.05-00.01.30:517][324]LogWindows: Error: 
[2022.05.05-00.01.30:517][324]LogWindows: Error: Crash in runnable thread TaskGraphThreadNP 1
[2022.05.05-00.01.30:530][324]LogExit: Executing StaticShutdownAfterError
[2022.05.05-00.01.30:530][324]LogWindows: FPlatformMisc::RequestExit(1)
[2022.05.05-00.01.30:530][324]LogWindows: FPlatformMisc::RequestExitWithStatus(1, 3)
[2022.05.05-00.01.30:530][324]LogCore: Engine exit requested (reason: Win RequestExit)
[2022.05.05-00.01.30:536][324]Log file closed, 05/04/22 20:01:30

[[CAMSO] MrChips]

โพสต์ดั้งเดิมโดย rhodesman:

I am having an issue where the game crashes every time I play. The crashing seems to happen at random times but looking at the logs it seems like an issue with the graphics?

I could use some advice, I have updated my display drivers, tried changing graphics settings in the game and nothing seems to help.

What's happening here is that your video card is crashing for some reason. What kind of card are you running?

[rhodesman]

โพสต์ดั้งเดิมโดย CAMSO MrChips:

What's happening here is that your video card is crashing for some reason. What kind of card are you running?

I have an RX6900XT

[[CAMSO] MrChips]

โพสต์ดั้งเดิมโดย rhodesman:

I have an RX6900XT

I have a 6800XT in my system, and yeah I've had it crash a few times myself a while back. Are you running the current AMD driver? I've had more luck with the 22.3.2 drivers and later with this; since that update, I've had no further video card crashes since updating to them. Also, make sure you're on the most up-to-date openbeta version as well too, since that seems to help as well!

[rhodesman]

โพสต์ดั้งเดิมโดย CAMSO MrChips:

I have a 6800XT in my system, and yeah I've had it crash a few times myself a while back. Are you running the current AMD driver? I've had more luck with the 22.3.2 drivers and later with this; since that update, I've had no further video card crashes since updating to them. Also, make sure you're on the most up-to-date openbeta version as well too, since that seems to help as well!

I'm still getting crashing issues. I uninstalled and did a factory reinstall of AMD drivers 22.4.2 and have LCV2.4 Opt-In Alpha (2.4.14 Hotfix) installed. With the change to the drivers, the game did seem to last a tad longer but still ultimately crashed again.

Looking at the logs, it seems the issue is no longer the graphics card but I cannot tell what the issue might be (maybe the unreal engine?).

[2022.05.05-03.12.41:197][712]LogStreaming: Display: Suspending async loading (1)
[2022.05.05-03.12.41:202][712]LogStreaming: Display: Resuming async loading (0)
[2022.05.05-03.12.41:204][712]LogSlate: Request Window 'Automation ' being destroyed
[2022.05.05-03.12.41:204][712]LogStreaming: Display: Suspending async loading (1)
[2022.05.05-03.12.41:261][712]LogStreaming: Display: Resuming async loading (0)
[2022.05.05-03.12.41:262][712]LogSlate: Window 'Automation ' being destroyed
[2022.05.05-03.12.41:269][712]LogWindowsTextInputMethodSystem: Display: IME system now deactivated.
[2022.05.05-03.12.41:300][712]LogWindowsTextInputMethodSystem: Display: IME system now deactivated.
[2022.05.05-03.12.41:348][712]LogExit: Preparing to exit.
[2022.05.05-03.12.41:348][712]LogMoviePlayer: Shutting down movie player
[2022.05.05-03.12.41:405][712]CamsoASyncLoadingLog: UAsyncObjectLoader - BeginDestroy
[2022.05.05-03.12.41:406][712]CamsoASyncLoadingLog: UAsyncObjectLoader - BeginDestroy
[2022.05.05-03.12.41:491][712]LogExit: Game engine shut down
[2022.05.05-03.12.41:612][712]LogExit: Object subsystem successfully closed.
[2022.05.05-03.12.41:652][712]LogD3D11RHI: Shutdown
[2022.05.05-03.12.41:652][712]LogD3D11RHI: CleanupD3DDevice
[2022.05.05-03.12.41:711][712]LogD3D11RHI: ~FD3D11DynamicRHI
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module AIModule (119)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module SessionServices (117)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module MovieSceneTracks (115)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module MovieScene (113)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module GeometryCache (111)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module Niagara (109)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module StreamingPauseRendering (107)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module AnalyticsET (105)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module SteamBPWrapper (103)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module RuntimeMeshComponent (101)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module ProceduralMeshComponent (99)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module Ansel (97)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module CustomMeshComponent (95)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module CableComponent (93)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module Composure (89)
[2022.05.05-03.12.41:711][712]LogModuleManager: Shutting down and abandoning module AutomationGame (87)
[2022.05.05-03.12.41:712][712]LogModuleManager: Shutting down and abandoning module FMODStudio (85)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module WebBrowserWidget (83)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module RuntimePhysXCooking (81)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module AnalyticsBlueprintLibrary (79)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module UdpMessaging (77)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module TcpMessaging (75)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module LightPropagationVolumeRuntime (73)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module PacketHandler (71)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module ClothingSystemRuntime (69)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module Overlay (67)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module MediaAssets (65)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module UMG (63)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module Slate (61)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module MRMesh (59)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module Messaging (57)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module HeadMountedDisplay (55)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module XAudio2 (53)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module Networking (51)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module Core (49)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module LevelSequence (47)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module ImageWrapper (43)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module InputCore (41)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module PhysXCooking (39)
[2022.05.05-03.12.41:819][712]LogModuleManager: Shutting down and abandoning module OnlineSubsystem (34)
[2022.05.05-03.12.41:819][712]LogOnline: Display: STEAM: OnlineSubsystemSteam::Shutdown()
[2022.05.05-03.12.41:819][712]LogOnline: Display: OSS: FOnlineAsyncTaskManager::Stop() ActiveTask:0000000000000000 Tasks[0/0]
[2022.05.05-03.12.41:844][712]LogOnline: Display: OSS: FOnlineAsyncTaskManager::Exit() started
[2022.05.05-03.12.41:844][712]LogOnline: Display: OSS: FOnlineAsyncTaskManager::Exit() finished
[2022.05.05-03.12.41:844][712]LogOnline: Display: Unloading online subsystem: Steam
[2022.05.05-03.12.41:844][712]LogOnline: Display: STEAM: OnlineSubsystemSteam::Shutdown()
[2022.05.05-03.12.41:844][712]LogOnline: Display: Unloading online subsystem: NULL
[2022.05.05-03.12.41:844][712]LogModuleManager: Shutting down and abandoning module HTTP (29)
[2022.05.05-03.12.41:844][712]LogHttp: Display: Http module shutting down, but needs to wait on 1 outstanding Http requests:
[2022.05.05-03.12.41:844][712]LogHttp: Display: 	verb=[POST] url=[https://datarouter.ol.epicgames.com/datarouter/api/v1/public/data?SessionID=%7B9AF574A1-4B28-40C2-1DD0-6BADC93331D5%7D&AppID=UEGame.UnrealEngine.Release%7C64D749D84F11AD42A55D6BAD2DC37799%7CAutomation%20Game&AppVersion=4.17.2-0%2B%2B%2BUE4%2BRelease-4.17&UserID=ANON-%7BFAE058C3-4820-E74A-98A2-A290D24F89BE%7D%7C%7C&AppEnvironment=datacollector-source&UploadType=eteventstream] status=Processing
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module SSL (28)
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module LensDistortion (24)
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module ShaderCore (22)
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module Landscape (20)
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module SlateRHIRenderer (18)
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module OpenGLDrv (16)
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module D3D11RHI (14)
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module AnimGraphRuntime (12)
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module Renderer (10)
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module Engine (8)
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module CoreUObject (6)
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module SandboxFile (4)
[2022.05.05-03.12.41:873][712]LogModuleManager: Shutting down and abandoning module PakFile (2)
[2022.05.05-03.12.41:874][712]LogExit: Exiting.
[2022.05.05-03.12.41:874][712]Log file closed, 05/04/22 23:12:41

[ketchup66]

Does anybody know why my game just dropped to 30 FPS when it Ran 60 FPS just fine the other day? My specs are still the same as when it ran 60 FPS.

[Malena the Foxtaur]

i cant download the latest update says content file locked

[Killrob]

โพสต์ดั้งเดิมโดย Malena the Foxtaur:

i cant download the latest update says content file locked

Try to restart Steam and your computer. Usually goes away. It is a Steam thing, nothing to do with the game.

[Zaza]

I used to play dx11 and now with the latest update it doesnt even give me an option and loads me in with dx12, which causes the game to run on 2-3 fps. stuttering and freezing all the time. I have pretty new hardware so i don't see why this issue is there in the first place. (im on a laptop with rtx3050 ti mobile and ryzen 7 5800u). I first experienced this when dx12 was added as i tried it and had similar thing happen and reported it to the bugs. nothing changed though.

[Killrob]

โพสต์ดั้งเดิมโดย Zaza:

I used to play dx11 and now with the latest update it doesnt even give me an option and loads me in with dx12, which causes the game to run on 2-3 fps. stuttering and freezing all the time. I have pretty new hardware so i don't see why this issue is there in the first place. (im on a laptop with rtx3050 ti mobile and ryzen 7 5800u). I first experienced this when dx12 was added as i tried it and had similar thing happen and reported it to the bugs. nothing changed though.

That does sound like a driver issue? Have you made sure you're on the absolute latest available?

[Zaza]

โพสต์ดั้งเดิมโดย Killrob:

โพสต์ดั้งเดิมโดย Zaza:

I used to play dx11 and now with the latest update it doesnt even give me an option and loads me in with dx12, which causes the game to run on 2-3 fps. stuttering and freezing all the time. I have pretty new hardware so i don't see why this issue is there in the first place. (im on a laptop with rtx3050 ti mobile and ryzen 7 5800u). I first experienced this when dx12 was added as i tried it and had similar thing happen and reported it to the bugs. nothing changed though.

That does sound like a driver issue? Have you made sure you're on the absolute latest available?

I will update the driver and then see if anything changes.

[Zaza]

updated the driver, but nothing changed

[[CAMSO] MrChips]

โพสต์ดั้งเดิมโดย Zaza:

I used to play dx11 and now with the latest update it doesnt even give me an option and loads me in with dx12, which causes the game to run on 2-3 fps. stuttering and freezing all the time. I have pretty new hardware so i don't see why this issue is there in the first place. (im on a laptop with rtx3050 ti mobile and ryzen 7 5800u). I first experienced this when dx12 was added as i tried it and had similar thing happen and reported it to the bugs. nothing changed though.

If you're on a laptop, you're going to want to double-check that you're using your discrete GPU and not the on-board graphics of your CPU.

[musclecarboiiii69]

Just bought the game, and whenever I try to play it gets stuck on "Installing Microsoft.NET" or something like that.

[Killrob]

โพสต์ดั้งเดิมโดย musclecarboiiii69:

Just bought the game, and whenever I try to play it gets stuck on "Installing Microsoft.NET" or something like that.

That usually means that Steam cannot install one of the required redistributables. One way to fix that can be to check windows update and pull down all the latest updates and then try again. Can also be that you got a corrupted .NET install, which would best be taken care of by manually uninstalling them and letting Steam pull down that required one for you after you install the latest recommended windows one.