-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flickering Effects with VFX Graph #4
Comments
Hi, thank you for using Record3D :)! Please read my advice mentioned in this issue marek-simonik/record3d_unity_demo#8 — I think that Github issue seems very similar to the problem you are describing. In general, I think the problem might be in the way the VFX graph is set up; you might try experimenting with how many particles are spawned and whether to even spawn new particles in each frame. Instead of spawning new particles, you might modify the VFX graph to spawn only a certain number of particles at start and then update the position of the existing particles. This should improve the performance and reduce (or eliminate) flickering. |
Experimenting as we speak, the linked issue page is exactly what I was looking for. Thank you for the prompt reply and help, Marek. One last question before closing this comment: Is it possible to obtain the raw depth map from the r3d file? |
To obtain depth images, just unzip the |
Marek,
Thank you for providing such a wonderful app. When you get a chance, would you mind helping me debug/make sense of an issue? I've cloned the repo and followed the READme, successfully setting up the project.
However, I'm facing an issue in which my r3d file keeps flickering when running the main scene with either VFX particle system (Simple and Particles). The VFX graph exhibits flickering effects and in some cases completely drops frames. I've checked the timeline settings, noticed it was set to 60 FPS, so I set it to 30 to match the frame rate in which the RGBD video was captured. Unfortunately, this hasn't resolved the issue.
If attaching a video would be helpful, I'm happy to share.
The text was updated successfully, but these errors were encountered: