I’ve just upgraded from 4.8 + VS2013, where I have also used Visual Assist X. I must have gotten some settings wrong because I’m getting red underlines under things like the PROJECT_API macro, and UE4 variables and functions (like CreateDefaultSubobject and .Value when iterating over a TMap). When I mouse over those errors, there’s a tiny blank box that comes up (I assume that’s where the error message is supposed to go). What’s even more worrying is that actual errors do not at all get sensed, ex. I type random text somewhere and get no underlines whatsoever. Everything compiles and runs fine however.
Can someone with working settings tell me what they’re using? Also goes for whether or not you disabled intellisense, etc.
Hey sgp-
The random red underlines are not an error with your Visual Assist setup but instead an indicator that intellisense does not understand what its looking at. With commands such as CreateDefaultSubobject and other UE4 Macros like you mentioned, this is expected since they are specific to UBT/UHT and can usually be ignored. Another option to avoid the misleading underlines would be to disable intellisense.
Cheers
I vaguely remember that back when I used VS2013 I did not disable intellisense, and everything was fine–no random red underfines. This time I did disable it (after trying things out with it on) and, even if I were to ignore those underlines, the fact there doesn’t seem to be any error checking going on everywhere else is worrying.
Visual Assist underlines unknown symbols only if squiggles are disabled in Visual Studio. The policy exists irrespective of the setting in the options dialog of Visual Assist.
If you want to see if Visual Assist underlines better than the IDE, disable squiggles in the IDE, then make sure underlining is enabled in Visual Assist. In the IDE, you don’t need to disable Intellisense entirely.