HILOK

is there a difference in the effect as compared to doing this using the FOV ZOOM keybinds? thanks

yes, currently exclusively F18

yep, same here. thought it had to do with dcs 2.7. let's hope the next vaicom update resolves this.

i have that happening occasionally. usually fast repair solves it (non-steam ed.)

hi @Rudel_chw thanks a lot for putting this little guide together -very helpful do you know, if it's possible to get the version numbering and description in ovgme without zipping the folders? thanks

uuuh man! at this point i would recommend asking the support...

that's not too bad either, is it?

good to know! someone here once pointed out that 197 is the equivalent to 12kt, but i can't find it anymore...yes, "turbulence 50" feels more like 8-12kt, so it doesn't quite end up, but i thought that could also partly be due the FM/balooning effect ok, reading your posts i was getting the impression you had some RL hornet experience, but that's ok, thanks for your insider info, and also for clearing that up

...strange, have a look here: https://www.digitalcombatsimulator.com/en/support/faq/repair/ otherwise i dont know

so no helping the nose for you in DCS, but RL is another story? i was under the impression the max value of 199 equals 12kt...but yes you have to work harder at a setting of 50 -why i was asking i think harder conditions really put the FM/engine model to the test.

not at all you can use the win search bar or look into your dcs launch folder. there should be a shortcut called DCS REPAIR. then you have several options. i'd recommend the FAST option first. dont think i ever needed the other ones... let me know, if it works.

@Stearmandriver thanks for the clarification. oh no, the mighty boeing!! -how could i didn't mean to offend you

thanks! two more questions, if you dont mind: in DCS, once you are trimmed for proper AOA, do you completely refrain from touching the pitch axis at all? and, have you tried night landings with turbulence factor set to 50 in the ME? -should equate gusts of 3kt, which is not much really. i would be interested in your judgement about how the DCS hornet FM compares to the real one in that case. that may just be due to the fact that currently it's one of the most popular modules.

i very much appreciate your knowledgeable inputs in this forum. and if the hornet FM/engine model are proven to be spot on, i'll rest my case, and accept that i am the issue. could be that the problem is just the missing butt-feeling that in RL would immediately tell you how much power to apply without overcorrecting. did you have a look at the facts presented in that engine spool time thread? i would be highly interested in your feedback about those. thanks

i agree on most of your statements, but you lost me a bit on those two ...yes, but only in mode CLIMB/IDLE DESCEND as far as i know. in ALT/VNAV/APCH mode FD commands keep the aircraft on altitude/glide path, and power controls SPD...i was under the impression this thread centers around power approach. ...you are probably referring to the airbus BUSS. but tbh outside of that i never heard of applying AOA/PA techniques on a commercial jet. especially during manual approach, where glide path is usually kept with pitch, and SPD controlled using power, as opposed to PA: keeping SPD using pitch, controlling glide using power. i dont think both techniques mix up well, it's either or, and it depends on aircraft design/instrumentation, as far as my understanding goes.

have you tried repair? i had the jhmcs disappearing occasionally (before 2.7) -fast repair always brought it back

personally i've always loved the ka50 for what it is, and i just wish ED could get long standing bugs and incomplete systems finally fixed. if that comes with a nice facelift and means i have to contribute a small upgrade price, that's fine. and:

thanks. if i understand correctly, you mean the player has to move his jet (even just a bit) before any other flight spawns, right? -at least that seems to work for me, but i only got to test it once so far...

here's what seems to be a workaround: [EDIT] make sure any other flights spawn on the deck after you first move your aircraft, even if it's just a few inches. unfortunately, you'll still have to make sure to hook up before other flights from your own package spawn on the deck, e.g. escort etc. for hornet cold starts, i set all other AI flights to spawn minimum 20 min after mission start. seems to work consistently so far. in liberation it's quite easy to do, if you look for the "in <time>" indication in the flights frame. in this example, flights are departing from incirlik, but you get the idea...

absolutely agree with this. still i think the reason for throttle overcorrection comes from incorrect engine spool times, as stated here:

recently, i am experiencing exactly the same behavior on liberation 2.5 & DCS 2.7. before everything worked flawlessly. there seems to be a connection to delayed flights, not sure though. anyone found a solution yet? would be highly appreciated EDIT: i am not getting a "flight delayed" message per se, but i do set my TOT 5min past the ASAP suggestion in the liberation GUI. "request launch", and also "req. startup" + "req. taxi" do not solve the issue.

thanks

what you guys did is just amazing! can i donate somehow without going through patreon? i prefer paypal, thanks

thanks! how do flight members know whether its PRI or AUX?

@Codguy thanks! a couple more questions, if you dont mind is there a special term for com-1 & com-2? what would the correct intraflight phraseology be for "switch to preset x-y"? thanks