<p>@kungfoo<strong> - thank you for this app. It is great, simple and just works!!</strong><br /><br />Thank you.</p>
Latest posts made by walkman
-
RE: New free MFD/ICP app to control Falcon BMS from touch devices
-
RE: YAME64 suite
Yes, g_bExportRTTTexture are set to 1 in 4.34 and 4.33, and there are no 3DHook dll files in the x64 folder that I am seeing. See Pics below:
And yes, the simple test of the ADI and Altimeter gauges works. I was surprised that they did.
The only problem appears to be that the MFDs, DED, and RWR symbology are not displaying. I have blacked out extractions for those displays.
Anybody have any suggestions? Help is greatly appreciated to solve this issue.
-
RE: YAME64 suite
Ok, seems all good. So please double check if the g_bExportRTTTexture is set to 1 in your falcon bms.cfg.
As a simple test, other gauges (like an altitude or ADI) do work?Yes, g_bExportRTTTexture are set to 1 in 4.34 and 4.33, and there are no 3DHook dll files in the x64 folder that I am seeing. See Pics below:
And yes, the simple test of the ADI and Altimeter gauges works. I was surprised that they did.
The only problem appears to be that the MFDs, DED, and RWR symbology are not displaying. I have blacked out extractions for those displays.
-
RE: YAME64 suite
I was referring to YAME configuration file, not Falcon.
My bad, the file is called YAME64.xml and should be located in conf folder of the yame installation path.
I can’t remember well as it is now all different…Here is a pic of my YAME64.xml. I could not figure out how to attach the file to this message.
Again, thanks for the help.
-
RE: YAME64 suite
Yes that is correct. There is no 3Dhook dll in the Falcon BMS 4.34/Bin/x64 folder, and the set g_bExportRTTTexture is set to 1 in the 4.33 and 434 falcon_bms.cfg file.[/QUO
Please, s3nd me your config.xml file
I am unsure where I can find this related file. Can you direct me to where I can find the config.xml file you are referring to. When I did a global search on Drive C for config.xml, these are the files that were retrieved.
Thank you for your help.
-
RE: YAME64 suite
Sure 4.34 does not contain the 3Dhook dll anymore and rttexport is set to 1?
Yes that is correct. There is no 3Dhook dll in the Falcon BMS 4.34/Bin/x64 folder, and the set g_bExportRTTTexture is set to 1 in the 4.33 and 434 falcon_bms.cfg file. Thanks for responding. Any further suggestions from anyone would be much appreciated.
-
RE: YAME64 suite
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?
-
RE: YAME64 suite
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.
-
RE: YAME64 suite
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?
-
RE: YAME64 suite
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.