4.11 bugs: initial build fails, editor exit causes crash always, others

Experiencing a few issues with 4.11 on windows:

  1. new C++ project (tried FPS) will fail to build initially as VC include directors are not set (they are blank) in Visual Studio. Need to put in manually. Once done, initial project builds but will not run Unreal Editor. Get the message, “The following modules are missing or build with a different engine version”. If you select Yes to build rebuild, there is no change in behavior.

  2. Editor ALWAYS crashes on exit/quit.

  3. Editor constantly unable to save all if C++ is modified and a hot-reload takes place. This will be tough to reproduce, but I notice about 50% of the time, any change to the C++, even if function prototypes/interfaces not changed will result in an inability to save the project. You get that “missing tangentia linked to a private something or other”. Editor needs to be killed and then restarted.

Hey -

Are you using the engine from the Launcher or have you built the engine from GitHub source? When creating a new code project, are you including or excluding the Starter Content?

If you are using the Launcher version of the preview, can you click on the drop down arrow next to “Launch” and Verify the version? If you are using source code, please try running GenerateProjectFiles.bat then building the UE4.sln again.

Cheers

This is not from source, but I am attempting to run it from Visual Studio (ctrl-f5). Have verified the version and have not included starter content.

Am trying to replicate on another machine. On other machine, I did get the “different version” after I added a plugin project, Unreal asked me to restart editor, I restarted, visual studio failed and gave me that error. However, I was able to load visual studio, rebuild all, and launch succesfully. So not sure what is going on. I appreciate it would be tough for you to replicate this.

Are you able to reproduce these issues easily/consistently on the original machine? If so, can you post the DXDiag for that machine?

Hi ,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you.