Wawar

Hi, Airstart jet, GBU10 loaded on the left CFT. At spawn, the LCFT seems not set up correctly in the pacs. Once the bombs have been manually set in the pacs, ASL for that specific station is bugged. Seems stuck in a corner of the hud, and the state "TREL" never appears. If I switch station, the ASL comes back on target and "TREL" appears on the hud. Track attached. GBU10 LCFT : GBU12 RCFT : ASL LCFT.trk

Thank you for the Klarification. Let’s hope Razbam is working on it, the current behavior makes the ASL not usable under certain wind conditions.

Any news about that ? Thanks. :-) Envoyé de mon iPhone en utilisant Tapatalk

Ok ! Thanks.

In this case of radar designation with AUTO release, shouldn't the radar switch to AGR mode during the last 15 seconds before the release? Like explained in the Baltic Dragon official manual, page 401 :

Hi, airstart jet, designation right on target. Without wind, the ASL is perfectly aligned on the target diamond. But with wind, the ASL is pointing towards the wind. The issue here is the ASL behaviour. The closer I am to the target, the more the ASL moves towards it. It is not "space stabilized". So, If I follow the ASL to the target, the plane will approach in a "curve" profile. Shouldn't the ASL be "fixed" in space, in this case to the right of the target, directly with the correct spacing? Track attached. ASL Drift With Wind.trk

Thank you for your answer. So you confirm that the AG Radar is not linked to any elevation database?

Hi, Airstart jet, patch map designation right on target. Target diamond on the HUD appears to be at the wrong elevation, under the ground. Track attached. null Radar Designate issue.trk

Yes, please. So important for cockpit users. Thanks ! Envoyé de mon iPhone en utilisant Tapatalk

Let's hope it's in priority in the roadmap. Can't wait to use my Strike with the exports.

Hi team, In the recent videos, the DLZ's Rmnvr cues do not seem to follow the same logic as the docs. To my understanding, the Rmnvr should indicate max range against a target executing a 4g turn towards a designed aspect angle. If the current target aspect is less than the designed aspect angle, Rmnvr equals to Rpi. So, in term of kinetic energy, from the farthest to the closest ; Raero, Ropt, Rpi, Rmnvr, Rtr. But in the vids, Rmnvr cue appears before RPI, timeline wise. Thanks.null null

So much. People should be happy to have had a TGP for the past 3 years. Indeed it's a pity to lose the "HD TGP" ability until Sniper, but it's only a matter of time. Capabilities are what they are, pilots must adapt to their systems, not the opposite.

Same issue. Picture and track attached. MT Ghost.trk

@JCTherik : More speed or more AOA, wich results in more depression on the upper wing surface. (Lift formula : coefficient of lift(aoa) x speed² x wing surface x 1/2p) So, due to DLC, for a straight and level flight with a defined speed : to counter the lost of wing surface , AOA must increase. Wich results in the same amount of lift generated by the wings. If you reduce the wing area and don't act on the AOA or the airspeed to counter it, your wing will just generate less lift. So, less wingload, so less wing flex. But, let's say you are in a descent at constant TAS, level flight is no more a factor. So, the AOA increase is no more required. Try this : Descent, constant TAS, DLC activated (so DLC in middle position) : if you extend the DLC more, the wings flex more. But, more the DLC is out, the less depression on the upper wing surface, aka less lift, aka less wing load. I presume that the wings should flex less. Maybe there is a story with the location where the lift is generated on the wing, idk. But something seems off to me. If a dev could clarify this, It would be cool.

Hey Heatblur, Just a little cosmetic remark/question... Since day one of the Tomcat, I noticed that when I activate the DLC, the wings flex more. Since the DLC "destroy" the lift on the wing upper surface, shouldn't the wingload be lesser, and therefore the flex should decrease? Thanks.

It works for me. Thanks!

@AstoThank you for your answer. I tried both of your fixes above. With the first, the George UI as Pilot is still on one of my other monitors. George UI as CPG not visible. With the second one, the George UI as pilot is back on the main screen, but far on the right side. George UI as CPG not visible. If I try to use the UI, the "Unit List" does not appear at all. With George UI as CPG, still not visible neither. EDIT : If I put the "correct" aspect ratio, so if I don't round the number to 3.56, the picture is "flattened", distorded. I never understood why, I have been running with this setup for a few years. But rounding up to 3.56, the image is no longer "flattened". And that doesn't fix my George UI issue.

The binding is correct, it worked before the first Apache hotfix. Now I can't see the George UI in neither seat. If I use the newest @Asto fix, I still can't see the UI from the front and from the back the UI is not on the correct monitor.

@AstoThe third monitor is for the third MFD : There are my specs and my monitorsetup.lua : Thanks ! Samsung Ultra + MFD.lua

@AstoHi, Thanks for your work on that code. I copy pasted the code that you posted March 26, but I still have the issue with it. I can see the George GUI as Pilot, but it's not on the right spot. In CPG I can't see it at all. There is my setup : Ingame with George UI summoned : Any idea?

Had the same issue when I was creating a flightplan. Workaround : I Create an homeplate first, then the waypoints. Otherwise, Jester will update the current aircraft position on one of the waypoint I asked for.

According to the team (and so SME I suppose), it can't :

IIUC, the DTOS mode fills the void between CCRP and CCIP. In the Viper, the CCRP doesn't do any precise slant range calculation. It just means "shoot on coordinates". So, slewing your TD BOX in the HUD (or the HMCS) from a CCRP designation, to a target, will not calculate a precise slant range. In CCIP, the plane switches the FCR to the AGR mode, in order to obtain the precise range between your plane and the target and provide the better accuracy possible for the ordnance. In DTOS, the plane does the same thing, but from that mode you're able to designate the target with a TD Box in the HUD. The point is to be able to do a "CCRP" drop but with more precision. I suppose that's why the Viper is not supposed to be able to create a markpoint from the HMCS in CCRP, since the plane doesn't compute any precise slant range in CCRP, and the system doesn't like to establish a mark without a precise slant range.

That's clear ! Thanks

Thank you for your answer. About the SOI, what about the "Cursor Display Select" button ? Isn't it used to choose which display will accept the pilot imputs? (aka SOI) So, you could bring up the TADS display on a MPD, but it is not linked with the slew control of the backseat collective ? It just ignore the "Selected" display? (aka SOI) Same question about the frontseat collective. Would the frontseat be able to steer TADS from his HOTAS, rather than with TEDAC? Thought the TEDAC steering controls were "redundant" with the front HOTAS. Also, I heard several times both crew could exchange the control of TADS/PNVS. Maybe it concerns the IHADSS slave.