YAME64 suite
-
I’m back from my forced vacation!!
I really hoped the new version would be out by now. Roccio, what are you doing man?!
ehehehe welcome back!
We are working hard, but RL job takes too much time… keep in touch
-
Thanks for the “welcome back”, it’s good to be back! I fully understand that RL takes priority. Do take your time, but hurry up!!
Hehehe… now to see if I can understand how to integrate the moving map to my Helios profile… -
Two new suggestions now that I’m playing with the moving map…
1. Is it possible to have TWO of these? Or have ONE but show up in two places? Reason I ask is because I’d like the option to have one CPD display the VVI/HSI/etc. but have a separate one that’s just dedicated to showing the moving map.
2. How is “layering” determined? How can we set that Gauge A shows up over Gauge X, but UNDER Gauge Y? Please add a way to control this.A bug that’s annoying the hell out of me: I now have three “windows,” one for my left screen, one for my center screen, and one for the “hidden” CPD. While trying to tweak the X/Y coordinates and size of the CPD window, I noticed some of my gauges would “migrate” to the third screen (CPD) or would stay on the center screen but have their sizes changed (VVI and AoA tapes in particular). I have also “lost” my HYD B gauge again, which means something is messing with the layout .xml file even though I’m not doing so.
-
Two new suggestions now that I’m playing with the moving map…
1. Is it possible to have TWO of these? Or have ONE but show up in two places? Reason I ask is because I’d like the option to have one CPD display the VVI/HSI/etc. but have a separate one that’s just dedicated to showing the moving map.
2. How is “layering” determined? How can we set that Gauge A shows up over Gauge X, but UNDER Gauge Y? Please add a way to control this.A bug that’s annoying the hell out of me: I now have three “windows,” one for my left screen, one for my center screen, and one for the “hidden” CPD. While trying to tweak the X/Y coordinates and size of the CPD window, I noticed some of my gauges would “migrate” to the third screen (CPD) or would stay on the center screen but have their sizes changed (VVI and AoA tapes in particular). I have also “lost” my HYD B gauge again, which means something is messing with the layout .xml file even though I’m not doing so.
For your integration of cp60 with helios i can tell you that next update will integrate full native touch support, so you don’t need helios (for this). As the moving map seems to be a favourite thing maybe we can add a new gauge for this (in future release). Same for zindex of gauges, will add to the todo list. For the bug i will try to replicate.
-
Just experienced the bug again, this time my VVI changed from default to MLU. I never used the MLU. My altimeter also migrated to the CPD screen without my input. I change back the VVI to default, set the altimeter to display back to the RIGHT window, run YAME client, it does the mask calculation, and then shows my VVI at double the size. Close YAME client, input the correct size, run YAME client again, mask calculation, and all is fixed and back to “normal.” Until I mess with my windows settings again.
While I appreciate the integration of touch support for the CPD, well, I’d still need Helios for the rest of my pit. One suggestion I’d make if you plan to add more functionality to the CPD – make the OSB controls work like they do in BMS. At the moment, this isn’t an issue since the left and right buttons only work for the moving map but if you want to add functions to control the ADLI/Alt/Mach/VVI/AOA and especially the EHSI, then it may get very confusing very quick. So for example, in the map screen, the top-left OSB zooms in, 2nd-top-left OSB zooms out and let’s say the user maps this to [,] and [.] keys. Then in the Flight Plan screen, you can have the top-left OSB to do [next page], 2nd-top-left OSB is [previous page]. So whether the user is in the map page or the flight plan page, let the [,] key and the [.] key control the first two OBSs and let their output be dependent on what screen the user is currently in, just like MFDs. I hope that made sense.
-
Got several instances of YAME crashing as I was trying to set the key combinations for the CPD buttons. It seems like YAME is having a hard time with SHIFT+CTRL+ALT combos and would crash. Also, it seems that the more complex the key combo, the less “reliable” button-pressing in Helios becomes. Sometimes, pressing the button will work, sometimes it won’t. I’m also getting some sync problems with the Show/Hide command for a window.
So one more suggestion:
3. Can we have a specific command for Show and another specific command for Hide instead of having one command to toggle? Just as we have switch-state callbacks and toggle callbacks in BMS, it would be very useful in guaranteeing displays sync with the button press.Thanks!
-
Two new suggestions now that I’m playing with the moving map…
1. Is it possible to have TWO of these? Or have ONE but show up in two places? Reason I ask is because I’d like the option to have one CPD display the VVI/HSI/etc. but have a separate one that’s just dedicated to showing the moving map.
2. How is “layering” determined? How can we set that Gauge A shows up over Gauge X, but UNDER Gauge Y? Please add a way to control this.A bug that’s annoying the hell out of me: I now have three “windows,” one for my left screen, one for my center screen, and one for the “hidden” CPD. While trying to tweak the X/Y coordinates and size of the CPD window, I noticed some of my gauges would “migrate” to the third screen (CPD) or would stay on the center screen but have their sizes changed (VVI and AoA tapes in particular). I have also “lost” my HYD B gauge again, which means something is messing with the layout .xml file even though I’m not doing so.
Just my personal opinion, but as far as common people know, F-16s currently only have 2 regular MFDs or maybe the CP60. A moving map in a single MFD is unknown, so for me that’s low priority fictional item. But will be added to the feature request list.
IIRC layering now is determined in the xml itself. The lower the item is in the xml, the higher it is in the layers. So if you are overlapping gauges, the one you wish to see completely should be below the other one in the layout file.
As Rocchio says, adding z-index will be added to the feature request list also. -
Just experienced the bug again, this time my VVI changed from default to MLU. I never used the MLU. My altimeter also migrated to the CPD screen without my input. I change back the VVI to default, set the altimeter to display back to the RIGHT window, run YAME client, it does the mask calculation, and then shows my VVI at double the size. Close YAME client, input the correct size, run YAME client again, mask calculation, and all is fixed and back to “normal.” Until I mess with my windows settings again.
Strange, I know it’s a bit of a pain, but try starting from an empty layout and built your way up to see which item is causing the issues.
@-Ice:While I appreciate the integration of touch support for the CPD, well, I’d still need Helios for the rest of my pit. One suggestion I’d make if you plan to add more functionality to the CPD – make the OSB controls work like they do in BMS. At the moment, this isn’t an issue since the left and right buttons only work for the moving map but if you want to add functions to control the ADLI/Alt/Mach/VVI/AOA and especially the EHSI, then it may get very confusing very quick. So for example, in the map screen, the top-left OSB zooms in, 2nd-top-left OSB zooms out and let’s say the user maps this to [,] and [.] keys. Then in the Flight Plan screen, you can have the top-left OSB to do [next page], 2nd-top-left OSB is [previous page]. So whether the user is in the map page or the flight plan page, let the [,] key and the [.] key control the first two OBSs and let their output be dependent on what screen the user is currently in, just like MFDs. I hope that made sense.
Already so in current beta for next release, MFD & C60 bezels have clickable OSBs and those OSBs can be linked to keystrokes.
-
So one more suggestion:
3. Can we have a specific command for Show and another specific command for Hide instead of having one command to toggle? Just as we have switch-state callbacks and toggle callbacks in BMS, it would be very useful in guaranteeing displays sync with the button press.Will be added to the feature list
-
Just my personal opinion, but as far as common people know, F-16s currently only have 2 regular MFDs or maybe the CP60. A moving map in a single MFD is unknown, so for me that’s low priority fictional item. But will be added to the feature request list.
No worries there Focal. I wasn’t making this suggestion for a “realistic” profile. My current Helios profile displays the WDP kneeboard data on a separate monitor so I just thought it would be awesome to have the CPD on the center pedestal but still be able to show the moving map in a bigger scale on the 2nd touchscreen.
IIRC layering now is determined in the xml itself. The lower the item is in the xml, the higher it is in the layers. So if you are overlapping gauges, the one you wish to see completely should be below the other one in the layout file.
As Rocchio says, adding z-index will be added to the feature request list also.Aha! Good to know! Thanks!
Already so in current beta for next release, MFD & C60 bezels have clickable OSBs and those OSBs can be linked to keystrokes.
As long as the OSBs can use the same keystroke and the “result” will be dependent on what page the CPD is on, that’s fine!
Will be added to the feature list
Please, please, please, please, please, please, please, please, PLEASE be in the next release! Shouldn’t be too hard to do and will increase the awesomeness and reliability of this a thousand-fold!
-
Make your wishes -ice…
-
Well, that’s it for now. I promise to be a good boy this year Santa!
-
Is there a limit to the max size of the moving map? The default size is 2048x2048 and for some reason, the airfields aren’t marked. Is it possible to make it work with bigger maps? Red Dog’s Korea ONC Map is 4096x4096 and 3x bigger in filesize but there is a lot of useful information on the map and the airfields are marked. I can’t seem to resize this map to be smaller but still keep the info readable.
-
This post is deleted! -
Try thisone, not perfect but useable
https://www.dropbox.com/s/ug83md3rimaj3l8/korea.png?dl=0 -
Yeah, that’s the result I’m always getting. While it’s useable in terms of being a “map,” there is very limited data considering what info you could get from the original map. 2048x2048 seems like a hard-coded limit; I could use a bigger map but the CPD map will only use the 2048x2048 coordinates.
-
Yes, for now hardcoded to 2048. Will add to the todo list
Inviato dal mio Y635-L21 utilizzando Tapatalk
-
Can’t wait for the new release…Awesome software , well done dev team
-
Any change to be able to add other theater maps / support please?
-
Can’t wait for the new release…Awesome software , well done dev team
Thanks!
Things are progressing a bit slower at the moment because both Roccio, Scorp and I have more other obligations, but still about 1 or 2 beta’s get released each week for internal testing so we’re still going forwardAny change to be able to add other theater maps / support please?
This, together with the higher res maps request are added to the roadmap.