Buzpilot Posted October 18, 2013 Posted October 18, 2013 Should Maveric's after locking on target loose lock, if you go back to TGP display? i5 4670 - Sabertooth Z87- GTX Titan - Dell U3011 30" - 2x8GB RAM 1800 - Samsung 840 EVO 512GB SSD - Warthog HOTAS - CH Pro pedals - TrackIR5 - Win7 64bit EVERYTHING IS SUBJECT TO CHANGE :thumbup:
ralfidude Posted October 18, 2013 Posted October 18, 2013 different system. You can have the TGP on the left, and the maverick on the right MFD running at the same time. They don't work dependent on each other. [sIGPIC]http://i17.photobucket.com/albums/b66/ralfidude/redofullalmost_zpsa942f3fe.gif[/sIGPIC]
Buzpilot Posted October 18, 2013 Author Posted October 18, 2013 different system. You can have the TGP on the left, and the maverick on the right MFD running at the same time. They don't work dependent on each other. Thats why I ask, irl they are independent, and switching page on one screen should not change anything. like for eksample if you change from TAD to DSMS, and back, you don't loose or reset anything there. I consider using 2 different screens a workaround, but will it stay like that for ever? i5 4670 - Sabertooth Z87- GTX Titan - Dell U3011 30" - 2x8GB RAM 1800 - Samsung 840 EVO 512GB SSD - Warthog HOTAS - CH Pro pedals - TrackIR5 - Win7 64bit EVERYTHING IS SUBJECT TO CHANGE :thumbup:
Guest Izoul123 Posted October 19, 2013 Posted October 19, 2013 (edited) Thats why I ask, irl they are independent, and switching page on one screen should not change anything. like for eksample if you change from TAD to DSMS, and back, you don't loose or reset anything there. I consider using 2 different screens a workaround, but will it stay like that for ever? It will stay locked as long as it's within parameters to keep the MAV's war-head/cone sensor on it/correct range. If you move out of these parameters, the MAV will lose lock yes quite easily, it's way more finicky than the TGP to 'hold lock' as far as plane maneuvering ranges go. However you could switch back to the TGP then to reacquire/TMS UP long/china hat forward long/MAV SOI, then line up again if need be. At least I think that's what you are asking :lol: The retort would be why not select the MAV's first in the DMS, then left MFD to TGP, right MFD to MAV. Then use TGP as SOI, line your stuff up and go from there? That's how I do it. Extremely easy/efficient. Edited October 19, 2013 by Izoul123
Derbysieger Posted October 19, 2013 Posted October 19, 2013 The retort would be why not select the MAV's first in the DMS, then left MFD to TGP, right MFD to MAV. Then use TGP as SOI, line your stuff up and go from there? That's how I do it. Extremely easy/efficient. Or you can just use DMS left/right with HUD as SOI (Coolie Hat up short) to switch between weapon profiles. Much faster than using the DSMS page and as a plus you keep your hands on your HOTAS the whole time. If you have the mav page on one MFCD you can change your SOI from HUD to Mav with China Hat fwd short. CPU: AMD Ryzen 7 9800X3D | Mobo: ASRock X870E Taichi Lite | RAM: 96GB DDR5-6000 CL30 | GPU: ASUS RTX5090 32GB ROG Astral | SSDs: 3xSamsung 990 Pro 4TB M.2 Peripherals: Warthog HOTAS | Virpil MongoosT-50CM3 Base | TrackIR 5 | MFG Crosswinds | 3xTM Cougar MFDs | HP Reverb G2
Buzpilot Posted October 19, 2013 Author Posted October 19, 2013 (edited) It will stay locked as long as it's within parameters to keep the MAV's war-head/cone sensor on it/correct range. If you move out of these parameters, the MAV will lose lock yes quite easily, it's way more finicky than the TGP to 'hold lock' as far as plane maneuvering ranges go. However you could switch back to the TGP then to reacquire/TMS UP long/china hat forward long/MAV SOI, then line up again if need be. At least I think that's what you are asking :lol: The retort would be why not select the MAV's first in the DMS, then left MFD to TGP, right MFD to MAV. Then use TGP as SOI, line your stuff up and go from there? That's how I do it. Extremely easy/efficient. Looks like I got it wrong, I asumed it was because I changed back to TGP, but that was after I missed. Kind of strange what happened here. 0:50 I made the Point to SPI, TMS forward long, using laser too. 1:13 I locked the target at SPI, 6.4 Miles away (Edit it looks like it actually moved slightly too, did it lock onto the streetlight source, even if it was during day? I need to get some sleep :)) But when I 2:06 use China Hat Forwrd Long (Slave all to SPI), it moved away, to where Maveric hit ground, just because TGP was blocked, AFTER i shot? Could be I'm just expecting too much, irl a failed lock on Maveric would not migrate to TGP too. And ofc, at the end I was hit by a Sa-19 Radio Command/ Semi Active, and I was still on standby on ECM panel. But no missile warning at all? Here's the end from a different perspective. I would have provided the trackfile, to make things easier to look at, but it was 21MB large, and there's no way to shorten it. Edited October 19, 2013 by Buzpilot i5 4670 - Sabertooth Z87- GTX Titan - Dell U3011 30" - 2x8GB RAM 1800 - Samsung 840 EVO 512GB SSD - Warthog HOTAS - CH Pro pedals - TrackIR5 - Win7 64bit EVERYTHING IS SUBJECT TO CHANGE :thumbup:
amollen Posted October 19, 2013 Posted October 19, 2013 I almost always use the TGP to lock the target first and set the SPI, then I let the Mav slave to the SPI and shoot. (1) The TGP has much better zoom so you can identify and lock from much further out and (2) the TGP maintains the lock better than the Mav
Buzpilot Posted October 19, 2013 Author Posted October 19, 2013 I almost always use the TGP to lock the target first and set the SPI, then I let the Mav slave to the SPI and shoot. (1) The TGP has much better zoom so you can identify and lock from much further out and (2) the TGP maintains the lock better than the Mav I do too, but here when I slaved to SPI the second time, it changed position to 15m behind the target. ( I see I didn't mention first time I slaved it) i5 4670 - Sabertooth Z87- GTX Titan - Dell U3011 30" - 2x8GB RAM 1800 - Samsung 840 EVO 512GB SSD - Warthog HOTAS - CH Pro pedals - TrackIR5 - Win7 64bit EVERYTHING IS SUBJECT TO CHANGE :thumbup:
txmtb Posted October 19, 2013 Posted October 19, 2013 To get the most accurate SPI out of the TGP I make sure it is in Point Mode, and the laser is on before TMS Up to create the SPI. It seems if I don't use the laser, the SPI will be a point beyond the target, like it was looking through the target. Win 10 64 Pro, MSI Z390 I7-9700K @5ghz Kraken Z63, 32Gb Corsair Dominator, MSI RTX-2070, 1TB NVME 2TB SSD's, TM Warthog, Pro Rudders, OpenTrack w/ IR Clip
ralfidude Posted October 19, 2013 Posted October 19, 2013 On 2:06 you didnt press TMS up to set new SPI. That's what happened I think. So when you did china for long it went to the last known SPI, that being the last place you shot at. It's a common issue, it still happens to me when I think I held down the TMS up long enough to set a SPI but in fact I hadn't and my maverick goes totally fubar. At least that's what it looks like what happened. [sIGPIC]http://i17.photobucket.com/albums/b66/ralfidude/redofullalmost_zpsa942f3fe.gif[/sIGPIC]
Luzifer Posted October 19, 2013 Posted October 19, 2013 To get the most accurate SPI out of the TGP I make sure it is in Point Mode, and the laser is on before TMS Up to create the SPI. It seems if I don't use the laser, the SPI will be a point beyond the target, like it was looking through the target. Of course it will "look through" the target, it can't take the target into account simply from the optical image. It takes the planes location and orientation as well as the direction the sensor is pointing and computes the location of the SPI as the point where line of sight intersects with the ground (according to a detailed terrain elevation map). The shallower the angle and the higher above the ground you target, the more pronounced the effect. As soon as you use the laser, it will combine the range measurement from the laser with the position and line of sight data to compute the correct SPI location above ground.
Recommended Posts