How to enable red squiggly errors to Verse in VS Code?

[Og1ma]

When I type random text it is not marked as an error.
This error already existed when I first started working with Verse.
I also reviewed several posts on the forum to solve this problem, but unfortunately nothing helped.
Links to the posts I used to try to solve this problem:

Do not work verse Error Squiggles in VS Code

Apologies for the delay in response here, I’m not usually checking my direct pings. I’m fairly sure that plugin just does syntax highlighting and the actual language server support comes from UEFN itself. Have you tried launching VSC via the “Verse” button in UEFN itself? The plugin contains the language server and does not require UEFN to be open, though opening VS Code from UEFN does help with setting up some other features and making sure that the digests written out (which the language s…

Verse Language Server, IntelliSense

Haha! I like the hints, I’m very excited to see what you guys have planned! Don’t worry about any delay - 10 days is nothing compared to how long I’ve left you hanging here I have noticed that snippets do appear to show up from digests, but only very intermittently, and sometimes not at all. It’s only that I can guarantee the ones within the project itself to show up. I have noticed that the language server has crashed a couple of times during these periods, where I’ve had to res…

How to enable red squiggly errors to Verse in VS Code?

I found a solution everything worked for me when moved UEFN project from Onedrive folder to anther one

Platform(s)
Windows 10 Pro v22H2
VS Code 1.93.1

[Tsar]

Few things you can try and should think about.

Did you create a VSCode project outside of UEFN and then simply add a verse file into it? The verse server will not generate errors for you if you do it this way.

1. Load up UEFN, create a new project and add a new verse file. Creating it this way should initialize the verse server in your VSCode project. This project should now have the verse server initialized and should automatically start whenever you load your VSCode project up no matter if UEFN is running or not.

2. While VSCode or UEFN is running open task manager and go to advanced → details. Check if verse-lsp.exe is running. If not try restarting it.

3. If creating a new project doesn’t work and you’re simply never able to see any lines no matter where the project was created try verifying your UEFN itself.

[Og1ma]

I create all .verse files only in UEFN, just like in the official documentation. As for verse-lsp.exe, this process can sometimes be seen in the task manager, and sometimes it is absent. I have checked UEFN itself for file integrity several times.
Thanks for your help. But unfortunately, none of the above helped me.

[Og1ma]

@TechnicFix Hi, sorry for tag, but may be you can help me?
In another post you solved the problem with VLC.
Could you please elaborate on your previous post: “I found a solution everything worked for me when moved UEFN project from Onedrive folder to anther one”.
Thanks in advance.

[Jimbohalo10]

@Og1ma

“I found a solution everything worked for me when moved UEFN project from Onedrive folder to anther one”.

From 31.20
There is now a message that appears if you attempt to make or open a project on OneDrive

We do NOT use OneDrive as your Project is stored on a remote Microsoft server taking 10 times longer to access that the local SSD drive.

In Windows 11 the default path is always OneDrive therefore
C:\User\Owner\OneDrive\Documents\UnrealEngine will crash Verse and stop red Squiggly lines, due to the slowness

You must put this path as
C:\User\Owner\Documents\UnrealEngine

Windows 10 uses
C:\User\Owner\source\repos\UnrealEngine

In windows 11 the only path without OneDrive is the Download directory
Unreal Revision Control will break if you restore to OneDrive