Feature Request: Dynamic CAP Drum for F-14 RIO cockpit

[HomeFries94]

Per our discussions, I have enclosed the drum graphic to go with the proposed RIO MFD insert. Application of the categorized drums should match the following coordinates (note: these are approximate, though the width is always 210px):

Category	Start X	End X
Bit	50	260
Spl	325	535
Nav	590	800
Tac Data	860	1070
D/L	1125	1335
Tgt Data	1380	1590

MFD Pixels
Start X	325
End X	535
Start Y	350
End Y	795

Edit: Recommend onscreen placement coordinates be based mathematically on the LMFD screen position so that it adjusts accordingly whenever the LMFD position is updated.

[ScottyMac52]

Okay, awesome. I have some free time this week and this weekend so I will get started on this. We will likely have to implement this using a sub-module type of command and then the barrel selection will send the module and sub-module command.

When I come up with the command syntax I will document it and then maybe you can create a TMC test fixture for me to use?

It looks really good, I am looking forward to putting this in 2.6.

Thanks,

Scott

On Wed, May 15, 2019, 10:25 HomeFries94 notifications@github.com wrote:

Per our discussions, I have enclosed the drum graphic to go with the proposed RIO MFD insert. Application of the categorized drums should match the following coordinates (note: these are approximate, though the width is always 210px): Category Start X End X Bit 50 260 Spl 325 535 Nav 590 800 Tac Data 860 1070 D/L 1125 1335 Tgt Data 1380 1590

MFD Pixels Start X | 325 End X | 535 Start Y | 350 End Y | 795

[image: DCS F14RIO MFD] https://user-images.githubusercontent.com/6812091/57795825-ee258b80-7714-11e9-9ff8-63d5f911791e.jpg [image: F14 CAP Drum] https://user-images.githubusercontent.com/6812091/57795787-d4844400-7714-11e9-8145-93762c493d90.jpg

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ScottyMac52/MFDisplay/issues/56?email_source=notifications&email_token=ADKNOFDKXOUAMBR2VSNDJV3PVRBRZA5CNFSM4HNFM65KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GT7M3RQ, or mute the thread https://github.com/notifications/unsubscribe-auth/ADKNOFCFBA3YSW3GWZLN7B3PVRBRZANCNFSM4HNFM65A .

[ScottyMac52]

Hey, When are you releasing 2.34? I need the graphic file. ;-)

[HomeFries94]

You should be able to open these graphics and right-click to save. I have plenty left to do before releasing 2.34 (and 2.33 has only been out for a week). I also sent you the graphics on Discord.

[ScottyMac52]

Version 2.6.0 is ready to go that implements this request and fixes a few bugs.

[HomeFries94]

A recommendation for insert coordinates: the X/Y offsets for the inserts should be based on the coordinates of the original MFD JPEG rather than the screen display offsets. All overlays will be tied to the original JPEGs, so tying the insert coordinates to the original JPEG means that no adjustment is necessary when tweaking MFD screen placement.

Example: instead of <add name="DL" opacity="1" filename="~MFDisplay_Overlays\F14R LMFD_CAP.jpg" startX="276" startY="250" endX="520" endY="960" ... /> which uses startX/Y based on screen position, use the following <add name="DL" opacity="1" filename="~MFDisplay_Overlays\F14R LMFD_CAP.jpg" startX="325" startY="350" endX="535" endY="795" ... /> where startX/Y is based on the XY position in F-14\DCS F14RIO MFD.jpg

The difference isn't obvious here, but the second example should resize to match the MFD screen settings rather than having to tweak the numbers in the first example to match the screen.