There has been some good question, useful suggestions and bug reports in this threat, so please allow me to answer them all in one post. This may form some kind of FAQ
Oh, and again, thank you, everyone, for your feedback and all comments.
Yes, it's a good idea to let Jester finish slewing the pod to the desired location before using a search command as his default behaviour is to consider what is under the cross to be the search centre.
Jester automatically designates the targets he finds after using search command if they are in laser range. He should also automatically track those targets and use all modes to do it efficiently: AREA, POINT and QDES (although he uses this one mostly to recentre on the target after heavy manoeuvring). Manual QDES is not necessary and usually would result in worse results as selecting QDES will stop following the target. Finally, using QWP undesignates (LANTIRN feature not Jester) so you will be unable to use QDES. Since this can be confusing, QDES will be available from the Q modes menu only when a valid designated point is available.
LANTIRN is unable to spot other lasers, sorry.
That was how we taught Jester - always follow the circle and it worked like that in our tests. I'll investigate it since your observations suggest a bug. Could you describe your procedure of using QEYEBALLS more precisely?
This seems to be a bug because the relative location of the dot is exactly the input that we send to the LANTIRN pod. Could you give us more details which would be helpful in reproducing this behaviour?
I couldn't find in all available documentation any hint suggesting that the LANTIRN pod contained ballistic data for non-guided bombs so only the laser guided bombs are supported.
I suppose the issue is that the circles are displayed as if they were very far from you while the VDI display is quite close. I'll see if we can attach the circle to a physical position in the cockpit for the VR users.
That's a bug, and the fix is already uploaded to ED. Apparently, Jester thought that all static aircraft are dead. I'm dead serious.
Just use the option to deactivate Jester from the menu, submenu "crew contract". However, there is a bug in the current version which makes Jester unable to wake up from his nap. The bug has been fixed already and the patch is uploaded to ED.
When launching hot (either air or ground start), the pod is ready to go and aligned. If you use a cold start slot, Jester will switch the pod to on as a part of the startup procedure. However, we missed one scenario where you hot stat on the ground but then rearm. In such a case Jester did nothing until he was asked to switch to A/G. After your reports, we implemented new behaviour. Jester will turn the pod on always when the aircraft is on the ground and running, which should cover the rearm situations. Also, if you rearm within 4 minutes from hot spawning, the pod should be already aligned and cooled down, as if it had been installed when you entered the aircraft. We hope that should help in typical multiplayer scenarios where you rearm after getting into the aircraft.
That's a very good suggestion and we've been thinking about it. However, we didn't want to change the default behaviour of the A/G mode for those who had started using the F-14 as in the Bombcat role long before the release of the update. Depending on the feedback and future testing, we may add Jester selecting the bombs automatically if only one bomb type is loaded.
If the marker is too far away, LANTIRN may not enter the AREA mode. Jester has a time limit to enter a mode in which the pod will track the point itself. When that limit is hit, he'll just assume that it's impossible to track the point. We may want to add a voice feedback when such situation happens.
Unfortunately, he is unable to track structures unless they are placed as static objects in the mission. This is a design choice and it won't change. The pod is able to track any object. However, the abundance of the objects in the scenery would make searching for targets offering some reasonable return of interest for a GBU very tedious.
Jester should stow the pod when you select the landing mode and lower the landing gear, or after you land.
Actually, Jester lasers only when "laser always on" is selected. Normally, Jester uses auto-lasing offered by the pod. That's why you can see 'A' in front of the laser code on the display. Nevertheless, if you need longer lasing time, just ask Jester to lase constantly from the second page of the Jester LANTIRN menu.
Jester loved his new skills so much that he doesn't want to share the LANTIRN stick any more. If you want to operate the pod yourself, you may want to disable Jester from the "crew contract" submenu.
Jester, like any human, can memorise some things. For example, he memorises potential targets that he identifies when he looks at his display. Unfortunately, he likes to target first those objects which he spotted first. That's why you may see him moving away from the crosshair and picking other targets. We know how to fix this, and we prepared a dedicated class when we plan to teach Jester to move to the close target first. Unfortunately, this is not ready yet but should be available in November or December.
Additionally, we plan to improve his search logic further. It's a challenging task because we can't analyse the video feed, and we need to emulate Jester vision using synthetic information about the objects inside the pod field of view. By construction, it can never be as realistic as you using the VDI, but our goal is to get as close as possible, and the initial release of Jester LANTIRN is only the first step of this process.
I'm adding it to the TODO list. We should be able to ship it in November or December.