Unreal 5.2 - Editor target file does not exist - Cannot resolve DirectX

Yesterday I installed Unreal Engine 5.2 after official release.

When I create a new C++ project with version 5.2 without changing anything after the project creation
I have couple of issues:

  1. I get below warning when I try to launch the project. It says editor target file does not exist for my project, but it is already there. How engine could not detect the file ? What should I check to dig more ?

image

When I click Yes or No, Editor will open and works (I didn’t see problem with editor)
But I see this warning after Editor launched.

  1. And I get error for DirectX → “Cannot resolve symbol DirectX”

I researched a lot and could not find anything related with my problem.

6 Likes

Same problem here. Migrated a 5.0.3 project to 5.2, it compiles, runs and works well, but this DirectX error is showing all around Rider.

Did a full Rider cache invalidation, no changes.

1 Like

Same issue here. Though as the other poster mentioned the project still compiles and runs fine.

Got same issue, tried Rider cache invalidation, reinstall, einstall DX12, change MSBuild version and all the other stuff, nothing changes this, and yeah, still can compile and run. And got same 9 errors in same 4 files: ElectraPlayerRuntime.Build.cs (2 errors), ElectraSamples.Build.cs (2 errors), ShaderFormatD3D.Build.cs (1 error), DX12.Build.cs (4 errors).

And the question is: will it affect builds or something, or is it just Rider interpritation of Engine? If someone find out how to fix it, let us know pls

In my case, it causes to fail builds.

Btw, I’m using AMD GPU (5700 XT). What GPU you are using guys ?

3050ti
And I haven’t this problem with 5.1 with same setup and same rider settings, even now when I open same project for 5.1 everything works fine, problem only with 5.2, hope to find solution

Same problem here, after updating from UE 5.1 to UE 5.2, JetBrains Rider 2023 shows alot of problems:

I have the same issue with UE5.2 + Rider. Howver, this error is not showing with UE5.2+VS2019.
And also this error doesn;t show up with UE5.1.1 + Rider.
Any suggesions on how to fix this is appreciated.

+1 Same here

Edit: might be worth starting a support issue with JetBrains https://rider-support.jetbrains.com/hc/en-us/requests/new

I just opened my support ticket, but I am guessing, more customers they get this from more urgently they will approach to the problem.

1 Like

Having the same issue on Rider + 5.2.0 both on Linux and Windows

I got the same ‘missing target file’ error with VS2022

getting the same error, building from Rider works, but when compiing from Live Coding fails with this error

Running D:\Program Files\Epic Games\UE_5.2\Engine\Build\BatchFiles\Build.bat -Target="ProjectNameEditorNonUnity Win64 Development -Project=""D:/projects/unreal/ProjectName/game/ProjectName.uproject""" -LiveCoding -LiveCodingModules="D:/Program Files/Epic Games/UE_5.2/Engine/Intermediate/LiveCodingModules.txt" -LiveCodingManifest="D:/Program Files/Epic Games/UE_5.2/Engine/Intermediate/LiveCoding.json" -WaitMutex -LiveCodingLimit=100
  Using bundled DotNet SDK version: 6.0.302
  Running UnrealBuildTool: dotnet "..\..\Engine\Binaries\DotNET\UnrealBuildTool\UnrealBuildTool.dll" -Target="ProjectNameEditorNonUnity Win64 Development -Project=""D:/projects/unreal/ProjectName/game/ProjectName.uproject""" -LiveCoding -LiveCodingModules="D:/Program Files/Epic Games/UE_5.2/Engine/Intermediate/LiveCodingModules.txt" -LiveCodingManifest="D:/Program Files/Epic Games/UE_5.2/Engine/Intermediate/LiveCoding.json" -WaitMutex -LiveCodingLimit=100
  Log file: C:\Users\user\AppData\Local\UnrealBuildTool\Log.txt
  Using 'git status' to determine working set for adaptive non-unity build (D:\projects\unreal\ProjectName).
  Creating makefile for ProjectNameEditorNonUnity (no existing makefile)
  Couldn't find target rules file for target 'ProjectNameEditorNonUnity' in rules assembly 'UE5Rules, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'.
  Location: D:\Program Files\Epic Games\UE_5.2\Engine\Intermediate\Build\BuildRules\UE5Rules.dll
  Target rules found:
  
Build failed.

Customer support got in touch with me in regards of my support request and they confirmed it to be a bug. They created a ticket for developers to take a look: https://youtrack.jetbrains.com/issue/RSCPP-34310/Cant-resolve-DirectX-symbol-in-engine-sources-UE-5.2

Also support asked me to upvote this issue to bring it to attention of developers. So I am guessing it might help if everyone with account and experiencing the same issue can access it and upvote the issue.

6 Likes

I found a workaround:

  1. Create a blueprint project
  2. Add a C++ class (Tools → New C++ Class)
  3. Build C++ (in Rider)
  4. Restart Unreal

Rider still displays 20 errors in 9 files, but recompiling works fine.

Yep I removed 5.2 and downgraded to 5.0.3 for now. That solved the problem but then got some other strange errors despite following a tutorial line for line. I have decided to try UE4.

There is now a simple workaround in this post by Mikhail Zakharov in the Jetbrains Rider issue tracker that was previously posted here:

https://youtrack.jetbrains.com/issue/RSCPP-34310/Cant-resolve-DirectX-symbol-in-engine-sources-UE-5.2#focus=Comments-27-7378458.0-0

1 Like
  • DirectX Issue (there is a workaround)

I tried this work around. It works for me under specific conditions.
When I first create the project after this fix, new project still has directX issue, I need to regenerate the project files then it fixes the problem.

  • Editor Target File Issue (still happenning)

Do you any idea about other problem in my original post.
When I open the project, every time it says “Missing Target File”
You can see how silly this error is, I swear I have the file from the beginning :smiley:

1 Like

Hi,
Same here. I also have an AMD GPU and the build fails (in rider and VS)

To followers of this topic,

Can you try to remove “BuildConfiguration.xml” at C:\Users@Your Username@\AppData\Roaming\Unreal Engine\UnrealBuildTool

This worked for me and I guess if you add or change something in build configuration previously is preventing the build the engine. Try removing this file, it will be regenerated when you create or build a project.
This is also solution for another problem with 5.3, link below

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.