Jump to content

Search the Community

Showing results for tags 'particle system'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to UNIGINE Forums
    • News & Announcements
    • Getting started
  • Development
    • Content Creation
    • World Design
    • Rendering
    • Animation
    • Physics, Navigation and Path Finding
    • UI Systems
    • Sound & Video
    • Editor
    • C++ Programming
    • C# Programming
    • Networking
    • Sim IG (Image Generator)
    • VR Discussions
    • General
  • Improving UNIGINE
    • Documentation
    • Feedback for UNIGINE team
    • Bug Reports
    • Unigine SDK Beta feedback
  • Community
    • Add-on Store (https://store.unigine.com/)
    • Showcase
    • Collaboration
    • Tools, Plugins, Materials & Tutorials
    • General Discussions
  • Legacy
    • UnigineScript

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 4 results

  1. When are we getting PhysX 5 support so you guys don't have to rebuild your particle engine? (You can't even compare unigine to niagara or unity, none the less PhysX)
  2. So..... where's Houdini support and a new modern updated particle system to actually handle proper particle simulations? This is the last final thing that's holding unigine back in my personal opinion and curious where it's at on the road map!
  3. Hello, After instantiating a particle effect that isn't tied to a persistent object and lasts a finite amount of time (for example, sparks when a bullet hits a wall), how do I know when to destroy it? There doesn't appear to be any sort of property or callback in the ObjectParticles interface that could be used to determine whether it's no longer emitting particles. The Third Person Platformer demo in the SDK just loads a node, places it and forgets about it, which is fine for a demo, but having an unbound number of no-longer useful nodes remain in memory until potentially the end of time strikes me as something that would cause problems eventually. I tried writing a function that tries to calculate the total lifetime of a node from the properties of the ObjectParticles it's made up of, but because there are multiple ways of preventing it from running forever and most effects are made up of multiple emitters, some of which may be synced to others, it's difficult to make robust. Is there anything I missed in the API or am I just going about this the wrong way?
×
×
  • Create New...