Description

Using the Go to definition option on a blueprint node in the Binary editor opens Visual Studio but does not actually show the definition as requested. The user is instead given the following warning in their output log. The Go to definition option is also present in blueprint only projects, when it shouldn't be.

[2018.02.01-19.33.56:962][265]LogSelectionDetails: Warning: NavigateToFunctionSource:  Found symbols for [UKismetSystemLibrary::PrintString] - File [d:\build\++ue4+release-4.19+compile\sync\engine\source\runtime\engine\private\kismetsystemlibrary.cpp], Line [166], Column [0]
[2018.02.01-19.34.07:382][962]LogVSAccessor: Warning: Couldn't access Visual Studio
[2018.02.01-19.34.07:387][962]LogVSAccessor: Warning: Couldn't access module table

Steps to Reproduce
  1. Create a new blank C++ project in a Binary editor
  2. Create an actor blueprint
  3. In the blueprint's event graph, add a Print String node
  4. Right-click the node and select "Go to definition"
    Result: Visual Studio opens but you receive a warning and the definition of the node never appears.
    Expected: Visual Studio opens and shows the definition of the node.

Have Comments or More Details?

There's no existing public thread on this issue, so head over toAnswerHub just mention UE-54733 in the post.

8
Login to Vote

Duplicate
ComponentCore
Affects Versions4.194.20
CreatedFeb 1, 2018
ResolvedFeb 1, 2018
UpdatedJun 23, 2018