theIRIEone

This, really caught me off guard.. After having seen all the WPTs laid out nicely in the FAM flight, i went lazy mode and put my pen and paper away just to discover that i probably should have not done so. Also agree on the fact that radio presets should be utilized, and about missing the boat very much... glad NTTR is pretty beautiful itself though.

Block II Rhinos use different screens in which everything green is replaced by white, that includes the ADV-line. Everything Yellow stays Yellow and Red stays Red for obvious reasons. I don't think the "box" should be as prominent as it is in the DCS Hornet, but iirc Wags once said that indeed it was the case irl, so i'm taking his word on this.

You can see your current version number on the lower right side of the main menu (at least in standalone so i guess steam version is similar). You could check that against latest changelog or something i think.

Experienced the same, wondering if bug or intended behavior. Furthermore i had trouble getting the WPTdesignate to work in PP mode, but wouldn't be sure if i did everything correct at this point.

Hello NineLine, it was just a simple solo ground strike training mission i do once in a while. It was either the attached one or a variation of this with only one SAM site and 1 HARM / 3 MAV loaded, so basically the same thing. Most of the times when i fly this, the tanker will not be appearing, restarting sometimes help, and as stated previously, finding the tanker direction / range via TCN and then locking it up with JHMCS (in LHAQ mode) helped as well when i tried. EDIT: The tanker is set up to appear somewhat later, but by the time one took off and performed the strike it's there already for a little while CASE1_2xSA3_Oman_Port_traininig_2.0.miz

Hello and thank you not only for delivering the Hornet strong but also asking for feedback where it's needed. I have a couple of things to report regarding contacts not appearing on radar, so please bare with me: Situation 1 - Solo Ground Strike (HARM, MavF and MK-82 released), hitting up tanker after egress: The tanker never showed on radar, however after being a bit closer i switched ON the JHMCS and was able to lock it up via LHAQ. I switched OFF the JHMCS, blip disappeared but turned up again, stayed on radar until i reached tanker and switched radar off. Situation 2 - BVR training vs 2 SU-33 heads on ca 100nm (solo, airstart): SU-33 never showed up on radar, 29 was clearly visible on RWR / SA page as it should be so i knew where to point. They just locked me up, fired and i never stood a chance, never seen them on radar. I repeat that 4-5 times, then decided to add friendly AWACS. The E-3 lit up the hostiles, they appeared on SA page and shortly after on radar. Situation 3 - Multiplayer Sortie with the squad, loads of planes airborne, "live environment": I had 0 contacts during the whole sortie while squadmates had plenty. From that sortie i have a recording, and include timestamped 2 youtube links. 1st basically has flight member confirming he had 6 contacts (using the same white DDI mod etc) while i had 0 inbound for tanker before ingress. 2nd is confirming radar settings with squadmates and eventually switching off LTWS while reducing the azimuth, which didn't help neither. Thanks again for the time and energy put into this.

Hello, With tomorrow's update in sight i wanna start off by stating that "yes, i do love the new stuff and am still amazed by the speed the Hornet gets more and more features in front of our eyes. I also do realize that by now it is a completely different beast from when it was initially released, and tomorrow should mark another HUGE step into completion - despite still being a long way to go obviously. And i highly appreciate all of that." We receive regular updates on what's next for the Hornet as well, to a degree of transparency rarely shown by any game / sim developers. And here's what's messing with my head for a while: We constantly read about new (and very exciting) stuff, and receive them at a great pace, but there's little info on if / when the missing CPL Autopilot mode would be implemented, or contrast / brightness working for the AMPCD map for example.. I wonder if little things like these will be overlooked / overshadowed by the huge amount of other stuff still coming or if they are still on the roadmap? If so, could we have an update on it's state / planning? Surely looking forward for the next few updates, specially tomorrow and afterwards when the announced "bug fixes" hit - Inlet Ice and TCN Indicator on heading tape disappearing with active CRS select, i'm looking at you :)

180kts after break is totally fine.. I think it's weird but you indeed need to push stick forward to stay level at this time until you're trimmed out for AoA. If you find your aircraft pitching up after the 2nd turn when leveling for final approach, you're too fast, because at that point you should be on AoA and therefor control pitch (altitude) with throttle.

Hello, unfortunately i have to report that after the latest patch my PG and Nevada maps fail to load. While i'm not sure about Nevada since i didn't fly there for a while, i am certain that PG was working just fine prior to the latest patch. Both maps initially failed to load and eventually made DCS crash on 1//60 world preload, an update of my GFX driver made it being stuck and crash on 2//60 world preload now - no kidding! Besides updating the GFX driver, i tried deleting the "saved games/dcs.openbeta" folder and disabling Win 10 TDR by creating a DWORD in the specific registry, all without success.. Since i'm aware that there was (is?) a known bug out there i am hesitant to reinstall the maps. Any ideas? EDIT: updating my gfx drivers again to the latest version solved the issue for me dcs.log-20181124-145053.zip

