Jump to content

HILOK

Members
  • Posts

    493
  • Joined

  • Last visited

Everything posted by HILOK

  1. thanks, great news! will this also be released on github? or has discord become the main distribution platform now?
  2. hi max, thank you to clarify: is this only for people having issues with VCP after updating DCS to 2.8? i am still on 2.7 (latest) without any VCP issues. do you think i can just replace the DLLs and then update DCS (skip repair)? thanks
  3. yes, nice throttle they built. no issues with WW orion throttle and TM warthog stick/base on my side. you might not be able to use some fancy programming functions (across throttle and stick), dunno, cause i am not using those, but even those things (and much more) would be doable using joystick gremlin...
  4. https://tenor.com/view/leia-youre-my-only-hope-star-wars-gif-14502241 thanks so much i was holding back 2.8 just to keep vaicom going!
  5. are you guys using the new jetseat from andre or the older "gametrix" version ?
  6. had this happening some days ago (dcs 2.7). i think this is a new issue. ctrl+alt+c is supposed to open VCP's dialog window.
  7. i think everybody would be happy, if we could just save a user defined cockpit state as "cold and dark" for every aircraft
  8. nice one! thanks for the heads up
  9. confirm copilot firing constantly 'till out of ammo
  10. on the long term, yes. but for now i think we have to go "baby steps" or nothing
  11. now that we already have that nice 'METEO' wind direction feature in the briefing screen, would it be possible to round those direction numbers to 10 degress and add the windspeed in knots? something like that maybe: At GRND 4 m/s, 236° | Meteo 240° at 8kt this would be in line with western notation, so hopefully everybody should be happy
  12. some get the hang of it some dont, being due to lack of proper hardware (unprecise joysticks, bad framerates) or any other reasons. in a world that tries to be more inclusive, i dont see why some people would feel so bothered by an option to simplify AAR. even, if this is a high end simulation, after all it's just a game
  13. you can add vipergear to your list https://vipergear.eu/product-development-page/
  14. very impressive, guys! to anyone who finished his diy ffb base: what do you estimate were the total material cost? thanks
  15. this is reaaally goood ! thanks
  16. HILOK

    Huey wish list

    please working chrono*, working wipers (actually removing rain), and most importantly: instead of toggles, distinctive control/keybinds for autopilot functions, ROE and such; this would allow for better implementation of voice control
  17. +1 being able to communicate to ATC/AI using voice is such an important part of the whole experience. @Hollywood_315 has proven with VAICOM how well this can already be implemented in DCS, and for me it kills the immersion not being able to do this.
  18. one can only hope @Hollywood_315 is doing ok, and nothing too serious happened. to me he always seemed like a fine person in the past, and i am sure there must be good reasons for his absence. for me the added value of VAICOM is about on the same level as track-ir. being able to pass a message by pressing a PTT and speaking as it's supposed to be is just fantastic, and without it an important part of the experience is missing. as we dont know if or when the new ATC system will be implemented, i just hope that in the meantime the code could be picked up by someone else, or he is considering making it opensource. personally i wouldn't mind the few $ i "invested" -he definitely earned it !
  19. not yet, i am still hoping for a fix from WW : )
  20. thanks for your reply @Brother_Leb ! to answer your question, the preset labels bother me on my V1 base. so being able to replace them on V2 is actually an added value to me, when considering an upgrade. whish they had considered adjusting the position of the hornet throttle grips, though (should be tilted a bit CCW for ergonomics). anyway thanks
  21. quick question to those who got their unit already: are the new "panels" on the base removable? thanks
  22. "Lateral stick displacement greater than 0.5 inch causes the autopilot to decouple from the steering mode" i suppose that would also apply to lateral A/P engagement tolerance. i.e. above 0.5" lateral modes won't engage. although this doesn't necessarily transfers to longitudinal modes, it may be a hint to the general ballpark we're looking for.
  23. or maybe just hardcode a tolerance of 5% stick action. from my personal experience, i doubt that the A/P engagement criteria are set so tight in the real thing anyway
  24. just wanted to add the following experience i made on my end: NOT able to engage AP CPL nor getting tadpole at 6nm, when altering an existing mission (stock or user) by adding L4 and ACLS. seems to be related to changing an existing mission, because after setting up a brand new one, everything worked as expected.
  25. @Beamscanner thanks! what's the vertical axis in the graphs, the degree of clutter?
×
×
  • Create New...