ACME_WIdgets

In the F-16 WPN page with HARM-88, I have an analog "hat" mini-joystick on my VKB Gladiator Pro joystick. Analog input is detected, but the cursor jumps to the side of the page, in the direction of analog control (i.e. a slight UP on analog hat sends cursor immediately to top of WPN MFD). But when I switch the VKB "hat" to the "button emulator" mode, I do have control of the cursor to lock a HARM HAS emitter. The analog cursor is very smooth, and works great in the F-16 RDR CSR for FCR in BVR.

CCD and IR Maverick cross hairs in F-16 MFD are not displayed at 1280x768 resolution until after a lock is obtained.

No, I could not reproduce it. My guess is a MS Win10 update or something - it gave me other problems with my GPU. Thanks for trying.

For RTB go high, as others have said. I try to climb as fast as possible, as high as possible on RTB, until I slow to about 300kts IAS. Once you're about 30nm from base, ideally A30+ I nose over to point the nose at the base, and pull the throttle back to idle or zero. You still make good speed and use very little fuel. And on takeoff, try to avoid AB until you're above ~15k ft.

F-16 Cockpit: FIrst, I'm no graphic designer, but I can work Photoshop pretty well. Second, my system is the slowest of any, around 12fps on MP (GS) - it's an older Dell e6430 laptop, running 1280x768 w/1GB VRAM. So, I'm trying to figure out how to make the F-16 cockpit fps faster. I see others have done it with FC3 planes. I got the DDS add on for Photoshop. As @LucShep poinits out, many of the DDS files are 2k x 2k and some for the F-16 are 4k x 4k. Using Photoshop's batch processing I did the following on the F-16 Cockpit Textures ZIP files (after many trial and errors): - resized all DDS to 1024 x 1024 - saved only 3 mipmaps (so I think 1024, 512 and 256) - saved DDS Output to "Performance" vs default high quality setting Results: F-16 Cockpit Textures.zip went from 374k to 32k size file! 2-3fps faster in ME and MP but cockpit lettering is terrible on all panels (I know what the switches do anyway) a few artifacts, rotating button tops, some things too dark etc, MDF reflections become big dots I'm not saying this is playable, or a solution - just a data point or two for other experts. Note: I guess due to my low resolution 1280 x 768, even with the stock Cockpit Textures the DCS Settings Cockpit Resolutions all look the same at 1024, 512 and 256.

Thank you @ice41 . I understand it now!

My main problem with SPro3 is poor MP support, once over about 8 players it crashes trying to connect to MP.

@dorianR666 if I understand your question, yes all target tracks (white dots) become system tracks (with correct radar elevation/azimuth) to solid red triangles.

Sorry for the late resonse. It was on Growling Sidewinders, so auto started at spawn in. I started weapons/fuel loading already. Then I go left to right around the cockpit: Confirm nav lights OFF, TACAN volume to zero, EWS Volume to 50%, Comm1 volume to zero, Comm2 volume to 50%, then EWR power ON - and crash.

F-16 in GS MP, happend 3 times in a row. Did simple "repair DCS" after second crash. After first crash (turning EWR power ON in mid air), then after restart in MP no EWR display or tones (yes volume was up).3rd crash was turning EWR ON on the ground after arming (after being short down, because no EWR display or sound). log file attached, RAR log file too big 6.7MB. dcs.log

If youi go to F6 Missle View after firing a HARM, view from behind, once the missle is close to the radar source, you will see often anti-missle "flak" coming up from SAM or emitter sites.

Just a low, low, low end data point. 2.7 caused MP fps drop from 17fps to 11fps from 2.5.6. 1280x768 everything LOW/OFF. (YES, I know it sucks and yes it's not as much fun to play. And yes, I'm ready to order a real PC (3700x , RTX3060).)

And after firiring over 100 AGM-88 in MP, it has terrible terminal kill ratio/anti-AGM statistics. I was RedFor only 10nm at 400'AGL from an emitting HK site, locked, fired 2 AGM-88s(repeated lock sequence quickly) and both were defeated by counter measures at the HK site. (Growling Sidewinders server) This happens EVERY time with Patriot CMs, but that makes more sense since the AGM88 is going slower, due to being fired from further away(40nm ish). Maybe SAM site countermeasures are over modelled?

When using POS mode in F-16b50 with HARM, at M1.2+, at angels 45+, it won't let you fire until 36nm from target. So it's impossible to hit a SAM site that has a 50nm SAM range....

