YAME64 suite
-
Roccio,
May I humbly ask if there is any news on YAME64?
Any teasers?thank you
Sure. I am working (very little time) to support the new 4.34.1
Still alive
-
Sure. I am working (very little time) to support the new 4.34.1
Still alive
Hello Roccio,
many thanks for your effort and I know real life can be a pain in the a…!
Hopefully it supports 4.34.2 as well
Thanks again and have a great evening,
Tweety -
Hello Roccio,
many thanks for your effort and I know real life can be a pain in the a…!
Hopefully it supports 4.34.2 as well
Thanks again and have a great evening,
TweetyI’m running YAME with 4.34.2 very stable. Only thing if I exit and restart BMS I have to stop and start the YAME client as well
-
I’m running YAME with 4.34.2 very stable. Only thing if I exit and restart BMS I have to stop and start the YAME client as well
Yes, but should be fixed for the next update
-
Some info about my experience with YAME, maybe usefull for those with similar problems.
I was a happy YAME user. Have several PCs with BMS and YAME working like a charm (localy and networked).
On my newest rig, suddenly it stopped working: Once I pressed Start YAME client, it was unable to create the window, and so it never displayed any instrument. I was using 3 screens as a sinlge 1 using NVIDIA Surround, and an additional monitor for YAME (all under my GT2080).
It never mattered how and where I put that screen (left of main, under main, right of main), it crashed YAME.
If I used Main screen, it worked perfectly (but then it was over BMS 3D screen, so… no way).
As I´m really stubborn, yesterday I tried the following and it worked:
1-My YAME window is 1920x1080. I define YAME window on -1920 and 0 coordinates (left of main screen)
2-I set up my secondary screen under my main screen (in my case is 0 and 2160) just below the main screen. (you just do this using the usual windows screen configuration)
3-I launch YAME. This time It works, but as expected, it doesn´t display anything as the coordinates of the monitor are not the ones for the YAME window.
4-I change again the secondary screen position to left of Main screen (thus matching the ones for YAME window)
5-And voila, YAME shows up on the sceen!!Its a silly procedure, but it is the only way I could find to make it work!
Hope this could help other users.
Thanks for your wonderfull software, and keep it up!
-
Eres un melón…[emoji23][emoji23][emoji23][emoji23]
Enviado desde mi H8324 mediante Tapatalk
-
Ciao Roccio.
Any chance to see back Hook option in the next update?
It worked great!!!Regards
-
I’m having an issue with Yame 1.21 and BMS 4.34. Yame works fine until I try to click on a control in the Yame window. Focus just goes back to the BMS window and does not register the mouse click. Anyone else having this issue?
Also - I works fine with BMS 4.33 Mouse and BMS can share the focus -
Hi all
After a few months without running YAME64, today I resumed the extraction (with no changes, I have the same monitor, the same configuration, I keep BMS 4.33 in the computer…etc. The only change I made is an update from 4.34 to 4.34.1 and then to 4.34.2) but I have a problem
My problem is that I cant get the 2 MFD in the screen.All the instruments are extracted OK in the second monitor but no MFD ¿¿??
I got a message from YAME64: “…RTT is set to 0 so no extraction, please change to 1 in falcon BMS config…” or something like that,but that’s not true, I have RTT set to 1 in both configs (4.33 + 4.34)
I have two Thrustmaster MFD button bezels attached with velcro to the second monitor, this is the main reason for running YAME64, but now that part of the screen is blank!
Any idea?
best regards
-
Do you have the 3Dhook option still active in YAME ?
and have you removed the Hook Files ? (in YAME >>“Globals”) ?See here as well
https://www.yame64.com/how-to/ -
Problem solved!
For some reason, the name of my BMS 4.33 folder in was not the same that the one in YAME64.xml
I changed it and that made the trick! So now I’m enjoying YAME64 again
Everybody having the same issue please make sure that BOTH paths are exactly the same, for example in my computer:
C:\Falcon BMS 4.33
C:\YAME64\config\YAME64.xml <path>C:\Falcon BMS 4.33</path>Best regards
-
Hi,
YAME works very well for me in BMS 4.34U2. I can use CPD, DED and RWR for both F-16 and F-18C.
But DED and RWR doesn´t work for F-18E, CPD does.
Is this normal?Thank you.
-
Not on my PC at the moment so can’t check. But if the in pit position of DED and RWR is different than yes that’s normal. I’m currently elaborating how Yame reads from SharedMem so might give an more technical answer in the near future
Gesendet von meinem SM-G930F mit Tapatalk
-
Not on my PC at the moment so can’t check. But if the in pit position of DED and RWR is different than yes that’s normal. I’m currently elaborating how Yame reads from SharedMem so might give an more technical answer in the near future
Gesendet von meinem SM-G930F mit Tapatalk
Ok,thank you.
-
If you are using another theater and you are using the CPD moving map, you also need to change HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Benchmark Sims\Falcon BMS 4.33 U1\curTheater to reflect the new theater.
-
If you are using another theater and you are using the CPD moving map, you also need to change HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Benchmark Sims\Falcon BMS 4.33 U1\curTheater to reflect the new theater.
Moving map is working ok in both Korea and Balkans theater. My question is about RWR and DED not working in F-18E(F-18C is ok).
-
Moving map is working ok in both Korea and Balkans theater. My question is about RWR and DED not working in F-18E(F-18C is ok).
Have a look into this thread. Yame gauges and position reading is discussed and described there
https://www.benchmarksims.org/forum/showthread.php?35552-BMS-4-34-F-A-18-missing-needles-in-all-analog-gaugesGesendet von meinem SM-G930F mit Tapatalk
-
First I have to express my appreciation for all the work Roccio does, it is amazing.
With 4.34U2 running smoothly on W10 (btwI use Y64 only for CPD) this is my experience:
-Only Korea KTO map seems to work, and it somehow stays on even with other theaters.
-No data from WDP imported in CPD, I tried the options in the GUI
-The Nightvis mode works fine
-the ‘mode’ tab on the attitude page not function
-the zoom out tab on the attitude page not functional
-callback programming no problems hereI might have made mistakes on the workaround routine, have to recheck
Other than that I have been using Y64 almost everyday the last 2 months, love it:)
-
First I have to express my appreciation for all the work Roccio does, it is amazing.
With 4.34U2 running smoothly on W10 (btwI use Y64 only for CPD) this is my experience:
-Only Korea KTO map seems to work, and it somehow stays on even with other theaters.
-No data from WDP imported in CPD, I tried the options in the GUI
-The Nightvis mode works fine
-the ‘mode’ tab on the attitude page not function
-the zoom out tab on the attitude page not functional
-callback programming no problems hereI might have made mistakes on the workaround routine, have to recheck
Other than that I have been using Y64 almost everyday the last 2 months, love it:)
For the map issue, a work around for me was changing the registry key on both falcon version. Check my previous post
Sent from my SM-G960U using Tapatalk
-
If you are using another theater and you are using the CPD moving map, you also need to change HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Benchmark Sims\Falcon BMS 4.33 U1\curTheater to reflect the new theater.
If you are using a different theater, that key should already contain the name of the theater in use(?)