gulredrel

Yeah, on later tries both worked for me. So that should not be the problem. As said above, I sometimes encountered the problem that I needed to recycle the release mode to get right symbology and could release. Hopefully Harrier will get an overhaul including the drop modes. There are also other things not quite right.

Hello, I only own a throttle with a single throttle axis and would like to know if there is a way with just the DCS controller setup to have the same axis control engine throttle and than, when this is at max., switch to a different mode to manipulate boost control with the device throttle axis? There was a good Razorback for the civilian sim year ago with it's axis mapping where you could do this. Change the axis input achieved in game with a key command. Thanks Jens

Okay, thanks for the other report. Will keep that in mind.

Something is a bit weird. Had a different flight and needed to cycle the drop mode selector before getting the BFL, despite the selector was in AUT and HUD showed GAUT. As RAZBAM said on discord, they will eventually do more updates. Mirage also got a bunch of upgrades. I guess, we need to be patient.

Still an issue Experienced the same which was reported from in the first posts. ATC call not finished and making ground crew call to remove wheel chocks and after this, no more communication possible.

I just checked in a simple mission. Harrier, some waypoints, no TGP, 2xMk81, 2xGBU16, 2xMk83. WP2 set as steer point, EHSD press OSB DESG and than WP increment long made the T0 and I was able to drop CCRP the Mk81s on this point (had to cycle release mode to get drop symbology). WP3 set as steer point, EHSD press OSB DESG and without increment long this steer point was the designation to drop the GBU16 in CCRP on this point (they fell long without laser designation). Third drop with Mk83s, this time selected WP3, DESG on EHSD and WP increment long again to get T0. CCRP drop near target. With NWS / undesignate you can get rid of the designated target point and only have the normal waypoint steering information in the HUD and not the arrow pointing to T0, which you can see in the gun runs. First gun run created new T0. 20240118_AV8B_DESG_STP_WP_as_T0.trk

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?