YAME64 suite
-
Thanks for the update, roccio. I was wondering if your tool also “suffers” from the mfde problems with certain theaters or does it work reliably with all addon theaters currently supported in 4.33U2?
All the best,
Uwe
I have tested KTO and Balkans without problem. Can’t tell about other theaters.
-
Well done!
Not had long to wait after all
Had a glance though the manual and have a question.
I see you are able to get YAME to start other applications, can we set a delay between each application starting.
Mogas……
-
Well done!
Not had long to wait after all
Had a glance though the manual and have a question.
I see you are able to get YAME to start other applications, can we set a delay between each application starting.
Mogas……
There is no delay as you have to run every single application selecting it and press the “run” button; so you can wait whatever you want between one run and the other. Maybe in the future we can plan to do an auto run with delay.
-
There is no delay as you have to run every single application selecting it and press the “run” button; so you can wait whatever you want between one run and the other. Maybe in the future we can plan to do an auto run with delay.
Ok, thank you for explaining. I thought it might be like a .bat file.
Can’t wait to try this out later.
Mogas……
-
Thanks very much for the release. I
m probably misunderstanding instructions because I get blank mfd
s using the recommended ? D3D hook option with set g_bExportRTTTextures 0 as it seems to say. Mfd`s work fine in the other mode ( combined with set g_bExportRTTTextures 1 ).
Running just client with bms on solo pc. -
Thanks very much for the release. I
m probably misunderstanding instructions because I get blank mfd
s using the recommended ? D3D hook option with set g_bExportRTTTextures 0 as it seems to say. Mfd`s work fine in the other mode ( combined with set g_bExportRTTTextures 1 ).
Running just client with bms on solo pc.Check that the file d3d9.dll is present in your bin\x64 folder. Then send me your yame64.xml and the logs
-
I have no bin\x64 folder anywhere. I have a 442k d3d9.dll in the root of Yame (installed to my H:/ drive. I also have a 2k d3d9.dll in system32 folder
02/11/2016 19:01:22: Texture extraction resolution: 1200
02/11/2016 19:01:22: Data extraction: true
02/11/2016 19:01:22: Texture extraction: hook
02/11/2016 19:01:32: Unable to load briefing file.
02/11/2016 19:06:00: Client::run ended.<apps><falcon><windowed>true</windowed>
<keyfile>BMS - Full - Copy (2).key</keyfile>
<dtcfile>Cobalt UK.ini</dtcfile>
<path>D:\Falcon BMS 4.33 U1</path></falcon>
<server refreshrate=“30” port=“53000” hookport=“53100”><exportflightdata maxclients=“1”>false</exportflightdata>
<exporttexture maxclients=“1”>false</exporttexture>
<keyserver>false</keyserver></server>
<client refreshrate=“30” runserver=“false”><flightdata>true</flightdata>
<texture>hook</texture>
<server port=“53000” hookport=“53100”>local</server>
<smoothtextures>true</smoothtextures>
<layout>default.xml</layout></client></apps> -
I was referring to falcon bms x64\bin folder. Sorry for not being clear. Remember to hit apply in every tab.
-
I should have realised. Well no dll in that location but I copied it there from Yame64 folder but did not result in mfd getting graphics. Its likely my error and its working fine with the non hook method. Thanks
-
Okay, first off, you guys ROCK!! I really like the program and the ability to set size and screen coordinates of a gauge is really, really awesome! I’ve got the program to run on my networked PC but noticed that sometimes, after exiting a flight and then flying again, the client would not respond. I’m not sure exactly what it is I’m doing that causes this but I wonder if you guys have any idea what might be the culprit? To avoid this, I run both server and client, wait a few seconds, THEN start BMS.
One suggestion I would like to make…. can you please make the client-side install stop asking me to set BMS path/DTC/etc.? When I start up the client, it keeps saying “Value(s) not set… blah blah blah”… an option to “Never ask me about this again” would be great!
An issue I’ve come up against, again on the client-side, is that I can tick “Enable texture data” under the Extractions tab, but I cannot tock the “Use Direct3D hook”… the tick box itself does not become active.
So far, that’s all I’ve come across… I’m too busy dancing a jig for all this awesome work! I owe BOTH of you guys a couple of beers!
-
After setting everything up I must say I’m really impressed!
Well Done !!!
The textures look beautiful, setting up is very straight forward and the moving map bonus is a real treat.
As for for the FPS price…less than 5.
RWR…beautiful !A few issues/ requests:
1. Your ADI and HSI textures are different in size regarding the inner bezel in comparison to BMS (smaller).
Any reason for that?
2. Moving map doesn’t show the whole route as per the manual.
3. VVI display flickers all the time (bright to dark).
4. The DED is the only instrument that lacks the frame texture (cockpit bezel).And…can you please explain the meaning of the hook section.
What is it for?All in all…thank you !
For a version 1 it’s amazing. -
Thank you for YAME64, it’s fantastic!
I also can’t get the client hook function to work.
I have set everything as per the manual, on a single PC, with d3d9.dll copied from the YAME64 directory to the x64 directory.
I have tried the example configs and my own creations.
When I start BMS I have only still images on the MFDs, while the CP and ENG gauges are working normally.
The hook log shows the following:
03/11/2016 17:46:32: *************************************************
03/11/2016 17:46:32: * YAME64_d3d: InitInstance called *
03/11/2016 17:46:32: *************************************************
03/11/2016 17:46:32: Direct3D9 created.
03/11/2016 17:46:48: ERROR - Unable to load configuration file
03/11/2016 17:46:48: StartMFDThread–------------------
03/11/2016 17:46:48: MFDThreadFunc…--------------------
03/11/2016 17:46:48: ACCEPTING…
03/11/2016 17:47:11: …StopSendingData----------------------
03/11/2016 17:47:27: YAME64_d3d: ExitInstance called.
03/11/2016 17:47:27: CloseAll-----------------------Thanks again and let me know if there is anything else I can try to help diagnose my problem.
Cheers,
- Bear
-
I have no bin\x64 folder anywhere. I have a 442k d3d9.dll in the root of Yame (installed to my H:/ drive. I also have a 2k d3d9.dll in system32 folder
02/11/2016 19:01:22: Texture extraction resolution: 1200
02/11/2016 19:01:22: Data extraction: true
02/11/2016 19:01:22: Texture extraction: hook
02/11/2016 19:01:32: Unable to load briefing file.
02/11/2016 19:06:00: Client::run ended.<apps><falcon><windowed>true</windowed>
<keyfile>BMS - Full - Copy (2).key</keyfile>
<dtcfile>Cobalt UK.ini</dtcfile>
<path>D:\Falcon BMS 4.33 U1</path></falcon>
<server refreshrate=“30” port=“53000” hookport=“53100”><exportflightdata maxclients=“1”>false</exportflightdata>
<exporttexture maxclients=“1”>false</exporttexture>
<keyserver>false</keyserver></server>
<client refreshrate=“30” runserver=“false”><flightdata>true</flightdata>
<texture>hook</texture>
<server port=“53000” hookport=“53100”>local</server>
<smoothtextures>true</smoothtextures>
<layout>default.xml</layout></client></apps>If you don’t run Falcon BMS with the button “Start Falcon” you have to manually copy the hook files. These are d3d9.dll located in the installation folder of YAME and yame_d3d.cfg located in <yame installation=“” folder=“”>/conf
For a one PC configuration this config must be like this:
PORT: 0
FPS: 30
MFD: 0 0 0 0 0 0 0 0 0 0 0 0
DEDRWR: 0 0 0 0 0 0 0 0 0 0 0 0</yame> -
Okay, first off, you guys ROCK!! I really like the program and the ability to set size and screen coordinates of a gauge is really, really awesome! I’ve got the program to run on my networked PC but noticed that sometimes, after exiting a flight and then flying again, the client would not respond. I’m not sure exactly what it is I’m doing that causes this but I wonder if you guys have any idea what might be the culprit? To avoid this, I run both server and client, wait a few seconds, THEN start BMS.
First thank you! Never noticed your issue, will check.
One suggestion I would like to make…. can you please make the client-side install stop asking me to set BMS path/DTC/etc.? When I start up the client, it keeps saying “Value(s) not set… blah blah blah”… an option to “Never ask me about this again” would be great!
This is strange, this message should come only the first time you run YAME, then (answer yes to set values) it should never ask again. Check that YAME64.xml in conf directory and default.xml in layout directory has been created.
An issue I’ve come up against, again on the client-side, is that I can tick “Enable texture data” under the Extractions tab, but I cannot tock the “Use Direct3D hook”…. the tick box itself does not become active.
So far, that’s all I’ve come across… I’m too busy dancing a jig for all this awesome work! I owe BOTH of you guys a couple of beers!
In which tab you cannot tick the HOOK box?
If you want to use hook in network configuration only the server can be set. In local configuration only the client. -
After setting everything up I must say I’m really impressed!
Well Done !!!Thank you!
The textures look beautiful, setting up is very straight forward and the moving map bonus is a real treat.
As for for the FPS price…less than 5.
RWR…beautiful !If using hook you should get even less fps impact!
A few issues/ requests:
1. Your ADI and HSI textures are different in size regarding the inner bezel in comparison to BMS (smaller).
Any reason for that?Never noticed this
2. Moving map doesn’t show the whole route as per the manual.
In order to show the route you MUST save the DTC file when you are in Falcon 2d.
3. VVI display flickers all the time (bright to dark).
Never had this issue, will check.
4. The DED is the only instrument that lacks the frame texture (cockpit bezel).
If you like I think we can add it.
And…can you please explain the meaning of the hook section.
What is it for?The directx hook is a way to get texture data without using the default Falcon BMS extractor. It’s a fake d3d9.dll that is used as a “bridge” to the real one (you will find in windows/system folder), but with special functions so that it grabs the rendering buffer and send it to YAME client. The advantage is that it is done in a separate thread so that Falcon will not have to wait for the copy to finish. If you enable YAME hook and disable texture extraction in Falcon, you will have the smoothest experience.
Ask if you have problems setting it to work.All in all…thank you !
For a version 1 it’s amazing. -
This is strange, this message should come only the first time you run YAME, then (answer yes to set values) it should never ask again. Check that YAME64.xml in conf directory and default.xml in layout directory has been created.
Yes, it came up only once on the SERVER side where Falcon was installed. Obviously, on my secondary PC that does NOT have Falcon installed, I answer “No” and so it asks me that question each time I start up YAME64
-
Yes, it came up only once on the SERVER side where Falcon was installed. Obviously, on my secondary PC that does NOT have Falcon installed, I answer “No” and so it asks me that question each time I start up YAME64
ok thank you, will fix this!
-
1. Your ADI and HSI textures are different in size regarding the inner bezel in comparison to BMS (smaller).
Any reason for that?ADI is based on TomCatz high res pit textures, so if they are ike that in his version, it’s like that in YAME
HSI is based on a real picture I took, so it resembles real life size on that matter. -
If you don’t run Falcon BMS with the button “Start Falcon” you have to manually copy the hook files. These are d3d9.dll located in the installation folder of YAME and yame_d3d.cfg located in <yame installation=“” folder=“”>/conf
For a one PC configuration this config must be like this:
PORT: 0
FPS: 30
MFD: 0 0 0 0 0 0 0 0 0 0 0 0
DEDRWR: 0 0 0 0 0 0 0 0 0 0 0 0</yame>This fixed my problem!
Thank you very much for your work gentlemen.
- Bear
-
This fixed my problem!
Thank you very much for your work gentlemen.
- Bear
Remember to disable falcon bms default extraction for best performance! (set g_bExportRTTTextures 0 in falcon bms.cfg)