No announcement yet.

Plaintext Asset Files

  • Filter
  • Time
  • Show
Clear All
new posts

    [FEATURE REQUEST] Plaintext Asset Files

    Why are .uasset files stored as binary rather than plain text? They already have a textual representation which is used when copying and pasting blueprints, and which looks decently easy to read and work with.

    To me, it seems it would make more sense to just store the files in this text format. I realize this may be a fair amount of work to implement, however I feel that the quality-of-life improvements for any team collaborating on assets would be worth the effort.

    Some potential benefits of this approach:
    • Easier to diff two previous revisions
    • Ability to diff and merge assets using external tools
    • Ability to cherry-pick previous changes
    • More efficient version control storage
    • Exclusive checkout on assets would no longer be necessary
    If we can't get this, can we at least have all blueprints/tabs within an asset file separated into multiple files? Dealing with these files has been a pretty major pain point for my team.

    Many asset types are not compatible with that


      ASCII uassets format is in active developed.
      Or at least under research..
      | Savior | USQLite | FSM | Object Pool | Sound Occlusion | Property Transfer | Magic Nodes | MORE |


        If you're interested, here is a recent talk that mentions the potential introduction of text based assets for the similar reasons you have mentioned:
        LinkedIn, Engine Contributions
        Polars (WIP), Game Jam Projects
        Marketplace: Viewport Utilities, Blueprint Streams, Control Structures