YAME64 suite
-
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.
-
Thanks for the constant work that you do guys, and thanks for continuing on listening to feedback and adding to the feature request list!
-
The application runs but is minimized in the taskbar and I can not maximize. Does the same thing happen to someone? Any suggestions ??
My pc runs on win10.Enviado desde mi LG-D855 mediante Tapatalk
-
The application runs but is minimized in the taskbar and I can not maximize. Does the same thing happen to someone? Any suggestions ??
My pc runs on win10.Enviado desde mi LG-D855 mediante Tapatalk
Are you using 32 or 64 bit version?
Are you using 1.0.0 or 1.1.0 version?
Check in /yame64/config/yame64.xml in notepad and see what value is set in . Sometimes it seems x or y is set to -3200, so it’s rendered outside the window.
Windows aeroglass disabled might cause issues.
Enabling “trama S3TC” in OpenGl Texture compression might cause issues. -
Are you using 32 or 64 bit version?
Are you using 1.0.0 or 1.1.0 version?
Check in /yame64/config/yame64.xml in notepad and see what value is set in . Sometimes it seems x or y is set to -3200, so it’s rendered outside the window.
Windows aeroglass disabled might cause issues.
Enabling “trama S3TC” in OpenGl Texture compression might cause issues.64bit and the latest version….will check the folder later…thanxs for your quick answer…
Enviado desde mi LG-D855 mediante Tapatalk
-
I have had minimize issue in the past with v1.1 64 bit. I think all I did was start BMS normally using the BMS icon, then YAME started normally on the next occasion. I really do not remember precisely how I resolved the issue, but it was something funky like that.
-
Known issue and fixed in next release.
-
Had the values of x and y in -3200, I changed them to 0 0 and solved the problem, thanks roccio again
Enviado desde mi LG-D855 mediante Tapatalk
-
Hi, I was directed to yame a while back now and have been excited to finally getting around to playing with it, I am very impressed so far with all the additional features especially the ability to save layouts.
I am however wondering if there’s a way I can get it to start the client on windows startup and be ready for flight. I am currently able to add a startup listing for the software but this requires an extra step of starting the client once loaded.
I wondered if there was maybe a commandline flag i could add to the startup entry or such?