YAME64 suite
-
Thanks for your quick response to my question. I’m not sure what you mean by setting my keyfile correctly, but if you’re asking if the BMS (full) keyfile is sending the correct ICP callbacks to BMS, then yes, if I use my keyboard to operate the ICP it responds correctly. Is there some alteration that needs to be made to the keyfile in order for the YAME ICP to work?
No, my question actually was, have you selected the correct keyfile in the YAME UI globals tab. The third item needs to point to the keyfile you are using in BMS.
-
Yes, it is set correctly on the YAME UI globals tab on the machine where BMS and the YAME server reside. Nothing has been set on the Globals tab on the client machine. Does the location of BMS 4.33, the DTC file, and the keyfile need to be set there as well?
-
Yes, it is set correctly on the YAME UI globals tab on the machine where BMS and the YAME server reside. Nothing has been set on the Globals tab on the client machine. Does the location of BMS 4.33, the DTC file, and the keyfile need to be set there as well?
Client machine?
If you are running the ICP in the browser, which IP are you entering to browse? If it’s the IP from the server, the client is obsolete because it will send the callbacks to the server. That one needs to have the keyfile set. -
I am running the ICP in the browser, which is directed to the IP of the server. It has never been clear to me whether or not the client needs to be running in order for the browser ICP to work (given that the ICP doesn’t work, I thought maybe…). I am primarily running the client on the second machine in order to extract other gauges.
-
I am running the ICP in the browser, which is directed to the IP of the server. It has never been clear to me whether or not the client needs to be running in order for the browser ICP to work (given that the ICP doesn’t work, I thought maybe…). I am primarily running the client on the second machine in order to extract other gauges.
Client is only used to extract local or from server data. When your browser connects to the IP of the server, the client is not involved on that part.
Strange nothing happens.
What version are you using? v1 or v1.1? 64 or 32 bit? And what OS (type & 32 or 64)? -
The server is running on Windows10 64 bit. YAME64 v1.1.0
The tablet I’m using to access the server is Windows10 32 bit. -
The server is running on Windows10 64 bit. YAME64 v1.1.0
The tablet I’m using to access the server is Windows10 32 bit.I only have Win7 and no 32bit at the moment so I can’t test the very specific environment. But still, client should be irrelevant as it only sends data via web protocol to the server. Strange.
-
I have 3 monitor setup with a 12" USB monitor. I have setup YAME64 suite to open on the USB monitor but when falcon starts up and I get in the cockpit the extracted gauges with the screen jumps to one of my other 3 monitors. Is there a way to keep this from happening? I would have to alt-tab out of falcon and close the YAME64 suite and restart it. The screen then will load back on my USB monitor. Falcon doesn’t like when you alt-tab while in multiplayer. Thanks in advance for any help with this issue.
-
I have 3 monitor setup with a 12" USB monitor. I have setup YAME64 suite to open on the USB monitor but when falcon starts up and I get in the cockpit the extracted gauges with the screen jumps to one of my other 3 monitors. Is there a way to keep this from happening? I would have to alt-tab out of falcon and close the YAME64 suite and restart it. The screen then will load back on my USB monitor. Falcon doesn’t like when you alt-tab while in multiplayer. Thanks in advance for any help with this issue.
Maybe could be related to the arrangment of screen in windows (not yame) setup. Changing screen position relative to the main one could help. There was a discussion about this some page ago…
-
Maybe could be related to the arrangment of screen in windows (not yame) setup. Changing screen position relative to the main one could help. There was a discussion about this some page ago…
OK thanks I’ll try and find that page where this was mentioned.
-
The server is running on Windows10 64 bit. YAME64 v1.1.0
The tablet I’m using to access the server is Windows10 32 bit.Maybe could be a firewall blocking the calls.
-
-
Maybe could be a firewall blocking the calls.
I have my firewall turned off. I’m able to extract gauges to the tablet through 53000. Does the ICP use a different port?
-
I have my firewall turned off. I’m able to extract gauges to the tablet through 53000. Does the ICP use a different port?
Should use default 8080 port.
Are you starting the YAME server? And is the item ‘Key server’ checked on at the Server tab in the YAME UI?
Can you check what public IP is mentioned in red on that server tab and verify that is also 3 times the IP you see inside the /htdocs/sender.js? -
Should use default 8080 port.
Are you starting the YAME server? And is the item ‘Key server’ checked on at the Server tab in the YAME UI?
Can you check what public IP is mentioned in red on that server tab and verify that is also 3 times the IP you see inside the /htdocs/sender.js?The YAME server is running. The “key server” item is checked.
Does the 8080 port need to be forwarded in my router?
The public address is not mentioned in sender.js, but I’m running on a LAN and the local server address is mentioned three times. -
The YAME server is running. The “key server” item is checked.
Does the 8080 port need to be forwarded in my router?
The public address is not mentioned in sender.js, but I’m running on a LAN and the local server address is mentioned three times.If you are sending over your network I would indeed forward the port.
-
If you are sending over your network I would indeed forward the port.
No joy. I’ll quit bothering you guys about it. I appreciate the help. If I ever figure it out I’ll let you know.
-
-
I’ve just installe YAME to replace the MFDe in a client -server configuration. the system sometime it works and sometime not… before to say that i have problems i would like to understand the right config I’m a little bit confused about that.
I setup server with
listening port 53000
exporting flight data
use Direct3D hook listening port 53100So what port have i to setup in the client?
only one port could be set 3D hook is not able to be enableAs i understand in the “track” section of the manual remote client is always used as texture data it’s a server issue the Hook extraction… so what is the meaning of Hook listening port? and why is not enable on client? ( because Falcon is not there?)
On my BMS server PC i found, after installation, YAME set with admin right but on client no is this correct?BUGS
1. YAME CLIENT when i try to set export texture data i get a windows error (no code just “YAME64.exe stopped to work” … yes i know is not logic but a warning like if in client tab if “get data from Falcon BMS” is preferred .
2. When i stop Falcon and YAME Server, YAME Client stop itself automatically (or it seems so) than if Falcon, YAME server and client are started (without to exit) again YAME client gave error (not codded as above)New feature request
A small gauge/indicator that show if YAME server is connected and extraction available (like heartbeat or app status) especially during first setup for to check ports and connection you have to run always falcon and start flight also a test button on server can help to check the instruments like in preflight check list that switch on all the light and move to full scale all the indicator (or change the image to the texture data).at the end… great job
BravoCiao
-
Another question about Key Server
may I add functionality to the HTML page? i.e. may I add other callbacks like Gear down and so on?
I’m using the iPad as ICP with the iFlyBMS ( introduced by ICE if I remember well) via the TouchControl APP that is very versatile and if i’m right can handle also POST or JS, my target is change the key emulation with your JS that may be could work also without TouchControl serverotherwise I can migrate on a full web based extended tablet control