YAME64 suite
-
I could not get it to work properly either until now, but that’s what I did to get it working.
Roccio has said that 3Dhook does not work (yet), that is crystal clear.
But I got gauges and MFD via RTT texture extraction working.
To do so the key was to configure BOTH versions (4.33 and 4.34) to export the MFDs via RTT texture extraction.
That means no 3DHOOK file present on neither the :\Falcon BMS 4.33\Bin\x64 nor the :\Falcon BMS 4.34\Bin\x64 folder (where the Falcon_Bms.exe files are)
set g_bExportRTTTextures 1 on both 4.33 and 4.34 falcon_bmas.cfg files
And of course falcon cannot be launched via the big “Launch Falcon BMS” button on YAME´s Run Tab.
This way YAME is extracting the MFDs and the gauges ok on my PC (server-client config)
I do not know if this works if only BMS 4.34 is installed.
I hope it helps
Better explained , but thats what i wanted to say as well
-
On page 67 of the current Yama manual it states that for the UFC to run correctly in Yama you need the correct BMS callbacks, but it does not list the callbacks. I am using the DX setup from 4.34 and below are the callbacks listed in the key for for the DX profile. I assume that these are sufficent for Yama when Yama gets updated to 4.34. correct?
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “======== 4.06 ICP ========”
SimICPCom1 122 0 0X3B 0 0 0 1 “ICP: COM1 Button - Push”
SimICPCom2 122 0 0X3C 0 0 0 1 “ICP: COM2 Button - Push”
SimICPIFF 122 0 0X3D 0 0 0 1 “ICP: IFF Button - Push”
SimICPLIST 122 0 0X3E 0 0 0 1 “ICP: LIST Button - Push”
SimICPAA 122 0 0X3F 0 0 0 1 “ICP: A-A Button - Push”
SimICPAG 122 0 0X40 0 0 0 1 “ICP: A-G Button - Push”
SimICPNav 122 0 0XE 1 0 0 1 “ICP: NAV Mode (no such button In Pit)”
SimICPTILS 122 0 0X4F 0 0 0 1 “ICP: 1-ILS Button - Push”
SimICPALOW 122 0 0X50 0 0 0 1 “ICP: 2-ALOW Button - Push”
SimICPTHREE 122 0 0X51 0 0 0 1 “ICP: 3 Button - Push”
SimICPStpt 122 0 0X4B 0 0 0 1 “ICP: 4-STPT Button - Push”
SimICPCrus 122 0 0X4C 0 0 0 1 “ICP: 5-CRUS Button - Push”
SimICPSIX 122 0 0X4D 0 0 0 1 “ICP: 6-TIME Button - Push”
SimICPMark 122 0 0X47 0 0 0 1 “ICP: 7-MARK Button - Push”
SimICPEIGHT 122 0 0X48 0 0 0 1 “ICP: 8-FIX Button - Push”
SimICPNINE 122 0 0X49 0 0 0 1 “ICP: 9-A-CAL Button - Push”
SimICPZERO 122 0 0X52 0 0 0 1 “ICP: 0-M-SEL Button - Push”
SimICPCLEAR 122 0 0X53 0 0 0 1 “ICP: RCL Button - Push”
SimICPEnter 122 0 0X9C 0 0 0 1 “ICP: ENTER Button - Push”
SimICPNext 126 0 0X4E 0 0 0 1 “ICP: NEXT Button - Push”
SimICPPrevious 126 0 0X4A 0 0 0 1 “ICP: PREVIOUS Button - Push”
SimICPDEDUP 120 0 0XC8 0 0 0 1 “ICP: DCS UP - Push”
SimICPDEDDOWN 120 0 0XD0 0 0 0 1 “ICP: DCS DOWN - Push”
SimICPDEDSEQ 120 0 0XCD 0 0 0 1 “ICP: DCS SEQ (Right) - Push”
SimICPResetDED 120 0 0XCB 0 0 0 1 “ICP: DCS RTN (Left) - Push”
SimDriftCO 121 0 0XB5 0 0 0 1 “ICP: DRIFT C/O Switch - Tog. ON/NORM!”
SimWarnReset 115 0 0X1C 1 0 0 1 “ICP: DRIFT C/O Switch - WARN RESET”
SimSetWX 122 0 0XB5 1 0 0 1 “ICP: FLIR - WX Mode”
SimFlirLevelUp 122 0 0XC9 1 0 0 1 “ICP: FLIR Rocker - Level Up”
SimFlirLevelDown 122 0 0XD2 1 0 0 1 “ICP: FLIR Rocker - Level Down”
SimSymWheelUp 116 0 0X4E 3 0 0 1 “ICP: SYM Wheel - Increase HUD Brightness”
SimSymWheelDn 116 0 0X4A 3 0 0 1 “ICP: SYM Wheel - Decrease HUD Brightness”
SimHUDPower 116 0 0X9C 3 0 0 1 “ICP: SYM Wheel - HUD Power - Toggle”
SimBrtWheelUp 116 0 0X4E 5 0 0 1 “ICP: BRT Wheel - Increase FLIR Intensity”
SimBrtWheelDn 116 0 0X4A 5 0 0 1 “ICP: BRT Wheel - Decrease FLIR Intensity”
SimRetUp 116 0 0X4E 6 0 0 1 “ICP: DEPR RET Wheel - Step Up”
SimRetDn 116 0 0X4A 6 0 0 1 “ICP: DEPR RET Wheel - Step Down” -
No, it does not work on android tablets.
-
Hello, Question does the YAME works in Android tablets?
I would like to have in my knee as kneeboard a tablet with colour moving map like CPD software
Yes it works! I use it with an app called “spacedesk”. I use for CPD works great! But YAME only works for BMS 4.33, need to wait 4.34 version.
-
I do not know if this works if only BMS 4.34 is installed.
I hope it helps
Cenzi no trabaja ya lo probé, tiene que ser con las dos versiones intaladas, me imagino que asi se engaña al JAME para que haga su trabajo, Jame tiene que direccionarse a algun Falcon para que funcione. Un abrazo amigo.
In english:
Cenzano don’t work, I tried it, it has to be with both versions installed, I imagine that like this JAME is tricked into doing his job. JAME has to address to some Falcon install to make it work. -
No, it does not work on android tablets.
However if you extended your desktop to your Android tablet you could create a window with the proper X,Y coordinates to the screen of the Android and put YAME gauges there. So you can do what you want but it takes setting up your android with screen extending software first, then windows will just see the android as just another monitor. There a lots of them out there.
Sent from my iPad using Tapatalk
-
I have everything configured, g_bExportRTTTextures 1, on both versions, I just can’t get data pulled to MFD’s etc. It’s like I am missing step? Is there anything I need to put in"get data from network", as you can’t use “hook”, I think data got pulled one time, but I didn’t know what I did, as it never returned. Thank you
-
You only use “get data from network” on a client not running on the same computer. That is why you also need an IP-Adress for this to work.
Maybe, but just maybe you have to configure the client to show server and client status. I noticed a bug where if i don’t include them in the view, nothing else will show up. Took me several hours to figure this out, on Linux and as well on Windows 7, but you might have a different problem.
-
I have everything configured, g_bExportRTTTextures 1, on both versions, I just can’t get data pulled to MFD’s etc. It’s like I am missing step? Is there anything I need to put in"get data from network", as you can’t use “hook”, I think data got pulled one time, but I didn’t know what I did, as it never returned. Thank you
Hi Scottd5800
I had similar issue on my side, although I’m running YAME locally i.e. getting data from BMS (not from the network server). I couldn’t get data from BMS, although I done all the settings according to the YAME manual. Having spent few hours on this issue, I simply re-installed the YAME. Now it works perfectly! Try it out, hope this will help you too.
-
I could not get it to work properly either until now, but that’s what I did to get it working.
Roccio has said that 3Dhook does not work (yet), that is crystal clear.
But I got gauges and MFD via RTT texture extraction working.
To do so the key was to configure BOTH versions (4.33 and 4.34) to export the MFDs via RTT texture extraction.
That means no 3DHOOK file present on neither the :\Falcon BMS 4.33\Bin\x64 nor the :\Falcon BMS 4.34\Bin\x64 folder (where the Falcon_Bms.exe files are)
set g_bExportRTTTextures 1 on both 4.33 and 4.34 falcon_bmas.cfg files
And of course falcon cannot be launched via the big “Launch Falcon BMS” button on YAME´s Run Tab.
This way YAME is extracting the MFDs and the gauges ok on my PC (server-client config)
I do not know if this works if only BMS 4.34 is installed.
I hope it helps
Works for me !
Great info, thanks ! -
My Yame is crashing on startup….:(
-
Try to run program as administrator or reinstall.
-
Same here. I can’t start YAME64 It crashes immidiately after startup.
I tried uninstalling and installing.
(following the above advice for 4.34 compatabillity)
Updated GPU drivers
rechecked visual studio drivers
Ran as administrator
nothing works. any idea? -
I will make a try, but i think everything has already been said before. You need to have installed BMS 4.33. At start YAME looks for BMS 4.33 configuration files. After that … it will work without 3dhook … just taking the info from the memory. But i think some people have summarized this before already. Please review the comments before this one.
-
I’ve got 4.32 and 4.33 and 4.34 installed, and YAME64 is still working fine. I extract a couple gauges and 2 MFD’s to another computer (Win7 lenovo y70t laptop) over ethernet, display them on an attached (ASUS VT168 touchscreen) monitor, and all the MFD buttons work fine. (Laptop display is also a touchscreen )
Only problem I have, and this persisted before 4.34, is that I have to press an OSB twice for it to register on my main PC running BMS and for the life of me I cannot figure out why that would be. Same with the Master Caution and F-ACK buttons on the laptop native touchscreen display. Only every other press gets through, but this is a native touchscreen laptop and single clicks work just fine in any other application. It’s a ten point touch monitor, by Asus.
Any ideas or tips would be great. I considered using a different program for the buttons, but that smacks of effort and YAME64 works just great (except for the double-touch required to press any button). Is there anything I can do to make this better? Let me know if more details are needed. Cheers!
-
@Tul:
My Yame is crashing on startup….:(
This is what I have found to work in 4.33 at least regarding the crash.
1. Start BMS and chose the "full BMS (or what is is called) keyfile in the setup/controllers menu.
2. close BMS
3. Start YAME64 (it started with no issues with me as long as I took a standard .key file first and loaded it.)
4. Start BMS and now select your own key file (while YAME64 is still running)
5. Go blow stuff up.Hope it helps you out.
I know it is only a work around, and I haven’t had any luck getting Yame64 to work with 4.34 yet. I think I’ll wait for an update. Messing around with both Yame, .33 and .34 resulted in me having to do 2 complete re-installs.MIL
-
It worked!!!.. Thanks!
-
Anytime brother. I just hope we do not need this workaround, after the next YAME update.
-
I will wait for the next YAME64 update, I hope very soon
-
I feel difficult to understand callback configuration in yame : do i have to select a callback for each button of my yame cockipt (SimCBEOSB_1L for example) and manually assign the corresponding falcon4 bms key to this button ?