oldcrusty

Straight and level over PG map... finally remembered there were other maps then Syria

I simply put my 'in-cockpit' volume to 85. Everything else at a 100 except music

In the latest OB, mad dog 120 takes the cake by far in my experiments. I had AWACs D/L'd so I kept my nose cold. Once I saw the 'dot' (NO, NOT the NEW DOT ) I really focused on keeping tally and when within range I let 1 or 2 120s go. Splash every time. I placed an ace MI28 (armed) at low alt in my tests. In couple of engagements I used my radar only and was able to pick the helo up. He was flying at 90kts but... as soon as knew I was heading for him we went into notch and rapidly repositioned upwards. In my first fight I lost tally and got smoked with his guns since I decided to casually loiter looking around for him, bad idea! In the following fights I new what to do and sent a Spamram or two in time.

I'm OK with leftover decorations. As I mentioned in my previous post the HARM OVR in A/A mode is actually 'active' in current OB. We can change the on/off status without any visual feedback ( a BOX). You can see it changed by switching to A/G mode.

So cluttering up the stores display in A/A with unnecessary options is also intentional? If HARM's SP mode is not forcing any displays on DDIs in A/A why even show OVRD option there?

To add more to this fun, currently I can change the status of HARM OVRD from A/A mode... just doesn't show it there. It's always unboxed in A/A but if you press it and switch to A/G, you'll see it changed so why not show the 'box' in A/A also?

I'll be damn, I always thought that this was related to keeping your current selected steerpoint unchanged when flipping through different waypoints on DATA page and or editing them. If REFWP is unboxed, every time the up/down arrow is pressed the current steerpoint is changed to whatever is selected on DATA page. Just checked how it works here and looks like you're right... I think.

I saw the thread title... how timely. Just made my glorious return to carrier aviation on YT 90 kts down the angle. Let's see what a fixed, linear bump through 1600ft would be, hehe. Well, if that's the only way to create a cool pitching deck so be it https://youtu.be/JaUz6SHokBw?si=-hN3D_kH_cH5yJZq

Glorious return to carrier ops...

Put it in the bugs forum. Thanks for beta testing...

OK, after flying a few missions in ST... back to MT. On my rig MT definitely wins.

Fine, I won't cry Whatever I get it's not going to be dependent on meta or any other mandatory 'ping' crap

Sure, I had all pulldowns opened up, volts, temps, LOADs and the rest.

13900K on win11... I don't even try to get 'scientific' with this thing but out of curiosity I decided to have a peek at HWmonitor with ST running in VR and I saw all pcores at 5.6 with roughly evenly distributed loads running cool as a cucumber (whatever the heck they were running on top of DCS, lol) and all ecores were idling at 4.something. I think I'll go back to ST for a bit and see what happens. I didn't really have major issues with MT in single player other then some weirdness after shutdown with my rig just resisting to completely power down. and glitches with my Reverb G2's USB connection after running DCS (probably something with microshaft's WMR)

Yep, seems like they changed it, both AUTO and CCIP.

Hehe, I'm all on 'global' now :/

test

The bug is definitely there... where? I don't know. However for some reason I was able to hit the target (tank) with Mk82s pretty consistently in 2 tests in a row. All I did differently was re-designating with FLIR on top of WPDSG. We shouldn't have to do this tho' I'll post a vid in the screens and vids forum.

Today I only had enough time for a short hop. It was enough though to get me confused again. The temp was always 20'C, in previous tests and today for all types of deliveries. In level deliveries, AGR ranging was not a factor. Regardless of how the target was designated (WPDSG or FLIR) it seemed like the FLIR's laser was providing the range. Today, when approaching the target locked as WPDSG I decided to re-designate with FLIR (area bracket then TDC) Just to make sure, I undesignated WPDSG and repeated the FLIR lock, hehe. Both level and dive drops were bullseyes! Probably just today, lol. I'll do some more test runs tomorrow.

Why do I keep flying the Hornet... I guess I'm just a stubborn old goat. More ED stalls and drags their feet more I'd determined to stick to it. Creating my own band-aids and crutches and finding different ways to whack the bots (I stick to SP for now) :D BTW, I did notice small improvements here and there in 2.9. Taking gas from S3 at night for instance and being able to see their nav lights from a mile or so, Hornet's 'orbs' look quite a bit better, Paveway III behaves better too and few other things.

I just tested this, well at least I tried. The attack direction didn't quite workout the way I planned. When approaching the movers head on, I ended up a bit to one side and the sunlight was slightly hitting the sensors. Hot summer afternoon in both cases. When approaching the targets from behind, I was able to persuade the MavF's to lock. It seemed like the FLIR was updating the Mav's seeker on occasion, making the seeker 'jump' toward the target. The FLIR was tracking the first vehicle in the convoy but the Mav locked on the second. I wasn't going to waste time to correct just as long as I remembered which vehicle I fired on already... On the second test, approaching from a head on direction the FLIR was tracking for a while but the Mav never acquired. When the FLIR finally lost track I undesignsted and used the Mav seeker on its own. It was shaky but it worked. I'm not sure if this test helped to answer your question. Personally I think there were other factors, including of course the current modelling. https://youtu.be/TWeF_N9MIw4?si=QWkK9vJNEbIJRmTs

I had to come up with my own ways to deal with this issue. When using Ir Mavs, one method was to pre-configure the FLIR to max zoom on RDDI then switch to GMT on the same DDI, find and lock the track, switch back to FLIR on RDDI and watch the radar track the mover. It would track nicely provided I didn't touch the FLIR function buttons. When within 12 or 15 nm, depending on weather, time of day etc, I would ground stabilize the FLIR reticle right in front of the target vehicle and as it passes under the dot, I'd change to PTRK. The LDDI was reserved for IR Mav. I always set them all to NAR FOV ahead of time. Now... the target hand off is another story lol but it's doable.

Thanks for the heads up. I didn't have any stutter though on 546.29 (Reverb G2 in native res. @ 90Hz, MSAAx2, sharpening .7 - no other 'fancy' new stuff). I'll update anyway.

In my experience, switching to FLIR from A/G radar will not change the sensor priority but as soon as you touch the FLIR screen to say change the zoom lvl, the radar drops off.

What you will get is more of the same. Currently, diving deliveries hit short, level deliveries are reasonably accurate and 'lofting' (auto - w/o any pullup cues) hits long. A while back lofting was the most accurate... at least for me.