YAME64 suite
-
Sorry Roccio, I should have mentioned, I am trying to run the 32 bit version. I thought I had VC runtime installed, but I will check that now - perhaps not.
-
Yame64, I already have the vcruntime140 .dll. I needed 3 dll files, I have 3 in the client folder and copies again in the server folder, no luck. All three ar the 64 bit versions
-
It appears that I have .NET Framework 4 and VC++ 2013 Redistributable (x86) installed.
-
Ok, I will compile the new version with the libraries linked, so no need for download files.
Will post soon, keep in touch! -
New version released, see first post!
-
I still receive the message “YAME32_client.exe is not a valid Win32 application” when I try to run it on my client PC (Windows XP 32-bit). I have installed the VC 2015 Redistributable. Do I need to copy over any dll files? Does YAME64_server need to be running first?
-
I still receive the message “YAME32_client.exe is not a valid Win32 application” when I try to run it on my client PC (Windows XP 32-bit). I have installed the VC 2015 Redistributable. Do I need to copy over any dll files? Does YAME64_server need to be running first?
You don’t have to run the server before the client.
When I will be back at home I will try with my virtual machine.You can try is all works running the server and the client on the same machine.
Thank you
GNU file for Windows tells me that this YAME32_client.exe IS a 32 bit application, so the Windows task manager (puts a *32 after the name, indicating the 32 bit).
Try to run the client with no additional dlls others than the sfml-*.dll
-
Thanks roccio, the server now works, but the main app still gives me the same error as posted above
-
Thanks roccio, the server now works, but the main app still gives me the same error as posted above
ok, can you tell me your Windows version?
just google “the procedure entry point ucrtbase.abort could not be located” and found something with dll errors. try look for https://github.com/cmderdev/cmder/issues/501 -
Ok sorted the issue, i installed the 2015 redist c++ and it’s working now. Thanks Roccio Now to set it all up!
-
Hello Roccio, did you get a chance to try the client on your 32 bit virtual platform?
-
Hello Roccio, did you get a chance to try the client on your 32 bit virtual platform?
Tested and you were right. I recompiled the solution with XP compatibility, see first post for download link. Thank you very much.
-
Thank you for your work Roccio - the x32 client version now runs on my Windows XP client PC!
-
Thank you for your work Roccio - the x32 client version now runs on my Windows XP client PC!
Good news!
-
Hi Roccio, the CP display is up and running on the client however the altimeter reads 0 ft. and does not update - all other instruments on the CP display function properly. I looked at the engine display and noticed that the clock and RPM do not update either. This is on the 32 bit client.
-
Hi Roccio, the CP display is up and running on the client however the altimeter reads 0 ft. and does not update - all other instruments on the CP display function properly. I looked at the engine display and noticed that the clock and RPM do not update either. This is on the 32 bit client.
I will check in the next days couse now i am out for few days. I will fix all issues.
-
Maybe a stupid question, but I presume the d3d9.dll_nohook must be renamed: d3d9.dll??
-
I want to try YAME 64 using the dx hook extraction. I have a fairly typical 3 monitor setup on 1 PC with Windows 10 and BMS 4.33.1, and have been successfully using GPT and MFDE to display MFD’s and some gages. I have followed the YAME setup guide to the best of my ability but so far I can not get YAME to work. I have specified 2 windows in the client config.xml, one for right monitor and one for left monitor, in addition to the required YAME window. I have set the IP to my PC network IP of 192.168.1.151 and moved the 2 specified files to the BMS/bin/X64 folder. I left the default port values unchanged. I set the BMS path in server config.xml. The YAME server client appears to run without issue and starts the apps I configured. I get no error messages. Yet the 2 windows do not appear and I see no extracted gages. I have also tried both the hook the normal MFD extraction with the d3d9.dll_nohook file. My config files are attached. Does BMS cockpit gage extraction have to be activated?
YAME_d3d.cfg
PORT: 53100 FPS: 30 MFD: 0 0 578 200 200 196 0 824 578 200 200 64 RWRDED: 0 0 0 100 100 128 0 824 0 200 70 128
server config.xml:
<falcon><key_file>D:\Falcon BMS\User\Config\Habu BMS W10.key</key_file> <commandline><user_dtc>D:\Falcon BMS\User\Config\Habu.ini</user_dtc> <flightdataserver fps="30" port="53000">true</flightdataserver> <textureserver fps="30" port="53100">true</textureserver> <panelserver>false</panelserver></commandline></falcon> <apps><app><name>Notepad++</name> <path>e:\Utilities\Notepad++\Notepad++</path> <commandline><autostart>false</autostart> <autoclose>false</autoclose></commandline></app> <app><name>TrackIR</name> <path>D:\TrackIR\TrackIR5.exe</path> <commandline><autostart>true</autostart> <autoclose>true</autoclose></commandline></app> <app><name>Voice Attack</name> <path>D:\VoiceAttack\VoiceAttack.exe</path> <commandline><autostart>true</autostart> <autoclose>true</autoclose></commandline></app></apps> <installs><install><name>Balkans</name> <path>D:\Falcon BMS</path> <selected>true</selected></install></installs>
client config.xml
<windows><window><name>YAME</name> <width>1366</width> <height>873</height> <posx>521</posx> <posy>27</posy> <fullscreen>false</fullscreen> <border>true</border> <visible>true</visible> <background>2F3438</background></window> <window><name>LEFT</name> <width>768</width> <height>1280</height> <posx>0</posx> <posy>0</posy> <fullscreen>false</fullscreen> <border>true</border> <visible>true</visible> <background>2F3438</background> <showkey>F2</showkey></window> <window><name>RIGHT</name> <width>768</width> <height>1280</height> <posx>1920</posx> <posy>0</posy> <fullscreen>false</fullscreen> <border>true</border> <visible>true</visible> <background>2F3438</background> <showkey>F3</showkey></window></windows> <globals><server flightdataport="53000" textureport="53100">192.168.1.151</server> <enabledataexport fps="30">true</enabledataexport> <enabletextureexport fps="30">true</enabletextureexport> <smoothtextures>true</smoothtextures> <user>Habu</user> <bullseye show="false">390,464</bullseye></globals> <rwr><width>250</width> <height>250</height> <posx>186</posx> <posy>0</posy> <visible>true</visible> <window>LEFT</window> <shader>shaders/noblend.frag</shader></rwr> <left_mfd><width>436</width> <height>436</height> <posx>0</posx> <posy>332</posy> <visible>true</visible> <window>LEFT</window> <shader>shaders/noblend.frag</shader></left_mfd> <right_mfd><width>436</width> <height>436</height> <posx>924</posx> <posy>332</posy> <visible>true</visible> <window>RIGHT</window> <shader>shaders/noblend.frag</shader></right_mfd> <speedbrake><width>75</width> <height>75</height> <posx>24</posx> <posy>95</posy> <visible>true</visible> <window>LEFT</window></speedbrake> <cmds><width>156</width> <height>20</height> <posx>12</posx> <posy>5</posy> <visible>true</visible> <window>RIGHT</window></cmds> <nozzle><width>136</width> <height>136</height> <posx>0</posx> <posy>100</posy> <visible>true</visible> <window>LEFT</window></nozzle> <rpm><width>136</width> <height>136</height> <posx>0</posx> <posy>236</posy> <visible>true</visible> <window>LEFT</window></rpm> <fuel><width>200</width> <height>200</height> <posx>0</posx> <posy>508</posy> <visible>true</visible> <window>RIGHT</window></fuel> <fuelflow><width>145</width> <height>126</height> <posx>227</posx> <posy>107</posy> <visible>true</visible> <window>RIGHT</window></fuelflow> <hsi><width>229</width> <height>229</height> <posx>121</posx> <posy>464</posy> <visible>true</visible> <window>RIGHT</window></hsi>
-
Update: OK, I have been able to get my 2 extra windows running with the gages on them. Now it is a matter of fine tuning the sizes and positions. Still need advice on dx hook implementation.
-
For the hook to work you must set hook via the server application. It will rename the dll automatically. Launch Falcon with server button