Aries Radio System

[Snoopy]

No exact date for the Moment. I will start the upgrade with the next DCS model release.

 

Thanks for the update, looks like we won't be switching anytime soon then.

[Schleudi]

To be more precise... The next update is scheduled for December or January. (Currently we are also planning to support the VEAO Hawk.) But that also depends on the progress of the radar simulation.

[beynesairforce]

Hi, Is it possible to delete the OpenBeta HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AriesWings\ entry ?

[Random]

I've finally ironed out all the problems I was having. Enjoying aries a lot now!

 

Hope we see the GCI addon soon!

[towsim]

If you do not have the DCS open beta version installed, all open beta entries may be deleted. The entry is used by the TeamSpeak plugin DLL to find the open Beta export.lua and by the open beta configurator.

[towsim]

@random,

could you describe how you solved the issues? It could probably be for interest in the documentation.

[Random]

Im not entirely sure. But setting DCS to run as admin was the last change I made. Since then no problems!

[chromium]

Got an error since 1.955, PTT doesn't work anymore:

 

this is the log:

 

33 [00:00:00.259] Thread Radar Service started HDL: a54 ID: 17b8

2 [00:00:00.298] AriesAirborneRadio DLL initialized

33 [00:00:00.339] Thread Watch Supervisor started.

10 [00:00:00.409] Radio LUA started

10 [00:00:02.876] DCS in single player mode: 0

88 [00:00:03.064] SetCombinedArmsMode 0

44 [00:00:03.099] In MissionStartup version V1.955

77 [00:00:03.136] Opened existing file mapping

80 [00:00:03.172] Shared Memory client active Adr: 23e30000.

30 [00:00:03.214] DCS Application Window found 160bdc

11 [00:00:03.256] Sync time sent to Plugin: 3.214

33 [00:00:03.292] Thread AUXwindowPump started HDL: a6c ID: 17b0

11 [00:00:03.334] Start AUXwindowPump

33 [00:00:03.400] Thread RadioWatcher started HDL: a70 ID: 514

1 [00:00:03.442] Registered Window class instance: e74f0000

33 [00:00:03.484] Thread ScoreWindowPump started HDL: a7c ID: 1278

22 [00:00:03.525] Com hdl e0bf4 set to shMem 23e30000

22 [00:00:03.568] Sent window handle to TS3

11 [00:00:03.610] MissionStartup

44 [00:00:03.652] HotKeyThread started

33 [00:00:03.736] Thread HotKeyThread started HDL: b54 ID: 1360

e3 [00:00:03.784] KbdWatcher Thread started

66 [00:00:03.904] LoadBkGndFileName send C:\Program Files\Eagle Dynamics\DCS World 121\AriesWings\jet1.snd

34 [00:00:03.952] install DEVICE_HANDLER: CH COMBATSTICK USB

66 [00:00:04.023] LoadBkGndFileName send C:\Program Files\Eagle Dynamics\DCS World 121\AriesWings\UH1CockpitNoise.snd

66 [00:00:04.060] LoadBkGndFileName send C:\Program Files\Eagle Dynamics\DCS World 121\AriesWings\A10preStart.snd

33 [00:00:04.101] Thread ButtonWatch started HDL: 210 ID: 1b98

34 [00:00:04.145] DEVICE_HANDLER: trm->StartThread returned 210

34 [00:00:04.179] device handler 3 for CH COMBATSTICK USB installed. HDL: 210

0 [00:00:04.215] Program Execution Error in AUX_WIN::InstallDeviceHandlers

00000000e74f51ad EXCEPTION_ACCESS_VIOLATION

11 [00:00:04.289] TactCallSign = CA vehicle

33 [00:00:04.385] Thread PicWinThreadThread started HDL: b80 ID: 1a88

99 [00:00:04.425] TGPwindow long 1920 1080

11 [00:00:04.461] Air picture Folder: .\AriesWings, TGP window: 1500 400 420 420 -- 1920 1080

11 [00:00:04.505] InitialCtct with CA vehicle CAvehicle tpID: 1

81 [00:00:04.539] Configure Radio 0 Frequency: 0.000, Volume: 0.88 stereo: 0

81 [00:00:04.575] Configure Radio 1 Frequency: 0.000, Volume: 0.50 stereo: 0

