VSCode Extension supports Unreal Engine v4.25 / v4.26.1+ / and v5.0.0+
WARNING: 3.1.0+ changes the way this extension's 'enableOptionalFixes' optimization setting works. Enabling UE optimization disables red squiggle compiling for the Unreal Engine source code. This does not affect your project's source code (it still can have red squiggles). Navigation is unaffected. You can disable this in this extension's settings.
- File Changed: Unreal Source's .vscode/settings.json
Note: Check out the Running section of the Readme to take advantage of the smaller Tag Parser cache
- Simpler way for the extension's 'enableOptionalFixes' optimization setting. Now just uses Tag Parser for UE source. SEE WARNING ABOVE
- Added error if *.generated.h files aren't Built yet
- Added error if *.generated.h path isn't in rsp files
- Add error if using UE5 and using the wrong cppStandard
- Added info message about default cppStandard for UE4/UE5
- Better warning if UE path isn't in *.code-workspace file
- Show total # of errors/warnings messages at end of log
- Warn if using the extension's path setting without strict enabled
- Warning if project is using Source/(ProjectName)/(Public/Private) directory structure
- Launch json fix refactor.
- Launch json fix of this extension's previous launch json fix version to match console setting of UE5 to UE4
- Response file path regex for linux (and probably Mac)
-
Changed to a different way of checking for UE's Version.h
-
Changed all findFiles to fast-glob. findFiles(api function) was failing sometimes for unknown reasons.
Thanks to @heptaspirit for helping test this!
-
Converted from node read/write file to vscode api read/write file.
-
Removed convoluted progress bar code (The info bar already has a 'extension is done' indicator)
-
Changed reset detection - Now just warns to restart VSCode.
-
Fixed isValid project code so file watchers will now run
- Fix for UE5 Preview 1's malformed json in launch.json
- Mac M1 fix will auto set compiler path in c_cpp_properties (Can also change the path in new extension settings)
- New compiler.path setting to force compiler path in c_cpp_properties.
- New compiler.strictPath setting to force compiler.path setting in compile commands file.
- 4.26 now uses 4.27 code path. It shouldn't matter... and adds some of the new functionality to 4.26.
- Updated dependencies (security)
- Changed VSCode version compatibility version to 1.63.1+ (security)
- Fix for startup bug not finding *.uproject file thus not starting the extension
- Fix for Mac M1 users to change Intellisense Mode automatically (untested)
- Removed options for c++ standard not supported by UE
- (4.27+/5.0+) Changed the way compiler path was getting fixed in compile command files.
- (4.27+/5.0+) Added clang-cl.exe intellisense support to Windows. Add clang-cl.exe path to the cpptools extension User's compilerPath setting to use.
- Fixed an error message not getting logged
- UE 5.0+ now uses compiler path fix that 4.27 uses
- Allow cancelling all response file choices of missing compile commands by seesemichaelj
Thanks!