SpawnParticleSystem is not visible if player is further than a certain distance from the world origin

General Issues and Bug Reporting
, , ,
1

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Verse

Summary

If player character is further than a certain distance (approximately 140m) from the world origin, the particles spawned using the SpawnParticleSystem() function will not be visible to the player.

Steps to Reproduce

  1. Move to a position that is < 140m from the world origin and spawn a particle using SpawnParticleSystem() function. Particle is visible.
  2. Move to a position that is > 140m from the world origin and spawn a particle using SpawnParticleSystem() function. Particle is not visible.

See video demonstration:
2024-04-27 18-04-48.mkv (27.5 MB)

Expected Result

Particles spawned using the SpawnParticleSystem() should always be visible regardless of the player position from the world origin.

Observed Result

Particles spawned using the SpawnParticleSystem() is not visible if player is further than 140m from the world origin.

Platform(s)

Windows 11

2

Can confirm I’m getting the same issue, couldn’t understand why the method only worked on my side project, now I do


(does the same disappearing when going far away vertically)

3

As a side note, the method seem to spawn them outside the replication range, it’s just the client that won’t display them if outside the range

4

The status of FORT-738496 incident has been moved from ‘Needs Triage’ to ‘To Do’.

2 Likes
5

Just one additional observation… if spawning a Niagara loaded via @editable, it also doesn’t work

1 Like
6

Issue is still present and replicable, as another commenter has said a workaround is to put the niagara inside of a blueprint and instead spawn that, but that’s not really a great way for us to be using particle systems

1 Like
7

Bump, still not fixed 2 updates later

8

Gonna post to increase the importance of this.

2 Likes
9

Bumping as the degradation of server performance after calling SpawnProp (and disposing correctly) seems to only ever be increasing with each UEFN update. Fixing this niagara bug would allow an easy performance boost for many maps

3 Likes
10

Please fix this, We don’t want to spawn creative props anymore.

1 Like
11

Spawning too much creative props to activate vfx causes lag after the server has been up for more than 2 hours, probably after X amount of spawns it starts to affect the performance,
Has this been fixed? spawning vfx via verse is essential

12

You sure about that, I’m pretty sure I did a test with spawning thousands of them and it worked flawlessly (?)

1 Like
13

For my own knowledge, How does this work with the spawned prop limit or am I miss-understanding and you mean VFX spawned by Verse have no spawn count limit?

14

I was referring to spawning props, which now work well (even though they’re still not spatially loaded? not sure though)

The spawning limit is 5000 per creative device if I remember correctly

15

Wow I feel pretty silly, You know how HARD i’ve been working to keep spawning props under 200!?! That must apply to NPCs :frowning: haha

1 Like
16

I think this got silently fixed in v32.00