Verse isnt working there is 5k errors

General Issues and Bug Reporting
, , ,
1

Summary

im unsure whats happened/changed but when i loaded uefn after the update i am shown 2 errors then when i open vsc i have 5k+ errors

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Verse

Steps to Reproduce

Unsure never seen this its like the {} is missing

Expected Result

after the update it should work the same

Observed Result

its broken

Platform(s)

pc

2

image
image1158Ă—912 77.1 KB

3

If you click the verse tab and build verse code it fixes this so idk whats happening but yea if anyone has the same just click Verse tab at the top and build Verse code

1 Like
4

The verse errors come back every time you open the project :frowning: just keep re-building

5

All my Verse code flags red and when i rebuild it, it fixes, but then when i try to launch the session the editor disconnects/crashes. This all started happening after the update and a game that has been posted is being affected by this bug making it unplayable. Someone please fix this issue
.

6

Mine crashed too i opened a smaller project then the bigger project again i think the crash is todo with the errors showing as it shows on full screen for me while compiling shaders then it crashed.

Try like i said opening a small project then re open the one that crashes obv after you initially build verse code

7

I’m getting the same errors as described and shown in the pic. Happened after the update for me too.

8

I also noticed that when I try and load a session, the editor wants to save all my verse devices as if they’ve been modified. I have no idea whether I should or shouldn’t save them when it asks, but I don’t remember having to do this after any other updates in the past.

9

Don’t know if it’s related but my Verse Server is crashing and turning off as soons as I open the VS Code, but not in all projects, just in one for now. This disables the intellisense and it makes really hard to work. Building, pushing and lauching session still work though.

image
image1873Ă—580 86.6 KB

10

Investigating this! Thank you!

11

Sounds like we’re aware of this and investigating / working on it.
Thank you for reporting!

12

Hey all, just added this to known issues: You may experience the following error in VS Code: external{} macro expected here since the code is a digest. This isn’t a problem with your code, and you can work around this issue by recompiling Verse.

1 Like
13

Just fixed. It seems that the sanitizer is not properly finding “concrete”/editables miss usage
This was one of my culprits:

image
image722Ă—481 32.1 KB

The problem is, I’ve had the first version of the struct for about a month, with no errors whatsover, we’ve been even able to publish private versions.

Also seems it only happens with certain types of data, it’s really simple to reproduce:
If you comment out both the particle system and the animation sequence (which I’ve had in my verse-crashing structs/classes) no error happens even if you left the float, which should also requests a initial value. But as soon as you uncomment them, the server crashes without prompting any errors

using { /Verse.org/Assets }
using { /Verse.org/Simulation }

new_struct := struct:
    #@editable
    #ParticleSystem : particle_system
    #@editable
    #AnimationSequence: animation_sequence
    @editable
    MyFloat: float