SIMCOM X Voice application

[edakridge]

Roo, the new version definitely loads quicker, but it seems to be unable to connect to the sim. The sim light stays red and I am unable to select FSUIPC in the config.

[ATC Roo]

Yup FSUIPC is not implemented yet.

I'll have a look at the non connection to the SIM.

There is also a problem when using a joystick button as a ptt with that version.
If it loads with a Jostick PTT remembered, it will work back to front.
Setting a new button will correct it.
Will be fixed in the next version.

You should be able to speak to others though?

[edakridge]

Only testing with one other person. No sound yet. I think the problem is on his end (Windows 10).

[ATC Roo]

Sound should definitely work.
Check that the sound card SIMCOM reports when it loads up is correct.

I stopped it talking to the SIM if the box was ticked and it didn't detect it.

So having the SIM running first might help.
Else I'll be looking over that part of the code shortly when I write the FSUIPC part of the project.

A simple test is both have SIMCOM X ticked.
Both tune to the same freq manually.
If one of you ticks the ATC box then you'd show in the ATC section too.

I know I have a few things to iron out, but it should be useable at the moment.

[ATC Roo]

Version 0.0.22 now available.

THIS APP IS STILL IN BETA!
THERE WILL BE GLITCHES!
ONLY USE IT IF YOU WANT TO HELP TEST IT AND FIND THE BUGS!
I then fix the bugs until it's stable.
So please do let me know what DOES and what DOESN'T work.

A LINK TO THE DOWNLOAD LINK!

If this version proves good, I'll add FSUIPC support to the next version which will allow Xplane and FS9 users to use it.
I've just tested with FSX steam and all seems fine.

This version is not compatible with any previous versions.

The further away you are from another aircraft/station, the worse the audio quality until you can't hear each other at all.
So make sure you all start at the same airport to test initially.

To get started.
Open port 9988 in your router/firewalls and allow the app through your windows firewall when it asks on first run.

Once open set your Callsign, and PTT.
Click Config and choose SCX mode or group server and click save.
If you want to autoswitch when you tune the radio in your aircraft select the FSX tick box and the Autoswitch tick box.
If you want sounds when you switch select the sound tick boxes.
If you are acting as ATC select the atc..... you get the idea.

If Group server is selected..
1.Give your friends your IP that appaears in the SERVER box.
2.They then type your IP in the server box and click the Red button that says OFF (I might have to change that, its a bit confusing ).
3.They are connected.

If SCX mode is selected....
1.Click the Red OFF button to turn the radio on.
No IP is needed as SCX mode will look for others on the same frequency as you.
ONLINE ATC will also be displayed in the ATC box.

Once everything is green and says connected tune the standby freq and click the button to make it the active freq (as is done on the aircraft radio).

If somebody is on the same frequency and mode as you you will see them on the list and hear them in your ears.

[TexxasAl]

Currently running SIMCOM x version 0.0.22, with JoinFS, P3d V4, under Windows 10

Sounds from SIMCOM X are routed through the "Primary Playback Device" (as specified in P3d), which are my external speakers

P3d V4 Sound Device Routing.jpg (88.39 KiB) Viewed 13170 times

Sounds from SIMCOM X SHOULD be routed through the "Voice Playback Device" (as specified in P3d), which is my headset.

I believe this designation of the routed device should be controlled from the "SIMCOM X Config" screen, via a selected option?

P3d V4 SSIMCOMX Setup..jpg (71.52 KiB) Viewed 13170 times

This is similar to an issue I encountered 8 year ago, when initially Beta Testing the VRS Superbug, in that there was no way to route the sounds of the aircraft systems (radio. LAWS, etc) to my headset. Not only was this condition an irritant to others in the room, it was factually inaccurate since the F/A-18E has NO Cockpit Speaker in the airplane.

Thanks for all your efforts towards making flight simulation more usable through JoinFS.

Al Rosenberg

[ATC Roo]

Thanks Al.

I'll have a look then and see if I can set the output device.
I can't see why not, but I don't know how at the moment.

I'll be releasing .24 later today as I've just fixed a memory issue, which will speed the program up even more.

[ATC Roo]

0.0.25.0 now available.

I'll start looking at multiple sound cards and implement FS/XUIPC into the next version.

Let me know if it works for you and also the issues.

Seemed quick and stable on my tests.

[TexxasAl]

Quick test of latest release 0.0.25.0 seems stable

Planning to conduct more stringent testing in near future.

Will Advise.

Thanks

[ATC Roo]

Thanks Al.
I've just added FSUIPC support for FS9 and Xplane users running XUIPC.

I'm going to test that and make sure all is working as it should before releasing it and tackling the multiple sound cards.

