Sorry Pete, I missed this part.
Actually the function FSUIPC_Write is defined 5 different ways on the fsuipc.cs file in the SDK:
FSUIPC_Write(int dwOffset, byte param, ref int Token, ref int dwResult)
FSUIPC_Write(int dwOffset, short param, ref int Token, ref int dwResult)
FSUIPC_Write(int dwOffset, int param, ref int Token, ref int dwResult)
FSUIPC_Write(int dwOffset, long param, ref int Token, ref int dwResult)
FSUIPC_Write(int dwOffset, int dwSize, ref byte[] param, ref int Token, ref int dwResult)
So, you can use any of the 5 above: (I used the fifth one for 0x3380 and the first one for 32FA).
I wish I can have a valid answer, but awesomely enough that is the only value that when I pass gives me the time I want (in seconds) for the message to be displayed
I think that if you cannot answer that question yourself then I’m the last person on hearth to be able to answer it. The C# example that is on the SDK comes with it defined globally for all the functions within the application assigned as token = -1, and all the functions to set or get values use the same token.
Going over the fsuipc.cs file I found a definition of Token as: “Contains the unique identifier token used to Get the value”; At the moment is all I can sai about it. Sorry.
I guess is all about the money :D
Sorry I can’t be helpful; to be honest this is my first C# program ever as a matter of fact mi first program ever.
Thank you again, an thank you also for this beautiful piece of work --> FSUIPC