Mr. White

Poor moderation with simply closing your thread over there. Those 2 modules need an update since v2. You can use HDR instead of the anyway over-saturated DF. Yes, you'll loose a lot of the nice scenery effects etc, but at least you can use those 2 modules again ... Well, "meanwhile". Whatever that means in this case.

+1

+1

Thanks for sharing. Great stuff!

Thx for your test-mission, sgtmike. Unfortunately I am not able to transform that into the great TOOTALL mission with all its triggers. http://www.digitalcombatsimulator.com/en/files/431053/ I'm interested in the SAR PLB part of the mission where you have to localize a squad in the mountains through Mi-8 ARC-UD radio. After picking them up another team spawns and starts sending the radio signal again. I don't know how to put your solution into this system. Thx for any advices.

Thx sgtmike, didn't know this bug still exists. I'll switch to the other thread.

I'll use this thread, since I don't know what really causes the problem. I am hosting the mission and for me everything is working flawlessly. But the clients do not receive any signals on their radios, except the standard NDBs. In singleplayer though, they receive all the signals. Does anyone have the same issue or maybe an idea what's wrong? We are using the Mi-8 here.

Some like to simply "fly modules" and jump into a new cockpit every now and then (and I'm not meaning to categorize you there). The time between 2 releases is called "waiting". Others are looking for in-depth quality simulations and for real life procedures in every aspect of flight. The time between 2 finalized releases could be called "enjoying / studying", but the time between bugfixes / system-development when dealing with an unfinished module is called "waiting / frustration" as well. Totally different approaches here. "Better then nothing"-philosophy does not apply to everyone.

This sounds very interesting. Will give it a try soon. Thank you for your contribution.

If Belsimtek would only react to the bugs posted in the support forums to begin with.

Thx a lot, Esac_mirmidon. Works perfectly well. No hickups yet.

Is there a chance to get an info on what files have been updated incl addons? Unfortunately with every update there are new bugs and it's frustrating to wait until they have been fixed and released. You wait for a fix until you wait for the next one. It could lead to users fixing some minor bugs themselves in the meantime.

After endless tests and reinstallations of ARS and TS, we finally got rid of the TS crash. I can say that mainly the hint from Chichco lead to the solution: start everything as admin. Well, it's here right under your nose and you just can't see it, can you? Thx for your support everybody. We are only running into the spam-blocker-feature on our TS server, but from what I read we only have to adjust the options and we should be fine.

Alright, let's sit and wait then. Thx again.

Thx a lot, Alexandr! That answers a lot of questions. I tried every scenario you explained and it worked perfectly well. Now that I understand that because of incorrect implementation in the sim the batteries are getting charged by the AI-9 GEN, I can deal with the problem. Do you know if the development of the electrical system is still going on? Ground operation and preparation is more then half of a successful flight as you will know. It reminds me a lot of the time in the good old Project Tupolev's brilliant TU-154m in FS9 and it's electrical system, where you had to take care not to overload the APU GEN, while testing autopilot systems etc. It has its charm for sure.

I meant the green light on the Aries radio panel, but as both lights (Aries panel + TS) are illuminating simultaneously when there is an incoming voice package, I guess it's not relevant. Just wanted to clarify that. Other then that, I have done what you've said more then just once. I disabled all the buttons and pushed "send". But I will give it a try again, just to be 100% sure, that no one was accidentally transmitting while me operating in the options menu or anything. Ok, the fact that the old configuration apprears after restart is not an indicator of something being wrong - that rules another thing out. What about the fact, that my TS client crashes (although being disconnected) only after I start the Gossip Box? Does that lead to any other conclusion maybe?

You can disable Aries manually in the Export.lua file or you can use the Aries-menu in TeamSpeak (Plugins/Aries Radio/Export.lua entry on/off). You can further more generally disable the plugin in TeamSpeak.

Win7pro 64bit TS 3.0.16 Aries has been installed with administrator rights. TS crashes (with its internal error message and the link to the dmp-file) ... 1. ... as soon as I receive a transmission. The transmission-light goes on and TS crashes. 2. ... when I simply open the AriesGossipBox.exe (DCS not started and the TS client not even connected). In Eavesdropper mode TS does not crash. My buddy uses the same TS version and can hear me without his TS crashing, so it's definitely a local problem. I'm only running out of ideas what to try next. Thx again for your help.

Unfortunately it did not solve the problem. As soon as I recieve a transmission, the light goes on and TS quits. I have a dmp-file, if that is any help. I unpushed all the buttons (not just Horizon) too, but no luck. The options in the "Game Master" were reset after I restarted TS, if that makes any sense.

Thx a lot for the quick response. I will give it a try and report back soon.

Thanks for this nice piece of software and the great support.

We were giving Aries Radio System a try the first time using the latest TS client and unfortunately the TS client crashed as soon as I got a transmission on one of the radios. Eavesdropper mode worked well though. Any ideas?

Only went through the first 2 missions and I have to say that the atmosphere is incredible. I can only imagine the amount of effort it required. Thanks for your contribution. Cheers!

Confirm.

Yes, as described here as well: http://forums.eagle.ru/showthread.php?p=2334314#post2334314 The APU fails after its generator being used for ~ 30 seconds. That's the main problem. The autostart message confirms that the APU is "kaputt".