Jump to content

Recommended Posts

  • Replies 1.3k
  • Created
  • Last Reply

Top Posters In This Topic

Posted

Dear Aries users,

the latest official version 1.978 is available for download at:

http://www.ariescon.com/AriesWingsRadio1.987R.zip

Before you install the new version, please read the included document Version1987_ReadMe.pdf carefully. It contains a description of all new functions and a guide, how to install the new version.

The new version supports Nevada and Black Sea. If any trouble comes up, please send a short description to support@ariescon.com.

Have fun…

[sIGPIC][/sIGPIC]

Posted (edited)

so does this latest version supoport all the new features you mentioned in your last status update post. primarily i am wondering is this a standalone system now not needing teamspeak like you were saying?

 

 

*EDIT* ohh i got so excited about you announcing a new release i didnt realize the features i am asking about you said were for version 2.0 and this release isnt quite there yet.

 

So i answered my own question. thanks and really looking forward to 2.0 it will be a game changer for DCS literally. You should after 2.0 release make it donationware at the very minimum as i would certainly pay a reasonable amount for what you described and i dont think i am alone.

 

again thanks for all your hard work looking forward to 2.0

Edited by charlesnett

Charlesnett Callsign - "Fisherman"

Posted

Hello Gents,

 

I cannot get this working. My problems are two-fold. First: When I enter into an online mission and am in the spectator slot. I choose an aircraft and click briefing, then I click fly and Team Speak crashes.

 

Second: Other pilots in TS seem to not be able to hear the non-Aries people when I can.

 

Windows 10 64bit - not sure if that matters

Posted (edited)

Hi all,

 

We (TAW DCS) have been trying out the latest ARIES the past few days, but ran into a few issues.

 

We have 2 guys running Windows 10 x64 where it installs, they can get into SPECTATORS in DCS, but when they choose a slot DCS crashes.

 

One guy has Windows 10 x64 who has no issues.

 

3 guys have Windows 7 x64 and the program is working, but 2 can speak to people who do not have ARIES installed and at the same time speak to other ARIES users in-game.

1 of those guys (me) can not hear or speak to anyone outside of DCS ARIES.

 

Do you have any ideas on what to do or what kind of logs you want to see the issues?

 

Thanks so much for the program, great job so far!

Edited by Dutch Baron
http://www.TAWDCS.org ### JOINT TASK FORCE JTF-88 ### https://tawdcs.org/battalion/88th/ ### PC: i9 - 32Gb RAM - GTX 1080Ti - TM Warthog Stick and Throttle - MFG Crosswind Black - TrackIR5 - Buddy Fox UFC
Posted

@Fury_007 and Dutch_Baron:

Beside that, what Schleudi recommended, if the bug remains, I would need the log files from a crash session:

C:\Program Files\AriesWings\PRCL\ApplicationData\Aries_Session_Protocol.html

Please send it to support@ariescon.com. Even the file AirborneRadioInstaller_log.html would be needed. You find it in the folder where setup.exe was started.

[sIGPIC][/sIGPIC]

Posted
Please check the startup parameters of the DCS server: (all versions)

 

Server Settings -> Advanced -> Resume manual

 

Other settings can cause startup problems.

So "Resume on load" wont work? This setting means that the mission is running constantly.

"Resume manual" means that the mission must be unpaused manually. This will not work with dedicated servers. We can't have admins logging on for each new load of the mission.

Posted

Normally it will work. But we observed sometimes an erratic behavior of Aries Radio. It seems to be an initialization problem. With the “manual” setting you are on the save side…

[sIGPIC][/sIGPIC]

Posted

Feature request:

Currently I'm using for testing purposes with Aries my PCDash2.

I noticed, that the numbers of the frequencies are switching too fast, if I press a button.