since forward stick is needed anyways upon dirtying up, imho you can start trimming for AoA right away.. just needs to push stick forward even more for the time it takes to transition into AoA speed.. As others shoot for 11, personally i usually shoot for 8 units STABS UP and go from there..

either VFA-86 CAG (CVW-11 version), or the fictional ones from the virtual squad i'm with... i rarely use anything else tbh

Had noticed a jumping heading indicator (marker on heading tape in HUD) as well last mission, pretty sure we've been flying due North on that occasion as well.. I can post a video (with timestamp) displaying this behaviour if needed, but i assume the existence of this "bug" should be recognized by now.

What tanker is OP using? I find a KC-135 to be considerably harder than a KC-130, with the S-3 being in the middle of the two.. Also what others said: look at a reference point rather than the basket, and take it slow.. Try to be a step or 2 ahead of your airframe.. it's a lot better to be proactive with the slow response of engines especially, but for stick movement likewise.

So when i put the HSI to one of the DDIs, that renders the DDI's day / night mode useless. However, the AMPCD's day / night mode selector influences the DDI in question as long as it displays the HSI..? I doubt that this would be intended behavior but am not 100% sure so i am hesitant to post in the "bugs" subforum.. Short video displaying what i try to describe: EDIT: since i cant get the embedded version to work here's a link:

Sometimes she stays stable, most of the times not at all.. Also slight power adjustments require huge adjustment in pitch trim.. While the plane generally feels great, the trim "issue" makes it feel somewhat broken to me.. Then again, im not a reeal world pilot... If the purpose of trim is not making flight easier to the pilot, what is it used for? you SHOULD be able to trim for level flight, a certain climb rate etc.. non of this is possible in the F-5..

Just Vanu things... nothing to see here :P

Constantly having the exact same issue, also with a X-56. The solution is, as Truthkeeper suggested, setting the deadzones within your Logitech software to any value, save that, then set them back to your value, save again. Works evertime, but is really annoying. Since this is my standard procedure now before entering the cockpit, i also figured that everzy once in a while my set deadzones are deleted again and everything is back to 0. Guess that's another reason to double check settings within that wonky Saitek/Logitech piece of software/hardware...

In today's session, everything was back to normal! Only the updater updated, not DCS itself, but it just worked. Wondering if it was because of heavier winds in the other session or just something wrong when loading the sim or whatever.. I'll make sure to keep an eye on it and keep you posted with a track / recording if it happens again. Thanks.

Before latest update (as of June 14th 2018 ) the Hornet used to auto level the angle of bank back to neutral upon stick release while angle of bank was less than 5 degrees under normal flight conditions. That is, as far as i know, according to real life behavior. Now with the new update it doesn't happen anymore. Is anybody here able to elaborate on that before i rush to the "bugs" section to report something that might have been present on later models (Rhino) only?

Ouch! My bad... thanks a lot!

Selective Jettison is not working at all for me, at least not for centerline tank and pylons (i honestly never tried on the fuselage).. I am completely aware that this is functioning as intended for the majority of the people. As far as procedures go, here's a video of yesterday's flight displaying the behavior with the CTR tank (including F2 view checks to confirm the issue is still persistant for me). Just watch the next 30secs - 1min from timestamp (46:46) and disregard the rest of the video: System is Ryzen 5 1500x @ 3.9, 16GB RAM @ 3066, 1050TI, nvme for OS and regular SATA SSD dedicated to DCS... if you need more info please let me know. EDIT: i don't know how to embed that video here, sorry about that (feel free to let me know and i'll fix it)

more or less similar story here: i ran cmd with dcs_updater.exe update @openbeta.. after the update went through i was greeted by the Caucasus map wallpaper (had Persian Gulf before).. Persian Gulf is not seen in module manager and also wiped off of my SSD's dcs/mods/terrain/ folder.. However i was not asked for a serial number...

When you roll in for the attack, try attacking from the bow / stern of the vessels rather than from the beam if you're not already doing so..

Not yet, i just did a quick check on gfx & sound settings after updating and everything still was set up as i customized it. Therefor i assume all other options/settings must be same as i had it set up in the previous version as well. Will check for double settings when i get home in a few hrs. Thanks! EDIT: Indeed double input, problem with F-5E as described by OP remains - fingers crossed for friday!

Same problem with the F-5E here. On an additional note: SU-25T flies but gives random (and extreme) stick deflections as if there was a ghosting issue or something...