| T O P I C R E V I E W |
| JuanPablo |
Posted - Apr 06 2019 : 12:28:37 PM
Hello, recently I upgraded visual studio to 2019. After installing VA and try it with UE4 I noticed that the colors of the variables, classes and such are not showing. Also, when I try to use Find References it pops an error message saying "Find References is not available because the symbol is unrecognized".
I tried to do a test in an empty console project, even though the colors do show up the find reference tool still doesn't.
|
| 6 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Apr 10 2019 : 06:23:38 AM
Are you seeing this Find References problem on all symbols, or only some symbols? What about local variables? Member functions of your own classes?
I have loaded a sample Unreal project in VS2019, and Find References is running quite happily for me. I have tried this on several different symbols, including "UAbilitySystemComponent", "FGameplayAbilitySpecHandle" and "TArray".
Obviously something is going wrong here, but I am not sure what. If you look in VA's Open File in Solution dialog, is VA listing the files that make up your solution?
What do you have:
VA Options -> Unreal Engine -> Enable support for Unreal Engine 4
set to? |
| JuanPablo |
Posted - Apr 09 2019 : 11:56:28 AM
Ok, for the colors you were right, I had some files parsing now everything is as it used to be. But, for the "Find references", it still pops a message saying "Find References is not available because the symbol is unrecognized".
|
| ChrisG |
Posted - Apr 07 2019 : 9:01:55 PM
Something you might try, is to disable Visual Assist in the (Extensions -> Manage Extensions) dialog. Then, restart Visual Studio, re-enable Visual Assist and restart once more.
It could be that Visual Assist is stuck in some odd half-loaded state. |
| ChrisG |
Posted - Apr 07 2019 : 8:55:07 PM
I tested, and am having trouble reproducing your issue.
It sounds like Visual Assist is still parsing.
Do you see any messages in the bottom left status bar? The parse shouldn't take more than a few minutes, however, unless you have limited the number of parse threads.
Are you using the binary distribution of the Unreal Engine (through Epic games launcher) or are you building from source (from GitHub)?
When you rebuilt the database, did you see parsing activity in the bottom left status bar? |
| JuanPablo |
Posted - Apr 07 2019 : 6:39:52 PM
quote:
Originally posted by ChrisG
Hello Juan,
That's strange.
What build of Visual Assist are you using? You can check by navigating to (VAssistX -> Help -> About Visual Assist) then check the "VA_X.dll file version".
As a first step, try rebuilding your symbol database. Use the information on the following page to help you do this, see the "Symbol Definitions" section. You will need to restart Visual Studio after this, and it may take a few minutes to rebuild the database the first time you open your UE4 project.
https://wholetomato.fogbugz.com/default.asp?W215
Does rebuilding your symbol database help?
VA_X.dll file version 10.9.2324.0 built 2019.03.08
DevEnv.exe version 16.0.28729.10 Community
msenv.dll version 16.0.28721.110
Comctl32.dll version 6.10.17763.379
Windows 10 10.0 1809 Build 17763.379
8 processors (x86-64, WOW64)
Language info: 1252, 0x80a
I have already tried to do a rebuild, but the error message still shows up. Also, I tried to do a clean install of visual assist and still nothing. |
| ChrisG |
Posted - Apr 07 2019 : 4:41:17 PM
Hello Juan,
That's strange.
What build of Visual Assist are you using? You can check by navigating to (VAssistX -> Help -> About Visual Assist) then check the "VA_X.dll file version".
As a first step, try rebuilding your symbol database. Use the information on the following page to help you do this, see the "Symbol Definitions" section. You will need to restart Visual Studio after this, and it may take a few minutes to rebuild the database the first time you open your UE4 project.
https://wholetomato.fogbugz.com/default.asp?W215
Does rebuilding your symbol database help? |
|
|
