YAME64 suite
-
The DirectX hook is not working for 4.34. So disable it and remove the d3d9.dll from <falconbms>\bin\x64 folder</falconbms>
Thanks for the swift reply. I ended up reinstalling .34 and everything worked again.
But I just checked, there’s no such dll in the .34 bin-folder. Or will starting yame add that in the folder?
-
Thanks for the swift reply. I ended up reinstalling .34 and everything worked again.
But I just checked, there’s no such dll in the .34 bin-folder. Or will starting yame add that in the folder?
Yes, the dll is copied there by yame, so if not present no worries.
-
What do i need to modify in CPD 60 map file, in order for a/c position to be displayed properly in other theaters?
For example in EMF theater i save the map via WDP (png), then i resize it to 2048x2048 px but the a/c position is not properly displayed in map.
Any advice?
Thx in advance -
What do i need to modify in CPD 60 map file, in order for a/c position to be displayed properly in other theaters?
For example in EMF theater i save the map via WDP (png), then i resize it to 2048x2048 px but the a/c position is not properly displayed in map.
Any advice?
Thx in advanceThat map display wont work on all theaters. Will on a future update…
-
Just curious, yame64 for 4.34 is still alive? Or are we sticking with the 4.33 work around with no hook? Or waiting for the next bms update?, like i said just curious, as i check almost daily for news
-
Just curious, yame64 for 4.34 is still alive? Or are we sticking with the 4.33 work around with no hook? Or waiting for the next bms update?, like i said just curious, as i check almost daily for news
Yame is not dead, but it’s very late due to real life work. Please have patience and if someone wants to help let me know. (C++ skills required)
-
Sorry i do not even understand a++ let alone c++, however if you need somebody to put it through it paces at some point, i would gladly look for bugs/glitches problems before beta testing or beta testing, ….im happy running yame as it stands, i have no problems with it, the only down side was… running low on ssd space and looking at when i could remove 4.33 , sorry i cant help more, and happy to be patient, as i said i had not heard anything for a while, and was curious, its a great App, and i am sure others will now be relieved its still in the works …thanks HC
-
+1
-
Really wish I’d had the skills to help you Roccio
Keep up what you do, many many people truly appreciate it -
Yame is not dead, but it’s very late due to real life work. Please have patience and if someone wants to help let me know. (C++ skills required)
Curious why you haven’t made the repository public like on Github. if you need help that’s how to do it. Make it open source so others can contribute.
-
May be a dumb question. Where can I find a download for 4.33 from a trusted site? I have upgraded all my PC’s and don’t have it anymore.
-
Still download from releases and updates on this forum front page.
-
-
Is it possible to click the OSB buttons with mouse? every time I hover on them it switches the focus to bms.
-
This post is deleted! -
Hi folks,
I’ve reverted to YAMEv1.2 for now with BMS following the how-to guide posted on YAME’s website. The gauges extract & update fine, but I’m not getting any images from either MFD. Any idea what could be causing this?
RTTremote works fine OTOH, so it must be something on YAME’s end that’s preventing MFD extraction.
Thanks in advance & all the best,
Uwe
-
I can not get YAME 64 v1.2 to work on my Win 10 PC. Previously I had it working with BMS 4.34 but my windows crashed (for other reasons) so I reinstalled Win 10 on a reformatted drive. I then loaded BMS 4.33 U1-U5, BMS 4.34, and YAME64 v1.2. I also installed MS Visual C++ as shown bellow:
When I launch YAME, this is how it starts:
The Global tab is blank and looks like this:
When I start the Client I get this error message:
However, both Falcon BMS.cfg files in 4.33 U1 and 4.34 are set to 1 as shown below:
I also made sure the Registry was changed to C:\Falcon BMS 4.34 as shown below:
Additionally, the YAME64.xml path is set to the correct location as shown below:
The YAME log file looks like this:
At this point, I am not sure what to do. I tried to uninstall all versions of BMS and YAME64 v1.2, and then reinstalling them with no change in failure.
Again, I previously had YAME64 v1.2 running great with BMS 4.34 before my Win 10 crashed hard, forcing me to reinstall Win 10 on a reformatted drive. So I know my PC is totally compatible. I am thinking it is some setting or .cfg that is not correct, but I am unable to locate it. I followed the How-to from the YAME web site with regards to the v1.2 workaround and BMS 4.34.
I’m not sure what to do next. Any help would be much appreciated. Thank you.
I managed to get the YAME Client to start with the extracted screen to display on my second monitor (see picture below) but when I start to fly with BMS 4.34 the MFD, DED and RWR symbology is not extracted. The extraction remains blacked out. I’ve tried to reinstall YAME again and got the same results. Does anyone have any suggestions on how I can resolve this?
-
I managed to get the YAME Client to start with the extracted screen to display on my second monitor (see picture below) but when I start to fly with BMS 4.34 the MFD, DED and RWR symbology is not extracted. The extraction remains blacked out. I’ve tried to reinstall YAME again and got the same results. Does anyone have any suggestions on how I can resolve this?
All good now. I reinstalled BMS for the third time and the displays extract as designed. Thanks to all that gave input.
-
All good now. I reinstalled BMS for the third time and the displays extract as designed. Thanks to all that gave input.
Not so fast…I thought it was fixed, however I was using 4.33 when it was working. Realizing this, I changed to 4.34 and the extraction is still blacked out. So I’m back with the same issue. Any suggestions?
-
Sure 4.34 does not contain the 3Dhook dll anymore and rttexport is set to 1?