YAME64 suite
-
@Focaldesign +1
-
That doesn’t matter to me. It’s there in the real jet, not in BMS, so I liked having it in YAME so I can actually use it if I want in my future pit.
Same for the ADI etc.Hahaha!! Fair explanation!
Same here, in that logic, half of the stuff in BMS would also be useless. The FLCS PWR test and MAL & IND LST for example are also just eye candy.
The more realistic I can get it, the better.
It’s there for freaks like me, nobody obligated to use it.In that optic we’re even going to try and have the 4° nose up offset of the SAI implemented in YAME.
Agreed! Just wondering if I needed to put that in my Helios profile. I didn’t put the test stuff in my old profile, but as I’m re-doing it….
We are currently only looking into touchable buttons & gauge knobs (bezels, ICP, mach, adi, twp/twa), not parts that visually have to switch (all switches, rotary knobs etc).
Well, the TWP/TWA stuff lights up differently based on what’s going on around you…. I understand this line of thinking for things like the MFDs, ICP, etc… are there plans to have switches/rotaries/etc. implemented and have the image change as well (ie, ON/OFF state)?
Coming up.
Got it, thanks!!
-
Well, the TWP/TWA stuff lights up differently based on what’s going on around you…. I understand this line of thinking for things like the MFDs, ICP, etc… are there plans to have switches/rotaries/etc. implemented and have the image change as well (ie, ON/OFF state)?
TWP/TWA and other light bits are in shared memory so we can just read their state. It’s been in Yame since v1
For now YAME has ALR-56 (Block 40/42/50/52) as “default”, Carapace (BAF, RJAF) as “Carapace” and ALR-69 (EPAF, block 15/30/32) as EPAF. And ATD interface for all three too (ALR-56 & -69 as “default” and “Carapace” as retrofit or Carapace).TWP/TWA, eyebrows (both recent as slightly older EPAF), master caution, caution panel (again both recent and older block type based on MLU), ELEC (both GE as PW)… all in yame since the start.
No plans for switches & rotaries at this point.
-
all in yame since the start.
Ah, cool!
No plans for switches & rotaries at this point.
Thanks for confirming that!
-
Anyone suffering same problem?
Flying in multiplayer campaign, when some pilots leave 3D, my Yame stops extracting displays. I use to lose all my displays same as a AAA hit. Just when I have weight on wheels again after landing I recover all displays and information again. I have reseted Yame in flight and continued with all gauges and mfds in blank till weight on wheels. -
Anyone suffering same problem?
Flying in multiplayer campaign, when some pilots leave 3D, my Yame stops extracting displays. I use to lose all my displays same as a AAA hit. Just when I have weight on wheels again after landing I recover all displays and information again. I have reseted Yame in flight and continued with all gauges and mfds in blank till weight on wheels.Never tested multiplayer, but will lokk into this. So you are in flight and all extractions are ok, then when another pilot leaves the 3d you loose extraction. Is this right? Thank you for your report.
-
Anyone suffering same problem?
Flying in multiplayer campaign, when some pilots leave 3D, my Yame stops extracting displays. I use to lose all my displays same as a AAA hit. Just when I have weight on wheels again after landing I recover all displays and information again. I have reseted Yame in flight and continued with all gauges and mfds in blank till weight on wheels.I’ve used YAME in multiplayer campaigns and never had that problem so far.
Sometimes YAME stops working, but it happens to me both multiplayer and offline.
I am trying to narrow the problem down before reporting it, because I just can’t find a pattern behind the problem and the crashes appear to be random.Sent from my E5823 using Tapatalk
-
I’ve used YAME in multiplayer campaigns and never had that problem so far.
Sometimes YAME stops working, but it happens to me both multiplayer and offline.
I am trying to narrow the problem down before reporting it, because I just can’t find a pattern behind the problem and the crashes appear to be random.Sent from my E5823 using Tapatalk
Weird thing is I use it since before the original release and I never had such problems.
A friend in our sqn however reported regular random crashes since a week or two. Might it be related to an update of Microsoft Visual Studio redistributable 2015 x64? I noticed in his programme list it was updated pretty recent (came with an update of Teamspeak 3 it seems) and around that time the errors started occurring. -
Weird thing is I use it since before the original release and I never had such problems.
A friend in our sqn however reported regular random crashes since a week or two. Might it be related to an update of Microsoft Visual Studio redistributable 2015 x64? I noticed in his programme list it was updated pretty recent (came with an update of Teamspeak 3 it seems) and around that time the errors started occurring.Was the time around the time of version 1.1 release?
Version 1.0 never crashed.
I will try to give you more info once I’ve found a pattern…
Sent from my E5823 using Tapatalk
-
Was the time around the time of version 1.1 release?
Version 1.0 never crashed.
I will try to give you more info once I’ve found a pattern…
Sent from my E5823 using Tapatalk
No, way later, like 3 weeks ago or so it started.
-
Never tested multiplayer, but will lokk into this. So you are in flight and all extractions are ok, then when another pilot leaves the 3d you loose extraction. Is this right? Thank you for your report.
That’s afirm Roccio
-
Yame64 is a great application for extracting displays. I appreciate the work that went into creating it. I’m using it successfully, except I can’t for the life of me figure out how to get the functioning ICP to work. I have the server and client running on the machine that BMS runs on. I am extracting instruments from there successfully. I have the client also running on a windows tablet and I’m able to extract instruments from the server. I am able to use the explorer browser on the tablet to access the ICP html file located on the main computer where the server is running. However the ICP appears to be be merely an image file and is not interacting in any way with BMS. I believe my problem is that I’m missing the know how to make the vital link between the YAME client (which doesn’t offer any option to extract the ICP that I can find) and the browser/ICP html file. Has anyone else had success with this, and if so, what do I need to do to get the YAME client to communicate with the YAME server in regard to the “fully functional ICP”?
Thanks in advance for any help.
-
Yame64 is a great application for extracting displays. I appreciate the work that went into creating it.
Thx!
I’m using it successfully, except I can’t for the life of me figure out how to get the functioning ICP to work. I have the server and client running on the machine that BMS runs on. I am extracting instruments from there successfully. I have the client also running on a windows tablet and I’m able to extract instruments from the server. I am able to use the explorer browser on the tablet to access the ICP html file located on the main computer where the server is running. However the ICP appears to be be merely an image file and is not interacting in any way with BMS. I believe my problem is that I’m missing the know how to make the vital link between the YAME client (which doesn’t offer any option to extract the ICP that I can find) and the browser/ICP html file. Has anyone else had success with this, and if so, what do I need to do to get the YAME client to communicate with the YAME server in regard to the “fully functional ICP”?
Thanks in advance for any help.
If you get to see the image it should be loading the rest too.
The logic behind it is that there are touch area’s which contain the BMS callbacks associated with it. When touching an area, a javascript detects the id and sends that callback via ajax to the server. The server then reads your set keyfile and translates the callback to the mapped keystrokes.
Have you set your keyfile correctly?Expect a “native” clickable ICP with a more realistic picture (current html image is Real Simulator replica, native version will have real picture I took) in the upcoming release.
-
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?
-
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.