Howdy All,

We are attempting to use the remote server functionality without luck so far.  When I start the server, a remote client is unable to connect and gets the following attached error message.  I assume it is firewall port or AV related or similar. I believe that I have opened the 1337 port ok. No AV warnings etc.

I get the same message if we reverse the roles of client and server.  Any suggestions would be much appreciated.

Thanks,
Alex.

Ok this time with image...

Did you set a port forward in your router settings?

Hi Simon,

Yes. I have put a port forwarding rule on for 1337. I note in the setup on my router it allows for TCP\UDP. I assume that is ok. The ATVO dialogues all seem to point to HTTP...

I'm still thinking about the strange error message. I think it has nothing to do with the connection itself. I'll try to reproduce it to check if it's an issue on our side.

Thanks Simon. Much appreciated.

Hey guys!

I am having the exact same issue here and havent been able to resolve it. Have you found a solution to it? If so, please let me know.

Thank you!

Does it also happen without any theme opened (on both sides)?

I just realized that it had to be done with the theme opened on only one side... But now the part that I am not understanding is that after connecting I am assuming that if I make a change Then it should appear on his screen as well? If I am right on my assumption, then it is not the case, otherwise if you could help me out it would be really helpful!

In principle you can start the connection any time, but that is not recommended because the theme states do not synchronize when connecting. So you can start in different states and cause issues. However this error is something else, though likely also related to the theme being opened.

I recommend closing the theme on both sides, then starting the remote connection, then opening the themes again.

Yes, if 'follow server' is enabled, the server and all clients should remain in sync and anything you do on the server (or on any client) should also happen on the clients (or server). Assuming you all have the same theme loaded.

Nick Thissen wrote:
Yes, if 'follow server' is enabled, the server and all clients should remain in sync and anything you do on the server (or on any client) should also happen on the clients (or server). Assuming you all have the same theme loaded.

And it works only for TV graphics? Or for cameras as well? Like you can really control the coverage for let's say commentators who are also streaming the footage?

Yes, camera's too.

Is there any documentation for it? Or something we must know in order to use ATVO or Race Control remote?

I do have a problem with the remote control. But the problem we have is just that is doesn't want to connect. And yes I have had it working before, with the same ports.

Also, we had the issue that the host cant chance any camera stuff as the one joining won't follow that.

Common issues are due to firewalls or router configuration. Make sure the port is open, run ATVO as administrator, these kind of things can help.

Sorry to open this topic again, but does this have anything to do with Bug fixes in 1.29.7.0 beta?

Fixed several cases where theme actions were not always synchronized to any connected remote clients.

We were testing multiple case scenarios and found out that the only setup that works is a commentator/streamer as a server and TV direction as a client. Also, it worked only when we have 1 host and 1 client.

While TV graphics from theme is synchronizing well between ALL clients and host, switching TV cams and drivers actually works only between host and client and not between clients. (Follow Server is ALWAYS checked or switching wouldn't work at all)

Is that behaviour intended or could that be firewall / router restrictions?

Hi Nick and co, I have been trying to get the overlay to work in OBS, but I figured I need to have a browser source for it.
I tried the port-forwarding and enabling the remote server and client, but I can't seem to find a url that works to show the actual overlay in OBS.

Anything I am doing wrong? Thanks in advance!!

Lukas Redl wrote:
Sorry to open this topic again, but does this have anything to do with Bug fixes in 1.29.7.0 beta?

Fixed several cases where theme actions were not always synchronized to any connected remote clients.

We were testing multiple case scenarios and found out that the only setup that works is a commentator/streamer as a server and TV direction as a client. Also, it worked only when we have 1 host and 1 client.

While TV graphics from theme is synchronizing well between ALL clients and host, switching TV cams and drivers actually works only between host and client and not between clients. (Follow Server is ALWAYS checked or switching wouldn't work at all)

Is that behaviour intended or could that be firewall / router restrictions?

Sorry I missed this post earlier Lukas.

In case it is still relevant: I am not completely sure how we handle this scenario. I think perhaps we only sync from client A to the server, but then not back to other clients. Clients are not connected to each other, only to the server. I guess we can also relay a command from client A to server and then from server to all other clients, if we don't do that already. I can take a look.

The remote functionality could use some improvements which are in progress but not quite finished yet.

Bert Hoekstra wrote:
Hi Nick and co, I have been trying to get the overlay to work in OBS, but I figured I need to have a browser source for it.
I tried the port-forwarding and enabling the remote server and client, but I can't seem to find a url that works to show the actual overlay in OBS.

Anything I am doing wrong? Thanks in advance!!

This is not related to remote control, why do you think it is? Remote control is for synchronizing multiple instances of ATVO across a network or the internet.

As for your question: the ATVO overlay is not available as a browser source (it's not a browser). You have two options to capture the graphics:
1. Overlay them on top of an iRacing window and use window capture to capture the whole screen.
2. Use NDI to capture the graphics and enable an NDI source in OBS (you need an OBS plugin for this). NDI has its own forum with some explanations, there are two versions and you need to read carefully which one you want to use.