maxTRX Posted September 2, 2019 Posted September 2, 2019 I noticed some issues with GBU16's picking up my TGP's laser in early morning sun... from some angles. (could be related to something entirely different:D) At night targeting the same vehicles worked perfectly every time. Now... the vehicles I was targeting have certain anti-reflective features:smilewink: so that might be another story. Same goes for L Mavs. They would not lock on these vehicles... no problem at night. Mav F worked like a champ every time in every condition! Another (already reported) issue is TTI on HUD... always starts at 99 regardless of altitude and distance and keeps counting long after impact.
Gierasimov Posted September 2, 2019 Posted September 2, 2019 I have got similar mission time if not the same (as per your Z time on HUD) in PG and all TGP lased bombs find their targets. My TTI is correct as well. Latest beta version. Intel Ultra 9 285K :: ROG STRIX Z890-A GAMING WIFI :: Kingston Fury 64GB :: MSI RTX 4080 Gaming X Trio :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta
Gierasimov Posted September 2, 2019 Posted September 2, 2019 (edited) However, I never tried to drop 4 bombs at the same time. Did you try with another ground target? Edited September 2, 2019 by Gierasimov Intel Ultra 9 285K :: ROG STRIX Z890-A GAMING WIFI :: Kingston Fury 64GB :: MSI RTX 4080 Gaming X Trio :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta
Preendog Posted September 2, 2019 Posted September 2, 2019 (edited) In the 2:50 Maverick part, you didn't turn the laser on. In the bomb miss, I think your target point was wrong. When you fly over the target, your altitude shows 13900 feet, but the distance to W1 is only 1.8nm (should be 2.3 or more). edit. That may have just been due to the target's altitude, or maybe not. Maybe check if W1 is set to ground level, or hovering some distance above. Edited September 2, 2019 by Preendog
maxTRX Posted September 2, 2019 Author Posted September 2, 2019 In the 2:50 Maverick part, you didn't turn the laser on. In the bomb miss, I think your target point was wrong. When you fly over the target, your altitude shows 13900 feet, but the distance to W1 is only 1.8nm (should be 2.3 or more). edit. That may have just been due to the target's altitude, or maybe not. Maybe check if W1 is set to ground level, or hovering some distance above. WPT 1 was not co-located with the targets. @Gierasimov - I flew few approaches from different directions and couple of times the GBU's tracked. The TTI has consistently been wrong since before the latest beta... I'll look into this... perhaps I deleted more then FXO and Metashaders2:noexpression: @Preendog - well, it must've been double button or multi-button press that I didn't notice... like I said I've deployed L Mavs before with 100% success rate. Well, there is a chance something got borked up on my rig recently.
maxTRX Posted September 2, 2019 Author Posted September 2, 2019 OK... I'll take the L Mavs out of this. After re-configuring some of my buttons and switches the laser stays on. I made 4 flights in daylight and night time and Mav E tracked with no problems. I'm still trying to solve GBU16 issue: At night tracks every time, in the early morning... inconsistent. Perhaps ED simulates pilot's hangovers from night before... … and the TTI issue still stands. Giving reputation back to L Mavs (100% hit rate): https://youtu.be/_XJrvdVmI4M
maxTRX Posted September 3, 2019 Author Posted September 3, 2019 resolved! I resolved the issue, actually 2 issues... First, the TTI countdown - I switched to Caucasus theater and setup a mission with a moving ship (oil tanker) and using GBU16x2 and x4. The TTI after release from 16k @ M.7 level was 30 sec:) Dead on hits every time. Went back to PG. Voila... TTI was 30sec for identical release. Hits every time. Second issue with GBU's not tracking sometimes (perceived laser issues:doh:) It was my effing Warthog, TDC depress function to be specific. I put a hell of a dead zone and tweaked the axes and now it works OK. I blamed the confusion on this morning's hangover:noexpression: As far as TTI is concerned... I have no idea why it started working correctly after visiting Caucasus theater. The only difference I see is FXO and Metashaders2 folders are filled with lots of files. In PG theater these 2 folders contained only 1 file each... at least on my install.
Recommended Posts