Messages

1

TNet 3 Support / Hololens compatible?

« on: September 18, 2016, 02:14:55 AM »

Hi, Is it possible to deploy the TNet3 example to a Hololens? I get a range of errors e.g.

Assets\TNet\Common\TNSerializer.cs(17,36): error CS0234: The type or namespace name 'Formatters' does not exist in the namespace 'System.Runtime.Serialization' (are you missing an assembly reference?)
Assets\TNet\Server\TNTcpLobbyServer.cs(28,2): error CS0246: The type or namespace name 'TcpListener' could not be found

I understand that UWP doesn't support all the framework components so I am interested if TNet3 will work in this environment.

With thanks, Peter

2

TNet 3 Support / Two Scenes - Same Channel?

« on: August 25, 2013, 01:36:17 AM »

Hi,
Is is possible to have players in two different scenes connect to the same channel and thereby share RFC?

Every attempt I have made forces the initial server scene to be loaded on the client. As soon as I specify a different channel then the client scene will load, but I cannot share RFCs.

I gather I am missing the concept of the channel....

With thanks...

Peter

3

TNet 3 Support / Increasing scope for RFCs - across scenes

« on: August 19, 2013, 10:54:24 PM »

Hi,

What is the best approach to send an RFC (or alternative) between two devices in different scenes in the same App. The scenario is I am trying to control functionality on the desktop computer (buttons, sliders etc) remotely from the Android/iOS. The remote device is running a different scene (interface) to what is displayed on the PC.  Even though I am calling the same RFC on both devices as soon as the scenes differ, I lose control. Of course I could make the same scene that detects whether it is master or slave, but I would prefer to keep the scenes different if possible.

With thanks, Peter