YAME64 suite
-
OMG you’ve just made my day a lot better!! Thank you:bdance:
-
Hi folks, is there a way some gauges to be clickable in the next version?
I’m curious… why would you need gauges to be clickable and which gauges need this feature?
Also, if you need to interact with the gauges, why not use Helios in the first place? -
I’m curious… why would you need gauges to be clickable and which gauges need this feature?
Also, if you need to interact with the gauges, why not use Helios in the first place?Stuff implemented in Yame and not in BMS for one thing? For example the green indexer on the machmeter, the knob to set the ADI ball level, ATD buttons.
Use photo based parts of YAME instead of drawn textures from Helios for TWP/TWA/MFD… -
Stuff implemented in Yame and not in BMS for one thing? For example the green indexer on the machmeter, the knob to set the ADI ball level, ATD buttons.
Use photo based parts of YAME instead of drawn textures from Helios for TWP/TWA/MFD…Not sure what you mean on the mach meter… but isn’t the ADI ball level automatically level? What is "ATD buttons?
Also, if you’re interacting with the gauges, why not use Helios instead? Unless non-touchscreen like your test setup, Focal? -
Not sure what you mean on the mach meter… but isn’t the ADI ball level automatically level? What is "ATD buttons?
Also, if you’re interacting with the gauges, why not use Helios instead? Unless non-touchscreen like your test setup, Focal?The green triangle on the machmeter. It’s fixed in BMS, but IRL it can be set anywhere on the dial as a reference marker, by turning the knob on the bottom right of the gauge.
E.g they set it at rotation speed pre takeoff, at 300knts for briefed SID speed, at 330 for lowest corner speed etc etcNo, IRL the ADI ball isn’t always level. The knob with the white arrow in it bottom right makes the pilot able to turn the ball so it’s set correctly level.
ATD is Terma’s Advanced Tactical Display. RWR 2.0. Installed in all BAF MLU’s and in the pipeline for Danish MLU’s also. See the manual, it’s modeled in YAME to our best non-classified knowledge.
As I said previously, I like the photoreal items from YAME over the drawinglike visuals from Helios. So I prefer to offer the touch function on the ICP, MFD bezel, RWR TWP/TWA etc from within Yame without someone having to add another software layer over it.
-
The green triangle on the machmeter. It’s fixed in BMS, but IRL it can be set anywhere on the dial as a reference marker, by turning the knob on the bottom right of the gauge.
E.g they set it at rotation speed pre takeoff, at 300knts for briefed SID speed, at 330 for lowest corner speed etc etc.Ah, I see. Thanks for explaining…. but WHY would a pilot need to set a reference marker? Rotation speed can be a small scribble on the kneepad, same for briefed speed. Corner speed should be well in-grained to the pilot anyway. Maybe best for a “quick reference” for briefed speed though…
No, IRL the ADI ball isn’t always level. The knob with the white arrow in it bottom right makes the pilot able to turn the ball so it’s set correctly level.
IRL, sure. But in the sim, isn’t it automatically level? And always level?
As I said previously, I like the photoreal items from YAME over the drawinglike visuals from Helios. So I prefer to offer the touch function on the ICP, MFD bezel, RWR TWP/TWA etc from within Yame without someone having to add another software layer over it.
If it’s just the images that bothers you, then fair enough. It’s quite a bit of work to get the visuals to how they are and my own preference is obviously what I use on my profile. Should that change, I’ll work on photoreal images. My issue with the photoreal images is that my Photoshop skills are just basic so I can’t really make on-off images for indicators or up-down images for switches. As for “another software layer,” I wonder if YAME’s touch function allows the image to change as well? I mean if the Master Arm swithc is in the DOWN position and you flick it to the UP position, is this change reflected in YAME’s visuals too?
Any chance you can send me a copy of your YAME profile and the relevant images? I’d like to test whether the FPS hit of YAME + Helios is significantly higher than YAME only. Thanks!
-
Ah, I see. Thanks for explaining…. but WHY would a pilot need to set a reference marker? Rotation speed can be a small scribble on the kneepad, same for briefed speed. Corner speed should be well in-grained to the pilot anyway. Maybe best for a “quick reference” for briefed speed though…
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.IRL, sure. But in the sim, isn’t it automatically level? And always level?
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.
If it’s just the images that bothers you, then fair enough. It’s quite a bit of work to get the visuals to how they are and my own preference is obviously what I use on my profile. Should that change, I’ll work on photoreal images. My issue with the photoreal images is that my Photoshop skills are just basic so I can’t really make on-off images for indicators or up-down images for switches. As for “another software layer,” I wonder if YAME’s touch function allows the image to change as well? I mean if the Master Arm swithc is in the DOWN position and you flick it to the UP position, is this change reflected in YAME’s visuals too?
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).
Any chance you can send me a copy of your YAME profile and the relevant images? I’d like to test whether the FPS hit of YAME + Helios is significantly higher than YAME only. Thanks!
Coming up.
-
@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.