HILOK

happy to hear it's still on ED's list

yeah, i got exactly the same reply after getting in touch with the support. i find it disappointing that they dont offer better after sales... anyway thanks @CrashMeTwice for sharing the fix with us

the issue with this "logic" is that low visibility scenarios, where wind typically is around 3kt, will force tailwind landings for no apparent reason

hi @Comrade Doge fantasic job! thank you so much!! would you consider adding VFR flight plan capability to your already outstanding tool? -this would be extremely useful for a/c without RNAV capability, such as the huey, tiger etc and probably all WW2 era planes. a simple flight plan could maybe be displayed on your app (or be injected to the kneeboard, dunno) and look like this: WP HDG TRK DIST ETE #1 335 297 12 6 essential data being (wind corrected) magnetic heading and estimated time enroute. magnetic track and leg distance are for info only. basic workflow would go about like this: 1)user picks WPs on F10 map as usual 2)user entry required: IAS and cruising ALT 3)TAS can be derivated from IAS and ALT 4)wind corrected HDG and GS determined by current wind dir*/speed 5)ETE per leg results from GS *wind direction and track need to be magnetic (magn.variation varies, and can be retrieved using the magvar class -thanks @Chump). please let me know, in case you're interested and if i can be of any assistance. thanks

i see...sounds cumbersome. i would expect, it could pay off anyway?

hi everyone, is there a specific term in the US/UK military for the document, where maintenance lists current defects of a specific aircraft, so that amongst others flight crews can review what to expect on the aircraft allocated to them? i am not talking about the tech log onboard the aircraft. in civil aviation that document would be called f.ex. "hold item list" or "a/c status report". as not every defect puts the a/c AOG (according to the MEL), that list is usually part of the briefing, and might impact preflight decision making. i am looking for the specific term used in the USAF / NAVY / RAF. could be that things are done completely differently in the military...anyway, thanks for any help

qnh scale shows 3100 between 2999 and 3000 on the copilot's altimeter. both ways. track attached uh1-copilot-qnh-setting 2.trk

@Tim_Fragmagnet yes, i think you already mentioned that somewhere. i am very glad you have the understanding and time to dig deeper into what's wrong and how this could be solved. thanks so much for doing this! i'm just thinking, on the other hand, if the autopilot would just follow the heading bug, it would still do a better job despite the FM quirks. and it would be more useful as you could navigate with AP engaged. for info:

correct, and if you do, you can observe the pressure dropping on the hyd press indicator (below radalt). i on the other hand never bothered to verify, if as an effect the stabilators would drop...

i was gonna ask for the same @Bergison as you know, i very much appreciate all your great contributions to the community (incl. the g-seat ; ) is there any chance your moving map code could be ported to ios without too much hassle?

oh, ok, then it must be the ancient ios version i have running

happy to help some parameters can be adjusted to your needs. i recommend a mod manager to install it

just 5 min ago, it came to my mind -works! thanks on my admittedly old 'air 2', some of the background images are cut off, or don't fill the screen in portrait mode. is there anything that could be done here?

in case you guys weren't aware, @Chump did a great job at improving awacs and wingman calls (based on davidp57's initial mod). it can be found here: https://github.com/chump29/DCS_Mod

to reproduce: - open ME and choose any stock quick mission on marianas (tested with huey, hornet, viper) - note which airfields are blue and neutral - start mission, F10 map, look again

it isnt. currently only affects G/S on ILS frq

exactly. i put that on the wishlist.

autopilot mode "level flight" should follow the current heading bug as in a typical AP HDG HOLD mode. when the bug is placed to a new heading, the autopilot should turn towards it. think of it as the player handing over controls to the copilot in order to work on other tasks. as this is a multicrew aircraft, i think this would be a reasonable feature request. note: if this is implemented, please do not reverse the turn, when the heading bug passes the aircraft's current reciprocal heading. this is what some autopilots would typically do, but a simulated "human" should be smarter.

totally agree with this, and would even go as far as saying, the copilot should also be able to turn and follow new headings, whenever the player adjusts the heading bug

please : )

would you consider changing the background color and also that of the frames (top, bottom) to black?

this is actually quite interesting. thanks for pointing it out! i wonder if the ballistics of the weapons match the aiming sights indication nonetheless? haven't seen any complaints about the aiming accuracy. personally not shooting much with the huey...

i can confirm the animation of the china hat inside the cockpit is swapped around.

well, thank YOU then

maybe another benefit of getting this right would be proper simulation of the effects of inflight hydraulics failure