Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Resolved Get rid of ObjectToWorldTransform by default

Discussion in 'DOTS Dev Blitz Day 2023 - Q&A' started by JesOb, Aug 24, 2023.

  1. JesOb

    JesOb

    Joined:
    Sep 3, 2012
    Posts:
    1,081
    Current Unity Transforms design uses too many big components and waste big part of entity memory.
    Solution like @DreamingImLatios create in LatiosFramework dont use Matrices on entities and compute it in compute shader on entity data updating to GPU memory.

    This way we can store more entities per Chunk -> win
    The same for LocalToParentMatrix instead of matrix
    The same for LocalTransformIdentityTag for childs without any offset from parent

    and other ways to consume as small bytes as it can be to release room for gameplay data in entitychunk

    What UT have for us in this space of memory optimization? What thoughts, plans, etc.
     
    JesOb, Aug 24, 2023
    #1

  2. jivalenzuela

    jivalenzuela

    Unity Technologies

    Joined:
    Dec 4, 2019
    Posts:
    67
    It's a good idea and many times having a 1-1 transform with the rendered object on scene isn't necessary. In which case you can strip the transform data during baking and drive the position as you suggest.
     
    jivalenzuela, Aug 24, 2023
    #2