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. Join us on March 30, 2023, between 5 am & 1 pm EST, in the Performance Profiling Dev Blitz Day 2023 - Q&A forum and Discord where you can connect with our teams behind the Memory and CPU Profilers.
    Dismiss Notice
New Forum User Notice Performance Profiling Dev Blitz Day 2023

Question Byte size of numeric custom parameters in UGS Analytics

Discussion in 'Unity Analytics' started by jeffomatic, Jul 30, 2022.

  1. jeffomatic

    jeffomatic

    Joined:
    Jun 24, 2021
    Posts:
    14
    UGS Analytics custom parameters may be ints and floats, but the docs don't seem specify their actual precision in bits. Are these 32- or 64-bit values? Thanks in advance!
     
    Last edited: Jul 30, 2022
    jeffomatic, Jul 30, 2022
    #1

  2. Julian-Unity3D

    Julian-Unity3D

    Unity Technologies

    Joined:
    Apr 28, 2022
    Posts:
    133
    Hey @jeffomatic

    The platform should behave just fine with 64-bit values passed through in custom parameters.

    I'm interested to hear what your use-case is and what your concerns are?
     
    Julian-Unity3D, Aug 3, 2022
    #2

  3. jeffomatic

    jeffomatic

    Joined:
    Jun 24, 2021
    Posts:
    14
    Thanks for the response!

    The context is that I'm thinking about sending some memory usage telemetry via an int field, and was wondering whether byte-level precision was sufficient. A signed 32-bit int would give you the ability to report ~2GB, but if you wanted more headroom, you'd either need 64 bits or a lower resolution, e.g. KBs or MBs. Sounds like I'm fine doing bytes.
     
    jeffomatic, Aug 3, 2022
    #3