81 [00:00:04.611] Configure Radio 2 Frequency: 0.000, Volume: 0.73 stereo: 0

99 [00:00:04.649] TGPwindow int 1920 1080

66 [00:00:04.730] LoadBkGndFileName send C:\Program Files\Eagle Dynamics\DCS World 121\AriesWings\jet1.snd

66 [00:00:04.804] LoadBkGndFileName send C:\Program Files\Eagle Dynamics\DCS World 121\AriesWings\UH1CockpitNoise.snd

66 [00:00:04.842] LoadBkGndFileName send C:\Program Files\Eagle Dynamics\DCS World 121\AriesWings\A10preStart.snd

11 [00:00:04.881] AC type unknown (0) set

81 [00:00:04.917] Configure Radio 0 Frequency: 130.000, Volume: 0.88 stereo: 30000000

81 [00:00:04.955] Configure Radio 1 Frequency: 250.000, Volume: 0.50 stereo: 30000000

81 [00:00:05.025] Configure Radio 2 Frequency: 30.000, Volume: 0.73 stereo: 30000000

81 [00:00:05.070] Own Unit Name: CAvehicle channels: 30000000

30 [00:00:05.134] Callsign: CA vehicle ID: 1

10 [00:00:05.186] Ownship ID: 1 CAvehicle Model: 999 DLL: 1

10 [00:00:05.225] Changeing to Combined Arms Mode after 8710.310000 seconds

10 [00:00:16.506] DCS in ID 1000803 multiplayer mode: 3

10 [00:00:16.545] first Aircraft ID: 1000803

88 [00:00:16.583] SetCombinedArmsMode 0

11 [00:00:16.617] InitialCtct with AMVI_Chromium Ka-50 tpID: 16779267

81 [00:00:16.656] Configure Radio 0 Frequency: 0.000, Volume: 0.88 stereo: 30000000

81 [00:00:16.695] Configure Radio 1 Frequency: 0.000, Volume: 0.50 stereo: 30000000

81 [00:00:16.740] Configure Radio 2 Frequency: 0.000, Volume: 0.73 stereo: 30000000

66 [00:00:16.817] LoadBkGndFileName send C:\Program Files\Eagle Dynamics\DCS World 121\AriesWings\heli2.snd

66 [00:00:16.901] LoadBkGndFileName send C:\Program Files\Eagle Dynamics\DCS World 121\AriesWings\UH1CockpitNoise.snd

66 [00:00:16.943] LoadBkGndFileName send C:\Program Files\Eagle Dynamics\DCS World 121\AriesWings\UH1preStart.snd

11 [00:00:16.979] AC type Ka-50 (2) set

81 [00:00:17.021] Configure Radio 0 Frequency: 0.000, Volume: 0.88 stereo: 30000000

81 [00:00:17.062] Configure Radio 1 Frequency: 0.000, Volume: 0.50 stereo: 30000000

81 [00:00:17.099] Own Unit Name: Ka-50 channels: 30000000

30 [00:00:17.141] Callsign: AMVI_Chromium ID: 1000803

10 [00:00:17.182] Ownship ID: 1000803 Ka-50 Model: 2 DLL: 1

10 [00:01:16.056] Radio LUA stopped

34 [00:01:16.130] Thread Radar Service terminated normally after 0 ms status: e0000000

34 [00:01:16.175] Thread RadioWatcher terminated normally after 1 ms status: e0000000

99 [00:01:16.262] Positive Thread Hdl in ~HOTKEY

99 [00:01:16.304] ~HOTKEY calling EndThread

e3 [00:01:16.340] Kbd KbdWatcher Thread closed

e3 [00:01:16.388] leaving HotKeyThread

34 [00:01:16.430] Thread HotKeyThread terminated normally after 49 ms status: e0000000

99 [00:01:16.466] ~HOTKEY after EndThread

99 [00:01:16.504] leaving ~HOTKEY

99 [00:01:16.538] Deleted all deviceHandler

34 [00:01:16.575] Thread Supervisor terminated normally after 1 ms status: c0000000

34 [00:01:16.617] Thread ButtonWatch terminated normally after 7 ms status: e0000000

ff [00:01:16.695] Log file closed...

 

 

I run DCS, TS, Configurator as administrator (everyone). Reg entries are ok. Very same setting was working in 1.949

