[Odin Serializer Open Source – Contest] Win NodeCanvas and FlowCanvas Licences!

Forums Announcements [Odin Serializer Open Source – Contest] Win NodeCanvas and FlowCanvas Licences!

This topic contains 4 replies, has 3 voices, and was last updated by  Gavalakis 1 week ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #1837

    Gavalakis
    Keymaster

    [Odin Serializer has gone open source] and plans are to move from FullSerializer and into using Odin Serializer for NodeCanvas and FlowCanvas, thus utilizing Odin’s great serialization speed and capabilities!

    For going open source, DevDog/Sirenix along with ParadoxNotion, are celebrating with a contest running right now, where you can win a NodeCanvas and a FlowCanvas license by entering!

    > [ENTER THE CONTEST!] <

    Join us on Discord: https://discord.gg/97q2Rjh

    #1876

    louisgamedev
    Participant

    Where was the winner announced? Also is there a roadmap to when Odin serializer update is releasing?

    Cheers

    #1886

    Gavalakis
    Keymaster

    Hey!
    I don’t really know whom the winners are since I was not the contest host 🙂
    The integration roadmap is planned for version 2! (hopefully sometime soon after summer).

    Thanks!

    Join us on Discord: https://discord.gg/97q2Rjh

    #2481

    randomuser
    Participant

    Hi, will this come at some point?
    I want to use graphs for the Ability system for many enemies, which would require a lot of runtime instantiations. I read that graph instantiation currently has a little performance impact. I saw FullSerializer in the folder structure of the extension and it’s somewhat known that it is not the fastest. Maybe it’s not the serializer that’s responsible for the instantiation overhead, but if it is, is it still on the roadlist; implementing odin instead?

    #2484

    Gavalakis
    Keymaster

    Hello,

    Stock FullSerialize is not very fast, but I have modified and tailored FullSerializer to the framework a ton and it is much much faster than stock is. Furthermore, in v3.x, deserialization and initialization can take place Async on a separate thread, which basically means zero overhead on the main thread (this is an option found in the FlowScriptController inspector). As such changing serializer is no longer considered since it will not bring any real advantage to the table at this point after all the tailoring and customizations that have been done.

    Join us on Discord: https://discord.gg/97q2Rjh

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.