GrEaSeLiTeNiN

Before FCR was available, the L would get "data" from manual lasing first. Then we fire it and the L flies a curve leftwards or rightwards depending on pylon (I presume for the L to get a better radar return since it uses its own radar?) and then hits/misses depending on ground clutter. With the FCR 'photo' scan of the targets, does the NTS and ANTS now feed "data" to the Ls for firing?

With the addition of FCR and its related functions to come (C-scope, zoom, cued search), I sure hope ED could add QOL binding options like being able to cycle FCR modes, FCR scan size modes, TADS zoom modes, LST modes, etc. It is quite doable to keep most of these CPG flight and RHG/LHG functions on a hotas like the warthog with the help of a modifier, without resorting to using a secondary device like a game pad. These simple binding options would be a tremendous help and would be greatly appreciated..

Very good now, hope it stays that way.

Isn't GTM on by default after sight selecting FCR, at least for now? I don't suppose there is a 'EXP' option in the FCR to have some artificial spacing betw the scanned targets, like they have in the modern jets?

- Hmm.. after an FCR Scan, I cannot sight select TADS and there isn't an option for FCR when selecting ACQ. But I can sight select HMD and set ACQ to FCR though slaving only puts the dotted cross on the FCR TGT in the HMD. Guess I'll wait for the Link function. - Yes, TGT function in FCR using cursor to select a TGT, then select that TGT number in TSD COORD page to make it ACQ, then Sight Select TADS and slave. That slaves the TADS to look at the selected TGT. Thanks. - Will they work with AI wingmen in the future (at least in sending to AI wingmen for their action)? - Noted that other FCR modes will come later. - Managed to get Scan Size for pilot to work. Yeah FCR has to be Sight Selected though sizing only works when not performing a scan (makes sense), ie. can only be used in Single Scan mode when not scanning. Thanks very much for your answers.

I tried the new FCR and got some hits as CPG. But is there a way to have FCR (on one display) do scans while being able to slew the TADS (on another display) to look at your targets? I find that once I go to CPG GHS to slew the TADS video, I lose the ability to do FCR scans. If I then select FCR via the Sight Select Switch, I lose the TADS view of my targets (it repositions) and the ability to slew the TADS video. Update: - Pilot FCR modes (TPM, ATM, GTM, RMAP) not working yet - Pilot FCR Scan Size (N, M, Z, W) not working yet - As CPG, could not get TADS to look at FCR targets (correct as is?) - PF/NF zones work but not useful in SP as you can't send to AI (yet?)

It does register as an axes but no amount of tuning has made it usable for radar cursor slewing. I did not go with the slew mod. I simply unassigned the axes in the slew and use only the depress button part as modifier in all my modules. The latest Warthog hotas has a new and much better slew switch much like the modded one. (With each new module, you have to check all hotas axes as they may be improperly assigned or not assigned by default.)

Can’t remember the specifics but flight controls are very similar. You can fly and fight from the front without using George as pilot. If you like you can have a look at my mapping here to see what is shared and possible.

Designation diamond is not following the target prior to release but the LGB can still hit slow movers. Try APCs at 49 knts.

+1

Still not fixed in 2.9 post hotfix (as of 2 Nov). Has been reported here and here.

Still not fixed in 2.9 post hotfix (as of 2 Nov). Also reported here and here.

I think by now we all know that in summary: - CDES isn't working properly at the moment to keep the diamond on the moving target before bomb release - We were just hoping it got fixed in 2.9 - So for now we lead designate moving targets, we know how to do that, and we get that that's how it was done IRL as CDES wasn't reliable - PTRK is working and will keep the laser crosshairs on the moving target - Even if CDES gets fixed and works, it will not compute bomb fall line lead when a mover is designated because DCS does not model that in any of the targeting pods including newer pods like the litening/F18. You can still hit slow tanks (tested 15knts) but will likely miss fast APCs (tested 49knts) unless you lead designate.