Edited November 13, 2014 by chromium

[towsim]

@Chromium

I am working on it. Will contact you as soon as possible.

[chromium]

Copy: it might be useful to know that I use several controller in my Layout:

 

Saitek Pedals

Custom made panel (read as USB Joystick)

Microsoft FFB2 (x/y cyclic axis)

CH Fighterstick (Cyclic buttons, Throttle)

X-Box 360 Wireless Joystick (Rebuilded Cyclic, Cyclick buttons and view controls)

 

A button from CH Fighterstick is used.

 

What happen is that ARIES Works as intended to ear other voices, while the PTT button only isn't working. I Tried changing the button, but it's the same.

[Home Fries]

Towsim,

 

Just a thought on how you could do fullscreen implementation:

The configurator already allows hotkeys for adjusting frequencies and radio settings, so as long as FS users set some hotkeys all they need is an overlay (not a separate window like you have implemented). I use a Nostromo N52 to swap freqencies, even though I run in windowed mode. Anybody with a Nostromo or Logitech G13 could make this work easily.

 

Perhaps incorporating code like TSOverlay (which pops text on the screen whenever somebody presses PTT) could be used; all you would need is something like the following:

Radio 1: 124.000M
Radio 2: 19     P
Radio 3: 30.00  M

No need for another window, and fullscreen users can still manipulate the frequencies.

 

Just a thought; obviously not worth implementing until DCS 2.0 is out (for DX11).

 

EDIT: Another thought: if somebody could export the freqencies to the LCD on the Logitech G13, fullscreen users could have their cake and eat it too.

Edited November 14, 2014 by Home Fries
Another thought...

[LowLee]

Hi Towsim,

I have some problems:

- the openbeta configurator doesn't work, it replace the ini file from the dcs standalone

- dial buttons doesn't works if I fly an fc3 plane and I select presets frequences

 

Great job towsim! ;)

[towsim]

@Home Fries

Fullscreen would be possible meanwhile, even in the current version. Whereby, it is not fully tested. Former versions simply crashed DCS while the current version remains at least active. If you run DCS on one monitor in fullscreen mode and the Aries panel resides on a second monitor , there would be no difference in usage. The only disadvantage is, that it is impossible to have the Aries Panel on top of the DCS window. It will disappear in the background immediately. So fullscreen with a visible Aries Radio Panel requires an additional monitor which is not integrated in the DCS desktop area. Another case is FC3. FC3 has no controllable cockpit radio boxes. If the external radio panel is not visible, there would be no visual feedback unless you use the small LCD of the G13 or a similar device to display the frequencies. The latter is an interesting idea. I will have a look to it. Mission scripting, integrated in Aries, to display the frequencies in the screen is not an option because it would be too much for a normal user.

[towsim]

@LowLee

just tested this out. The open beta configurator does it's work. Probably you mixed up the icons? The open beta configurator is named AOB while the standalone radio configurator is named ARO. I have to admit, the naming is not that smart.

Even the presets with FC3 seem to work normal. I tested the F15. Changing to preset and incrementing and decrementing channels works normal.

If there is really a bug, please send a more detailed description to support@ariescon.com.

[LowLee]

Thanks towsim! We will try another time and I let you know! ;)

[LowLee]

I tried to open the openbeta configurator (AOB) and this is my last log:

10	[00:00:00.288]	Path C:\Games\Eagle Dynamics\DCS World found in HKEY_CURRENT_USER
ff	[00:00:08.959]	Log file closed...

This is singular because I have the correct path folder in the registry HKEY_CURRENT_USER\Software\Eagle Dynamics\DCS World OpenBeta

 

