YAME64 & touch screen, does it work?
-
So I just bought a touch screen and can fire up YAME64 to extract gauges and stuff without issue. I calibrated my touch screen so I could use that part of Yame but every time I touch the screen the sound from Falcon BMS goes silent almost like the focus is getting stolen from Falcon BMS. Also I none of the expected switches and stuff actually work. I know the key file needs all the callbacks and stuff to work properly but I made mine based off of the full key file so should that be enough?
For those that are going to say use Helios my response to you is “I’d like to but the site that hosts it is having issues and I can’t download it” plus it seems YAME64 is trying to fill the same gap and seems to be routinely updated so I’ve read.
So how can a complete noob to YAME64 and touchscreens get this all working? Being able to press those critical buttons without have to look at them in the 3D window would be sooo awesome.
Any help is much appreciated…
Sent from my iPad using Tapatalk
-
there are issues in yame 1.2 that should be fixed in next version. just have a little patience
-
there are issues in yame 1.2 that should be fixed in next version. just have a little patience
So your saying the touchscreen part doesn’t actually work at the moment in YAME64? If that is the case I am ok with waiting. I like the fact that YAME64 just kind of works out of the box and has some pre-setup layouts already, nice work there roccio . Dare I ask if there is an expected release date? Just curious, if not no need to reply with “3-4 weeks” LOL
Sent from my iPad using Tapatalk
-
So your saying the touchscreen part doesn’t actually work at the moment in YAME64? If that is the case I am ok with waiting. I like the fact that YAME64 just kind of works out of the box and has some pre-setup layouts already, nice work there roccio . Dare I ask if there is an expected release date? Just curious, if not no need to reply with “3-4 weeks” LOL
Sent from my iPad using Tapatalk
yes, it is almost not working, but shoud (it’s still in test) be all fixed now. the new version is quite ready, some finishing things, but most of all it need a manual, and that’s a big big work.so i will say that we need a little less than 3-4 weeks…
-
Weird, it works fine for me. I tested a couple nights ago to verify that the MFDs and ICP work, and I had no problems whatsoever. When I press a button on an MFD, the cursor immediately snaps back to the BMS window, never losing focus.
-
Curious starfuryth, do you run Windows10 or Windows7?
Sent from my iPad using Tapatalk
-
Sorry for the delay.
Running windows 10, the current version of YAME64, and spacedesk on my kindle fire HD.
-
So I can confirm that I finally got touch to work on my setup. It is very intermittent and to touch a button i have to double tap. This may be due to a setting in Windows 10. More investigation is needed.
Sent from my iPad using Tapatalk
-
So I can confirm that I finally got touch to work on my setup. It is very intermittent and to touch a button i have to double tap. This may be due to a setting in Windows 10. More investigation is needed.
Sent from my iPad using Tapatalk
the double tap is a yame issue, resolved in next update.
-
So YAME64 was working just fine without touch control. Extractions working good, until it stopped working at all. YAME64 launches and then shuts down immediately. EventLog shows it having an issue with VCRUNTIME140.dll. I’ve reinstalled V C++ 2015 several times and also reinstalled YAME64 several times but it is still doing the same thing. Not sure how to resolve this. I like the extraction of gauges that YAME64 provides but now I can’t use it.
Sent from my iPad using Tapatalk
-
At least you got it to work, I just installed the latest version to play with, downloaded the latest x64 C++ Redistributable (it’s https://aka.ms/vs/16/release/vc_redist.x64.exe now, manual is incorrect), and I got as far as Page 13 (First Install) of the manual to set the path in the Global Tab. The arrow pulls down to an empty blue line that data can not be entered in. No way to point it anywhere, nada…