Can't find file '/Script/EnvironmentQueryEditor

I’m trying to package a project and i’m getting Load Errors.

I’ve tried searching for the ‘Script/EnviromentQueryEditor’ and i found it in a Source folder, rather than the ‘Script’ folder

Text File

Not to sure how i can fix this, is there a way to redirect the blueprint using it? Or can i move the Editor into a Script folder?

Hello K.Hughson,

I have a few questions for you that will help narrow down what issue is it that you are experiencing.

Quick questions:

  1. Can you reproduce this issue in a clean project?
  2. If so, could you provide a detailed list of steps to reproduce this issue on our end?
  3. Was this project upgraded from an older version of the engine?
  4. Could you make sure that you have EQS enabled in your editor preferences? (This can be found under experimental)

Hey Rudy,

No to questions 1 & 2, It has gone through several engine versions and i do have EQS enabled.

I really dont think this is my issue (although it does take up a lot of the log)

The cook ends up failing with 2 errors and just over 200 warnings. From what i can tell the errors are just blank.

LogInit:Display: LogOutputDevice:Error:

UE4Editor-Cmd: begin: stack for UAT

LogInit:Display: LogOutputDevice:Error:

end: stack for UAT

I’ve tried building for both Windows and Android and i can build blank projects fine for both.

Thank you for the information. I have a couple more questions for you.

Questions:

  1. Could you check your Engine C++ Classes to make sure that you have the classes in the image below? (You will need to go to View Options and check show engine content to true)
  2. Have you made any changes to your config files?
  3. If you delete your config folder, saved folder, and intermediate folder, does this make a difference? (You may want to make back ups of these folders)

Image:

I ran into the same problem recently after upgrading a project. The solution is to ensure you have Environment Querying System enabled under Experimental in the Editor Preferences.

I agree. Enabling the Environment Querying System is likely the correct answer for most people.

Hello K.Hughson,

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.

This issue happened to me after the following:

  1. Ran Git clean after a good project commit.
  2. Move project via symbolic link from document\unreal projects → d:\Unreal projects
  3. Opened and build .dll without first generating VS project
  4. Issue appeared

In closing: Issue was resolved by disable->enable experimental eqs and repeating the process in the proper order.

solved reenabling it aswell. it randomly gone off same as some other editor preferences.

great ,thanks

Thanks! Enabling the experimental feature prevents the error.

How do you fix having this error when building a PAK from the command-line?

Enabling the Environment Querying System