Topper81

Then the switch should be set to down position (GUNARM), because PAC should only be active if you defenetly plan to fly a pinpoint attack with the gun. (My point of view).

Thiy is maybe not a bug, but when a mission starts in the air, the GUN PAC switch should not be in ARM position, because if so the plane aerodynamic behaviour is not optimal for flying arround and the planse works unnecessarily against aerodynamic forces and maybe some people don't notice that.

Do you miss something for this report? Or is it not clear?

Whats the status of this issue? I added some screenshots in a higher resolution where you can clearly see that it's alligned for ~ 5° which is a way to high and a track file. I also checked the behaviour for Tibilis Lochini and it's the same issue, it seems that they are all aligned for 5° instead of 3° since a while: Batumi: Tibilis Lochini: batumi_landing_5deg.trk

Hello, I noticed that the ALS for Batumi is not adjusted for 3° as described in the aerodrome chart. In this example, there are allready 3 red lights at a ~5° approach angle. I haven't checked if it's an issue for Batumi only or if other airfields are affected as well.

How can I detach the TGP from the gun piper to use the TGP for searching targets in AG mode with gun selected?

After firering rockets in CCIP mode, it's not possible to switch to GBU-12 (e.g.) and use them in CCRP mode in the store page (choosing "Auto" mode). It looks that it's not neccesarry to fire the rockets (see secnod track file), so I guess it happens after CCIP has been calculated somehow... ccrp_bug2.trk ccrp_bug.trk

Then CNN are fake news CNN: "The tone is a signal to the pilot that the missile has been fired and is on it's way to the target"

Hello, more a question, maybe a bug, but at 1:10 there is a tone and later, it's explained that this tone appears when firering an AMRAM. Why we don't have this tone in our DCS Viper (And maybe other modules)? I guess it could be a usefull feature because sometimes I don't really know if the fox is on the hunt till I see the smoke after a few seconds...

I just was happy to see some improvements here. I guess they did them but they hadn't finished them because they aren't in the logs, and there was no mini update etc. I hope to see more hornet improvements in the next updates and an explanation how it should work, but I'm still impressed by the lastest open beta and the implementation of multi threading is an acceptable reason that the Hornet needs to stand behind this time...

Hi, setup as follows: 0. Create a mission with a group of severals vehicles and use litening TGP with AGM-65F and start the mission. 1. Setup: Left DDI: Store => AGM-65F; Right DDI: TGP 2. Make TGP SOI by pressing Sensor Control Swicht (=SCS) - right 3. Move the TGP over a moving target, press SCS - right twice if TGP is over the target, so that you have 2 vertical lines and the TGP follows the target 4. Press Throttle Designator Controller (=TDC) Depress, so that the offset cursor (cross) appears 5. Move the "offeset cursor" over any vehicle of the group using TDC Left / Right / Up / Down or it's axis 6. Press SCS - left to make the AGM-65F SOI. If you done everything right, the maverick is following the target 7 (Sometimes) if the Maverick does not track the target, press TDC - Depress again 8 Press Weapon Release Button 9 Press SCS - right again to make the TGP SOI 10 Repeat steps 5 - 9 for any other vehicle of the group I also added the track of the youtube video, so you can take controll at any time or just use the mission... Hope that helps... mav_yt.trk

Seems to be fixed now, thank you!

I noticed that using the litening targeting pod in moving target mode in track mode, it's possible now since the last update to control the maverick seaker with the tdc. That means now it's possible to assign several target without losing the track, which is great improvment After moving the cross over the target, which appears if TGP is SOI pressing TDC down, you have to make the Maverick SOI, then it will acquire the target lock... I haven't seen this feature somewhere else, so I made a short video...

Can confirm this. A Maverick will be destroyed by the explosion of another Maverick even on a distance of > 130m. null See track file @ 8:01:40 tmp.trk

The FLIR of the AGM-65D is extremly bad compared to previous versions as I remember. Even from a distance of just 3.4 miles it's hard to recognize targets. null bad_agm_flir.trk

From the manual: “[SIDE NUMBER], [SHIP CALLSIGN] marshal, CASE II/III recovery, CV-1 approach, expected BRC [CARRIER HEADING], altimeter [PRESSURE]. [SIDE NUMBER], marshal mother’s [MARSHAL RADIAL BEARING] radial, [DISTANCE] DME, angels [ALTITUDE]. Expected approach time is [TIME]” However, there is no info if recovery is caseII or caseIII: I'm also not sure if BRC means final bearing? case2or3.trk

From the manual: But there is no push time in the communication after the established call: I know that this should be called at DME 21 e.g., but my question is how do I know when I have to be at DME 21?

when I use "Takeoff from runway" I recive this depature calls. By using "Takeoff from parking hot" it will not be transmitted. no_com.trk

Does "Ground units are now more visible on A-G radar." means that stationary, not moving units will be more visible in map mode?

@BIGNEWY, and could the team take a look on it and confirm it as a bug?

What is the point of this feature? Is it just to select an PDLT and see it on the HUD / Helmet? Will it be possible to command the FCR to aquire a STT from a PDLT? Will it be possible to fire an AIM120 to a PDLT without STT? (Should be possible technicaly because the AIM-120 is steered anyway by a kind of "datalink" till it goes pitbull) Will it be possible to command the wingman to engage my PDLT?

I guess the issue is that after dropping JDAMS, the gun crosshair is aligned for "Sea Level". That means for Sea Level it's still correct, but as soon as you attack something higher than sea level, it's not accurate anymore. However, it seems that ED has not set the priority for finxing bugs of the Hornet and bring it out of early access very high, priority seems to be on Apache and Viper atm...

As told before, I guess I a can explain the behaviour much better know: That the missile will not loft is just a result of a wrong calculted distance to the designated waypoint because the missile amis not the waypoint but instead the intersection point of the line of sight on launch and the terrain (The point where the line of sight intersects the terrain for the 'first time'). I have updated the description.

harm crash 5.trk @BIGNEWY Here it's another track file. You are right the missile will loft, but it's hits the montain anyway. I guess it aims the intersection point between the line of sight on lanch and the terrain which is between the missile and the waypoint at launch. See, on the first two missile launches, the is terrain between missile at launch and the waypoint, so the missile aims the inteseciton point of the terrain. On the third launch, the runway where the waypoint is positionized is in sight and the missle impacts exact on the runway.

Did you tried Right Shift + END key ? Action is called "Throttle OFF"