 |
| Clicking on Air Surv will abort current FCR operation and switch to an active air scan (air surv mode) |
The keyboard command list is looking horrible if you want full control over this. The shot cut keys work fine however. I made some tweaks to the heading tape symbols and the Air Surveillance Mode has been adjusted according to recent feedback posted. No sweep indicator is displayed (? is that correct) but the radar is still active. And not NTS or targeting is available. This mode is not available if either crew station has FCR as the selected sight. Either crewman selecting FCR or cycling through HMD/TADS/FCR will cancel this mode.
I made attempts to smooth out the logic for simple joystick control so you can hot key from mode to mode.
FCR Scan and FCR Scan burst will cancel each other out with immediate effect, no waiting for a scan cycle to complete (which is what it did before).
I'll adjust the scale of the FOR box shortly. The dot isn't active yet, will fix that shortly and then I'll correct the cue dots in the HMD,
That will be as much time as I want to spend on the FCR. I think it's not too shabby and does nearly everything it needs to do for now. Completing the command list for the sensors now means I can finish the default control setup for new installations.
For full control on a joystick you need 3 hats minimum.
- 4 Way Sight Select (HMD, TADS, FCR)
- 4 Way FCR Mode Select (GTM, ATM, other to come)
- 4 Way FCR Footprint Set (Zoom, Wide, Medium, Narrow)
There are also keys assigned to FCR Mode Cycle Up/Down to keep the control count down on smaller sticks.
As always if I've got it wrong then please leave some feedback however I'm unlikely to embark on any more major changes for now. Quite pleased with the detail and how it works.
Id say that KDU looks good enough... Does it have dual state buttons?
ReplyDeleteI'm wondering if the FCR can be aimed up/down for faster scanning in the real apache?
Rich, AIR SURV option is not presented if FCR is the active sight. It is replaced by "MTI ONLY", if you switch to TADS or HMD as your active sight then AIR SURV is available.
ReplyDeleteWill more details added later on? Are you trying to push a beta out?
ReplyDeleteAs always it's a work in progress. No doubt we'll return to it post release but I need to nail down the basics and not get hung up on too much detail.
ReplyDeleteI'll fix the bits from yesterday and the rest will have to wait till beta.
BTW The MPDs look like they will fit beautifully on an eight-inch Android tablet screen, they can be picked up really cheaply.
ReplyDelete@jefffyd123 by dual-state buttons you mean up/down graphics on the keys?
ReplyDeleteNo it was quickly thrown together using mousezones and sending the input string to the TComputer message handler. Literally a 10 min job (plus 15 to prepare and export the bitmap font atlas).
It's still quicker to use the chat console. IF this is something we want to keep I think I'll make it a mode of the chat console (which incidentally can be toggled on some MPD UTIL pages). Currently it doesn't accept keyboard input but could easily enough.
ya the up/down graphic, sorry
ReplyDeleteI see, so the KBU isnt used for the Nav computer I guess.... more for show maybe.
After thinking about it for a minute, I wouldnt bother using it for chat personally.... Id just use the PC Keyboard.
I'm wondering if the FCR can be aimed up/down for faster scanning in the real apache?
ReplyDeleteScan elevation can be adjusted yes...
thanks bushmaster
ReplyDeleteI only recently added the air targeting mode sector scan and the ability to pivot the FCR offset for that mode.
ReplyDeleteIt works much like it does in LB2, only prettier :)
They way I've coded the radar is that classification happens after the first full complete scan burst. So narrowing the scan duration by adjusting the wedge size and direction will give you an edge in response times.
Couple of things. MTI ONLY was mentioned as a function of GTM. Is this to do with filtering mobile tracks using Doppler shift?
And finally, I fixed up the CPG and Pilot High Action Display regions. Someone with keen eyes spotted in the above screens the pilot position is selected (source is prefixed with "P") but the field of regard box has the CPGs 90 degree tick marks. Now corrected and the scale has been adjusted also.
I may add the ZOOM function at some point. Is this used a lot? At all? Because my vector fonts are slightly bigger than the real ones it makes it hard to fit but is possible to move the FCR count up into the corner.
There's one last command for the source selector to add. "Link" as clearly visible on the control grips next to HMD, FCR, TADS. From what I gather this should move the FCR centreline to the selected source? So if TADS is the selected source then pressing Link will rotate the FCR (if not active) to the position in the TADS. And position TADS to look at the location indicated by the FCR's NTS target?
That makes sense to me and how I want to implement it. Now you're going to tell me it's all wrong :)
You got it mostly right :) I will comment later..
ReplyDeleteBy zoom, do you range adjustment of the FCR or a sort of zoom "cheat".
ReplyDeleteI would think (unofficially) the range adjustment would be crucial.
Zoom is used on MPD presentation to establish better target separation. We don't adjust the range like Viper pilots do. On a given GTM/RMAP mode arcs and tic marks show us our range at all times which always the same. Max FCR tgt range display (on HMD/TEDAC) is 9.9km.
ReplyDelete