Major (Resolved) - Verse scripts won't compile, "/Fortnite.com/Devices" path is unrecognized.

[Fresnella]

11/7 Update

Ok good news, “Fortnite.com/Devices” path errors are still there the reason my script didn’t run was because of my own syntax mistake! Thanks @RayBenefield for the help! So for any creators reading this, even if you get an “Invalid Verse path ‘/Fortnite.com/Devices’ Cannot find module” compilation error in your script, if you have correct syntax your script should run fine. Ignore that error and just look at your own syntax.

So this isn’t Blocker but I’m still listing it as Major because I’d like to request that Epic communicate to creators somewhere that the current incorrect " Invalid Verse path ‘/Fortnite.com/Devices’ Cannot find module" compilation error is not the creator’s fault. Because the default script from Epic gives errors, specifically about the “Fortnite.com/Devices” path, I was less likely to scrutinize my own syntax around devices. Axel told me they experience this error too, so I think it might be a widespread thing? It’s hard for creators to know when we’re actually making mistakes, if red underlines and compilation errors are there by default. Especially if we don’t know that the default errors with the default script are known.

I propose adding this known compilation error bug to the list of Known Issues on the 22.35 November Release Notes https://forums.unrealengine.com/t/uefn-22-35-release-november-1st-2022/681729/1. We’ve got a lot of newer creators who are going to be making their first Verse scripts and I want people to know the red underlines are normal.

11/6 Original post

Please, I really need help with this. After this update, for me Verse is completely broken. So I’m blocked from working on mechanics. I’ve created working verse scripts before the update, so I don’t think it’s my fault.

Based on the error log, it appears that the “using” paths at the top of the default script might be outdated, because Fortnite.com/Devices is not being recognized. I think that’s why the rest of the script is being flagged. From the moment I opened the default script without making any changes, there were a bunch of red squiggly error underlines in the code. I tried adding my own code anyway, and whenever I tried to build the script I got several compilation errors and was unable to create my device.

Here’s my script with all of the squiggly lines:

Here first errors I got when I tried to build the script:

Because of the first line, “Script error 3506” Unknown identifier ‘button’. Did you forget to specify using {/EpicGames.com/Temporary/UI }", I added {/EpicGames.com/Temporary/UI } to the top of my script, but this didn’t help.

Here are the errors I got the second time. Lots of “Unknown Identifier”, and “cannot find module” for Fortnite.com/Devices and EpicGames.com/Temporary/UI.

I think the reason Verse isn’t recognizing identifiers is because it’s doesn’t have access to the info that it should be getting from Fortnite.com/Devices.

I tried to Push Changes to the game anyway, and I could not, because I got a "Failed to validate for Upload message.

When I exited UEFN and reopened, the problem persisted.

I spoke with Axel, who told me that they’ve experienced the red lines but that their scripts still work.

On WertAndrew’s Advice, I clicked “Verify Files” on UEFN in the Epic Game Store like this. This caused some changes but Verse is still broken for me.

Here’s what happened this time: I was able to compile the script one time, in order to create a device that I could drag into the scene, which I couldn’t before. The red error underlines were still present, and the message that Fortnite | Juego multiplataforma gratuito - Fortnite was not recognized. I started the game, and I still got error popups about compilation errors, and “Failed to validate for upload” In the output log, I saw that my printouts that I was using to test the script were showing, even though I had gotten errors.

However, I can’t add devices as properties on this script, because they don’t show up listed in the Details panel. And when I tried creating a second script I could not create a device for the new one. Basically the only thing that changed when I verified the files in the Epic Games Store was that I was able to build one Verse device one time, and never use it again.

Thanks in advance for the help!

Here are my logs:
This one is from before I tried WertAndrew’s advice:
Logs_BlueClairy_Nov5.zip (155.6 KB)
This one is from after I tried it:
Logs_BlueClairy_Nov5_2.zip (173.2 KB)

[AxelCapek]

Just pitching in to say I having a similar issue with red lines, however with the correct code im able to compile successfully.

[RayBenefield]

Hey Blue! Looks like you have a syntax error. You put button.device instead of button_device so it’s looking for a different library. You shouldn’t need the UI library.

EDIT: Looks like the same with cinematic.sequence.device which should be cinematic_sequence_device.

[Fresnella]

Thanks so much Ray! Very goofy mistake on my part. I updated this post to show that you helped me solve it! I’m still leaving it as Major because I think that the "Invalid Verse path ‘/Fortnite.com/Devices’ Cannot find module” compilation error could be a big problem for new Verse users or creators who aren’t aware of the known bug, it’s confusing. Is there a way Epic could better surface the fact that that particular error should be ignored by creators? I suggested mentioning it in the Known Issues on the recent release notes. Personally I checked the Known Issues when I was trying to figure out my case.