4.9 Preview 2 Windows 10 Launch Problem

After installing the 4.9 Preview 2 release, and making a copy of my project I can no longer open my UE4 project by double clicking on it in Windows Explorer. I get the cannot build message, and to try and build the project manually. The build in Visual Studio 2013 does work. But I still cannot open the UE4 project from Windows Explorer.

I decided since the build worked in VS I would run the project via F5 (debug). Unfortunately I get the following error:

It appears to be a path error. From the screenshot it appears as though 4.9\Engine\Intermediate\Build\Unused is invalid. Are there any steps I can take to fix this?

This was originally reported in the forums:

Hello ,

What type of error do you receive when you attempt to run the project via the .uproject file after building the project? Does it still say that it needs to be built? Have you tried opening the project from the Unreal Project Browser (The window that appears when first opening the editor).

Also, does this only occur with this particular project or does it also happen with fresh projects?

Well that helped me figure out what the real problem was: an incomplete conversion (most likely).

I made use of PlaySoundOnActor, which isn’t supported in the 4.9.0 release. The problem though is that even after opening the 4.9.0 Visual Studio solution file and making the change the project is still not seen as a 4.9.0 project.

Trying to open the converted copy from the Unreal Project Browser kept asking to make a copy, or otherwise cancel, even though a conversion took place but “failed” due to a source code issue.

After making the fix in my original source, I then performed the conversion, which worked fine. Unfortunately I did encounter an error when running my game but did notice a stack trace in the error window (something that wasn’t there before). At this time I’m in the process of putting the 4.9.0 Preview 2 through the motions and testing out my game, including debugging with VS 2013. I’ll post a follow up shortly and also in the forum thread.

Please let me know if there’s something specific you’d like me to do.

I can open the project as 4.9.0 Preview 2, and I can manipulate the items within the UE4 Editor.

However, pressing F5 in Visual Studio still gives me the bogus path as noted above.

The same debugging problem from Visual Studio occurred with UE4 Preview 3:

alt text

54037-ue4.4.9.preview.3.visual.studio.debug.error.jpg

It seems like it may be the project settings themselves in relation to Visual Studio. Can you check the debug settings in Visual Studio to see if they may be pointing to that directory?

Hello ,

We haven’t heard from you in a while. Are you still experiencing this issue or was my last suggestion helpful to you? I would like to investigate further if you’re still having problems. In the meantime, I’ll be marking this issue as resolved for tracking purposes. If you would like to continue, please leave a comment and the question will reopen.

I’m still having the same problem, even with Preview 4:

I’m sad to see that this is still occurring for you. I forgot to ask, do you have UnrealVS installed? That is needed to run in debug successfully.

UnrealVS is installed for 4.8.3. I didn’t perform the process specifically for 4.9. Is that a requirement too? If needed, can the two installs live side-by-side?

You shouldn’t need a separate install for it, I just wanted to make sure you had it.

Have you given this a try with a fresh project as of yet or has it only been with your existing project? It would be helpful to know if this is project specific or not to help narrow the issue down.

That’s a good point. Let me test it with a new project and provide an update later today.

Interesting. I am able to create and debug the Advanced Vehicle project with VS2013 and 4.9 Preview 4:

Do you know what the manual settings are supposed to be for the project? Maybe I could set them up so that I can test 4.9 with my own project.

I’m not quite sure what project-specific settings could be causing this, but would it be possible for you to send a copy of the affected project? If you’d like to keep it private, you can send a link to me in a private message on the forums. My profile is [here][1].

If it is based off project settings, it should occur for me as well.

Hi
You could try comparing the NMake->Output property for the two projects. This should point to the editor exe. I think this is what VS uses to determine what it tries to run when you start debugging (unless it’s overridden in Debugging->Command)

Chris,

For the most part the 4.8 and 4.9 NMake settings look pretty much the same. Please see the screenshots below.

Which project is set as the Startup Project and what are the active build config and platform when you see this error? The BuiltWithUnrealBuildTool config in your screenshot above suggests these were set to something invalid.

Chris (and ),

To clarify, the project name in the images above were changed to protect the innocent, if that is what you were referring too. Secondly, and more importantly, the Startup Project wasn’t set correctly. Something I didn’t notice. It now works.

Thank you both for helping me with this.

On a slightly different note, when the project was migrated, and also when you generate Visual Studio project files from the context sensitive menu in folders, the newly generated solution file loses its filters. All hierarchy is lost. The project space is flattened. Do you know if this is fixed in 4.9?

Hey ,

I apologize but I’m not sure I understand what you mean by the hierarchy being lost. Could you give me an example? I haven’t heard of an issue related to this so I’m not sure if it would be fixed or not in 4.9.

, the folder hierarchy in the image below is lost during the upgrade process. And I noticed this occurs when you recreate the VS project too. Along with the missing hierarchy the startup project is set incorrectly also.

58114-folder.hierarchy.jpg