SickSidewinder9

No, it used to show the location of the emitter and not move with the plane.

Should I not be seeing GPS Time and NTR on, or not on right away, or what? Is this the real start procedure or a bug? It kinda messes up my learned startup flow from left to right.

It seemed a little different at first, but I figured it out after a couple 3 landings. As mentioned, you should be using pitch trim to get on speed and the throttle to regulate descent. The only time I need to use fore/aft stick once I'm on the glide path is with auto throttle.

The Pirouette move is friggin proper now. Also, less fighting with autothrottle when landing. I turn it on when I'm on speed abeam the carrier and it helps all the way through the turn and right to the wires. Some fore/aft stick is needed but it doesn't feel like I'm having to fight it as much as I used to and then floating over the deck. Now, if I could just catch the 3 wire.... >.< LOL, 43,000lbs and splat into the runway. That poor Hornet is now grounded XD

No, I asked you to explain it to me since the change note doesn't really seem to capture it. You seem to lose a lot in translation when I write.

Yes, still doesn't seem to work right. Thought maybe I was missing something. Hmmm.

It's not venting. There is no keybinding for arm/disarm ejection seat as there should be.

So, starting the plane, I don't turn MIDS to on until after alignment and set INS to NAV. I look at the DLINK page in the DED and GPS Time and NTR are still off, Sync is course somehow and the datalink seems to only kinda work. I fiddle with the NTR and GPS time off and on and eventually it shows time and sync FINE and I see more stuff on the DL. Am I doing it wrong?

Hot starting the plane or using autostart puts the ejection arming lever down. It should never be put down until you are on the runway. If I remember correctly, hot started Hornets don't arm the ejection seat and/or it doesn't do it during auto starter. I don't remember exactly because I haven't used autostart in a long time. And it completely ridiculous that after all this time, there's no keybind for it. Yes, I know it can be manually added, but I couldn't seem to get 1 keybind to work for arm/disarm and whenever the game updates it overwrites it. It's long past time to fix stuff like this. It's alt-e on the Hornet do arm/disarm and it needs to be added to the Viper. This, among other things, is what I'm talking about when I say there is a lack of consistency between modules to the point that it's like the teams didn't talk to each other.

What I mean to say is, if you change compass heading, the emitter stays in the same spot on the RWR as though it was moving with you. It used to work normally. At some point it started working wrong, people have mentioned this, and it hasn't been fixed. How did QA not notice this is a problem? How would that even happen? It works correctly showing the priority emitter in the helmet mounted display. It's like the code for this plane is mushy ramen and no one who worked on it talked to anyone who worked on the Hornet. It's long past time to fix the weird inconstancies between the two.

It does seem to run a tad better on a busy server with lots of scripts. I'll have to checkout the new areas. Thanks for adding content.

Been using the CZ button (before today's update). It seems to work?

Is there a reshade setting that works for this? I couldn't find one.

Help with Steam addition please. My multithreading exe seems to be gone. Yes, I did a validate. How do I set the launch options now? No beta updates? MT Preview?

I did. They have not been acknowledged in the forums, AFAIK.

Can you please just get the runway intersection signs the right way around?

I'm even noticing that it's true in the A4 cockpit. I can't set lat/long without zooming in on the number rollers at least a little.

If we ever get an update 0.o

Except TMS doesn't exactly seem to always go back to the steerpoint the first time. I think it just unlocks it from inertial/point tracking mode, but it also seems to move it somewhere sometimes. And the mask warning still doesn't work right at all.

I would appear people can actually hear me on VOIP despite the in-game settings test creating a horrific noise. Once thing I noticed, aside from the fact that people insist on not using it, is that you don't seem to have the option to see who's talking. Or do you? It would be nice if it showed a name in the same place you see the AI subtitles. I guess I'm just used to being able to see it in SRS. That or people need to get used to saying their name first when they broadcast like irl.

I could have sworn I changed the variables in the config as suggested to slow things down. Not sure it did? I used 7 zip to explore the .miz. Moved the relevant file to the desktop, edited it, but it back in the .miz, saved the mission in the editor. Is that not the correct steps? Maye the sectors that are close just resupply quickly? Also got a CTD. Sent the crash log in, but idk if that helps you.

Gotchya, thanks. The skins are great.

For me, the cockpit doesn't get sharper till I zoom in. That's one of the things that makes it so weird and frustrating. The more you zoom in, the sharper it gets. Like the opposite of how you view a Monet painting. Or most pixel based images. There's some kind of resolution or sharpen mask that is missing at the normal cockpit zoom causing all HUD, HMD, MFD, and warning light elements to be a little blurry. This is at 1440p. Single 27" monitor. No reshade. Sharpening built in to the monitor as it has some good post processing itself, but that pretty much all I'm using. Still getting a little ghosting too with DLAA and G sync amd 144hz capable and mabe some adaptive response time. And some low vsync or whatever that is. Adjust HUD, HMD, and warning light brightness helps a little, but it's not sharp enough and there's no additional sharpen mask that helps. I have posted several pictures in these forums. This is true in both the Hornet and Viper cockpits and has been since the debut of 2.9. It's not great.

Try hitting up and down on the waypoint number if it seems stuck. Not really sure I even understand what you're experiencing, I don't think I have the same problem. But I use TMS down on my HOTAS, never the CZ OSB, so it may in fact be glitched.

Wait, distance but not direction? That sounds backwards. A VORTAC frequency should provide direction, and a corresponding frequency and devices should provide distance. Same with ILS. 1 of those freqs is the localizer and 1 is the glideslope. I forget which is which offhand, but the corresponding one should always be the same. Maybe TACAN DME and VOR DME are different, but if the listed frequency is what you're using you should at least get baring (bearing?). It's like using ADF. My bad, I guess I had it backwards. TACAN is only UHF so it can only use the corresponding DME function for civilian VOR. The V in VOR is VHF, and the DME part overlaps with TACAN in the UHF. Now can someone tell me how to guestimate slant range to horizontal? Thanks.