Stubbies2003

Yeah have tried the request launch bit as well when spawning on a cat. No dice. I think the trigger spot is right behind the JBD so requesting a launch is expecting you to be back there to start the process.

Have also seen this on MP servers. Not super common but it does happen. Just like the OP I wasn't using my radio at the time. It just popped up on it's own.

Agreed as another buddy of mine also uses the WH but doesn't use the CMS switch for SCS function and doesn't have an issue with it. In changing his config the OP fixed whatever was the real culprit.

He is still correct in that what I end up seeing is at times the range to the TACAN gets "stuck" at a certain distance which requires a cycle of TACAN power to get it back on track.

Okay something is wrong with your config most likely as we are matching up on everything but the switch used for the SCS. I use what would normally be the CMS switch (thumb) on the WH SSC. Every time I use HARMs it is on the left DDI as well. The only time I have ever seen it not give the diamond on the left DDI is when I am NOT in A-G master mode but am still in Nav. The HARM page looks the same AFAIK in both Nav and A-G but if in Nav it is impossible to diamond the page.

Which means you know basically nothing of the YF-16 as that is pre A model and we are seeing a Block 50 in sim. This has a TON of functionality and systems already included the A model pilots would have killed for. Let alone a pre production YF-16.

Seriously dude this is what you are going to do with multiple aircraft is just compare them to unofficial wiki specs then talk ish about ED? I let it go when I saw it in the 18 section but take your troll elsewhere.

I launched off a Stennis several days ago (before the latest OB patch) and it worked jsut fine.

At least in OB mad dog mode is broken at the moment and was noted as being such on the patch notes so yeah there is a reason for it at the moment.

I have the left/right HDG set up on the HOTAS and use the left VR controller to enter the HSEL on the UFC for large changes from current setting and have no issues with it at all just FYI.

Refer to Ramsay picture/first video below your post I am responding to as it demonstrates the white out via smoke quite well.

The only difference between what you did and what I've done is cold start versus hot start on the servers I go to. I have not seen this problem at all with the 18 on SC from hot start.

Harker asked me about the smoke color so I very well could be off on not happening prior to patch as the MP servers I fly on don't use smoke thus that part might have simply been the red smoke causing it. Odd that smoke would do that but when I moved the sensor over the smoke it would go totally white and I could reverse it by moving the sensor away from the smoke.

Yup you are on it. It indeed was red.

Sounds kind of related to an annoying bit I've seen recently where at times if the flashing LOST is up in the HUD and FCR lock is lost the flashing LOST in the HUD will stay there until you have locked another target. I've flown across the map on PG MP and had it up the entire time I was crossing the map until I got another target. Got to see one that was even more goofy with the LOST bit. I had turned off from a target with a slammer in the air so I could defend the incoming missile. The HUD was counting down time to active and as soon as it got done with that timer it went to flashing LOST even though at that point I was looking completely away from the bandit.

I just posted on the other subject covering FLIR video issue but the middle picture from above is exactly what I saw when I was flying OB after the 10 June patch and had pointed the FLIR sensor from a Mav F at a smoke marker on the ground the map creator had put there. Completely washed out white as if it was pointed at the sun.

I flew on OB prior to today's patch but after the 10 June patch and besides seeing the DDI disappear when back lit by the sun I also saw this anomaly on the Mav F FLIR video. My buddy had a smoke marker at a base and any time I pointed the seeker at the smoke the ENTIRE page would turn completely white as if it was looking at a huge heat source. Moving the seeker away from the smoke would bring the video back to normal. This kind of issue was also seen but to a lesser extent if I was trying to target in the area of something that had just exploded. This wasn't an issue prior to the 10 June patch and no I'm not running mods. Made targetting vehicles a massive PITA though.

This just isn't true. I use the Rockeye on the F/A-18 all the time versus T-90/M-1/Challengers. Now granted you very well might need two shots to fullly kill a MBT with the Rockeye but it works just fine against MBTs. Anything below a MBT in armor I kill with a single Rockeye. If there aren't any SAM/MANPAD defenses to worry about in the target area the Rockeye becomes my go-to weapon to clear an airbase. If there are I clear those with Mav F prior to getting my feet wet over the base.

Also run the WH and haven't flown the 18 since the OB patch but it worked fine up to that point at least.

This is incorrect for the WH with the off/idle command that the OP found. It works properly with just the one switch per throttle assigned to the proper command.

I have noticed on occasion the FCR can get confused and even going from guns to AMRAAM mode won't fix it. For some reason though going to AIM-7 mode will snap it back to flying right.

https://forums.eagle.ru/showthread.php?t=270609&highlight=dogfight

This. Don't hit the brakes to keep yourself from going backwards. Just wait till you stop rolling via friction THEN raise the hook. I have never had a problem with a stuck wire doing it this way on either the Stennis or the SC. Not sure why people would need to be told to go to MIL as in case of a bolter this should be automatic for anyone landing a non VSTOL aircraft on any carrier.

OK I am confused by this one. What I would think would be a norm with any decent pedals (and crosswinds are more than decent by far) would be x axis left toe brake y axis right toe brake so if you indeed got twice as good braking adjusting the x axis I would think stomping on the left brake would give you a left turn as well since the right (y axis) shouldn't have been affected at all.

Exactly what Eldur is saying. I run the Rift S in DCS and at this point wouldn't run it any other way BUT in VR. Going from TIR 5 to VR is almost like going from no head tracking to TIR. Yes you lose some visual clarity when compared to monitors at the moment but the gain in immersion and WVR fighting ability IMO makes the trade off 100% worthwhile. I also have the TM MFDs and if you leave them in the same place as well as a controller (I only ever use the left controller for button pushing etc.) it doesn't take that long to get used to it. MFDs you just have to button count to get to the right button to push. Not as nice or fast as being able to see it but it still works. IMO yet another one that is worth the time to get used to. I use the TH WH + MFDs for most of the work and anything else the left controller so I never touch the keyboard at all in the hi fi modules like the F/A-18.