Once the sound cards are implemented I think that's all the functionality done.

I'll then start work on the ATC client so controllers can call each other and conduct handovers etc.

[ATC Roo]

I'll be releasing the first stable version sometime this week.
This version will support FSUIPC and selection of input/output audio devices.

[ATC Roo]

V0.1.00
Download here!



I've not made it the stable release yet as I added a fair bit to this version and optimised a lot of the code.

Once people have confirmed there are no errors this will be the first stable version.

This version....
The main thing is a new installer.
This clears up all files on uninstall (unlike the previous installer).
I would advise uninstalling any older versions from add and remove programs before installing this new version.
Else this newer version will install alongside any previous versions.
Not an issue, but you don't need 2 versions.
After add and remove programs delete folders named Roo in C:\Program Files(x86) and C:\Users\YOUR NAME\AppData\Local
As the previous uninstaller won't remove those folders.

Added FSUIPC support.
So FS9 users can join in.
This should also work with XUIPC for Xplane users.
Latest XPUIPC can be found here.

And now with less hair than I started with.....
I've added the ability to choose your audio device.

Other changes include...
making the background sounds a little quieter so voice can be heard (useful for a voice app).
Adding a tick box to disable the background static noise.
Optimised the Distance funtion where a station goes quieter the further away the get.
Added miles from a station to update in the client window.


As always let me know the pros and cons.

I'm not planning on changing anything for a bit as it seemed to hold up well for me.

[ATC Roo]

I've found a few small issues with the recent testing.
That's what testing is for.

So there will be an update in the next couple of days.
I'll post it here shortly.

I've just added an update check into the version I'm working on at the moment.

Basically it'll pop up and ask you if you want to install the latest version, if you haven't already got it.

I'm also looking into ways to check if your UDP port is open correctly, which I noticed a few people having issues with and should also help.

At the moment there is a test frequency active on 122.800 in SIMCOM X mode, which will not need port 9988 open.

Feel free to test on this frequency.

If you wanted to test the group mode, use roo.servebeer.com in the IP box.
Again you will not need your port open for that either.

As always, please let me know the issues so I can fix them.

[kc10b747fe]

Hey Roo,

I've been trying to use the SIMCOMX app V0.1.0.0, and I'm not sure what I am doing wrong, but I can't seem to get connected to another person using the app. We installed and initially had a problem on WIN 10 saying there was a problem with Visual C++ and it would not install. We tried installing the most current vc_redistx64, but that would not work. When using the 32 bit vc_redistx86 the app installed and we were able to configure with no issues.

We initially selected SCX mode. I turned on the power button and everything appears correct and green. I am able to see my name in the On Frequency Box and also the UNICOM Freq 122.800 in the Online ATC box. I've opened UDP port 9988 within my router, and also created a inbound and outbound rule in the Windows firewall for UDP 9988. The person I am trying to connect to has opened port 9988 on his router also. His SIMCOMX app shows green in SCX mode also. We are able to connect via JoinFS and see each other, but when we tune to the same freq, neither of our names shows up on the others list.

We tried Host Group Server both ways. In the server box the only thing that shows is Group Host, but I gave him the ip address that was listed on the config screen (which is the same one JoinFS is connected to) and tried to connect, and he received a message in the text box saying "check that the ip address is correct" and no connection was made. We also attempted having him as the Group Host and I received the same message. We also tried without SCX or Group Host selected and in the server box either localhost showed or 127.0.0.1. When inputting either ip address in the server box the power button would not turn on.

I also received an error about TeamSpeak which I did not have turned on and am not currently using. I attached a jpg that shows the error and also shows both our aircraft joined via JoinFS.

I know I must be missing something simple but any help is greatly appreciated.

Thanks for your hard work and support for the community. Looking forward to the update.

Tony J

[ATC Roo]

Thanks Tony.

The bad news is that the version you're using has an issue at the moment.
The issue does cause everything you describe above.
I noticed it during the testing the other day and I'm in the middle of writing a check for it which will fix it.

The good news is I should have the version I'm working on now, available very shortly.

I'm assuming that you have no issues with the auto switch feature (when tuning your SIM radio) and that the app is making noises at you to your headset or speakers?
Ie the sound card selection works?

It's just that you're not seeing anybody else in the channel with you?

Until the new version is out....
Have no tick boxes selected.
Pop roo.servebeer.com into the IP box and connect.
Have your friend do the same.

Does that work?

[kc10b747fe]

Roo,

Thanks for the quick response. What you said is correct. The auto switch works correctly, and I am receiving the TX and RX sound when keying my PTT. The audio card selection feature also checked out. However as stated above we are unable to connect, see or talk using any of the 3 methods. We'll try your work around and report back.

