koobas.hobune.stream
Particles not showing in build but are in editor play mode
All I need to put is the images and you can see for yourself...
The game in editor play mode: 
The game in build: 
In the game the particle system is always in-front of the camera, regardless of where the camera is. The particles are in world space and positions are set manually via script.
Any help or suggestions on a fix for this will be greatly appreciated.
I should clarify, what you see in the build are not particles but are sphere meshes, for close up suns.
The particles are created during runtime, which I've checked. Plus I've done some other checking the only possible cause is something to do with the particle renderer...
Upon further investigation it may be a result of a culling bug...
I've found a "solution". Abandon this buggy particle system and use the legacy particle emitter. Works easy and no performance issues from using it.
The issue with the new system is the messed up culling of the particle system, even if all settings have culling of it disabled.
Here's the final product, in build. My infinite space looking good now :) 
With subtle Post Effects 
This doesn't seem a great solution, have you reported a bug? I'm seeing the same problem.
From my personal experience I've only been using unity for a couple months but particles don't play by their self in editor mode you have to press simulate for them to play in editor and when you enter play mode they auto play
"editor play". As in the play mode in the editor.
The top image is from the play mode.
The bottom is from when you click Build and Run. Code is the same. No reason why this should happen.
Idk but that's just how unity works just like how all animations don't just play in build at once because it would be hard to work with that but yea you can only simulate particle affects manually in build and once you click off of it they stop then when you go to the play mode they play like they would in the game
You seem to be answering a different question ZeaVillain, I'm seeing the same issues.
I just doubted it would be fixed. I found evidence of this bug existing since the old system was made legacy. Like 2012?
