Verse Language Server connection error - no syntax highlight

Summary

When opening my verse files, I get an error saying that “The verse Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted.”

For clarity, and because this issue only happen on a specific UEFN project of mine, I will be refering to it as “My project”.

This makes me unable to see any syntax highlight or to ctrl + click on elements and be redirected to their declaration, which is VERY bothering for the workflow.

The code still compile and run without any problem while the session is launched.
This issue only happen on “My project” and not on any of my other UEFN projects.
There was no issue on “My project” as of Thursday february 20, before the Fortnite update 34-00, and the problem appeared after doing the 34-00 Update.

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Verse

Steps to Reproduce

  • I tried opening the verse files of “My project” on another computer, and the problem still persist
  • I tried opening the verse files of another UEFN project and the problem isn’t there anymore
    Therefore, it seems like the step to reproduce is to:
    Sync “My project” with any Fortnite account on any computer and launch verse on it.

Expected Result

Verse launch without any issue and connects to the Verse Language Server, giving me access to syntax highlight and the ability to ctrl + click on elements and be redirected to their declaration.

Observed Result

Verse launch, but with an error that says “The verse Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted.”

  • I am not able to see syntax highlight
  • I am not able to ctrl + click on elements and be redirected to their declaration

Platform(s)

PC

Upload an image

Additional Notes

I don’t want to publicly share more details about “My project”, but I am obviously willing to give all the necessary informations privately to Epic (My Epic ID and name of the project to test the issue)

I had this before try this…

It re installs vsc things

Itll show something bottom right when installed i didnt get it into the snip view sorry

“The verse Language Server server crashed 5 times” already occured a few patches ago. There is also a new bug with this Update, which says “Connection got disposed” once you open VS Code.

Hi, thank you for your reply.

I should have included this in my original post, but I already tried reinstalling the Verse plugin in VS code. However, this didn’t fix my issue.

1 Like

Did you get the 2 verse errors when opening the project ? Click verse tab and build verse code might also help

I had the same thing when i got the 2 initial errors i re installed what i showed and clicked verse tab and build verse code then it didnt do it again so idk what to tell you. Weird updates lately break everything

I am not gettig this, so it might be a different problem.

Also I can confirm that other people have had similar issues in the past as I found a few post on the forum about it, but it seems different from my problem.

Crazy

Sorry couldn’t help more

Hope you get it sorted

hi @YU7A , @Vilvalas , @Vilvalas ,

This error was originally traced to project being saved on MS OneDrive, which is the default for Windows 11. The symptom was missing the red underline in VC Code/ Verse

check in File Explorer the your project path is NOT like example
C:\Users\Owner\OneDrive\Documents\Unreal Projects

The path must begin
C:\Users\Owner\Documents\Unreal Projects

so that path is stored on the SSD.

There is in later versions of UEFN/Fortnite a message for new projects creation ,
but this does not appear for older projects, especially under Windows 11

Hi, thanks for the information.

Again, this is a solution that I found on previous posts and that I should have mentionned in my original post.

I already checked that my project isn’t saved on OneDrive and is indeed saved on my own SSD. Same for when the issue appeared on a different computer. So, it seems to be a different problem :pensive:

Btw the way, my main computer is still on Win 10, and the second computer I tried it on is on Win 11.

hi @YU7A ,

How big are your Verse files there use to be a 64k limit which now seems to be about 96k, the connection to server error occurred. When the developer cut out a lot of new code for the UI the error went cleared .

The problem lies in size of VS Code Workspace and we users cannot change that.

Is it a limit for a single verse files, or for all verse files of a project combined?

Anyway, I don’t think we reached it.

I found how to reproduce the issue:

  • Writing mesh as an editable makes the verse server crash.

@editable Name : mesh

The code doesn’t give any errors about it, it can still compile and run without any issue, which makes it very hard to detect.

I encountered the same error, but my situation was slightly different.
The solutions mentioned above didn’t work for me, and I didn’t have a Mesh object.
My solution was:

  1. Intentionally build incorrect code, causing a build error.
  2. Close VSCode.
  3. Go back to UEFN, where I saw the Verse build error warning.
  4. From the UEFN menu, select “Open VSCode” again.
  5. Somehow, after that, it just started working normally.

This issue occurred after the v34.00 update.

1 Like

This started happening in one of my maps too yesterday and the only thing that I changed in Verse (in comparison when it was working fine before) was adding simple TeleportTo to change position of 2 Timer Devices, nothing else. The code and whole map is otherwise working fine, the issue is “only” with a feature of highlighting syntax in the editor.

And after I wrote this and opened that project where it was happening yesterday, It is now happening also in my other project that I was editing in Verse just fine few minutes ago until now (restart of UEFN did not helped) :frowning:

Thanks for the posts about this issue.

To workaround this issue you need to define your respective @editable variables with a default value

This will workaround the issue:

test_class := class:

hello_world_device := class(creative_device):
    @editable MyMesh : mesh = Meshes.Box_D2757564

    @editable TestClass : test_class = test_class {}

This will continue to crash the Verse Language Server:

test_class := class:

hello_world_device := class(creative_device):
    @editable MyMesh : mesh

    @editable TestClass : test_class
1 Like

FORT-864653 has been ‘Closed’ as a duplicate of an existing known issue.

The duplicate ticket is SOL-7775

This method works for me too

Duplicate ticket for tracking: SOL-7775

Thanks everyone! (Hi @YU7A :slight_smile: )