Error compiling the Automation Tool after updating Visual Studio today (Unreal 5.3.2)

Development Platform & Builds
, ,
62

I have been able to build a clean solution in a new project using 5.4, without the visual studio extension.

Currently, there is a bug which will throw an error related to Catch2 in a new unreal project when opened in VS. This bug has a quick fix available at Current Available Quick-Fix Solutions (also see UE 5.4 compile error Catch2 - #14 by Amanda.Schade). Fixing the bug using the QFE should enable us to build the solution.

My next task is to see if I can get the visual studio extension working. Its not updated and released for 5.4 yet and I have created a request for that in Developer Community. That link also has a workaround which I haven’t tried to check if it works but at this point I would rather wait for the extension to be officially released. Maybe a few votes would make it a priority :wink:.

63

that worked for me, thx

64

This didn’t solve all of the problems, but got the ball rolling again. Apparently, in 5.3.2, it’s a good idea to verify the engine’s files after updating Visual Studio.

Update: bit the bullet and started building Unreal from source. Indeed, the fixes described here for BgScriptReader and CheckForHacks fix all problems related to the AutomationTool. I’m currently working on the AutoRTFMTests, which seems to be just a missing download.

Update #2: The AutoRTFMTests project is internal to Epic and requires code not available to the public; it shouldn’t be built by licensees. So just unmark the project in the Build/Configuration Manager window in Visual Studio and it will be skipped, removing the error.

65

Do same as Images

1
11863×1000 115 KB

2
21651×1010 154 KB

find page by click on errors in Error List

3 Likes
66

thanks you saved my day!

1 Like
67

solved! Thank you

1 Like
68

Thank you. You’re hired.

69

Please Set My Post as Solved.

70

It works for me by removing the Android components! Thanks a lot!