YAME64 suite
-
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)
-
Can someone point me to how to work with hook extraction in the manual? I’ve tried looking and can’t seem to find anything relevant. Again, my setup is having a server PC and having a different PC on network.
Also, on the Client -> Windows -> Edit, I have Fullscreen, Visible, Masked, and Antialiasing ticked. On the server PC, when I run the client, the gauges show up but I can still see my PC’s desktop/background. On the client PC, I run the client and the gauges show up but I cannot see my PC’s background, there is a colored background that shows up. I tried exporting my .XML setup file from my server to my client PC, load it on the client PC, but still no joy… running YAME client on the client PC still shows a background and not the desktop. Any ideas?
-
Okay, three suggestions now:
1. 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!
2. When going to the Edit Gauges part of the program, please make it possible to move a gauge with the arrow keys and make the movement 1-pixel per press. That would enable me to make super-accurate adjustments without getting carpal tunnel from gripping the mouse too tight.
3. When going to the Edit Gauges part of the program, please make it possible to have the option to have the grid on or off by default.Thanks!
-
Can someone point me to how to work with hook extraction in the manual? I’ve tried looking and can’t seem to find anything relevant. Again, my setup is having a server PC and having a different PC on network.
You can use hook in server side or client side, depends on your configuration. As you said you have a network configuration this is what you have to do:
-
Start YAME on server PC
-
go to SERVER TAB and enable the texture data checkbox
-
enable “use Direct3D hook” and set port as you like
-
hit Apply
-
go to HOOK TAB and check that you have selected “send texture to client”
-
hit Apply
-
Start YAME on Client PC
-
go to CLIENT TAB
-
check “enable texture data”
-
check “use Direct3D hook”
-
set “Get data from network”
-
set server ip
-
set server port for flight data
-
set hook port (the one you set in server pc)
-
hit Apply
Now on server PC you can hit “Start YAME server” and on client PC “Start YAME client” on the RUN TAB.
Then on the server PC you can hit “Launch Falcon BMS” to start Falcon and the hook files will be automatically copied in the right folder. If you run Falcon of your own, th you have to copy “d3d9.dll” located in <yame_installation_dir>and “yame_d3d.cfg” located in <yame_installation_dir>/conf in <falcon_installation_dir>\Bin\x64Also, on the Client -> Windows -> Edit, I have Fullscreen, Visible, Masked, and Antialiasing ticked. On the server PC, when I run the client, the gauges show up but I can still see my PC’s desktop/background. On the client PC, I run the client and the gauges show up but I cannot see my PC’s background, there is a colored background that shows up. I tried exporting my .XML setup file from my server to my client PC, load it on the client PC, but still no joy… running YAME client on the client PC still shows a background and not the desktop. Any ideas?
I don’t fully understand this part. Why you are running the client on the server PC? Do you want extraction on multiple PC?
The fact that you see the desktop under the gauges is due to the “Masked” setting. Untick this and you will have a solid background.</falcon_installation_dir></yame_installation_dir></yame_installation_dir> -
-
Okay, three suggestions now:
1. 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!
2. When going to the Edit Gauges part of the program, please make it possible to move a gauge with the arrow keys and make the movement 1-pixel per press. That would enable me to make super-accurate adjustments without getting carpal tunnel from gripping the mouse too tight.
3. When going to the Edit Gauges part of the program, please make it possible to have the option to have the grid on or off by default.Thanks!
Thank you for your suggestions!
1. have been resolved and released in next update.
2. will implement this
3. you can enable/disable the grid right clicking on the window background (no on a gauge) and set the option. -
AOA and VVI gauges…confirmed there is an issue.
1. They are not steady and keep moving up and down in minute frequent movements/ like micro stutters.
2. AOA ticks/ marks keep flickering to a point that it’s not comfortable to look at the whole gauges.As for the hook…indeed everything is much smoother and fps went up by 10 !
-
You can use hook in server side or client side, depends on your configuration. As you said you have a network configuration this is what you have to do:
-
Start YAME on server PC
-
go to SERVER TAB and enable the texture data checkbox
-
enable “use Direct3D hook” and set port as you like
-
hit Apply
-
go to HOOK TAB and check that you have selected “send texture to client”
-
hit Apply
-
Start YAME on Client PC
-
go to CLIENT TAB
**_- check “enable texture data” -
check “use Direct3D hook”_**
-
set “Get data from network”
-
set server ip
-
set server port for flight data
-
set hook port (the one you set in server pc)
-
hit Apply
This is where I’m having problems. On the client PC, I am on the CLIENT Tab, “Enable flight data” and “Enable texture data” are both ticked but I cannot tick the “Use Direct3D hook” checkbox. It is not active, I cannot click on it.
As a result, I have “Get data from network” ticked and IP and port is entered but the Hook port section is still grayed out.
I don’t fully understand this part. Why you are running the client on the server PC? Do you want extraction on multiple PC?
The fact that you see the desktop under the gauges is due to the “Masked” setting. Untick this and you will have a solid background.I think I’ve sorted it out. My client PC has two screens arranged as 2-1 meaning my secondary screen is on the left, main screen on the right. My instruments are set up as if my main screen is 0, 0 coordinates on the upper left (so secondary screen is -1920, 0). On the CLIENT -> WINDOWS tab, it is set as 1920 width and 1080 height. For some reason, YAME draws the instruments based on the main screen, respecting the 0, 0 coordinates but the masking starts on the leftmost screen, using the -1920, 0 coordinates despite Pos X: 0 and Pos Y: 0. The fix was to set the width at 3840 and height at 1080 so that the masking stretched across both screens.
-
-
-Ice, send me your YAME64.xml (located in conf folder) please, I will check.
-
How?
-
This is where I’m having problems. On the client PC, I am on the CLIENT Tab, “Enable flight data” and “Enable texture data” are both ticked but I cannot tick the “Use Direct3D hook” checkbox. It is not active, I cannot click on it.
As a result, I have “Get data from network” ticked and IP and port is entered but the Hook port section is still grayed out.Take a look at the one to last final chapter on the traineer/instructor setup. That should be the same for a network/client setup with two different pc’s.
If you wish to use 3Dhook, the server should be in 3Dhook; but the client cannot because it has no BMS running to extract 3D from. So client should receive from server. The server will convert the BMS 3DHook textures to normal textures and send it to the client, where it is interpreted as regular non-3DHook textures. -
Ah, will try that then! Thanks!
-
First of all… BIG TIME THANKS.
Secondly.- HUGE TIME THANKS.
An finally (as expected) a request: As an F18 lover, is there any way to fix the extraction of MFDs/DED/RWR for the F18’s? (and possible to other flyable jets included in 4.33)… they showed messed up.
Also, how/where do we have to put/include new maps, in what format/size etc.
Keep it up and one more time: THANKS!
-
First of all… BIG TIME THANKS.
Secondly.- HUGE TIME THANKS.
An finally (as expected) a request: As an F18 lover, is there any way to fix the extraction of MFDs/DED/RWR for the F18’s? (and possible to other flyable jets included in 4.33)… they showed messed up.
Also, how/where do we have to put/include new maps, in what format/size etc.
Keep it up and one more time: THANKS!
For the F18 I think we can put the possibility in a next release, as seems to be one of the fav planes. For other planes maybe we can try to add some new “generic” gauge so you can build your pit as you like.
For the maps for now you can replace the one provided in YAME64\gauges\cp60\maps as png at 2048x2048. or adding new theaters it will be in future version.and
Thank you!
-
Just plugging my other thread here just in case anyone can help… basically need assistance getting Helios to work over a network.
-
roccio, can YAME display stuff at negative coordinates? My center screen is 0, 0 so the left screen is -1920, 0. I want to display stuff on the left screen but when running YAME, the gauge (Landing gear) disappears.
ps. check PM!
-
roccio, can YAME display stuff at negative coordinates? My center screen is 0, 0 so the left screen is -1920, 0. I want to display stuff on the left screen but when running YAME, the gauge (Landing gear) disappears.
ps. check PM!
Yes it can. I have my second screen running above my main screen, so starting at x:0 y:-1980
-
Hmmm… didn’t work for me, so what I did is set the start at -1920, 0 and adjusted all my gauges. Works for now!
-
Hmmm… didn’t work for me, so what I did is set the start at -1920, 0 and adjusted all my gauges. Works for now!
You can also just go to the “edit gauges” mode, when temporarily set “borders” on for that window, & drag the window onto the correct screen.
-
Dragging is so inaccurate and old-school!
I like to drag to get it in the general area, then fine tune on a per-pixel basis. Takes longer, that’s why I asked for the ability to “nudge” the gauge using arrow keys.Focal, do you use Helios?