YAME64 suite
-
At least on my Setup in order to get Yame 64 with BMS 4.3.4 running I had to install 4.3.3 as well and set g_bExportRTTexture on both
-
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.
-
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.
-
I’m having the same issues on my end with YAME1.2 at the moment and haven’t found a solution yet (I’m extracting the gauges using YAME 1.2 and use RTT remote for the MFDs as a workaround, check your BMS “Tools” folder).
I’ve double checked the falcon bms.cfg settings, the 3dhook.dll (or its “non-presence”, rather :)), both 4.33 and 4.34 are installed, so mfd extraction should work in theory (and it does with RTT remote and in komurcu’s android app, just not with YAME).
I can post my yame64 cfg later if that’s any help.
All the best, Uwe
-
A long shot, but for at least 1 person I know of it worked: Can you hit the “remove hook files” button in the “globals” tab? Even though no visible 3d hook dll files present before, after clicking that button it suddenly did recognise the rttextracture setting.
-
A long shot, but for at least 1 person I know of it worked: Can you hit the “remove hook files” button in the “globals” tab? Even though no visible 3d hook dll files present before, after clicking that button it suddenly did recognise the rttextracture setting.
Just tried it, sadly the “remove hook files” is ghosted on my “global” tab. Checked the logs, didn’t see any obvious errors, I’ll paste the yame config shortly.
Cheers, Uwe
xml config:
-
Hello everyone!
I think since the update “KB4522741 .NET Framework 3.5 and 4.8 for Windows 10 Version 1903” for Windows 10 I cannot open Yame anymore. I’ve installed the update on 3.12.19. Before everything was good. No changes we’re made from my side.
The issue:
Clicking on Yame, no window opens. Application doesn’t start.
My tries to fix it:
1. Run as admin: no success
2. Install the Windows fix update: https://support.microsoft.com/en-us/help/4530743/kb4530743-update-for-net-framework–-no success
3. Bitdefender Anti-virus software is checked. No block from the software.Falcon Config File
g_bExportRTTTexture= 1YAME64.xml
<apps version=“1.2”><falcon><windowed>false</windowed>
<path>C:\Falcon BMS 4.33 U1</path></falcon>
<server refreshrate=“30” port=“53000”><texturehook>false</texturehook>
<keyserver>false</keyserver></server>
<client refreshrate=“30” runserver=“false”><texturehook>false</texturehook>
<server port=“53000”>local</server>
<smoothtextures>true</smoothtextures>
<mipmaptextures>true</mipmaptextures>
<layout>Ice1ScreenSetup_v121.xml</layout>
<usetouchscreen>true</usetouchscreen></client></apps>Any suggestions?
Thank you!
-
Hello everyone!
I think since the update “KB4522741 .NET Framework 3.5 and 4.8 for Windows 10 Version 1903” for Windows 10 I cannot open Yame anymore. I’ve installed the update on 3.12.19. Before everything was good. No changes we’re made from my side.
The issue:
Clicking on Yame, no window opens. Application doesn’t start.
My tries to fix it:
1. Run as admin: no success
2. Install the Windows fix update: https://support.microsoft.com/en-us/help/4530743/kb4530743-update-for-net-framework–-no success
3. Bitdefender Anti-virus software is checked. No block from the software.Falcon Config File
g_bExportRTTTexture= 1YAME64.xml
<apps version=“1.2”><falcon><windowed>false</windowed>
<path>C:\Falcon BMS 4.33 U1</path></falcon>
<server refreshrate=“30” port=“53000”><texturehook>false</texturehook>
<keyserver>false</keyserver></server>
<client refreshrate=“30” runserver=“false”><texturehook>false</texturehook>
<server port=“53000”>local</server>
<smoothtextures>true</smoothtextures>
<mipmaptextures>true</mipmaptextures>
<layout>Ice1ScreenSetup_v121.xml</layout>
<usetouchscreen>true</usetouchscreen></client></apps>Any suggestions?
Thank you!
Don t know what Is the problem, bit are you dire that game shoul rum on a monitor ti the letto of the main One?
Try to set ui pos x to zero -
The problem is, that I can’t start Yame for some reason. When I click on the .exe file, nothing happens.
-
Try to set in yame64.xml the ui pos x and y to 0.
-
Okay thank you. Will try it today.
-
I had no success with this change. Maybe I have to change something other?
Maybe it has to do with this windows issue? I installed the windows fix, but no success.
-
good evening
I have W10 1909
No worries with Yame.
I give you my .xml for a test if you want it.<apps version="1.2"><falcon><windowed>false</windowed> <path>C:\Falcon BMS 4.33 U1</path></falcon> <server refreshrate="30" port="53000"><texturehook>false</texturehook> <keyserver>true</keyserver></server> <client refreshrate="30" runserver="false"><texturehook>false</texturehook> <server port="53000" sync="false">192.168.0.38</server> <smoothtextures>true</smoothtextures> <mipmaptextures>true</mipmaptextures> <layout>FALCON 4_34 4K.xml</layout> <usetouchscreen>false</usetouchscreen></client></apps>
-
Dear Santa, all I want for Christmas is YAME v2.
-
Dear Santa, all I want for Christmas is YAME v2.
-
-
Dear Santa, all I want for Christmas is YAME v2.
……then I would finally be able to migrate to 4.34
-
……then I would finally be able to migrate to 4.34
What’s holding you back? At least 4 in our sqn are running Yame and 4.34 just fine.
-
……then I would finally be able to migrate to 4.34
Same here I run YAME with 4.34 without any issues
Gesendet von meinem SM-G930F mit Tapatalk
-
What’s holding you back? At least 4 in our sqn are running Yame and 4.34 just fine.
I think you’re referring to 4.34 with the 4.33 ‘workaround’, yes?