YAME64 suite
-
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?
-
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?
I mean dragging the entire window. In Windows 7 it snaps to the left top corner on my pc. My second screen is is on top of my main screen, and aligned left so they both start at x:0. That’s the easiest way.
Nope, no Helios. -
You can even move the window on the screen you want to use, then right click inside the window and use the “Align to monitor” to set the window coordinates to exactly (0,0)
-
:: mind blown! I’ve not thought of that!
Anyway, that’s for later, need to sort out networking issues with Helios now. I’m surprised neither of you use it… I’m guessing you guys just extract cockpit MFDs and gauges to a slave PC? Helios allows you to send callbacks to BMS, ie, push OSBs, flick switches, rotate knobs and works best with a touchscreen…
-
:: mind blown! I’ve not thought of that!
Anyway, that’s for later, need to sort out networking issues with Helios now. I’m surprised neither of you use it… I’m guessing you guys just extract cockpit MFDs and gauges to a slave PC? Helios allows you to send callbacks to BMS, ie, push OSBs, flick switches, rotate knobs and works best with a touchscreen…
I use a single pc and extract all on a second screen. I have MFD’s and ICP hardware on top of that screen.
Next to that I’m using the built in YAME key server and my iPad for touch device and flipping switches etc.
And in the future all touch stuff will get replaced by a full pit. Lots of panels already made, but no room to make the entire pit yet: https://www.dropbox.com/sh/x0rgrohzdpa02vt/AACucgQ76FqpG6swXb6-6qDpa?dl=0 -
Beautiful! Yeah, that trumps Helios any day!
-
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.
Same problem here…
I got the gauges to work, but not the hook extraction.
The gauges work beautifully, very smooth and responsive.
roccio, big thanks to the devs for your work. i hope I can get the hook extraction to work on my server-client configuration because that would give me an extra 10-15 FPS which are very much welcome.
POST EDITED: Sorry, I had not realized the explanation by FocalDesign
-
Congratulations, fantastic job
Fenix1234