2-4 numbers up or down by one strike. :(

 

Though: A delay after reading the input from any device would be nice.

I think 0.1sec would be ok. TIA!

Posted

The software evaluates one mouse click for one number change. Could it be, that your mouse hardware bounces on your left mouse button? To be sure, you should try another mouse device to test the button reaction. If the behavior remains, let me know.

[sIGPIC][/sIGPIC]

Posted

I assumed, that you use a mouse input. With this device even another reason should be checked. The device driver software allows normally to recognize the rising and the falling edge of a signal or only a pulse. In the first case you would receive two signals. The latter case produces only one signal. You are using a foil keypad. This points most likely to hardware bouncing.

[sIGPIC][/sIGPIC]

Posted
You are using a foil keypad. This points most likely to hardware bouncing.

Jep, but as it's only a DX-device I think that the neccessary delay to catch the bouncing can be solved by software. Bouncing can occur with any input device. Sure, with a foil keypad this chance is higher...

Posted
As explained in a post before, TeamSpeak may be used in parallel for meetings, chats and briefings. But it is not required for Aries Radio anymore. If the things are running as planned, it will be Ares Radio V 2.0.

 

That would be a game-changer! <51>SERVER will be 100% supporting this.

51PVO Founding member (DEC2007-)

100KIAP Founding member (DEC2018-)

 

:: Shaman aka [100☭] Shamansky

tail# 44 or 444

[sIGPIC][/sIGPIC] 100KIAP Regiment Early Warning & Control officer

Posted

Hey guys,

 

Still having some issues with Aries (I think), included below is the CRASH log from a few minutes ago. It occurred after choosing a slot and trying to load into the module.

I just played another session before without issues.

 

EDIT: We did try MANUAL ON LOAD on the TAW servers which did not change anything for the people who have trouble constantly when loading in DCS.

 

# -------------- 20160329-095257 --------------

 

# C0000005 ACCESS_VIOLATION at E04D1B75 00:00000000

00000000 00000000 0000:00000000

E04D1B75 0024E7E0 0000:00000000

E04D1F6C 0024E810 0000:00000000

E04E166E 0024E9C0 0000:00000000 luaopen_AriesAirborneRadio()+A21E

E04E191F 0024EA00 0000:00000000 luaopen_AriesAirborneRadio()+A4CF

E04E1A26 0024EA40 0000:00000000 luaopen_AriesAirborneRadio()+A5D6

E04E0D2E 0024EB90 0000:00000000 luaopen_AriesAirborneRadio()+98DE

E04E1091 0024EC70 0000:00000000 luaopen_AriesAirborneRadio()+9C41

E04D603D 0024ED10 0000:00000000

EF167254 0024ED50 0000:00000000 luaD_growstack()+7A4

EF176FB5 0024EED0 0000:00000000 luaS_newlstr()+49C5

EF167541 0024EF00 0000:00000000 luaD_growstack()+A91

EF16684F 0024F080 0000:00000000 lua_getinfo()+11AF

EF16785E 0024F0C0 0000:00000000 lua_yield()+9E

EF162440 0024F110 0000:00000000 lua_pcall()+60

EDA75761 0024F170 0000:00000000 ?call_func@Config@Lua@@AEAA_NPEBDPEAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@ed@@@std@@HH@Z()+E1

3F4ED198 0024F1D0 0000:00000000

3F4C7EE2 0024F240 0000:00000000

3F4CC9C5 0024F2A0 0000:00000000

3F4E2634 0024F2D0 0000:00000000

3F4E2584 0024F300 0000:00000000

3F5874FC 0024F9B0 0000:00000000

3F58AB55 0024F9F0 0000:00000000

76C859ED 0024FA20 0000:00000000 BaseThreadInitThunk()+D

76EBB371 0024FA70 0000:00000000 RtlUserThreadStart()+21

 

Is this enough info, or do you also need the other log file?

 

W7 x64

http://www.TAWDCS.org ### JOINT TASK FORCE JTF-88 ### https://tawdcs.org/battalion/88th/ ### PC: i9 - 32Gb RAM - GTX 1080Ti - TM Warthog Stick and Throttle - MFG Crosswind Black - TrackIR5 - Buddy Fox UFC
Posted

The Aries log file would be for interest. You find it at C:\Program Files\AriesWings\PRCL\ApplicationData. Have a look to the time to find the right log file. Send the file to support@ariescon.com. On the first sight it seems to be an initialization issue if a second mission was started out of the same session. The Aries log file will hopefully show the moment when the crash occurred.

[sIGPIC][/sIGPIC]

Posted

@Dutch Baron

Thank you for the log file. Unfortunately, it shows the version 1.986 instead the latest version 1.987. Since the GameGUI.dll is involved in the protocol, which was not the case in version 1.986, I assume a version mix up in your Aries Radio installation. I would recommend to uninstall your current Aries Radio and do a clean install of the latest version 1.987. It is even wired, that you have a protocol file at all. Because you started a single player mission without TeamSpeak. TeamSpeak is responsible to start the protocol software. It seems, that you started the protocol application manually (very smart). Let me know whether it worked with a new installation.

[sIGPIC][/sIGPIC]

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...