gulredrel

As of my understanding it must be this T0 coordinates and designated target for every CCRP release. T1...T4... and such target points only work for pre-planned JDAM attacks. Even JDAM TOO mode needs this T0 as designation. From Chuck's Guide page 420 "Targetpoints": Targetpoints are navigation points on which weapons can be employed . “T 0 ” corresponds to the System Designation and gets replaced/updated each time a new designation is made . “T 1 ” to “T 9 ” are targeting points that are used for multi -target drops with JDAMs . Take note Target Point T 0 is updated and memorized every time you press the Air -to -Ground Bomb Pickle Button and release a bomb in CCIP . This functionality is quite useful if you need to perform subsequent passes on a single target.

It was on discord in December: https://discord.com/channels/536389125276827660/1109145442102562929/1180903836395774032

For me, the track didn't played well. You had no TGP attached, just 4 GBU16. There was a TGT designated on the EHSD, but when replaying you were flying in a different direction and I saw no drop indication, just the arrow pointing to the rear left. Have you studied Chuck's Guide for the AV-8B? https://assets.chucksguides.com/pdf/DCS AV-8B Harrier Guide.pdf I didn't get if you did this WP increment button long press to transfer the coordinates into this designation target 0. I took control, set a point with the DMT and the TDC depress and with WP incr. long designated that as T0 and was able to CCRP drop on this point (of course without laser guidance, the bomb just fell like a dumb bomb in CCRP somewhere near the designated point).

Just a quick update. Did two AAR with the F1EE. Tanker was going 300 kts IAS at 15000 ft. For me it worked best when starting with a good amount of down trim, so I had to constantly pull on the stick to keep same altitude. Once connected regulating the throttle and relaxing the pressure to not gain any altitude when the CG shifts a bit and also the attitude wants to change with the change in power. It's just a matter of practice. The down trim and constant slightly pull is especially helpful, if your stick has some wiggle in center position. So you the necessary corrections do not move through possible dead zone which is maybe applied (hope I've explained that right and you know what I mean). Haven't tried with external tanks yet or with an KC-130 going slower than 300 kts IAS, but this will be next level.

Currently I'm in the F-14 and managed to get around 11000 lbs of fuel without disconnect in between. Need to try my luck with the F1EE.

18 and 2000 are full FBW, so there is much more automation involved. I was fairly successful in the Tomcat lately, haven't refueled F1 for too long. With everything, it's a matter of practice and getting used to the changes needed to compensate for the increasing fuel weight.

I also think just PIO. You are falling slighly behind, adding power, than closing in too fast and reducing power far below the level it was before increasing power. Power changes are accompanied with pitch changes. I think, you just need to anticipate the changes in pitch when changing power to not overcorrect. Constantly tiny power changes are better than large bursts.

Also what's the tanker's and your own speed and AoA? Maybe you are on the edge of slat extension?

Some South Atlantic flying and glacier recon with the TARPS.

@BIGNEWY It's a fairly large track file, but I also experienced the freezing needle and distance in the F-5's TACAN in Nevada in single player multithreading (DCS/2.9.2.49940). On the second part in the track I was taking off a second time. Tuned a tanker TACAN. At first, heading and distance were correct, than didn't change. Tuned a different TACAN and it worked again. After this I set Nellis 12X TACAN. Headed to the northeast away from it to run back in. Again, closing in distance froze at 31 nm and needle didn't move. Changed TACAN frequency to a non existent and back to 12X. Now distance und needle updated and worked all the way in. Don't know if it's a altitude or masking issue, but as soon as there is enough altitude and signal, it should work again. Track file in dropbox, cause it's 8 MB large: 20240107_F-5_Nevada_TACAN.trk Thanks and hope this helps finding the issue.

Great video and first newsletter of 2024. @3:20 Saving Private Ryan Beach scene. How to recreate this moving MG42 view in game?

Glad I found this and it's something known. Got only around 4000lbs from the S-3 to my Tomcat and than the S-3 returned to the boat. Will need to check fuel level in ME. My S-3 launched from a carrier, so there should be no bingo long range problem I guess?

I guess priorities @ @Vibora are still in further developing the F1 and it's variants. I had some longer range flight lately but didn't experience the bat over temp situation. I suspect it not only is a thing of OAT but of your flight level. Being lower at temps around 20°C you will not get it when being not higher than 15000ft. But I also got the over temp frequently when being in Nevada. We can only speculate, what the cause is, maybe a wrong counter or one that will not correctly reset itself after flying higher, where OAT should be low enough to help cooling IRL.

TARPS is available as loadout on the rear right tunnel hardpoint, but I also had no luck with the boarding ladder. I placed static F-14A and B on the ramp but they only had the intake covers attached. Same with AI planes with option uncontrolled.

I see you...

49 vs. 51 % Looks like no real preference

That needs more practice, wrong dive angle, missed speed and altitude... Or do the WPs behave so much different from HE rockets?

No problem. Just wanted to do this flight anyway, Doing some VOR navigation radial flying and using the TACAN to receive the DME ranging info. So I now know I need to have the extra fuel in the current state.

And an update for completeness of data. Did the same flight with the EB version. Started with 1980 lbs fuel regarding mission editor. The fuel warning light came on as the fuel flow meter showed a total used fuel of 1540 lbs. Fuel gauge was roughly showing 400 lbs fuel left. Shortly after landing, fuel totalizer showed 1600 lbs of used fuel, fuel pressure warning came on and the engine quit. Fuel gauge showed around 300 lbs of remaining fuel. Here is the corresponding track file: 20231210_C-101EB_fuel_empty_on_taxi_back.trk Regarding the manual, the low fuel warning comes on at around 370 lbs remaining fuel. Being near the airport, this amount should be sufficient to do a missed approach and a circuit, landing and taxi back to the parking space. Thanks Jens

It's operator specific, but I think we can agree, regardless of where the jettison chute area is, there is someone collecting it in a short period of time to not interfere with further aircraft. So for the game and different aircraft using the drag chute we could pretend, the dropped chute object should be removed after x amount of time. Maybe 30 - 60 seconds?!

I've put such a TACAN frequ. pairing sheet in the saved games kneeboard folder, so it will be available on any map and aircraft.

Caucasus map only has VORs without DMEs. In South Atlantic there are some real VOR/DME stations. For example Punta Arenas on 114.100 MHz. Corresponding TACAN frequency is 88X. In C-101EB, you can tune VOR for the heading information and TACAN: Or in C-101CC (which does not has TACAN) you can tune just 114.10 MHz and setting DME on the VOR receiver to get heading and ranging information. Doing the same in MB-339 you can also receive the ranging information with 88X on the TACAN receiver and have the 114.10 MHz on the VOR. Problem is, HSI will only show either heading information, when VOR is selected as NAV source (large picture below, heading, but distance indicator striped with no indication) OR ranging information, when TACAN is selected as NAV source (inset picture below, I'm less than a mile away from the VORDME, so it shows 0 NM). You can't have both at the same time. But as MB-339 has GPS/INS system, you can show distance information on one of the data pages of the NAV display.

@Vibora: Thanks for investigation. Here you go with the trk file: 20231203_C-101CC_fuel_empty_on_taxi_back.trk Also some screens taken from the cockpit yesterday. Fuel flow gauge and fuel gauge after engine went out.