YAME64 suite
-
Just a preview of my next Helios profile and YAME…
-
… placing YAME extractions, gauges & lights on top of it
You mean placing the YAME stuff on top of a Helios profile? Does that work ? I’ve tried but my Helios profile always stays on top and I have to create transparent areas in order to see the YAME stuff.
Judy
-
You mean placing the YAME stuff on top of a Helios profile? Does that work ? I’ve tried but my Helios profile always stays on top and I have to create transparent areas in order to see the YAME stuff.
Judy
I don’t use Helios.
It’s just a background image I made and added in YAME as window background. -
You mean placing the YAME stuff on top of a Helios profile? Does that work ? I’ve tried but my Helios profile always stays on top and I have to create transparent areas in order to see the YAME stuff.
Which profile are you using, Judy? Take a look at my profile or Weepop’s and you’ll see our panels have cut-outs in order to see the gauges underneath. This has always been the case even before YAME. There’s no reason for YAME stuff to be “on top” of Helios.
Focal uses YAME to control stuff in the sim and thus places stuff “on top” of YAME, but we already have Helios for that.
-
Focal uses YAME to control stuff in the sim and thus places stuff “on top” of YAME, but we already have Helios for that.
No I don’t
I only have Yame extractions/gaages and a yame window background image. So nothing on top of it. (if you don’t count my hardware like an ICP and MFDs).
I have no touchscreen so I can’t even use Helios. I use BMS in windowed mode and my mouse for testing touch/click zones in Yame beta. -
I see. I stand corrected then. My apologies.
-
You guys have some serious resolutions!!
-
I think it’s 4K main screen for Focal, then a 1920x1080 second monitor?
For me, it’s 5x 1920x1080 monitors. Three are on an nVidia Surround setup at 5896x1080 res and two individual touchscreens at 1920x1080 res each. That black rectangle on the left side is part of the left monitor and I’ll be using as space for Teamspeak when flying online. The black space to the right is actually just an empty space.
-
Hi folks, is there a way some gauges to be clickable in the next version?
Also pls consider the support of more theaters map on the center pedestal…If any of these are already covered in a previus post and missed it, my apologies…Keep up the good work dev team…AWESOME software!! -
I think it’s 4K main screen for Focal, then a 1920x1080 second monitor?
Correct; 40" 4K & 27" HDHi folks, is there a way some gauges to be clickable in the next version?
Also pls consider the support of more theaters map on the center pedestal…If any of these are already covered in a previus post and missed it, my apologies…Keep up the good work dev team…AWESOME software!!We have several clickable in current beta. We hope to have some of those in the next public release. No promises. We are deciding what to keep for release and start finishing up because otherwise we just keep on adding new stuff
As for the maps, there’s a quick fix for that in the current release, just save your other theater map as the KTO version for example and choose that one in the UI -
As for the maps, there’s a quick fix for that in the current release, just save your other theater map as the KTO version for example and choose that one in the UI
you mean the release on Nov 2016 on the 1st post? I already tried to enter the photo from the Ikaros theater (same format as KTO) but no joy on the scroll sown menu only Korea & Balkans map available…Thx in advance
-
you mean the release on Nov 2016 on the 1st post? I already tried to enter the photo from the Ikaros theater (same format as KTO) but no joy on the scroll sown menu only Korea & Balkans map available…Thx in advance
Yes,
You save the map as KTO filename and chose KTO in the dropdown, it will load your other theaters map you saved over it then -
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