range as an argument in 'sync', 'race' or 'rush' will cause your project to crash everytime

General Issues and Bug Reporting
, , ,
1

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Verse

Summary

When having range as an argument for the marcos sync, race, or rush, the UEFN project will crash on your next build and everytime you reopen the project

Steps to Reproduce

write sync(i:= 1..2) anywhere in your verse code and build your code

Expected Result

The code should build successfully with no issues

Observed Result

The editor crash once built and will not open unless you removed the marco with range argument

Platform(s)

PC

Additional Notes

This has been tested only on ‘sync’ and ‘rush’

2

Just by curiosity, what is this supposed to do instead of crashing ? :smiley:

Did you find this syntax on the doc also ?

3

Ranges are not limited to for but can be used in those marcos I mentioned too. VS does not give any error when using them but when pushing verse changes, the editor will crash and will not open unless removed

Edit: I think I misunderstood your question. What will simply happens is exactly like for loops. Those marcos will be executed the same way they do but with range used as an argument. So each iteration will have a new value

IMG_2380
IMG_2380828×177 88.9 KB

1 Like
4

Uhm ok I see, but what’s the expected result then ?
Should it repeat the whole wrapped thing many times ?

Like for race: it would exit the race and enter it again ?
Why not wrapping the race with a for() loop then ? :smiley:

I understand that there is a problem because it’s in the doc and it compiles, but I can’t figure out why it’s there :smiling_face_with_tear:

1 Like
5

To be honest, it has no difference from using for loops. So yeah the expected result will be as same as using race: inside for: but using range in race: will save you from writing for: so once race is exited it will re-enter again with new value :man_shrugging:

1 Like
6

Hi. I reported a bug about it previously, but there was no response.

You guys are right, we could substitute the for.

2 Likes
7

The status of UCB-1010 incident has been moved from ‘Awaiting Validation’ to ‘Closed’.

1 Like