Holton181

WOW! I'm speechless! Thanks for this video! I've could not have done it better myself! (literally, I can't...) Do I have your permission to put it in the first post and the download page?

Might very well be as you say. After all, real life piloting is a completely different world than siming. But I still believe that is what he talked about. Let's see if he comes back to clarify.

The same as the R44 I fly. But I never felt it as pronounced as in-game. I guess we just notice things differently.

If I understand Jan correctly, it is the constant, "circular" oscillation up-down-side-to-side one can observe the nose is doing in forward, stabilized(!) flight (as if the helicopter was pivoted at mass center). Unless a very lightweight helicopter like the R22, one can expect that kind of motion not to be that pronounced as the case in the DCS Huey, both due to mass and directional stabilizers. At least that is my own experience from a rather limited number of flights as passenger in Longranger's and even during my 140h of piloting the R44. But I have never had the honor of being even close to an operational UH1 of any version to actually know. And I'm rather satisfied with the DCS one myself, even if this oscillation feels rather artificial sometimes.

Why don't you activate rudder trim then? For you with only twist grip, the rudder trim would make it feel better, I believe.

Ah, yes. There we have the "radio" tutorial I mentioned ;-) Thanks!

I understand him. The majority of campaigns and single missions, both professionally and community made, are for Caucasus. Very little is made for other maps. And the vast majority of players are mainly SP, not MP, me included (have been confirmed by ED). I quite often regret buying other maps for this reason, not so fun playing self made missions (on basically completely flat terrain, too) where you know everything that is going to happen and where all enemies are (and not much of a point coming up with a good storyline for the same reason).

It comes with some interactive tutorials and they are okay in my opinion. In one tutorial, I believe it is the weapon training but isn't sure, there at leas was a bug previously where you are asked to enter a specific doors gunner position but also to hit the key for the other position. I don't know if it is corrected. I also think the same mission had problems with loadouts in tje early stages of DCS 2.X, not having any door gunners at all, but I think that is corrected. Otherwise just edit the miz file and add them. Also in the radio tutorial there have been reports of a bug where you are supposed to turm a radio ON by clicking a dialer with your mouse. If I remember correctly, the radio is already ON so following tje instructions doesn't make the mission to proceed to the next step. Instead you need to turn the radio OFF with the other mouse button and then turn it ON again. It's been a long time since I went through these tutorials, so I might be quite wrong (memory failure, missions corrected).

It almost feels like a new dawn on helicopters considering resent news. The Gazelle getting some well awaited love, Kiowa announced, the Shark being upgraded, Huey seems to finally get the multi-player multi-crew and recently the BO-105 projects showed to still have some life despise being officially put on hold. I'm generally a realist (i.e. pessimist), but this feels good [emoji106]

As the other guys have said I guess. But to give an additional plausible reason why it doesn't have something similar as the Huey, if my memory serves me well (it not alway do, that bastard!) the Garmin nor the playable gunner position existed when the Mi-8 was released. But then again, the cocpit has a great number of other switches and buttons and dialers to distract you from actually flying...

Adopted for latest OB 2.5.5.38040

Sorry for being out of the loop, but where did you see any updates to this subject? Edit: Disregard!

You will find a way, I'm sure of it! Really looking forward to this [emoji106]