Each ARD and AOB makes changes only to the ini file in DCS World standalone folder :(

My teammate Pigon has the same problem..

[towsim]

@LowLee

Could you check even HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AriesWings. The protocol entry seem not to be right. If you say standalone folder, do you mean the regular DCS folder or the Aries Radio standalone version?

[Eddie]

towsim,

 

We're having issues with 1.955 where people in the sim running aries can still hear people talking in the channel who are not in the sim (not running aries). Any ideas what the cause could be?

 

Interestingly when running Gossipbox the same problem is not present, it correctly mutes people not running in sim etc.

 

Edit:

 

Looks like something to do with "Eavesdropper". Even when someone doesn't touch the eavesdropper in the TS menu, if anyone else in the channel has/does it seems to affect everyone. Very weird.

Edited November 15, 2014 by Eddie

[Kaiza]

towsim,

 

We're having issues with 1.955 where people in the sim running aries can still hear people talking in the channel who are not in the sim (not running aries). Any ideas what the cause could be?

 

We have the same issue (although have had this in all versions we have tried so far). We also still have the DCS crash on exiting as well.

 

Do you guys have gossipbox working with the lastest version of Airborne Radio? I keep getting a version error when I try to install.

[towsim]

@Eddie

Yes, it is a known bug.It is in the List.

@kaiza

If you have a .crash file from such a session, it would be helpful if you could send it to support@ariescon.com. The Gossip Box for version 1.955 is almost done. It should have been released on Nov. 11th. But we experienced a receiver trouble with uncontrolled white noise.The reason was not found up to now.

[Hansolo]

Noob question @Towsim. I noticed that the Intercom panel selection rotary changes position when selecting a radio on the HOTAS. Is this related to Aries, as I haven't noticed it before.

 

Reason I am asking is that it seem to be working first time after PC startup, start Helios, start TrackIr, start teamspeak, start game, start multiplayer.

 

If for some reason I gets disconnected then upon reconnect the rotary doesn't change position anymore and the Aries radio panel doesn't show selection.

 

The bad part of it is that I can't get it to work unless a complete restart of PC. Simply restart TS and DCS won't do it.

 

Cheers

Hans

[towsim]

@HMA

it was the unfortunate attempt to connect the rotary switch to the radio selection, like in the Huey. I think it is only one way in real life. Means, if you set the rotary switch, a specific radio or intercom is selected for transmission. If you select a radio with HOTAS throttle coolie, the rotary switch should be unaffected. I will change it with the next release. The behavior after reconnect is strange because all variables in the DLL are set to initial values. The rotary switch should be in the empty position (no label) and no radio is selected in the Aries Radio panel. Nevertheless, I will test it out.

[Hansolo]

@Towsim,

 

Thanks a lot for your switch comments. In the mean time I will try and remove the mapping of the selector switch and see if that helps the re-connection.

 

Cheers

Hans

[Schleudi]

If for some reason I gets disconnected then upon reconnect the rotary doesn't change position anymore and the Aries radio panel doesn't show selection.

 

The bad part of it is that I can't get it to work unless a complete restart of PC. Simply restart TS and DCS won't do it.

 

Can you just check your "Export Lua" entries?

 

Make sure, that the line

 

dofile("./AriesWings/AriesRadio.luac")

 

is the first before the TacView entries.

[Snoopy]

@HMA

it was the unfortunate attempt to connect the rotary switch to the radio selection, like in the Huey. I think it is only one way in real life. Means, if you set the rotary switch, a specific radio or intercom is selected for transmission. If you select a radio with HOTAS throttle coolie, the rotary switch should be unaffected. I will change it with the next release. The behavior after reconnect is strange because all variables in the DLL are set to initial values. The rotary switch should be in the empty position (no label) and no radio is selected in the Aries Radio panel. Nevertheless, I will test it out.

 

That's not correct for the A-10C. The rotary should only affect what radio is enabled when pressing MIC-Forward.

 

INT - Provides intercommunications with ground crew or boom operator. If HM (2) is disabled, the MIC switch on the throttle must be depressed to talk to the ground crew or boom operator. If the INT monitor switch is in the enable position, the ground crew or boom operator may call regardless of the position of the rotary selector switch. To answer the ground crew or boom operator, the selector switch must be INT or the HM switch must be in the enable position.

 

FM - Not used for MIC-FWD. Enables aft radio (ARC-210-2 or VHF/FM) receiver audio to be monitored regardless of FM monitor switch position.

 

VHF - Provides microphone input to the VHF/UHF/SATCOM transmitter and permits keying of the transmitter when the mic switch on throttle lever is used.

 

HF - Not Used.

 

Unplacarded - (full counter clockwise position) - Not used for MIC-FWD. Enables tacan receiver audio to be monitored regardless of TCN monitor switch position.

 

In fact, the rotary is normally not touched at all by the pilot and left in the VHF.

 

position.