YAME64 suite
-
Yes, it could be a long setup, but once done you can just power up your pc and start Flying.
-
Not in current v1.1
In future v1.2 you will have touchable mfd (f16 & f18), Icp (regular & block60), center pedestal, master Caution, atd, twp, twa, machmeter index, altimeter pressure, adi horizon, hsi/ehsi…Man I can’t wait for that. That would be awesome. Again thanks for all your hard work on this extractor.
-
Hi mate,
Normally in Windows you can add items in the start list in the start menu IIRC?
V1.2 will have the ability to add command line options to autostart several stuff (-layout -client -server -falcon -batch -minimze). So in theory you can have a shortcut with the something like “yame64.exe -layout snowman.xml -batch -client -falcon -minimize” and it woud start yame, load your layout, start the batch run of other programs you have selected to be in the batch in the first UI tab, start the client, start falcon and minis to system tray; all at onceThx
-
Is it possible to choose for the option to have YAME start on Windows startup including the extraction? That would mean I only have to start BMS
Maybe have YAME start when BMS starts…. unless you only turn on your computer to play BMS… nothing wrong with that though!
I’m using one of the test versions of YAME and I have a button that starts up YAME and with command line options…
-
Hi all,
I have a problem with YAME window. When I start the program it is minimize on the toolbar but when I select opened YAME on the toolbar to launch client and BMD it never maximizes then I can’t access to YAME software.
Any idea to solve it?
Thx
-
Hi all,
I have a problem with YAME window. When I start the program it is minimize on the toolbar but when I select opened YAME on the toolbar to launch client and BMD it never maximizes then I can’t access to YAME software.
Any idea to solve it?
Thx
Close yame first, then check the yame64.xml in the yame64/config folder and check if the UI x or y coordinates don’t have a negative number or huge (most common error in v1.1 is that x or y is set to 320000 or something). Set both to 0 and start Yame again. The UI window should be in the top left corner then.
-
Have a strange issue all of sudden. I haven’t ran this extractor in quite some time. I ran it today and my HUD was showing the Left MFD and MFDs had the HUD split between them. Any idea of what’s happening here? Should delete the profile I’m using and start a new one?
-
Never had this myself or received a bug report like this.
Sounds like the wrong texture interpretation. Are you flying a viper or a hornet? And how is the gauge set up? Sounds like the layout is set for viper and you are flying a hornet or vice versa.
In case the above is not the case. Please provide the following information:
Are you using v1.0 or 1.1? In case of 1.1, 32 or 64 bit?
What os? What version of visual redistribution 2015?
Optionally send us the config & layout file. -
Never had this myself or received a bug report like this.
Sounds like the wrong texture interpretation. Are you flying a viper or a hornet? And how is the gauge set up? Sounds like the layout is set for viper and you are flying a hornet or vice versa.
In case the above is not the case. Please provide the following information:
Are you using v1.0 or 1.1? In case of 1.1, 32 or 64 bit?
What os? What version of visual redistribution 2015?
Optionally send us the config & layout file.Oh boy my bad I was flying the Viper and I had the Hornet gauge setup.:uham:
-
Oh boy my bad I was flying the Viper and I had the Hornet gauge setup.:uham:
Yes, this issue is resolved in the next release.
-
Yes, this issue is resolved in the next release.
Technically it’s not a fix, because it wasn’t a bug.
We implemented an extra feature it will autodetect wether the active plane is a Viper or a Hornet and adjust the texture readout accordingly -
Technically it’s not a fix, because it wasn’t a bug.
We implemented an extra feature it will autodetect wether the active plane is a Viper or a Hornet and adjust the texture readout accordinglyYou are right.[emoji2]
Inviato dal mio Y635-L21 utilizzando Tapatalk
-
I am a newbee here.
Just trying out Yame64.
Where is the Falcon BMS DTC file located?
thanks.
-
nevermind. I figured it out. (sorry)
-
Close yame first, then check the yame64.xml in the yame64/config folder and check if the UI x or y coordinates don’t have a negative number or huge (most common error in v1.1 is that x or y is set to 320000 or something). Set both to 0 and start Yame again. The UI window should be in the top left corner then.
Sorry for the delay. I’ve done the changes and everythig is OK.
Thanks a lot.
-
Gents,
I have been experiencing lagging in the UI and in game using YAME. This only started after I recently updated to Windows 10 CU from Windows 7. After updating required drivers to get my X52 working (I/m old and cheap) it worked fine for about a week.
Then today, I was flying in the ITO and saw that the extracted displays began to lag the in game displays, first by a little and then they became completely unusable. I restarted both the game and YAME, downloaded and reinstalled YAME, adjusted update rates and checked this forum for similar issues. After reading these posts, I noticed it was lagging in the UI as well, with up to a couple of seconds between click and tab change.
I assume that the lag is related, but don’t know how I would prove that. The Win10 update also may have had an impact. YAME was being run in Win7 compatability mode, but changing this didn’t seem to effect anything.
Is there a setting somewhere that could be causing this that isn’t YAME related? Like I said, it just started happening today and is very frustrating, as the main window MFDs work fine.
Thanks for any help you can give me, I’ve been using YAME for about 6 months no problem. It’s a great product, I sure it must be operator error on this side.
-
Gents,
I have been experiencing lagging in the UI and in game using YAME. This only started after I recently updated to Windows 10 CU from Windows 7. After updating required drivers to get my X52 working (I/m old and cheap) it worked fine for about a week.
Then today, I was flying in the ITO and saw that the extracted displays began to lag the in game displays, first by a little and then they became completely unusable. I restarted both the game and YAME, downloaded and reinstalled YAME, adjusted update rates and checked this forum for similar issues. After reading these posts, I noticed it was lagging in the UI as well, with up to a couple of seconds between click and tab change.
I assume that the lag is related, but don’t know how I would prove that. The Win10 update also may have had an impact. YAME was being run in Win7 compatability mode, but changing this didn’t seem to effect anything.
Is there a setting somewhere that could be causing this that isn’t YAME related? Like I said, it just started happening today and is very frustrating, as the main window MFDs work fine.
Thanks for any help you can give me, I’ve been using YAME for about 6 months no problem. It’s a great product, I sure it must be operator error on this side.
I don’t think it’s somewhat related to Windows10CU (my development pc has this same window version). More likely it’s a little bug in the network code that should be fixed (is under massive testing) in the next update.
Maybe Windows10 CU exposes more this issue, sorry for this inconvenience. -
Maybe it’s related to a recent VisualStudio 2015 redistributable update? On my win7 I had serious issues after updating VS15red at a certain time, a couple of days later, another update came and problems were gone. Just guessing here. Have no Win10.
-
I don’t think it’s somewhat related to Windows10CU (my development pc has this same window version). More likely it’s a little bug in the network code that should be fixed (is under massive testing) in the next update.
Maybe Windows10 CU exposes more this issue, sorry for this inconvenience.After some testing, I think I have fixed the lag problem by deselecting Antialiasing in YAME. Although I wouldn’t think that would cause that much lag, I guess it is possible.
Thanks again for the response and for a great product!
-
After 3 days of reading forums, my bleeding eyes force me to ask for help.
I am running bms 4.33 on a 27" NON touch screen. The computer is 64 bit.
I am using 2 different extractors.
One is f4bmsserver, running two android tablets. These show the Lmfd, RWR, plus the Rmfd and DED. They work very well, all my keypresses work.
I also have a windows tablet that is running off of YAME 32. Therein is my problem. When extracted to the PC (the main 27" screen) I get full functionality. My key bindings work just fine. But when I extract it to the Windows tablet I lose all functionality. It sits on the block 60 fictional panel. It will not go to the map, the flight plan or present itself with any functionality at all. It doesn’t matter how I try to get there. Keyboard callbacks, Voice, Touch. Non of them work, it simply sits on the default blk 60 screen. BTW, that screen works perfectly.
Help please?