Map Indicator will not enable via verse

Summary

After hours of messing about im unsure if this is direct verse but if you disable the map indicator either at game start or via verse you cannot then re enable it ???

This use to work on my map with the verse i have but now its not working and ive spent hours trying to work this out and the only thing i know is if you disable via the device or with verse and then try and re enable it the device never enables

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Devices

Steps to Reproduce

place a map indicator device and turn off enabled on game start

try and enable via verse

or

Disable via verse with the enabled at game start set to true on the device

then try and enable

The device never re enables

Expected Result

it worked on my map for ages and i noticed it stopped working and it should work as expected

Observed Result

it never re enables the device

Platform(s)

pc

Update:

If i Disable() via verse at game start on a delay ie Sleep(10.0) then it lets me Enable() and it works

image

this is the Enable()

image

If i remove the sleep that is on Disable() the Enable() never works

Update 2:

Event with a Sleep(5.0) it doesnt work so idk whats going on here

I’ll get someone to take a look. Thank you!

1 Like

Hey @AtAshTag - Could you try to reproduce this on a blank project? We’re having trouble reproducing this here.

1 Like

I have tried on a blank island and it does indeed work.

The sleep fixes the issue for me so its not the end of the world but if you think this could have impacts with verse or something then i will gladly zip the project and share as I’m testing in a blank island with nothing in it. The island i have the issue on is a big island with maybe 12+ verse devices things running all over so the environment is completely different its the Sleep(10.0) that I’m not understanding but if it does it for this then it could be a limitation we just haven’t seen currently which is worrying.

Either way I’m fine as with Sleep(10.0) its fixed for me but this is strange and i spent hours trying to work it out and even a Sleep(5.0) makes it not work like i don’t get this one bit

Or i could share the code with the issue and someone can advise if they want prints ect adding

Hi @Flak

Before you answer my response let me do a quick video as this is not right and i do strongly feel they is something wrong with functions firing or something.

@Flak

Please see this

I have tried to show basics of the verse device and the map indicator ect but it shows the issue and I’m lost at how a delay on a Disable() has an impact like this

As im sure some will agree this is very odd but more so concerning

Thank you, we have a repro here. Please ping me after the new year for an update.

1 Like

TY @Flak

Have a wonderful break and try get some relaxation in!!!

what you do here on the forums we all appreciate so so much even if it isn’t said enough

Have a great holiday :slight_smile:

1 Like

FORT-839191 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

The above ticket is a duplicate of FORT-839189

Thank you for the ticket and the workaround!
Only after rolling back to a previous working version before I realized the issue wasn’t on my end.

i spent hours and hours trying to work out why is wasn’t working and i was like what is going on :rofl:

Its not the biggest issue tbh so i could live with this but its more we don’t know what other things are effected or what’s the reason for this.

Having thought about it i have a issue with time on another map and the materials via verse will not work until after 14 seconds after launch so weird. Maybe they is a issue with things when you hit a certain thing

Do we have an update on this one ty ?

I believe I’m experiencing this issue as well in 0535-3255-9081.

  • Enabled on game start set to false

  • Using .Enable()

1 Like

I was losing it trying to work it out took me maybe 4 hours :frowning:

They will fix it soon I’m sure

At least we can use Sleep() to fix it in the mean time