Jump to content

Recommended Posts

Posted

I tried several times, I created a simple mission to test it but neither the agm-65E nor the gbu-12 are guided by the hornet tgp laser. Strange even the flir pov button I bound to the WH throttle doesn't work anymore. Open beta, already repair/cleanup, no mods.

Bug pod.trk

PC: i7-13700K - Gigabyte RTX 5080 GAMING OC - 64GB DDR5 6400 - VPC MongoosT-50CM3 - VKB GF pro - MFG Crosswind - Msi MPG321UR-QD + LG OLED 32GS95UE - TrackIR5 - Quest 3

Posted

Flir POV wont work with TGP if you have a maverick called up on another ddi. Mav takes priority regardless of SOI.

 

What are you steps for lasing the target?

Working fine here with latest OB.

 

 

 

Sent from my SM-A530W using Tapatalk

[sIGPIC][/sIGPIC]



 

Amd Fx 8350 4.3 GHz - MSi Gtx 1060 6gb - 16gb DDR3

 

A-10C - AV8B - F-5E - Mig-21 - FC3 - CA - UH-1H - Black Shark - AJ3-37 - M-2000C - F-16C Viper - F-86F - Spitfire - Fw-190 - F/A-18C - F-14 - Normandy - NTTR - Persian Gulf

Posted
Flir POV wont work with TGP if you have a maverick called up on another ddi. Mav takes priority regardless of SOI.

 

The procedure I follow, as you can see in the track: AG mode, all 3 forward switches (tgp, laser). I select the MAV, I enter the code, the MAV moves to the target selected by the TGP, I shoot the laser, the word LTD/R comes out, but in the MAV E display the full green square does not come out, and I can't shoot it, same thing with the GBU, it doesn't follow the laser, even if I press the trigger and the word LTD/R comes out. I haven't used the hornet for a while, but I've never had problems before..

PC: i7-13700K - Gigabyte RTX 5080 GAMING OC - 64GB DDR5 6400 - VPC MongoosT-50CM3 - VKB GF pro - MFG Crosswind - Msi MPG321UR-QD + LG OLED 32GS95UE - TrackIR5 - Quest 3

Posted (edited)
I tried several times, I created a simple mission to test it but neither the agm-65E nor the gbu-12 are guided by the hornet tgp laser. Strange even the flir pov button I bound to the WH throttle doesn't work anymore. Open beta, already repair/cleanup, no mods.

 

Strange little bug you've found, it seems it might be due to the static target, the laser is working and the L-Mav can even see it i.e. the L-Mav search stops/tracks the laser spot.

 

However the L-Mav can't lock on the laser spot (it behaves as if it didn't recognise the code ? ),

 

lCVkWWa.jpg

 

Moving the laser spot to the ground in front of the building, the L-Mav locks ok.

 

gmoWij1.jpg

 

Stripping out the track data and re-saving the mission under 2.5.6.47404, seemed to fix the issue and I'm no longer able to reproduce the problem (unless taking control of the original track).

Edited by Ramsay

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted

Really strange, I'll try to remove the hornet and reinstall it. It doesn't work even if I use scripts like moose or cltd to lase the target with a jtac...

PC: i7-13700K - Gigabyte RTX 5080 GAMING OC - 64GB DDR5 6400 - VPC MongoosT-50CM3 - VKB GF pro - MFG Crosswind - Msi MPG321UR-QD + LG OLED 32GS95UE - TrackIR5 - Quest 3

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...