1-In the F-16 bl50 Sim, with active Link16 data, TWS mode and radar ON, first target lock using TMS UP, I cannot switch to next enemy target wtih TMS RIGHT. This is with all solid red diamonds being displayed on FCR MFD. TMS Up works fine to lock targets with cursor, and to even switch to STT. But TMS RIGHT will not move to the next sold red target. Now, if TMS Right is used for an initial lock, then TMS right DOES cycle all solid red targets. 2-Also, with IFF, why are friendlies locked if using TMS right (i.e. a green IFF friendly is in radar scan zone, but closer than an enemy)? Seems like the target lock should ignore a friendly when hostiles are in the radar scan zone.

Adapt this fromSu33 to Su27 ?

You can target most carriers, blue (40x codes) or red. But good luck getting close enough to one of the BlueFor. When flying close to the coast, I'll setup ground based SAM on Table 1 and ship based SAM on Table 2. TIP: turn off not needed scan codes to make the sweep much faster. i.e. if I know only BLueFOr HK and P are present, I turn the other 3 off. CTR instead of WIDE also makes the scan much faster, as others have stated.

My RedFor AGM-88 hit rate lately is about 1 in 15 missles. I'm usually at A35+ and M1.2+, the AGM rectangle is flashing on the HUD (whatever that means), with the SAM directly in front of me (at unknown distance) and this is WITH the SAM emitting (when on RedFor, I can see "P" or "HK" on RWR - no diamond for lock, and I can Lock AGM88 on the target - then steer so locked target is middle of Left MFD crosshairs). Same hit ratio if I wait until RWR shows MIssle Launch. I've even tried flying level after launch to SAM and keeping A-G mode ON and it does not help (Just a test). Often times I know I'm close to the SAM as the Lock in Left AGM starts to drop (I need to dip nose of plane to stay centered in crosshairs). I need to fly more BluFor to see if the hit ratio is different. Also, typing in the AGM Table(s) when playing RedFor is a royal PIA after every time I'm shot down.

So I'm just learning the F-16, and tried the AGM88 HAARM a few times, with no success. I can lock on to an emitter just fine, but I have no idea when I'm in range with the HAARM. Yes, I'm fast and high up. So theoretically 60-80nm max range. When the HUD rectangle at the bottom blinks, does that mean HAARM is in range? Is putting the target in the middle of the X on the left MFD better than nose up 15 degrees to help the loft off the rail? Thx all !

Do you get IC Fail if you open DCS and go directly to MP? I have a bunch of mods, and as others have stated, if you are in ME and then try MP you may get IC errors. I often have to close DCS due to IC, restart, then go directly to MP with no IC. Sometimes I get IC error when existing a server.

I saw a news story on the real AirForce F-35 simulator. Here are some screen shots from the video story. A female reporter was in the sim at the time. A target aircraft was about 30 miles ahead, with AIM-* and 2x 1,000lb bombs on board. All touch screen, no OSButtons. Note the very cool 3D "globe" type view on the left display.

Might be a friendly (round) data link aircraft, showing hot to the right ish flight direction.

OK, so I just ran repeated tests. I apologize, as it is ILV mode(default) in SCN that causes the significantly reduced radar range sensitivity. Test: Su-33 at A40 hot against 3 F-15c at A40 (abreast 23nm spacing) in ME, open-beta. Results: Su-33 radar: SCN - ILV = avg 45nm first detected SCN - Hi = avg 60nm first detected TWS - Hi = avg 62nm first detected Notes: SCN and TWS show about the same azimuth coverage (23nm left or right from center F-15 at 62nm distance hot) If switching between SCN and TWS more than 3 times, the radar seemed to go wonky(not detect until targets were about 30nm).

I read somewhere in DCS that Russian SCAN mode ihas about 15% less range than TWS mode. Plus there is a speed trade off (the TWS is a faster scan - since it's a narrower scan cone). When BluFor jam, the SU-xx radar switches to SCAN mode automatically - so indirectly BluFor jamming reduces the Su-xx radar range. My BEEF is that when BluFor jamming stops, the radar should go back to TWS AUTOMATICALLY. Seems like a no brainer to me. I'd also like to see the SU-xx radar target RANGE/elevation/target size be "stored" so when going from RADAR to EOIR and back to RADAR - I don't have to reset the scan distance and elevation. This creates a HUGE advantage for BluFor in mid ranges (30-6km) as it takes many seconds to reset radar range/elevation/target size. The same should be for the EOIR elevation - once I set EOIR elevation, remember it damn it. Even if I go radara - eoir - radar, etc.

@WytchCrypt Thank you VERY much, it works great. BUT - can you add it to the HDD data link display also? I tried to edit the .dds, but I only see a totally black image. Thx