Jump to content

Nero.ger

Members
  • Posts

    838
  • Joined

  • Last visited

Everything posted by Nero.ger

  1. some good news befor we all go into Xmas: So far everything works fine with "integrity check" and "MP" :)
  2. 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}
  3. 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 :)
  4. 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
  5. 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
  6. 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)
  7. thx for the info :)
  8. your wellcome, i was a little scared it will not work cause its my first mod-package :)
  9. the 'HUD mod' gave me the green Shield :)
  10. 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
  11. 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.....;)
  12. 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)
  13. 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 :)
  14. 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 :)
  15. showcasing lowlight capabilities of the TV-System:
  16. 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
  17. 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".
  18. 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
  19. very nice, also interested in the final product. But more because i want to see how you code it :)
  20. A little update, hopefully i can get a video going the next days to better show the functionality. MFD buttons on the right side are linked to the NAVTGTs of the PVI. you can switch throu them and save them with just one click (TGT MEM) or recall them into the Abris/shkval so you can slew you shkval to the TGT. The small BOX in the HUD shows the position of the NAVTGT, like in the A10c. Also the MFD tells you what to to when you want to save a point for example. like "Lock target" "uncage shkval" etc. The HUD is obviously clean up, and it does not change much when switching modes, so you dont loose important information. The big line represents the horizon like in the M2000 and the little arrows left and right of the CenterMarker move up and down with your Vertical Velcocity.
  21. if you ask if they will be clickable, maybe. but there will be 20 new Keys in the controlls so you can bind them to the thrustmaster Cougar Panels for example. and yes those will do something, like in the a10 mfds :)
  22. mod has been removed because its no longer maintained and caused problems in newer DCS versions. Also it included modified LUA-files from ED and sharing those is no longer allowed --last update:19.01.2017--BETA What is this MOD all about: well i think we can all agree that the Ka50's Cockpit systems are a bit outdated by now compared to the A10's for example. So i decided to give it an overhaul but stay true to realism. I looked at pictures from the different Prototypes and also of the Ka52's Cockpit and decided that replacing the TV-Screen with a modern MFD display would be a realistic option. The idea was to control most of the systems by the MFD and its 20 Buttons, so instead of remembering what you mapped to your 'Cougars' you actualy can see it on the screen. this MOD does not replicate an actual model of the Ka50, instead its a modernized version of our model how i see it (and how i was able to code it) The change of the HUD was more a medical necessity, because the old pitch-ladder always made me nauseating after 30minutes :) so in a nutshell, the only 'real new thing' is the ability to display a terrain-point in your HUD everything else is just another way to deal with the Ka50 current systems. UPDATELOG: 30.12.2016 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 31.12.2016 Manuel uploaded 01.01.2017 Manuel updated (some functions were missing) 06.01.2017 feature update (but no new release version yet, still some bugs to fix) https://forums.eagle.ru/showpost.php?p=3008127&postcount=64 07.01.2017 new release. now considered BETA now and feature complete :) DL link below. If you installed it and it "worked/did not work" pls send me a quick PM, even if you hate the mod and deinstalled it seconds later :) a tutorial/explenation video will follow (hopefully this evening). 08.01.2017 Hotfix: default.lua for joystick was missing so you could not bind anything other than keyboard keys. the beta version from 08.01.2017 allready has this fix included. 09.01.2017 Hotfix: bug in HUD only view 15.01.2017 using the "Scales reject"-function of the ka50 to hide FPM and Horizonline to clean up hud. MFD box was remove and Shkval is now back at its original place. 19.01.2017 there is now a "HUD Only" version available that leaves the Shkval completly original. Of course any function releated to the new MFC-Shkval are not available. Feature List (stuff will be added as i implement it) -HUD *overall cleaned/decluttered to improve overall readability (removed most of the Scales, moved Shkval off-hud-indicator to bottom) *added Horizonline and larger pitchladder and VVindicator Flight Vector Marker ability to display "Point of Interest", this can be a Location, NAVTGT or Abrismarker -Shkval modern LCD replaced the TV. removed "light-bleeding" into the HUD with nightvision 20 new buttons to control the MFD and its function -MFD Functions easier use of NAVTGT and DATALINK Display locations/Coords as Markers on the HUD Coords can be directly entered (JTAC), copyed from abris or from PVI ability to determin if you have LOS to a Marker/point Database with Missiondate and Custom textpages (set by player or mission designer) ---- [b][u][size=4]----Full Mod ---- BETA release![/size][/u][/b] --FULL MOD version:15.01.2017-- --HUD Only version: 19.01.2017-- since it replaces many files make sure you make a backup of your ka-50 folder. Manual will also be in the Download-link.(still a bit lacking and outdated ...sorry) [u]install:[/u] unpack the zip file to 'C:\DCS\Mods\aircraft\Ka-50\' [u] uninstall:[/u] hopefully you made a backup.... [u]UPDATE from Alphaversion(31.12.2017): [/u]best way would be to copy the original files back or run a repair of your DCS installation because some files that had change previosly are no longer included in the MOD because of changes in the file structure. most important would be the Fonts.lua in your scripts folder. if you see strange letters or "(NULL)" everywhere, chances are you are not using the original Fonts.lua (copy from backup or repair DCS) [u] how to use:[/u] still working on the manual, but short version: Bind the new keys to your Cougar (Controlls/MDF) Buttonlayout: [code] 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 Thanks to every other modder out there (yes i looked throu your stuff and learned) and everyone who documented something, no matter how small :) mod responsible - make Backups!
  23. you sure you not refering to the r27E version missing?
  24. ok so its not just my SRS coughing up
×
×
  • Create New...