Nero.ger

i made the same transition, got the UH first and then the BS. in my optionen they are worlds apart, flying wise. UH1 is more muscle memory while the BS feels like a discussion with the Autopilot and trim system about the flight direction. i do not own the MI8 but coming from the UH1 you will have to relearn how to handle a Helo + all the electronic gizmos. But still i would recommend the BS in your case, simply because the MI is similar in role to the UH1 and the BS will give you a complete new expierience. Also, go ony youtube and watch some videos to get a an idea what the bird is about

regarding yellow line: you can draw lines and markers on the Abrismap, so this will be something drawn by the mission developer. maybe there is something written in the brifing explayining what it i the shading is a threat area, yes. BUUUUT: red is good, blue is the enemy. ;) and if there is a legend it must be somewhere in the manual

----Full Mod ---- Alpha release! so finaly there is an Alpha version of this mod. Since its my first mod to be released my hands are sweaty as hell i decided to release it even without the full manual because i have difficulty writing it because ...english is not my strong language. anyway, be aware that its alpha and you have to figure out stuff yourself for now (more or less ) Google Drive linke below General question, post here Bug reports, please send a PM to keep thread clean and yes it passes integrity check :) https://drive.google.com/drive/folders/0B0WafwTWChLITC1iQ3Z3eXZ6eHM?usp=sharing since it replaces many files make sure you make a backup of your ka-50 folder. install: unpack the zip file to 'C:\DCS\Mods\aircraft\Ka-50\' uninstall: hopefully you made a backup.... how to use: still working on the manual, but short version: Bind the new keys to your Cougar (Controlls/MDF) Buttonlayout: 11 12 13 14 15 1 6 2 7 3 8 4 9 5 10 16 17 18 19 20 some buttons have a Short press function and a "hold for more than 1 sec"- function(in both cases the function will be called when you release the button) known issues the lcd monitor does not react to lighting conditions no clickability, you have to use the 20 key bindings if you find a bug, pls send a PM, its easyier to keep the thread clean. General questions belong in the Thread, course they might interest others

how did you find out how to use this, or find it in the first place. I am too trying to find out how the functions of the cockpit but its harder than splitting an atom :) (or i am just to stupid)

but....i did....:(:( or did you clear that part from your memory ;)

some good news befor we all go into Xmas: So far everything works fine with "integrity check" and "MP" :)

i think i should not write at 2 am in the morning, what i wanted to say was that the Horizon line is never correct because i was to lazy to adjust for altitude :) anyway, its been fixed, but it needs an additional parameter, so it will only work in the "full-release". if you want to rise the line a bit so its at least closer to the horizon, search the HUD_NAV_COMMON_page.lua for pitch_horizon_line.init_pos =and preplace the stuff after "=" with {0.0,(-pitch_K * math.rad(0.1)/GetScale())+0.0,0}

the horizonline is never exact because depending on your altitude, your view is slightly different. It was one of the first things i made so maybe its time to revisit it with my increased knowledge now. I never realized that it might block the Range, will check it :)

Flight vector tells you were you crash into the ground, vertical velocity tells you only when ;) anyway its implemented and was one of the easyier things

it may be hard to see but the sideslip is allready displayed. its the Small diamond that moves horizontaly. I never thought that the AoA would give usefull data for a helo, will look into it :) edit: the sideslip marker is not in the released HUD mod because it needs an additional param,but you can see it in the videos updated 1st post with feature list

you could try "outsorce" the declare_kneeboard_device.lua and init.lua to the ka50s cockpit script folder changing the device_init.lua dofile(LockOn_Options.common_script_path.."KNEEBOARD/declare_kneeboard_device.lua") to somthing like dofile(LockOn_Options.script_path.."KNEEBOARD/declare_kneeboard_device.lua") of course copy both files in the folder mods/ka-50/cockpit/scripts/KNEEBOARD also you must edit the appropriate line in your copied init.lua. did not tryed it myself(!!), but i thought i share the idea that popped into my head while reading this :) be carefull tho because you can royaly **** up your ka50 (backups are your friend)

thx for the info :)

your wellcome, i was a little scared it will not work cause its my first mod-package :)

the 'HUD mod' gave me the green Shield :)

i think there are some things which cannot be balanced. Player count and Player skill beeing the worst offenders here :) on the subject of su25 and Mig21's,f5's...its like bringing a knife to a gunfight, and you are actualy hurting your team by selecting a sub-par Aircraft, unless you are a God in it. and...Zhen...its kinda creepy knowing that you were watching me..... :-D

ok a little sneak preview, since the MDF will still take a while to complete: the HUD System itself as a little MOD so its not all pictures and nothing to try out :) https://www.digitalcombatsimulator.com/en/files/2253758/ as allways, backup your files bevor because this is still beta or alpha.....;)

well, in staying true to the Ka50 in "systems not talking to each other" :-D i am not accassing most of the data by aditional functions. Most of the stuff is grabbed from the cockpit itself. Saving a NAVTGT for example is done by actualy pressing the right buttons at the right time and than looking at the coords on the PVI display :). I hope that, by doing it this way, that the mod will be Integrity check Friendly.Which we will find out soon because i am about to port it to the actual version of DCS (was using an older one for several weeks) so to get back to the DataLink. It might be easier to use but its still limited to its the original function and drawbacks(that TGT 1 might not be TGT 1 om your Wingmens ABRIS for example)

the texts are part of the Shkval-viewport, so they will be exportet to another screen. i am not sure how helios handles the inputs back to DCS, but there are 20 new Keys, so you should be able to link them to helios right? and thanks everyone for the words of encouragment so far :)

using coords from Jtac to mark target and kill it :) btw, if someone know how to acces "coord.MGRStoLL(table MGRS)" in the Cockpit enviroment let me know. until then, no MGRS :)

showcasing lowlight capabilities of the TV-System:

thats actualy not an easy question to answer, because the original ka50 comes without an MFD for example, so that alone would be something it does not originaly have. The Ka52 was more of an inspiration to start this mod, not an "aim" to implement its systems (i have no idea whats in it anyway). Nightvision for the Shkval for example, one Model of the Ka50 has it as far as i know, so technicly it would be a reasonably upgrade. And thats my idea, reasonably upgrades to the avionics, like the modern MFD replacing the old Shkval TV instead of just adding features for "MOA POWER". depending on how things work (and how carried away i get with typing code ;) )out with integrity check,i might split it into 2 versions, one for MP and one for SP

+1 for this idea :)

to be honest i did not tried it yet. Since it just presents information that is allready available in the Module, i dont see a problem with Integrity. But i aim for "passing integrity check".

ok i managed to make my first youtube video ever :music_whistling: just a quick show how you can create NAV Targets, cylce throu them and display them in abris/Shkval/Hud using the MFD

very nice, also interested in the final product. But more because i want to see how you code it :)