Thanks again,

Tony J

[kc10b747fe]

Roo,
I was able to connect and do some testing with my buddy for a couple of hours today. He was able to connect to your server. I on the other hand on my primary Win7 machine could not. I attached a screenshot of what everything looked like when I tried to turn the power button on.

Screenshot 2018-11-01 09.24.38.jpg (128.12 KiB) Viewed 12761 times

.

I tried a different computer and checked in the router that 9988 was open, checked with Port Forward Network Utilities, and that computer showed that the port was closed however I was able to connect to your server and we were able to test. Everything seemed to operate normally with an occasional stuck transmit and receive. If I transmitted, the TX light would turn red and stay red and he would see his RX light turn green, but then it would stick and would remain green. The callsign name in the On Freq box would turn red on his end and remain red. I would press my transmit button and the headphone icon in my systray would turn red and go out when released but the TX light would remain red. To clear we had to shut the app down (not just power off). Auto switching seemed to work well and we were able to go through different frequencies inside the airplane and transmit and receive very clearly. Manual switching also worked. We were also able to see each other in the On Freq Box, however sometimes it appeared that a 0 or 1 would attach to the end of each of our callsigns like a ghost user.

I shut down the computer I used to connect to your server, but when I brought it back up, I was unable to connect to your server. Again that particular computer showed that 9988 was closed originally but it still connected to the app. Don't know if I have a configuration issue, but JoinFS connected on both computers normally even though the 6112 port shows closed also.

hope the info helps

Tony J

[ATC Roo]

I've just uploaded v0.1.0.4

This has an update checker.
So if you fire it up one day and there is a newer version, It'll let you know.

Hopefully this has resolved a few issues.
Again it seems fine for me, but everybody doesn't have their PC setup the same as me.....

Let me know.

[ATC Roo]

Roo,
I was able to connect and do some testing with my buddy for a couple of hours today. He was able to connect to your server. I on the other hand on my primary Win7 machine could not. I attached a screenshot of what everything looked like when I tried to turn the power button on.Screenshot 2018-11-01 09.24.38.jpg.

I tried a different computer and checked in the router that 9988 was open, checked with Port Forward Network Utilities, and that computer showed that the port was closed however I was able to connect to your server and we were able to test. Everything seemed to operate normally with an occasional stuck transmit and receive. If I transmitted, the TX light would turn red and stay red and he would see his RX light turn green, but then it would stick and would remain green. The callsign name in the On Freq box would turn red on his end and remain red. I would press my transmit button and the headphone icon in my systray would turn red and go out when released but the TX light would remain red. To clear we had to shut the app down (not just power off). Auto switching seemed to work well and we were able to go through different frequencies inside the airplane and transmit and receive very clearly. Manual switching also worked. We were also able to see each other in the On Freq Box, however sometimes it appeared that a 0 or 1 would attach to the end of each of our callsigns like a ghost user.

I shut down the computer I used to connect to your server, but when I brought it back up, I was unable to connect to your server. Again that particular computer showed that 9988 was closed originally but it still connected to the app. Don't know if I have a configuration issue, but JoinFS connected on both computers normally even though the 6112 port shows closed also.

hope the info helps

Tony J

Thanks Tony.

The port doesn't need to be open to connect to roo.servebeer.com as open or not it would have connected.

I'll have to keep an eye on the stuck transmit, only seems to happen when a joystick button is set and is fine with keys for a ptt.
But most of us(me included) like to use a joystick button for our PTT.
If it does get stuck it SHOULD timeout after 15seconds. let me know....

0 or 1 is indeed a ghost user, a previous you which happens if you've rejoined a channel quicker that it took for OLD you to timeout.
I'm hoping I've just added something to correct that too, but it's bottom of the list at the moment.

And don't worry about port 6112 as I've noticed it doesn't seem to respond to ping requests.
Maybe Peter wrote it that way?

If you know your port is forwarded correctly then don't worry, as I said the version you were testing with was flawed.
This new version should correct that.

Thanks for the feedback, it's appreciated.

[Grumpy]

Greetings, Roo

Josh and I are playing with SC-X

So far, we have met with limited success.

simcom X mode gives Josh this error


We changed to using your server as a host.
Under NETWORK , nothing is ticked.
Under Simulator, FSX is ticked
The stuck TX and RX key is still there, changed to Left CTRL cured THAT.
Josh does NOT have FSX or any sim running on his laptop.
At this point, we have ONE working Freq, 119.400
When ever I try to change freqs, nothing. Nothing happens, still 119.400
It LOOKS like I have changed, but it LIES!!!
we have tried 123.450 NO!
122.800 NO

Apart from these few hangups, , veeery interesting.

Regards etc......

Bob