YAME64 suite
-
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? -
I have a curious problem with YAME.
When i start/edit the gauges on my main monitor it works fine, but as soon as i try it on a external window it instantly crashes and i can’t figure out how or why.
I tried running it as admin, update driver’s, update windows nothing seems to work.
I’m currently on Windows 10 64 bit. -
I have a curious problem with YAME.
When i start/edit the gauges on my main monitor it works fine, but as soon as i try it on a external window it instantly crashes and i can’t figure out how or why.
I tried running it as admin, update driver’s, update windows nothing seems to work.
I’m currently on Windows 10 64 bit.What do you mena with esterna monitor?
-
What do you mena with esterna monitor?
I mean that i have 3 monitors, a 4K display, a 1080p and a 720 15inch screen witch i use for my MFD’s.
And when i use YAME on my main monitor, The 4K display it works fine but when i drag a new “Window” on the other 2 monitors and save it, as soon as i try to edit or start it it crashes
Sorry for the confusion -
I mean that i have 3 monitors, a 4K display, a 1080p and a 720 15inch screen witch i use for my MFD’s.
And when i use YAME on my main monitor, The 4K display it works fine but when i drag a new “Window” on the other 2 monitors and save it, as soon as i try to edit or start it it crashes
Sorry for the confusionTris is strange. Can you send me (eden in pm) tour layout XML file.
-
Hi all, I am trying to set up the digital HYD B gauge and follow the instructions Ice gave a few threads back, but where is this file located???
<hydpressb><width>84</width>
<height>83</height>
<posx>1640</posx>
<posy>837</posy>
<visible>true</visible>
<window>RIGHT SCREEN</window>
<type>default</type>
<digital>false</digital></hydpressb>Change “right screen” to whatever your window name is and you should be good to go.
-
Yame folder /layouts/<yourlayout>.xml</yourlayout>
-
Bedankt!! I opened it in the wrong format which makes it look like garbled klingon writing, Wordpad did the trick!!!
-
Best to use Notepad++ for any future editing needs
-
Hi everyone
Could someone try to help me to extract the data for the Mirage 2000 ? Please ?
The values are different from RRT Remote and I would like to extract the same data for YAME
in conf/extraction.xml<extractions><layout name="Mirage 2000"></layout></extractions> ```Thank you :) Regards Digle
-
MIrage 2000? Do you not just extract the same stuff as you do with the F-16?
-
IIRC the values are different cuz 3dckpit files are different from F16 files
Same for the F18, that’s why a dedicated config is present in the conf/extraction.xml file -
If I remember correctly the mirage uses 512x512 texture size, so it is not possible to extract in the current version of YAME.
In the next version will work, but not using directx hook.