Yame64 - Win10 - Lilliput UM-80/C/T?
-
I’m looking to buy two Lilliput UM-80/C/T touchscreens to use as MFD’s but from what I can gather Yame64 MFD extractor got broken with the 4.34 release, has anything changed? It seems Helios is similar but also not working. Is it a just wait for the update kinda thing? I want touchscreens to avoid using the TM OSB button setup, going to be enough wires to make it look like a small town in Thailand as it is…. Any pictures of Yame64 working in 4.33 (or 4.34)?
-
See https://www.yame64.com/how-to/
You can make it work with 4.34 with a workaroundPics of ot working in 4.33 see the same site under “screenshots”.
My pit with 4.34: https://www.instagram.com/p/B0sPZ09inZC/?igshid=nlt1tjyrh1uu -
Holy crap that cockpit is amazing!
-
Ok, I looked at the workaround link, thank you. I do have both 4.33 and 4.34 installed, and both config files have "set g_bExportRTTTextures 1 " in them. I installed the latest C++ redistributable (I corrected the Manuals outdated link below, this goes straight to the 64 bit file), fresh install of Yame64, per the Yame 1.21 Manual as shown here -
“3.1. First install
NOTE: Visual C++ Redistributable for Visual Studio 2015 is needed to be able to run this application.
You can download the 64 (x64) bit version at https://aka.ms/vs/16/release/vc_redist.x64.exe.
Make sure the bit version of this installer is the same as the bit version you will install of Yame (x64 vs x86).
3.2. First run
The first run needs a little setup, so go to the Globals tab and set your preferred folders (see in detail in
“globals tab” section).
Introduced in v1.2 YAME will try and determine the location of the BMS install, the used callsign/DTC and
keyfile files and the active theater.”I found the Blanked out location issue for paths under the Globals tab was in the Yame64.xml file, it was pointing to “C:\Falcon BMS 4.33 U1” and my install was on D:. Once I corrected it all came up in Global as expected!
-
locate the yame64.xml file in the config subfolder of you YAME install. Look for the lines <path>.
Set the correct location, e.g.<falcon><windowed>true</windowed>
<path>C:\Falcon BMS 4.34</path></falcon></path> -
LOL, beat ya to it! I thought of that as I was typing my original response and edited it to reflect, but thanks Focal!
-
Just a follow up, set up 4.34 to run windowed from the Run Tab (had to reduce resolution in game to 1920x1080 also), have MFDs up in the YAME64 client, refresh rate to 40 and the external MFDs are perfectly in sync with the game. Now I wait for my touchscreen panel to arrive. Have not found a way to get the “Launch Falcon BMS” button to point to 4.34 (it starts 4.33 U4 for me though!) and I need to figure out what keyfile i’m going to use as i’m just using my CH Fighterstick in 4.34 with the BMS_Full file and in 4.33 I used the whole HOTAS and a CH_HOTAS (similar) setup…
-
Just a follow up, set up 4.34 to run windowed from the Run Tab (had to reduce resolution in game to 1920x1080 also), have MFDs up in the YAME64 client, refresh rate to 40 and the external MFDs are perfectly in sync with the game. Now I wait for my touchscreen panel to arrive. Have not found a way to get the “Launch Falcon BMS” button to point to 4.34 (it starts 4.33 U4 for me though!) and I need to figure out what keyfile i’m going to use as i’m just using my CH Fighterstick in 4.34 with the BMS_Full file and in 4.33 I used the whole HOTAS and a CH_HOTAS (similar) setup…
Launch falcon BMS will indeed still launch 4.33, it cannot be changed via a config file. The workaround is indeed by adding a 4.34 item in the run tab (as mentioned under number 3 of the workaround on the websites how-to).
-
Launch falcon BMS will indeed still launch 4.33, it cannot be changed via a config file. The workaround is indeed by adding a 4.34 item in the run tab (as mentioned under number 3 of the workaround on the websites how-to).
Actually there is a workaround to get 4.34 to start from the Launch button but it breaks the Global Tab parameters so don’t do it! Using Regedit go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Benchmark Sims\Falcon BMS 4.33 U1 and modify the baseDir line from C:\Falcon BMS 4.33 U1 to C:\Falcon BMS 4.34 (change this to reflect your own BMS 4.34 install path). Done.
-
Actually there is a workaround to get 4.34 to start from the Launch button. Using Regedit go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Benchmark Sims\Falcon BMS 4.33 U1 and modify the baseDir line from C:\Falcon BMS 4.33 U1 to C:\Falcon BMS 4.34 (change this to reflect your own BMS 4.34 install path). Done.
Thx! Updated the how-to-page on the website with this info
-
Launch falcon BMS will indeed still launch 4.33, it cannot be changed via a config file. The workaround is indeed by adding a 4.34 item in the run tab (as mentioned under number 3 of the workaround on the websites how-to).
Focal, I finally got my 1st Lilliput 80 and started to play with it. 1st thing I see is the “registry fix” to get the “Launch BMS” button to run 4.34 broke the Global Tab selections. You have to keep the registry setting at X:\Falcon BMS 4.33 U1 or it won’t work. Not a big deal, just use the added program entry to launch it, just thought i’d put it out there! Got my right MFD up, touchscreen buttons work, going to toss some other usefull stuff in the 200x600 unused space and go with it! I use BMS Full key, didn’t have to touch the Callbacks, worked out of the box… amazing.
-
Ok, everything got packed up a few weeks ago for the move to my new place. Now have a 2nd Lilliput ordered and an great twin arm monitor holder, a Flight stand and all my gear up to snuff. Mounted the Lilliput I have on the right and tossed together a YAME window with the Right MFD on it. Works great, displays the Right MFD but I can not for the life of me get the OSB’s to work. Have calibrated the touchscreen several times, have the bezel showing, have checked “Use Touchscreen” in Misc. tab, and (even though I don’t think I did it last time) listed the Right MFD callbacks in the Callbacks window. What the heck did I miss, worked before!
Edit: OK, fixed the touchscreen issue, it was a setting in the eTouch Calibration utility. Needed to tell it which monitor it is (#2 in this case) and tic “Enable Multiple Monitors” in the Display Tab… I wrote the following up for a buddy’s first install of a Liliput UM80 Touchscreen as I also had the dead screen with blue blinking light when I first ran it here, think a Win10 update broke the old Displaylink drivers and there are new ones out. That and I don’t want to forget what I did when my second Lilliput shows up! Maybe it will help someone else.
After plugging in the Lilliput UM80 and installing the latest Displaylink drivers (9.3 is latest for Win10 as of 12-17-19), located here and the eGalaxTouch 5.14.0.19506 drivers located here, and then setting the screen as Extended 800x600 in Win10 Display Settings it should show the desktop on the Lilliput.
1. Run the eGalaxTouch Calibration Utility (it will be a hidden icon on bottom right of Taskbar). Select the “Display” Tab, then tic “Enable Multiple Monitors” and “Full Screen” under Operation Mode. Double click the graphic of the monitor you are working with in the “Display” window. Click “OK”, it will shut down the utility, so restart it.
2.Go to the “Tools” tab, click “Clear and Calibrate”. Press and hold (until it says “OK”) the calibration buttons on the Lilliput touchscreen. If the calibration touch buttons are showing up on the main monitor you didn’t do step #1 correctly. If all went well Click the “Linarization” button to do a 9 point calibration, same deal as 4 point, push buttons on the Lilliput as they appear until you see “OK”.
3. Close the Utility, you should be good to go, get busy with YAME64!
-
This post is deleted! -
Focal, any more development being done on YAME? Seems like Helios is getting some love but i’m used to YAME64 and how easy it is to use!
-
Focal, any more development being done on YAME? Seems like Helios is getting some love but i’m used to YAME64 and how easy it is to use!
Main difference is Helios and MFDE are OpenSource so a lot of people can contribute and get the development done, whereas Yame is closed source.
-
Focal, any more development being done on YAME? Seems like Helios is getting some love but i’m used to YAME64 and how easy it is to use!
It’s not dead, that’s all I can say for now…
-
No not dead, but i assume the project is laying on IC. And after that a loooooong revalidation.