CptTangerine Posted November 29, 2018 Posted November 29, 2018 Hi I have been practising using the Mavericks with the DMT. I lock the target by putting the marker on the target and pressing the DMT action button (it isn't set to the toggle mode) and then slew the DMT until it is over the target. I then push the sensor select switch fore to select IRMV. The mav doesn't lock so I press the DMT action button again (as has been described in some of the video tutorials) to try to persuade it to lock. Instead of locking the DMT locks onto wherever I am pointing as a new target area and the mav's focus follows it. Am I missing something or has the setup changed recently? I am getting pretty close to the target and the mav isn't locking. I just get to a certain distance and the cross-hairs disappear rather than focusing in on the target. I have had this working in the recent past so I'm not sure why it isn't working now. I am doing a cold start on the Tarawa with Red Kite's tutorial scenario so it is possible that I am not switching on a system that I should be switching on at startup. Any suggestions gratefully received. Cheers! CptT CPU: Intel Core i5 4590 3.3GHz, RAM: 32GB HyperX Fury 1600MHz DDR3, GFX: EVGA GTX 1080, OS: Windows 7 Home Premium SP1, Joy: TM Warthog, Peds: CH Pro Pedals, TrackIR3, VR: Vive
Lixma 06 Posted November 29, 2018 Posted November 29, 2018 I think it's a bug with IR Mavs and cold starts (or re-arms) not playing nice with each other. Try them from a mid-air mission start - they've worked OK for me that way.
Shadow_1stVFW Posted November 29, 2018 Posted November 29, 2018 Which DMT button are you pressing? SSS Down or TDC down? Sent from my SM-G960U using Tapatalk Aurora R7 || i7K 8700K || 2TB 7200RPM SATA 6Gb/s || 2TB M.2 PCIe x4 SSD || GTX 1080 Ti with 11GB GDDR5X || Windows 10 Pro || 32GB Dual Channel DDR4 at 2667MHz || Virpil Warbird Base || Virpil T-50 Stick || Virpil MT-50 Throttle || Thrustmaster TPR Pedals || Oculus Rift
CptTangerine Posted November 30, 2018 Author Posted November 30, 2018 Thanks. It will be annoying if it is a bug. I'm pressing the TDC down not the SSS (although I have tried both). CPU: Intel Core i5 4590 3.3GHz, RAM: 32GB HyperX Fury 1600MHz DDR3, GFX: EVGA GTX 1080, OS: Windows 7 Home Premium SP1, Joy: TM Warthog, Peds: CH Pro Pedals, TrackIR3, VR: Vive
feefifofum Posted November 30, 2018 Posted November 30, 2018 1. Slew DMT/TGP to target 2. Confirm maverick displays "RDY" on stores page 3. Uncage maverick. Mav seeker should slave to DMT/TGP 4. Select maverick with sensor select on HOTAS (IRMV boxed on HUD) 5. Press FOV soft key on maverick MPCD to switch to narrow seeker FOV (zoomed in) 6. TDC action to lock maverick seeker 7. Profit! THE GEORGIAN WAR - OFFICIAL F-15C DLC
CptTangerine Posted November 30, 2018 Author Posted November 30, 2018 Thanks for that. Do you think that the fact that I'm not zooming in on the display is causing the DMT to unlock when I press the the TDC action switch? I haven't got time to test it tonight. CPU: Intel Core i5 4590 3.3GHz, RAM: 32GB HyperX Fury 1600MHz DDR3, GFX: EVGA GTX 1080, OS: Windows 7 Home Premium SP1, Joy: TM Warthog, Peds: CH Pro Pedals, TrackIR3, VR: Vive
CptTangerine Posted November 30, 2018 Author Posted November 30, 2018 As a matter of interest, the TV is coming up on the right hand MPCD and the Mav IR screen is coming up on the left. When I select the Maverick as the SOI the TV image doesn't go away. Is this normal? CPU: Intel Core i5 4590 3.3GHz, RAM: 32GB HyperX Fury 1600MHz DDR3, GFX: EVGA GTX 1080, OS: Windows 7 Home Premium SP1, Joy: TM Warthog, Peds: CH Pro Pedals, TrackIR3, VR: Vive
Shadow_1stVFW Posted December 1, 2018 Posted December 1, 2018 As a matter of interest, the TV is coming up on the right hand MPCD and the Mav IR screen is coming up on the left. When I select the Maverick as the SOI the TV image doesn't go away. Is this normal?Yes. Two different sensors are providing those feeds Sent from my SM-G960U using Tapatalk Aurora R7 || i7K 8700K || 2TB 7200RPM SATA 6Gb/s || 2TB M.2 PCIe x4 SSD || GTX 1080 Ti with 11GB GDDR5X || Windows 10 Pro || 32GB Dual Channel DDR4 at 2667MHz || Virpil Warbird Base || Virpil T-50 Stick || Virpil MT-50 Throttle || Thrustmaster TPR Pedals || Oculus Rift
CptTangerine Posted December 1, 2018 Author Posted December 1, 2018 Brilliant thanks! I'll give that a go when I get some gaming time. CPU: Intel Core i5 4590 3.3GHz, RAM: 32GB HyperX Fury 1600MHz DDR3, GFX: EVGA GTX 1080, OS: Windows 7 Home Premium SP1, Joy: TM Warthog, Peds: CH Pro Pedals, TrackIR3, VR: Vive
mvsgas Posted December 1, 2018 Posted December 1, 2018 Thanks for that. Do you think that the fact that I'm not zooming in on the display is causing the DMT to unlock when I press the the TDC action switch? I haven't got time to test it tonight. The system is suppose to lock when you release the TDC action. To whom it may concern, I am an idiot, unfortunately for the world, I have a internet connection and a fondness for beer....apologies for that. Thank you for you patience. Many people don't want the truth, they want constant reassurance that whatever misconception/fallacies they believe in are true..
CptTangerine Posted December 1, 2018 Author Posted December 1, 2018 So, I should be holding the TDC action button down the whole time until I get the Mav IR screen up slaved to the daylight TV? Is this why there is a toggle option for the button? CPU: Intel Core i5 4590 3.3GHz, RAM: 32GB HyperX Fury 1600MHz DDR3, GFX: EVGA GTX 1080, OS: Windows 7 Home Premium SP1, Joy: TM Warthog, Peds: CH Pro Pedals, TrackIR3, VR: Vive
Shadow_1stVFW Posted December 1, 2018 Posted December 1, 2018 No. You don't need to. The system slews a little slower for finer control while the TDC is depressed. When released, yes the system will lock. But you can slew without depressing the TDC and the system will still lock (albeit after a second or two). In practice I haven't seen much of a difference between sleeping with the TDC depressed or not in the Sim. But that is how it should work. Sent from my SM-G960U using Tapatalk Aurora R7 || i7K 8700K || 2TB 7200RPM SATA 6Gb/s || 2TB M.2 PCIe x4 SSD || GTX 1080 Ti with 11GB GDDR5X || Windows 10 Pro || 32GB Dual Channel DDR4 at 2667MHz || Virpil Warbird Base || Virpil T-50 Stick || Virpil MT-50 Throttle || Thrustmaster TPR Pedals || Oculus Rift
CptTangerine Posted December 2, 2018 Author Posted December 2, 2018 So, really, it's a case of pointing the Mav seeker head at the target with the TV, switching to IRMV mode, and then just waiting for it (hoping for it) to lock? CPU: Intel Core i5 4590 3.3GHz, RAM: 32GB HyperX Fury 1600MHz DDR3, GFX: EVGA GTX 1080, OS: Windows 7 Home Premium SP1, Joy: TM Warthog, Peds: CH Pro Pedals, TrackIR3, VR: Vive
Shadow_1stVFW Posted December 2, 2018 Posted December 2, 2018 So, really, it's a case of pointing the Mav seeker head at the target with the TV, switching to IRMV mode, and then just waiting for it (hoping for it) to lock?You need to be close enough for the system to pick up the contrast in the image. So, kind of. Most times you still need to depress the TDC to lock. Sometimes it'll lock by itself. Sent from my SM-G960U using Tapatalk Aurora R7 || i7K 8700K || 2TB 7200RPM SATA 6Gb/s || 2TB M.2 PCIe x4 SSD || GTX 1080 Ti with 11GB GDDR5X || Windows 10 Pro || 32GB Dual Channel DDR4 at 2667MHz || Virpil Warbird Base || Virpil T-50 Stick || Virpil MT-50 Throttle || Thrustmaster TPR Pedals || Oculus Rift
CptTangerine Posted December 4, 2018 Author Posted December 4, 2018 I have got it working. Thanks for all your help! It seems that what works for me is locking up the target on the DMT TV then uncaging the Mav, putting the Mav as the SOI, then zooming and then, when I'm within 7Km pressing and holding the DMT action switch until I'm at about 6Km and releasing it. I'm not sure if it's because it's zoomed in but it doesn't unlock the target point and it does lock. I'm very relieved that this isn't a bug. Cheers! CptT CPU: Intel Core i5 4590 3.3GHz, RAM: 32GB HyperX Fury 1600MHz DDR3, GFX: EVGA GTX 1080, OS: Windows 7 Home Premium SP1, Joy: TM Warthog, Peds: CH Pro Pedals, TrackIR3, VR: Vive
Shadow_1stVFW Posted December 4, 2018 Posted December 4, 2018 I was playing around with this last night and did find that with LMAVs and the TPOD when the TPOD is in HTS mode pressing the TDC in will cause the aircraft to lock the DNT on the FPM if it is over land. This is incorrect behavior Sent from my SM-G960U using Tapatalk Aurora R7 || i7K 8700K || 2TB 7200RPM SATA 6Gb/s || 2TB M.2 PCIe x4 SSD || GTX 1080 Ti with 11GB GDDR5X || Windows 10 Pro || 32GB Dual Channel DDR4 at 2667MHz || Virpil Warbird Base || Virpil T-50 Stick || Virpil MT-50 Throttle || Thrustmaster TPR Pedals || Oculus Rift
Harlikwin Posted December 4, 2018 Posted December 4, 2018 Yeah, I occasionally have issues with locking up the Mavs. My latest weird bug (or maybe just me) is that I started on the tarawa in the gulf, took off, turned on the mav's flew to my target, and it wouldn't uncage at all. Seeker showed ready, so I'm not sure what its about. Right after that I fired up my standard start in the air Neveda Mav practice and I had no problems uncaging, and locking and firing. So I'm not sure if its that there is something different with the way the plane is setup on the runway or if its a bug, or its me. New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1) Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).
Recommended Posts