CappuccettoRosso Posted June 10, 2023 Posted June 10, 2023 Hello, I wanted to report this issue I have. I'm playing the Multi-Thread version. I also add that I love all of your modules and I hope to not bother you. First, Jester has very big difficulties finding ships with LANTIRN. He can lock on tanks barely visible on land but he can't find a ship as big as the entire display. You have to be really really close in order to have a lock on a ship from him. And of course this can be a problem when the ship fires missiles at you. But ok, I can live with that. Second, and this is not bereable, if I switch seat, controlling the RIO myself, I can just lock the ship myself. I point-track the ship correctly, set it as a target and fire the laser. Good, this way I can just get over the noobness of Jester. But as soon as I return to the pilot seat, Jester decide to remove my point-track lock and start doing weird stuff and move the LANTIRN. What I would expect: if I manually lock on a target as a human RIO, Jester should NOT interfere and not touch the LANTIRN at all. Unless, of course, there's a specific new command from the Jester Menu. I hope I have described the problem well and I thank you for your patience.
Whistler_RIO Posted June 12, 2023 Posted June 12, 2023 This is a really annoying bug since the introduction of auto-lantirn. it drives me nuts. thanks for posting about it. 1
Silhou Posted June 12, 2023 Posted June 12, 2023 (edited) Hey! Thank you very much for your report. I've tracked two issues ("Jester having difficulty to find and lock ships with LANTIRN" and "Jester overrides point track, lasing etc set by player when switching back to front seat") as DCSF14-456 and DCSF14-457 accordingly for the team to investigate. Edited June 12, 2023 by Silhou
2circle Posted August 29, 2023 Posted August 29, 2023 I'm having similar issues with Jester and his use of LANTIRN. My scenario is as follows: DCS MT, 4xGBU-16, master arm on, 1688 laser code for the pod and bombs. I find several targets located near an airbase, ingress at 22,000 at 350 kts IAS. Command Jester to cue to the appropriate waypoint (which he does), I see the target aircraft on my VDI on the ramp, I then task him to "find aircraft". After a few seconds he finds the aircraft and states "valid laser ranging". And that is it! He never provides steering cues or time to release. I have him "undesignate" and then I command him to designate using the Jester menu. Once again, he states "valid laser ranging" but again, I never receive and steering cues or TTR, and am therefore unable to release any weapons. I've tried cueing using eyeballs, using head, a variety of targets such as armor or statics, but each time the result is the same. Any help here would be appreciated - I'd rather not have to learn how to be a RIO! F-18C/F-14/P-51/F-86 Pico4/Quest2 VR with Intel Core i9 3.0GHZ 24 -Core, 16GB, GeForce RTX 4070 ti
draconus Posted September 11, 2023 Posted September 11, 2023 On 8/29/2023 at 3:06 AM, 2circle said: Any help here would be appreciated - I'd rather not have to learn how to be a RIO! Master mode -> AG VDI mode -> TV Jester -> AG -> Select weapon ->4xGBU-16 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
2circle Posted September 13, 2023 Posted September 13, 2023 As before, thanks Dranconus. The problem was the last step. Even though the Jester menu showed GBU as being selected (and the HUD indicated ORD), unless you command Jester to select the GBU's, he will never give you the talk on needed to release the weapon. On a related note, how do you find using the LANTIRN at night? I find it essentially unusable. The red filter blocks out too much light, and even with the filter removed, I can find no contrast/brightness combination that makes the VDI useful for GBU employment at night. Interestingly, the RIO's scope works fine at night. After I cue the LANTIRN to the target, the target looks great in the RIO's cockpit, but it's completely washed out on the VDI. I'm playing Open Beta DCS MT in VR in case you think that's making a difference. F-18C/F-14/P-51/F-86 Pico4/Quest2 VR with Intel Core i9 3.0GHZ 24 -Core, 16GB, GeForce RTX 4070 ti
Recommended Posts