Not necessary, happy to support. Thanks! Thanks for making me aware that I had not changed my sig as I thought I had long ago. I actually had changed it in the "about me" section, but obviously not in my sig. Corrected now. Good to know (would be good to have mentioned in the manual, maybe I just missed it?), but the AC switching is one of the things I experience not working correctly. But this is mainly for more than one device connected. If I have only one phone connected, it seams to work better. Might as well be so. Need to look over my network (actually not me who set it up, it's left "as is" from the people we rent the house from, but I have access to configure it to my liking) Thanks! Had a new look. Started DCS 2.5 OB with the aInstruments display profile but without aInstruments running. No flickering of the mouse pointer. Restarted but now with aInstruments running and with two phones connected. Mouse pointer flickering. Same with only one phone connected. Thanks! Will do. Will do. Thanks!

Hi Colo, I'm having quite some issues with aInstruments. I apologies if this will sound harsh, not my intention. First some suggestion regarding the Viggen: * Pleas add the "Datapanel IN/UT Input / Output Switch" to the android app. Without it the data panel keyboard isn't of much use, since one needs to reach for the PC keyboard/mouse to flip it, and it is used quite frequently. * Would it be possible to replace the non-functional RB-05 stick in the app with the "Mode Selector" (the rotary on the left panel) and have it functional similar to the "Datapanel Rotary"? not a big thing, just a suggestion. Now... I have successfully configured aInstruments and DCS so that I get the exports to a second monitor and my phones. 1) Unfortunately the different settings in aInstrument on the PC that are supposed to alter the app appearance work rather randomly. Sometimes the app changes according to new setting, but most often nothing relay happens. 2) I lose connection very often and it's tedious to get it back, no automatic reconnection functionality. 3) For the Viggen, when having two phones connected with different panels on each, I can't get the radar and the data panel display to work correctly simultaneously. Either the data panel display tuns out correct, but then the radar is frozen. Or the radar is working but the data panel display has wrong scaling and doesn't fit in the frame. 4) My mouse pointer is flickering, making it hard to use (might as well be a DCS issue but figured I mention it here since it papered in relation to configuring aInstruments) 5) Settings for each aircraft isn't remembered. Not between sessions and not between aircraft swishing. Feels a bit tedious to re-do everything every time (especially when testing for bugs...) 6) The app on the phones crash from time to time. 7) A strange issue I don't know if it is due to aInstruments or what, but I mention it her in case someone knows how to handle it: I have three phones, one on Android 5.1.1, another on 6.0.1 and a third on 8.0.0. The two older ones are recognized by aInstruments correctly with correct IP and all. But the third, the one on android 8.0.0, a rooted Sony Xperia X (the other two also rooted), isn't recognized correctly and can not be used with aInstruments. On the phone the app displays the correct IP for it, 192.168.1.228. The router as well. But on the server side on the PC a IP is detected but it is a completely different, 172.20.119.186. The server state it as connected, but the app on the phone is stating "Waiting for Connection". Why on earth does the server get the other, strange IP? I have only tested with the Viggen and Ka-50, the only supported modules I have. Having only one phone connected seems to work slightly better in general. Unfortunately there is too many issues for me to really make any use of aInstruments for the moment. I really hope these things get sorted, I really like the concept. Maybe some of the issues are due to other things not actually related to aInstruments, then I hope someone can help me sort them up on my end as much as possible. My specs below. If you want me to share more information please don't hesitate to ask, most likely I have forgotten something. Tanks.

I had a quick look, and it seems (if I interpret what I read correctly) to support WMS. If we can get access to your map by WMS or similar standard, one can use our favorite maping app on our phone/tablet together with my own DCS add-on "DCS-to-GPS" and have a great moving map for Caucasus, not forced to use real world maps or occupie a big part of the device memory with the downloaded version from Combatflight. I really hope to see this! Good luck!

I have done some investigations on this, and I'm now familiar with what Virtual Airlines and live acars are at least. What I have not found are any protocol description, i.e. how to build the messages to be sent. If you have any NOOB friendly information pleas feel free to share.

So, I finally installed SRS myself just to verify your findings, and sure thing it works! Added the info in OP and download page, crediting you :thumbup:

Same here. I guess the bell47_2_collision.edm is a good one, but the n3d-crush109a.edm still needs updating (it's actually much more resent the one in the link [12/03/17] than the one I had [31/10/12]). I actually had that N3D-crush109a.edm error before, but didn't notice. Thankfully Hawkeye60 is back on it :thumbup: Edit: I saw now that the link you provided was the original upuaut link. He actually has a "to do.txt" file mentioning the damage model. I haven't looked in that folder for a while, happy to see the project is alive.

Thanks [emoji106]

Where did you find that bell47_2_collision.edm? I would like to try it too. I only get the error from that file being wrong version, not for the n3d-crush109a.edm. I doubt n3d-crush109a.edm is even part of the Bell 47? You have any other moded aircrafts?

If you open the dcs.log and search for anything related to this aircraft, you will find an error related to a certain file not loading due to something like "wrong version" or something (sorry, don't remember the file name, but it's not any of the sound files generating errors). It has something to do with damage model. That file, for what I understand, has to be recreated (using up-to-date tools) by however has the original file (in another file format) created by the developer. That will most likely never happen, i.e we will most likely never fly the Bell 47 in DCS 2.5.5 and later (it works in earlier versions). Sorry for a not very detailed answer, but I simply don't remember the details.

Sorry for the delay, but now APX-72 Master Knob key and button assignments are available through this MOD. Redownload from first post.

So, after popular request I finally got some time to figure out the APX-72 Master Knob. Thanks to the link provided by -0303- and of course LeCuvier for the guide, I have now added the APX-72 Master Knob to this MOD (not published yet). I have not figured out how to make it a 2-button rotary (CW/CCW), only separate keys for each setting. I am now waiting to see if we get some update for the OB today to verify it will work for that version, then I hopefully will get the time to release it.

Perfectly fine place to ask. With this MOD you get the flashlight, not supported by default. I have made a flashlight MOD for the Ka-50 too if you are interested, just search for it in the Ka-50 forum.