Search Unity

  1. Unity 2018.3 is now released.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We've updated our Terms of Service. Please read our blog post from Unity CTO and Co-Founder Joachim Ante here
    Dismiss Notice
  4. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  5. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

Would Unity support local GI like the new NavMesh Component in future?

Discussion in 'General Discussion' started by asdzhh, Aug 9, 2018.

  1. asdzhh

    asdzhh

    Joined:
    Jan 20, 2018
    Posts:
    1
    Not only rely on a scene.
     
    joshcamas likes this.
  2. joshcamas

    joshcamas

    Joined:
    Jun 16, 2017
    Posts:
    384
    I think this approach - leaving the scene structure as much as possible - is pretty important. In my opinion, occlusion, GI, and others should be detached from the scene. Not sure if the data structures for these things, specifically GI, would be able to work in a component form, but it'd be the best if that would be possible. With all the focus on squeezing as much optimization as possible, it's odd we still have slow load times due to not having much control on scene loading and scene data.

    I personally see a future where we can completely drop Unity's Scene structure, and create our own system, if we so desire. That fits Unity very well, in my opinion. but this is just a dream at the moment.

    Of course, the Navigation Components are still unfinished. Which is odd as well. Unity is generally very good at getting features out, other than I guess the Input System and Navigation Components. (Probably others I missed)