How does TrueSyncInput.SetByteArray and .GetByteArray work with the key parameter?

ScriptGeek
ScriptGeek ✭
in Photon TrueSync (discontinued)
I'm trying to figure out how to send more customized input data via TrueSyncInput.SetByteArray and .GetByteArray, but these methods require a byte parameter... It seems simple to serialize an object into a byte array using a magical black box like ExitGame.Client.Photon.Protocol.Serialize(), but with the byte parameter on SetByteArray it seems to imply that it's unable to determine which class it is when deserializing. And on the other side of the SetByteArray, where it's necessary to GetByteArray, how would it know which class to get? I'm confused, how does this work? Thanks.

Comments

  • ScriptGeek
    ScriptGeek ✭
    Well I figured out to get it to work, but I don't really understand why it was designed in such a way. I can work with this, though.

Cookies,
anyone?

We use cookies and related technologies to enhance your experience, show you personalised content and analyze performance and traffic on our website. By clicking on the „Accept All“ button you consent to the use of non-functional cookies and the subsequent processing of personal data to optimize our website and services as described in more detail in our Privacy and Cookie Policy.

By clicking on the „Customize or Deny all“ button you can decide otherwise. Clicking on the „Customize“ button will take you to a page where you can configure the usage of non-functional cookies (and related technologies) or deny all of them. You can access these settings at any time and also subsequently deselect cookies at any time in the footer area of our website.

ACCEPT ALL

Cookie Overview

We use the following categories of cookies and related technologies to enhance your experience, show you personalized content, and analyze performance and traffic on our website. We respect your right to privacy and accordingly you can chose to not allow some types of cookies (and related technologies). Click on the different category sliders and change our default settings to manage your cookie settings.

For more information on the specific cookies/related technologies we use and on how we use these, please see section 15 E. of our Privacy and Cookie Policy.

ABSOLUTELY NECESSARY

Authentication cookies we use are required to run our services … Cookies are required: Link

FUNCTIONAL AND MARKETING COOKIES

These cookies collect anonymous data and allow us to optimize our website and user experience. These cookies are listed here:

ANALYTICS

Help us to understand how visitors interact with our services, enables us to analyze and improve our services (also through third party analytics).