Can't launch editor after building (4.0.2)

Development Programming & Scripting C++
, , , ,
1

I can’t launch the editor after successfully building in VS 2013 professional. I have seen a few different post related to this issue but they don’t seem to be the same issue as I’m having.

To be specific the editor launches and then starts compiling shaders and then just exits with no warning.

The log seems to mentiond that the following files don’t exisit:
Address = 0x76ff652d (filename not found) [in C:\Windows\system32\kernel32.dll]
Address = 0x7722c541 (filename not found) [in C:\Windows\SYSTEM32\ntdll.dll]
Address = 0x7722c541 (filename not found) [in C:\Windows\SYSTEM32\ntdll.dll]

I have checked and all the files do exist and I have checked that I can access them. I have also tried launching as administrator and launching cmd as admin and then lauching the editor as that was mentioned in previous articles.

I am using Win 7 64bit. I have 2 GTX 760s and have tried running in sli and with it disabled. I have the latest Geforce drivers installed (as of this writing) 335.23. Also I have no issues running and using the editor that you directly download and I only have issues with the compiled version.

I have attached the dxdiag and will attach log file in a reply as it seems I can only attach one file
link text

2

here is the log file: link text

3

Are you running a restricted (non-admin) account? I know you said you ran as admin, but the editor launches some other processes which may not inherit the settings.

Can you try rebuilding the ShaderCompileWorker program in VS2013? It’s in the Programs folder. Build for Development/Win64.

4

I am running a regular administrator account. I mentioned that because I saw in some other posts it was recommended to run “cmd” as an admin and then launch the editor. I had tried that and it didn’t change the result so I wanted to mention it. sorry for not being more specific.

I tried rebuilding the ShaderCompileWorker in VS 2013 and it built successfully. I used the Development/Win64 build. With no difference in the result. I also did a diff on the log files and everything is identical except for time stamps and memory locations.

One question on that build type (Development/Win64). I was following the build video on the site which said to build using the Development Editor/Win64 so that is what I did previously. I tried a clean and built with of everything with Development/Win64 and now I at least get the crash reporter to come up. The output of that is attached here

Thanks for the assistance

5

I just wanted to check if you guys had any other suggestions to try. Maybe your still trying to figure it out I just thought I would check. Thanks

6

Try compiling sources from the master branch, they have fixed some bugs there.

7

Thanks for getting back with me Stephen. I am still having this issue.

You are correct I am compiling the source code for UE4 in “Development Editor, Win64” in VS2013 without issue.

When I launch the editor It display the small rectangle telling me the things it is loading. The last one I see is a message saying it is compiling a shader. it shuts down with now message.

Also Yes, I am able to launch the regular editor (non source built) with no issues.

8

Hi BlueByLiquid,

Apologies for the delay, is this issue still occurring for you?

To reiterate, you compile the source code for UE4 in “Development Editor, Win64” in VS2013 without issues, but once you launch the editor it exits shortly there after while compiling shaders. This issue does not occur in the binary version of the editor from the Launcher. All correct?

9

Does this file exist at this location on your disk after you compile ShaderCompileWorker?

C:/Users/The Smile Man/Documents/GitHub/UnrealEngine/Engine/Binaries/Win64/ShaderCompileWorker.exe

If not, does that .exe exist somewhere else?

10

yes, ShaderCompileWorker.exe is at that location

11

So I have tried completely removing and re-downloading and rebuilding several times with no change. I was trying a last ditch effort to try one more time before just giving up and hoping 4.1 would solve it I had the idea to put the files on my secondary hard drive which is faster. Everything worked and it didn’t stick. I have no idea which this would be an issue. I checked to make sure my main drive had plenty of space and it does. Anyway I hope this helps someone if they are having a problem.