I tested the F18 litening pod + LGB using PTRK on tanks at 15knts and then fast moving APCs at 49knts. No problem hitting the tanks but it was hit and miss (falls short) with the APCs depending on aircraft speed/altitude. If I understand correctly, even with newer pods like the Litening, for moving targets using PTRK, the bomb fall line is dynamic and correct until point of bomb release. Then it depends if the LGB has enough energy to catch up with the moving target. I might be going a little off topic with the F18 but I'm curious what is the real life procedure for hitting fast moving targets with newer pods such as the Litening pod/F18: - Fly head on to moving target or at a certain aspect to reduce chance of LGB falling short? - Forget LGBs and choose another method like IR Mavericks or just strafe? - Or is there a certain aircraft speed/altitude required for Litening-PTRK-LGB to succeed with fast movers? - Or does the pilot use lead designation and if so, how do you get the laser to auto track the target with the designate point farther ahead (if it is even possible)?

My point is that in the sim, the litening pod (Lpod) in the F18: - Gives you the correct 'designate' point (ie, diamond remains right on the moving target) at the time of bomb release. I don't know if that means the bomb fall line calculated some lead. If it didn't, I would expect the Lpod LGB combo to miss very fast moving targets often and tutorials to suggest lead designating and ignoring use of PTRK for fast moving targets. I have not seen any tutorials like that. I think simmers assume PTRK is good for moving targets and expect the LGBs to hit every time (when within other procedure parameters). - Once PTRK captures a moving target (SCS to Lpod), the designate (TDC depress) HUD diamond done prior to PTRK, jumps to follow the PTRK gates on the moving target. TDC depress again just puts a small cross within the PTRK gates in the Lpod screen and isn't necessary. The current F15E Lantirn (Tpod) cannot do the above even with CDES on (bug?) in that the PTRK cross hairs follow the moving target in the Tpod but the HUD designate diamond stays fixed on the ground. Hence, the need to lead designate each time. Am I right to say that when CDES is fixed in the F15E, in the sim at least, the HUD diamond would then follow the PTRK on the moving target?

Yeah I thought it was lightning at first but I guess it might be some gfx anomaly (using DLAA).

My understanding is that with say the F-18's Litening pod, PTRK on a moving target constantly updates and moves the release point of the bomb fall line. And the bomb fall line is tied to the diamond which moves with the moving target. You can see the horizontal cue bar move upwards as the target moves further away from your aircraft during an active pause. In the F-15E Lantirn pod, this is not happening because the pod or whatever does not have this capability. It's a 'static' bomb fall line post designate in the sense that the bomb fall line and release point are tied to the last static or fixed position of the designate diamond on the ground. Hence the need to lead designate.

On OpenBeta MT. DLSS Quality didn't seem to give me better frames than DLAA. With generally medium and mostly high settings, with DLAA I was able to stay above 40fps in the Apache at low level in a valley of all trees in South Atlantic. With DLSS Quality or MSAA2, all else equal, my FPS would go down into the high 30s in that same valley. I could use DLSS Balanced but the AA along the cockpit frame edges would not look as good as with DLAA.

In my case (5600X, RTX3070, 32RAM, MT, OpenBeta), all other settings equal, it seems: - DLSS Quality gave me about maybe 1-2 fps more than MSAA 2x - DLAA with no upscaling gave me about 5-6 fps more but similar AA quality as MSAA 2x Was using MSAA 2x previously but will switch to DLAA.

Did you turn the left side comms panel knob to "GRND CREW"? If you have the Normandy map, you can try this mission where it works (select slot with Ka-50 III Hokum at the FARP). BT Normandy 2 - River Thames II.miz

I think for the pilot, the warthog hotas should be enough as the modifier layer was added for additional convenient commands like kneeboard or external views, which you can ignore. But for the WSO, with 4 devices in the back seat, a modifier is needed unless you have another device like a gamepad or something. Or, if you decide to not ever fly the jet when working as WSO, you can remove the WSO hotas (flight) commands and focus on mapping the warthog for just the L/R hand controllers. I think later on they will add more AI capability to the pilot. Just to check though, are you using the old button slew in the warthog throttle as modifier like in the profile? (If so, did you unmap the axes and any other existing bindings?) With so many modules, I often fly with a jpeg of the module's hotas layout in the background (Alt+TAB) for a quick reference if needed.

IIRC a few functions (manual SBR AIM-9, TSD track on/off, VV un/cage) associated with this button are not implemented yet.

Some of those commands are problematic. They step up or down in one direction and then stop. I hope they can give more options like a true single button cycle.

Yes. Just clear any existing binding so the button is freed up to be a modifier. Modifiers like bindings (except the shared UI layer ones) are specific to that module only.

TGP OA1 OA2 still messed up for me. Often I can get TGT and OA1 but not OA2.