Announcement

**falola** · 08-08-2017, 07:32 PM

Does it work with Visual Studio 2017?

**Rama** · 08-08-2017, 08:26 PM

Originally posted by falola View Post

Does it work with Visual Studio 2017?

VS 2017 support started in UE 4.14.

You still need VS2015 update 3 even if you want to use VS 2017, at least that was my experience when I tried compiling in 2017

If anyone discovers otherwise let me know

Rama

**Zeblote** · 08-08-2017, 08:33 PM

VS 2017 is working just fine for me

**kamrann** · 08-09-2017, 06:07 AM

Originally posted by Rama View Post

You still need VS2015 update 3 even if you want to use VS 2017, at least that was my experience when I tried compiling in 2017

If anyone discovers otherwise let me know

Last I tried, you needed some minimal components but it worked after uninstalling 2015 and installing the standalone build tools.

**kamrann** · 08-09-2017, 06:09 AM

Note a number of people have reported having this incredibly annoying bug with compiling projects for 4.17. It seems to be hit and miss, but may be specific to VS 2017.

**kamrann** · 08-09-2017, 06:12 AM

UHT is stricter in 4.17, you may have to fix up some issues with incompatible specifiers that it previously let slide.

One requirement is that USTRUCTs with Blueprint-accessible UPROPERTYs are themselves marked as BlueprintType. If you have structs that are used as bases only and shouldn't be exposed, but still provide Blueprint-accessible properties for structs derived from them, you can mark the base struct as BlueprintInternalUseOnly instead.

**TheJamsh** · 08-09-2017, 08:55 AM

A few changes to plugins. My project relies on plugins / modules HEAVILY, so I'm running into issues left right and center at the moment. The First change is that UBT will no longer compile the following - but you don't get any warning, it will just completely crash. Instead plugins can only have one 'Type' specified. In theory this should always have been the case anyway, but UBT never used to outright crash...

Code:

{
	"FileVersion": 3,
	"Version": 1,
	"VersionName": "1.0",
	"FriendlyName": "ST Cascade Extensions",
	"Description": "Adds new modules to Cascade",
	"Category": "Stormtide.FX",
	"CreatedBy": "Stormtide Ltd.",
	"CreatedByURL": "www.stormtide.co.uk",
	"DocsURL": "",
	"MarketplaceURL": "",
	"SupportURL": "",
	"CanContainContent": false,
	"Modules": [
		{
			"Name": "ST_CascadeExtensions",
			"Type": "Runtime",
			"LoadingPhase": "PreDefault"
		},
		{
			"Name": "ST_CascadeExtensions",
			"Type": "Developer",
			"LoadingPhase": "PreDefault"
		},
		{
			"Name": "ST_CascadeExtensions",
			"Type": "Editor",
			"LoadingPhase": "PreDefault"
		}
	]
}

Becomes:

Code:

{
	"FileVersion": 3,
	"Version": 1,
	"VersionName": "1.0",
	"FriendlyName": "ST Cascade Extensions",
	"Description": "Adds new modules to Cascade",
	"Category": "Stormtide.FX",
	"CreatedBy": "Stormtide Ltd.",
	"CreatedByURL": "www.stormtide.co.uk",
	"DocsURL": "",
	"MarketplaceURL": "",
	"SupportURL": "",
	"CanContainContent": false,
	"Modules": [
		{
			"Name": "ST_CascadeExtensions",
			"Type": "Runtime",
			"LoadingPhase": "PreDefault"
		}
	]
}

Another thing. I don't know why the hell this was changed because it seems totally unneccesary, but if your plugin depends on other modules in it's build .cs file like so:

Code:

// Copyright (C) Stormtide Ltd. 2017. All Rights Reserved.

using UnrealBuildTool;
using System.IO;

public class ST_FX : ModuleRules
{
    public ST_FX(ReadOnlyTargetRules ROTargetRules) : base(ROTargetRules)
    {
        PublicIncludePaths.AddRange(new string[] { "ST_FX/Public" });
        PrivateIncludePaths.AddRange(new string[] { "ST_FX/Private" });

        PublicDependencyModuleNames.AddRange(new string[] { "Core", "CoreUObject", "Engine", "InputCore" });

        // Custom Plugin Includes - Assertions
        PrivateDependencyModuleNames.AddRange(new string[] { "ST_Core" });
        PrivateIncludePathModuleNames.AddRange(new string[] { "ST_Core" });
        PrivateDependencyModuleNames.AddRange(new string[] { "ST_Assertions" });
        PrivateIncludePathModuleNames.AddRange(new string[] { "ST_Assertions" });
        PublicIncludePaths.AddRange(new string[] { "ST_Core/Public" });
    }
}

Then you have to add those Plugins to the uplugin file for that plugin. My ST_FX plugin relies on ST_Core, so I now ST_FX.uplugin has to look like this:

Code:

