YAME64 suite
-
I’m confused… you said you have a Helios profile? That should solve everything… unless your Helios profile is not on a touchscreen?
I use second monitor with mfds on it. I use all rockets and buttons with actions in BMS and all of them are used. I run also an hellios profile for setting key combinations for change B60 center mfd, as you can see in my video, for instance, change zoom, map color and son on. But I manage with mouse not a touch screen.
-
-
man - helios works now on w10-32bit-tabelt, i installed the dx9 setup from the bms install files, so the 8 butons working …
-
man - helios works now on w10-32bit-tabelt, i installed the dx9 setup from the bms install files, so the 8 butons working …
Looking nice!
Care to elaborate on how you set this up? -
Looking nice!
Care to elaborate on how you set this up?dx9 ? Open “DirectX_Jun2010_redist_2011-04-18.bsf” from BMS setup files, after this, i could then install helios.
I’d rather have the buttons in yame!!! -
dx9 ? Open “DirectX_Jun2010_redist_2011-04-18.bsf” from BMS setup files, after this, i could then install helios.
I’d rather have the buttons in yame!!!We’re looking into some options. Most likely the new release will not yet have the outside bezel (as pit builders tend to have real hardware bezels) but the labels would be clickable so it can work with a touchscreen
-
Came across this error today; I simply took out a few lights from my YAME profile, saved it under a new profile name, then ran YAME CLIENT. It gave me that error for both screens and my gauges still showed up but no masking. I edited a gauge in my center screen (+1 pixel on both horizontal and vertical) and that seemed to force YAME to make a new mask for my center screen but my left screen still showed the error and still had no masking. I had to edit a gauge on THAT screen to force YAME to make a new mask for the left screen. Both screens are working now, but weird that they didn’t re-mask all by themselves and I had to do this workaround.
-
I fly BMS single-player mode in 64 bit; however I also enjoy flying multi-player on the VG server (32bit). I am therefore trying to install both YAME64 and YAME32 on the same client PC. Installing YAME32 after installing YAME64 corrupts both programs. Perhaps because YAME32 automatically installs in the same folder as YAME64 with no install options to choose another. YAME32 returns the following errors:
MSVCP140.dll missing from your computer
VCRUNTIME140.dll missing from your computerLog folder is empty. I tried installing YAME64, then remaming YAME64 folder, then installing YAME32. YAME64 will then run, but not YAME32. Any suggestions how to overcome this problem?
-
I fly BMS single-player mode in 64 bit; however I also enjoy flying multi-player on the VG server (32bit). I am therefore trying to install both YAME64 and YAME32 on the same client PC. Installing YAME32 after installing YAME64 corrupts both programs. Perhaps because YAME32 automatically installs in the same folder as YAME64 with no install options to choose another. YAME32 returns the following errors:
MSVCP140.dll missing from your computer
VCRUNTIME140.dll missing from your computerLog folder is empty. I tried installing YAME64, then remaming YAME64 folder, then installing YAME32. YAME64 will then run, but not YAME32. Any suggestions how to overcome this problem?
For the missing dlls for YAME32, you need to have the visual studio 2015 x86 files installed, not only x64.
Install path error between versions will be added to the issue tracker, but you should be able to run BMS 32bit with the YAME64 version.
-
Thanks. Figured out how to run YAME64 with BMS 32 bit.
-
-
Well, actually I am not totally sure, it just worked by starting the YAME64 client, then starting BMS 32 bit from the BMS icon. I think one must copy YAME d3d9.dll and yame_d3d.cfg to BMS/bin/x64 folder.
-
The d3d9.dll provided with YAME64 and YAME32 is not compatible with Falcon BMS 32 bit. It’s only for the 64 bit. If you want, we can build a specific dll for the 32 bit version.
-
The d3d9.dll provided with YAME64 and YAME32 is not compatible with Falcon BMS 32 bit. It’s only for the 64 bit. If you want, we can build a specific dll for the 32 bit version.
roccio
I have a 64bit operating system, win 8.1 but I have to run BMS in 32bit because of problems with FreeTrack if I use 64bit.
So do I need the “specific dll for 32 bit version” if so then yes please to your kind offer.
weepop
-
but I have to run BMS in 32bit because of problems with FreeTrack if I use 64bit.
cough!!TrackIRcough!!
-
After rechecking, my bin/x86 folder does NOT have a d3d9.dll file, so I am not sure why it works. I do use TrackIR, though.
-
After rechecking, my bin/x86 folder does NOT have a d3d9.dll file, so I am not sure why it works. I do use TrackIR, though.
the dll is only there when you use 3Dhook extraction instead of RTTexture extraction.
-
roccio
I have a 64bit operating system, win 8.1 but I have to run BMS in 32bit because of problems with FreeTrack if I use 64bit.
So do I need the “specific dll for 32 bit version” if so then yes please to your kind offer.
weepop
Try opentrack, works very well
Inviato dal mio Y635-L21 utilizzando Tapatalk
-
Try opentrack it works very well
Inviato dal mio Y635-L21 utilizzando Tapatalk
-
Hi Roccio, first of all, thank you for your excellent work. It’s wonderful, great, I have no qualifiers to describe it. I wanted to make a suggestion, if possible of course, if you could implement in your program the possibility of sending the DED to keyboards, with screen, like G15, G13, etc. It would then be super. Of course it is a constructive criticism. THANKS AGAIN MY FRIEND.