This forum is no longer active. Reference only.

I've made a few tweeks which should help the PTT reverse at least.

Let me know.

Good!

Ok, I guess the new version is the one I can download, right?

Done and installed it, I'll let you know once tested.

Thank you again!

Hello!

We have a copy of SimCom X running on a server, it's not got MSFS installed on it but it's running in host mode and all the ports are forwarded.

Should we be able to connect to it? I have SimConnect installed and the voice says online on the host mode is green.

When I connect a client it also says voice green.

Just wanted to check if there is any requirement for the host to have MSFS running on the same machine it for it to work?

Thanks

Gnome

ATC Roo wrote: ↑Wed Dec 30, 2020 12:16 am I've made a few tweeks which should help the PTT reverse at least.

Let me know.

I've dowloaded the new version and - so far - no more PTT mapped button (on the A-10 HOTAS throttle) reversal.

Also, setting the Auto COM switch in the Config, I can see COM1 and COM2 indicated. I still can't see them if I do not tick this setting.

Thank you!

DenisFerrari wrote: ↑Sun Jan 03, 2021 4:30 pm
Also, setting the Auto COM switch in the Config, I can see COM1 and COM2 indicated. I still can't see them if I do not tick this setting.

Thanks for the feedback Denis, it's appreciated.

I'm not sure what you mean by COM1 and COM2 aren't indicated.

The displays should show ---.--- in all boxes after pressing the PWR button.

Does this not happen?

Correct, the displays indicate ---.--- on both. Shouldn't this indicate the cockpit set freq's ?

They only show cockpit COM1 and COM2 freq's set if I tick the AUTO Comm Switch (or similar voice) in the Config.

Is this correct?

Thank you very much again!

Denis

OK, that sounds correct then.

Simcom X can be used without running a flight simulator.

If the Autoswitch is Unticked, a user can input a frequency into the STBY box and the press the switch button (in the middle of the frequency displays) to make it the Active frequency.

Somebody acting as ATC might use it this way for example.

The Autoswitch is only for users who wish to change frequency using their flight sim radio stack.

Full details of what Simcom X should do are on my website.
https://dotdash.space/simcom-x-pilot-client/

I hope that helps.

Ah ok then!

I did not try yet to insert a freq in StdBy , without the sim....

Very good then!

Thank you
Denis

2.2.1.14 available now.

I've played with a lot of things, so I hope I've not missed anything.

I've now added a feature that I've called Nearby ATC.
It can be enabled by a tickbox in the config window.
It will also be compatible with the ATC VCCS im still working on.

If a Simcom x user acting as a pilot, flys within 40nm of a SimCom X user acting as an ATC.....
The pilot will hear a beep, will have a message displayed in SimCom X and one in their simulator (although uipc is being picky with messages, so xpuipc users may not have a message in the sim) saying which controller is active and a frequency you can contact them on.

I thought this may be handy by drumming up business for ATC and help to stop pilots accidentally flying through controlled space.

NaughtyGnome wrote: ↑Sun Jan 03, 2021 4:08 pm Hello!

We have a copy of SimCom X running on a server, it's not got MSFS installed on it but it's running in host mode and all the ports are forwarded.

Should we be able to connect to it? I have SimConnect installed and the voice says online on the host mode is green.

When I connect a client it also says voice green.

Just wanted to check if there is any requirement for the host to have MSFS running on the same machine it for it to work?

Thanks

Gnome

Hi Gnome,

Appologies as I've just seen this post.

Running that way is fine.

No sim is needed in order to use SimCom X and it can be used as standalone.

Roo

Super Thanks Roo,

I am having some issues getting the system working as a server.

It's clearly a firewall issue, as if I turn off the firewall it works and I can connect to it.

However with the firewall on and a rule passing UDP packets on port 9988 to the SimComX application I cannot connect to the server.

I have noticed there is a SimCom X.exe and a Simcom X Server application as well. Which should have the packets being allowed through?

I've also noticed that there are some other UDP ports in use when checking the Processes and what ports they are using:
Any advice or thoughts?

I am running Windows 2019 Server Standard Edition

Try the below link
https://dotdash.space/scx/firewall.html

I wrote it a while ago, but it should help.

Thanks,

Tried that and it didn't ask again for permission to go through the firewall.

Have re-added manually.

Any other thoughts?

Definitely does sound like a firewall issue if you can connect with the firewall off.

Simcom X should cause windows to ask if you want to add a firewall exception on first run.
If it doesn't ask, could there be a rule still there that you missed?
Have you got another rule enabled that would interfer with the rules you're adding for Simcom X?
Block all UDP connections or another rule for port 9988 for example.

Did you enable the rule for both private and public?

This is a good site which might shed light.
https://www.osradar.com/how-to-open-a-f ... 2019-2016/

Have you forwarded a port on your router or are you using the Upnp option? Just curious.

Only UDP port 9988 is needed to be opened.

What does. netstat -an show?

I've finally got it working, thanks for your help Roo.

There seems to be some NAT going on in a part of the network my server is connected to that I can't control.

Logging exposed the wierdness and now I've modified the rules to allow it.

Thanks again!

Good stuff!

I've just released a new version after I broke it

Enjoy

[.net and ts3client.dll error]
Good day everyone - We have a group of pilots using both joinFS and simComX and want to say a very big thank you to the devs.

About 4 or 5 of us are having constant crashes with simComX and I check the logs and show the following errors messages. We are using simComX in group mode and not using it to control teamSpeak:

[.net runtime]
Application: SIMCOM X.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at TeamSpeak.Sdk.Client.NativeMethods.TryStartConnection(TeamSpeak.Sdk.Client.Connection, System.String, System.String, UInt32, System.String, System.String[], System.String, System.String)
at TeamSpeak.Sdk.Client.Connection.Start(System.String, System.String, UInt32, System.String, System.String[], System.String, System.String)
at SIMCOM_X.Form1.Connect2()
at SIMCOM_X.Form1.COM2_Click(System.Object, System.EventArgs)
at System.Windows.Forms.Control.OnClick(System.EventArgs)
at System.Windows.Forms.Button.OnClick(System.EventArgs)
at System.Windows.Forms.Button.OnMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ButtonBase.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Button.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
at SIMCOM_X.Program.Main()

[ts3client.dll error]
Faulting application name: SIMCOM X.exe, version: 2.2.1.22, time stamp: 0x601b2967
Faulting module name: ts3client.dll, version: 0.0.0.0, time stamp: 0x58b44480
Exception code: 0xc0000005
Fault offset: 0x000170dd
Faulting process id: 0x1354
Faulting application start time: 0x01d701898a5106ef
Faulting application path: C:\Program Files (x86)\Simcomx\SIMCOM X.exe
Faulting module path: C:\Program Files (x86)\Simcomx\windows\win32\ts3client.dll
Report Id: 2f6a7a8d-85e2-4d83-bdd0-cefaea6261d5
Faulting package full name:
Faulting package-relative application ID:

Please let me know if you need further information and I shall be glad to provide.

Kindest regards
Jim

Thanks Jim.

The info you posted was helpful.
Leave it with me and I'll tell Simcom X to stop being silly.

There'll be an update shortly.

Sorry Roo your reply made me chuckle, reminded me of the kids.

Glad you liked it.

You couldn't post the Simcom X log too could you Jim?

I could double check things that way.