@tiag Thank you! The way I solved it and what has worked for me consistently has been updating the threat steerpoints/steerpoint lines on the map, joining a flight, loading the Link 16 plan from that flight into my DTC, and saving the DTC.

@Seifer I wanted to circle back on this to let you know that I’ve flown five more campaign missions in VR with no issues. So I don’t know if this is work the squeeze to chase at this point.

Yes just uninstalled Nvdia control Panel and updated drivers its working again problem solved I hope.

@Seifer said in 4.37.7 Audio - Betty has a stammer for Pull Up: @rubbra yeah, your install is foobared. I recommend reinstalling. @rubbra

@oakdesign thanks

@airtex2019 So I’ll leave this option active and check this log file sporadically if I experience any anomalies with my inputs. Thank you for your clarification on this subject.

we will see what can be done about this sound issue.

Ok, I tested what you’re reporting and I believe I’m seeing the same as you. Even with the aircraft blocking the path between laser & target the TGP (regardless of WHOT, BHOT or TV) will stay locked and no “M” is noted. Definitely appears to be a bug.

Hi all. During campaign me as client @vAiCon as host, I get a CTD right after loading the 3D world into Ramp (didn’t try taxi or takeoff). vAicon has no issues and can start the mission normally. Setup: 4.37.6 (x64) Build 2987 ITO Online campaign, Day 1 2×F-16I B52+CFT IAF vAicon and I tried to debug the situation. We were able to connect to a dogfight session and a TE session with the same setup of vAicon being host and me as a client. I could get into the 3D world with no issues. Same goes for a fresh new campaign, everything works flawlessly. This campaign attached repeatedly causes CTD. Crash dump and campaign save in this link Best regards, Zohar

As per title, the HAF F-16CM Block52M 3d model intake LINK16 Antenna has a dark color, as the image shows the correct is white-light color and the LINK 16 Antenna is slightly larger than this one. https://i.imgur.com/61KfnkA.png https://ibb.co/vC8x3BBs https://ibb.co/S7xdjCc4 [image: 61KfnkA.png] [image: Ant2.jpg] [image: image.png?ex=67e63c3c&is=67e4eabc&hm=3f13b0f08f2d1d418ed98b12cb223ab82eca09d99b2617217f58b01239c789ff&=&format=webp&quality=lossless] [image: IMG_2892.JPG?ex=67e66d58&is=67e51bd8&hm=3c5068e40c50012f0870eda48d9eecd682dff62bdc5d9faa6995c3d63c8b426e&=&format=webp] [image: unknown.png?ex=67e645ad&is=67e4f42d&hm=bd46a539389d0119e4c10974b3bea024c2bcc738e9659f232471b8d35c202f41&=&format=webp&quality=lossless] BMS 4.37.7 [image: Ant1.jpg]

@airtex2019 ok , throttle issue solved, thank you

@MaxWaldorf Thank you. Maybe if the sound engine is upgraded at some point in the future, this will solve the problem indirectly, too. I’ll just continue routing the audio directly to my headset as a workaround for now.

The hand-off status label on TGP format is displayed twice. In this picture there is the complete “C” hand-off indication both above the station and to the top right of it. There should be only one indication on top of the station number. [image: bPsfF9r.png] The WPN format is correct but it does not show the status if it is different from complete. [image: 6fMloki.png]

@oakdesign said in MFDs turn off: @fvelazdem just be aware that in a MP environment even if you have the fix on your side if there is any other player that doesn’t have the fix can cause other players to have their MFD’s turn of as well Is there a way I can force my opponents MFDs to malfunction in multiplayer?

@lixus - slight subtlety…you can still have a “valid” solution, in this case. Which may or may not be “correct”. You are left to employ your airmanship to judge and take a valid shot. Or not.

Problem solved. Or almost… dxdiag command return an error 22 on a device Checking devices (Win+X / Device Manager) give me: Intel Iris Xe Graphics -> Enabled Meta Virtual Monitor -> Disabled NVIDIA GeForce RTX 4070 Laptop GPU -> Enabled Virtual Desktop Monitor -> Disabled If I turn off Intel Iris Xe Graphics -> Falcon BMS come to work as usual (but my external monitor will die). I tried a few seconds in 3d I’ll try better in the future, I’m exhausted from this battle. Thank you all again!

In CCRP/CCIP with backup attack sensor BARO, the baro setting is not used. There is no change in elevation of the SPI or length of the pipper fall line when BARO setting is changed. The RALT backup sensor is working fine.