{
	"FileVersion": 3,
	"Version": 1,
	"VersionName": "1.0",
	"FriendlyName": "ST FX",
	"Description": "This plugin defines some reusable actor classes for spawning effects in the world, like explosions and impacts.",
	"Category": "Stormtide.FX",
	"CreatedBy": "Stormtide Ltd.",
	"CreatedByURL": "www.stormtide.co.uk",
	"DocsURL": "",
	"MarketplaceURL": "",
	"SupportURL": "",
	"CanContainContent": false,
	"Modules": [
		{
			"Name": "ST_FX",
			"Type": "Runtime",
			"LoadingPhase": "PreDefault"
		}
	]
	"Plugins": [
		{
			"Name": "ST_Core",
			"Enabled": true
		}
	]
}

**Jess.Hider** · 08-09-2017, 09:29 AM

Hey everyone, I just wanted to let you know we are aware of the UHT/UBT issue and wanted to point you to Ben's response on another thread

**TheJamsh** · 08-09-2017, 10:00 AM

Just found this one. OPTIONAL_BINDING is no longer valid in Slate syntax.

This:
ECGame_RichTextBlock.cpp

Code:

	TAttribute<FText> TextBinding = OPTIONAL_BINDING(FText, Text);

Becomes:

ECGame_RichTextBlock.h

Code:

protected:
	PROPERTY_BINDING_IMPLEMENTATION(FText, Text);

ECGame_RichTextBlock.cpp

Code:

	TAttribute<FText> TextBinding = PROPERTY_BINDING(FText, Text);

**BrUnO XaVIeR** · 08-09-2017, 11:36 AM

Originally posted by TheJamsh View Post

A few changes to plugins. My project relies on plugins / modules HEAVILY, so I'm running into issues left right and center at the moment. The First change is that UBT will no longer compile the following - but you don't get any warning, it will just completely crash. Instead plugins can only have one 'Type' specified. In theory this should always have been the case anyway, but UBT never used to outright crash...

Code:

{
	"FileVersion": 3,
	"Version": 1,
	"VersionName": "1.0",
	"FriendlyName": "ST Cascade Extensions",
	"Description": "Adds new modules to Cascade",
	"Category": "Stormtide.FX",
	"CreatedBy": "Stormtide Ltd.",
	"CreatedByURL": "www.stormtide.co.uk",
	"DocsURL": "",
	"MarketplaceURL": "",
	"SupportURL": "",
	"CanContainContent": false,
	"Modules": [
		{
			"Name": "ST_CascadeExtensions",
			"Type": "Runtime",
			"LoadingPhase": "PreDefault"
		},
		{
			"Name": "ST_CascadeExtensions",
			"Type": "Developer",
			"LoadingPhase": "PreDefault"
		},
		{
			"Name": "ST_CascadeExtensions",
			"Type": "Editor",
			"LoadingPhase": "PreDefault"
		}
	]
}

Becomes:
...

Nope;
In first code there you declare three modules with exactly same signature, should never do that, I don't know how this didn't cause you problems before 4.17.
Each "Name" value must be unique; that's probably a bug that they've fixed now with better module management code added, this is why now you see a crash (because that you were doing is wrong).
So not really because "Type" definition, it's a crash because you had multiple modules with the same name.

**TheJamsh** · 08-09-2017, 12:40 PM

Originally posted by BrUnO XaVIeR View Post

Nope;
In first code there you declare three modules with exactly same signature, should never do that, I don't know how this didn't cause you problems before 4.17.
Each "Name" value must be unique; that's probably a bug that they've fixed now with better module management code added, this is why now you see a crash (because that you were doing is wrong).
So not really because "Type" definition, it's a crash because you had multiple modules with the same name.

I know that now, at the time I was copying the format from another plugin - now I've read up on the types and know I don't need three. Even so, in prior versions it didn't crash UBT and now it does with a very obscure error - so posting incase someone runs into the crash. Ben already told me the change was unintended.

**ZioYuri78** · 08-09-2017, 04:32 PM

Hey all,

when i try to launch editor from VS2017 i have this error:

Unable to start the program 'C:\Program Files(x86)\Epic Games\UE_4.17\Engine\Intermediate\Build\Unused\UE4.exe'

File not found.

and of course because i don't have UE4.exe in that folder, any idea on how to solve it/why happen?

EDIT:

Solved
https://forums.unrealengine.com/show...l=1#post748433

**SlimeQ** · 08-10-2017, 06:38 PM

I'm using the steam api in my project and I was initially getting this crazy syntax error in my gen.cpp files when AddDynamic was used

I eventually managed to build the thing by going into the steam api headers and changing every instance of ARRAY_COUNT to STEAM_ARRAY_COUNT. There is a macro redefinition issue with the steam api that has been throwing warnings for a while, but something in 4.17 made it a showstopper

**huatson** · 08-10-2017, 07:19 PM

Originally posted by ZioYuri78 View Post

Hey all,

when i try to launch editor from VS2017 i have this error:

and of course because i don't have UE4.exe in that folder, any idea on how to solve it/why happen?

Workaround for that :
1. Delete vs/Binaries/Intermediate/Save folders
2. Delete Solution File (Not project File), optional delete VC Data File
3. Right click on Project File and " Generate VS Project Files"
4. Open New solution file and Rebuild.
5. Done!

Announcement

c++ 4.17 Transition Guide

c++ 4.17 Transition Guide

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment