Dawgboy

I have no choice but to believe you; however, if you look at the one pic above, I'm within 10nm, looks like 8nm, and I can see these HUGE Blackjack with my own eye, each of them, but the radar still "sees" only one. I can imagine, as I said, there being only one AWACS SA ELINT correlation. Hmmmmmm.....

@BIGNEWYany luck with the team?

Does this happen in real life? I'm seeking to understand, not splitting hairs.

@tweetI have suffered this problem, too.

@BIGNEWY Here you go; clean MIZ with air start...specs: I have a flight of 4 x Fencer off to my left, and the 4 x Blackjack singletons are to my right. AWACS is off to the north. Me in my Viper The Fencer flight is slightly farther away. First detect on Blackjack around 60nm. Fencer about 40nm. Between the 40nm and 20nm range threshold, I continue to see the same on the scope: I can break out the Fencer but not the Blackjack, either in EXP or non-EXP. I can visually see the Blackjack in formation outside 20nm. Inside the 10nm to 5nm threshold, I can break the Blackjack apart, the same with the full-up MIZ file. I shot at the Blackjack to see if they'd scatter earlier. Once within the label range, I see the Blackjack labels for each. in this one, I seem to get multiple AWACS SA Blackjack tracks on the FCR, but not on the HSD. I always get multiple Fencer SA tracks from AWACS, and the same with Flogger in other missions based on the same full up MIZ file. Still seems fishy the Fencer throw off a better return in EXP or non-EXP modes. F16vBlackjackTestSPairStart.trk

@BIGNEWY Hopefully in order, you will see 4 x Fencer in EXP mod at 30.8nm. Next, 4 x Blackjack showing as a singleton, NOT EXP, just outside 20nm. Lastly, 4 x Blackjack in EXP showing as a singleton on radar and AWACS feed, just outside 20nm. The JPG file names are labelled accordingly. For my other pictures, when the Blackjack flight breaks apart, I acknowledge there is latency between that event and when I get the networked SA feed showing hostile-red tracks. I'm not expecting those trons to flow at light-speed. Later, I get the corresponding SA track, albeit lagging the radar return on the FCS, which I guess would be normal latency within 10nm. Further to this, while I don't have a track file to prove it since DCS CTD when exiting that MP mission, my "live" Hornet wingman didn't have either radar or SA tracks until after the flight broke apart. I did have pics from that mission, but I didn't include them...you have correlated pix from the track files I included there. Clearly, something's amiss...if you want to fly my MIZ, let me know.

I did EXP, and it did not alleviate this issue. I think I have a pic of Blackjack fail and Fencer success. Will attach when I find it. @BIGNEWY

@BIGNEWY Here's the track file and screenshots from the same mission file, flown in single-player mode. No difference compared to MP mission. Specifics: HSD showed single AWACS system track for Blackjack while in Incirlik HAS during preflight config, hot from parking. Fencer showed multiple overlapping AWACS system tracks. Initial Blackjack radar detect: ~60nm, single constant AWACS system track. Tally engine smoke and aircraft dots around 34nm, might have been farther. Blackjack scattered within 5nm of rear intercept, then I picked up multiple radar tracks, single AWACS system track. After they scattered, multiple AWACS system tracks, within 1-2 miles. In most of the pics, I left enough of the panel to show the multiple overlapping Fencers on the HSD. I have not flown a clean mission yet with just me, the Blackjack, and the AWACS. Maybe tomorrow, @Deano87 F16vBlackjackTestSP.trk

@BIGNEWY @Deano87 No, but I will run in SP and report back. What is the purpose for flying the mission from the Mission Editor? Just curious... BTW, since that other track didn't work correctly, here's a shot I took when I had a tally on the Blackjacks. At this point, I could see all four of them clearly, but only lock the one aircraft.

Baseline: OB 2.7.8.16140 Syria Map Multiplayer (this mission has just me, but flew with a "live" Hornet with same results) Track File (too large to upload) From the moment the system tracks are generated by AWACS and fed to my Viper, I see all the 4xSu-24 Fencers, meaning multiple RED systems tracks on the HSD. However, despite 4xBlackjack being there, only a single system track is evident on the HSD. See Picture1. Furthermore, while at 40NM and less, I can see all the Fencer on the radar, EXP and break them out (Picture2); however, not so with the Blackjack (Picture3) until they scatter within 10NM, even tho they are larger aircraft that I get a single radar return at ~60NM. It might be ECM/jamming, but there's no indication and that might be WIP, symbology not there yet in the Viper. Are there any bugs here with the Blackjack versus Fencer radar returns and AWAC systems track feed? Thanks, db

Does the real jet do this?

@dutchiliI had a similar problem when DCS automatically and improperly mapped a new USB device as the HOTAS. I had to go in and delete all the assigned settings of the new device and map them to their intended settings. Might be the same or not. Something to try.

Could it be the opposite? The Hornet radar is hosed versus we need to cripple the Viper?

Thanks, @MROK73...after I figure out what works and doesn't work as intended in Viper EA, i.e., fly it, I'll learn how to work on the jet.

If the Viper is fly-by-wire, I would guess the control surfaces are not on the hydraulic systems. But the question remains, what drives the "cold/dark" control surfaces' positions? True?

@Lurcher I am having this crash when entering the mission (select role/aircraft, then fly) on SP/MP Marianas map, using this MIZ file, which was also created on the same PC. DCS OB 2.7.7.15038 with me hosting on the same PC as the sim. Marianas Map w/a single Viper and single Hornet. It happens when my buddy hosts and I host, but only I crash, not my buddy when he hosts this mission. It started after the update after the map expanded island content. All of my old Marianas missions fail in the same manner. This MIZ file is created on the new map on the latest OB update. UPDATE: I ran a repair and that didn't alleviate the issue. Still CTD when entering role/aircraft. I can sometimes get the mission to run in the Viper when in single-player mission mode. I've uploaded that SP track (MarianasTest.TRK), along with today's MP track after repair (server-20211109-052033.trk). dcs.log-20211108-171114.zip F-16C&18_MAR_IA_Hot StartNEW.miz MarianasTest.trk server-20211109-052033.trk

I guess I'm still wondering what is real life reality and what is DCS reality, to the OP's point. I hate to split hairs, but...

@BIGNEWY Sounds as if this is really WIP; "Correct As Is" would imply it's working as it does in real life, which is why I asked the question the way I did. Your answer suggests to work as if in real life, we need the data cartridge functionality and blank means blank across the mission computer and TGP, which is fine, since this is no huge operational issue. My concern is whether when I get into the jet, if it already says 1688, will it work when I lase for myself and/or a buddy, without me entering a code in the blank DED Laser page?

After the Viper's TGP powers up, and I go to the Laser Code DED page, which is blank, the TGP shows a 1688 code in the MFD view, as indicated in the attached picture w/red boxes. Is this correct, and if so, where is it getting this value? I don't think this is the weapon code since when I change the LST code on the DED page, the MFD TGP code above the LSS line changes to the new value, and in the case of my example no-box picture, 1687. I'm thinking the TGP view at power up should be blank. True? If so, then if DED LSR PAGE = Blank, TGP MFD = Blank. If DED LST line = X, TGP MFD = X. DCS 2.7.7.14727 Open Beta Single and multi-player Syria Map Incirlik AB HOT ON RAMP start w/the following actions by me: Power on TGP w/right hardpoint power on. TGP selected on right MFD in A2G master mode. Await TGP power up and showing view, which has the 1688 as shown in the red-box picture. DED LIST > MISC > LASER/5, code shows blank, enter 1688 code and hit enter for both lines, after dobbering down. It sticks in DED when I go back into DED, and of course, the MFD TGP view doesn't change since it already read 1688. Same functions in previous line, above, changed to 1687, which sticks and shows on TGP as 1687. Track attached showing me entering 1687 first so you see the TGP MFD code change from 1688 to 1687, and then 1688 to see it change back. LaserCodeTGP-DED.trk

Yes.

@DCSopingI was just in a Syria map mission against an AI SU-27, and I locked him up, about co-altitude, at around 40nm. He was doing the funky chicken on me, going left and right, and the lock was persistent. I had a successful AIM120C shot within pitbull range, slightly lookup.

I haven't tried it, but can't you just back off the fuel slider bar to just the internal fuel load?