Honestly I never even thought of that but it makes sense. I looked at the option where you can stretch the image but never looked at what the actual size was. Thanks

Sent from my iPad using Tapatalk

Thanks so much for the comparison! It was very helpful.

All my best,
Rob

As this feature was introduced a long time ago, the fix for it was posted during that time as well:
http://ihpff4bms.blogspot.com/2015/11/beta-profile-update.html

I’ve been playing with a YAME/Helios setup for quite a while and no issues. Played yesterday, no issues (other than getting waxed by SA-15s twice). Today, when I open YAME I get a brief blank window and it crashes to desktop. I uninstalled/reinstalled restarted, etc. No joy. Anyone wrestle with this problem?

I’m running windows 10, GTX 1070 (416.34 updating now to 417.35, but it’s been working so I don’t expect that to help…), TM warthog running through a target script, and a slightly modified version of Ice’s Helios profile. Let me know if there’s anything else that may be relevant info.

Sent from my iPad using Tapatalk

Tried that, and no difference. Helios will SHUT DOWN if I try to open the profile that was working for a year on WIN 8.1, but will stay open and run fine if I create a new file and save it.
So I’m not sure YAME is the problem, seems HELIOS might be. It acts as though the monitor setup is wrong, but I can’t get into HELIOS to sort it out.
Next guess?

For some unknown reason it decided to work again…. No clue why.

@dureiken:

thanks aniway 🙂

some actions are going from BMS to Helios, but not for buttons.

that’s awesome anyway !

things that are available in BMS shared memory are indeed picked up by Helios. That’s only for output (altimeter setting, indicator lights etc), not input (switches & buttons).

Zero, not sure if I got your problem right, but if you change something in your keyfile, Helios will recognize that change as long as you use there the same keyfile as in BMS.

Concerning TARGET you only have to take care that the changes are made there as well.

See you current keyfile as the master:
All changes there shall go from there to the ‚clients‘. Not vice versa.
At least that‘s the way I‘m evolving my config.

All overall the configs are kinda hard to screw up.
As always: Save your working config-files and then make improvements on them.

YAME64’s user manual helps to do this I believe.

http://www.yame64.com/manual/YAME64-manual.pdf

HELLO IM A NEWBIE INSTALL ALL THISD COOL BMS STUFF AND RAN ACROSS THE FACLCON MFD APP FOR MY ANDROID I HAVE IT ALL IN COPED THE STUFF LIKE THIS (SimHsiCrsDecBy1 -1 0 0XFFFFFFFF 0 0 0 1 “HSI CRS 1 deg dec”).I CAN SEE THE MFDS BUT IM UNABLE TO USE THE BUTTONS LIKE THE GENTALMEN ABOUT …NOT WHAT TO DO PLZ HELP

Thanks Starfuryth, currently I am out but as soon as I return home I will answer you.

@Stevie:

I also find it VERY useful to take screenshots of the checklists, airport diagrams, approach plates, etc. and store them in Albums as .jpeg in Photos via iTunes.

Why taking pictures?
Use a PDF reader like “GoodReader” and transfet all the chart in .pdf into it. You can even sync a folder (could be your Briefing folder and or WDP datacard folder) on DropBox and access it thought your iPad or more simply, upload any .pdf (or .rar/.zip for a package of .pdf) via wifi ino “GoodReader” directly using your Internet explorer, Mozilla or any other web navigator.

Already read through that.

As I mentioned, Helios works just fine on its own, so it’s not a key file issue. The problem is that windows isn’t allowing Helios buttons to be clicked when BMS is “in front”.

I have a Corsair mouse and keyboard . . .

I ask the developers of falcon bms asking if in the next updates it will be possible to change the coordinate system of the touchscreen from absolute to relative so that you can use the cockipt even with a single touchscreen main screen and not just with the mouse. or implement variables in the sharedmemory to solve the problem and read the mouse position and convert it from absolute to relative

Getting a lot closer now. Rogue’s cockpit is properly aligned to my monitor’s upper-left corner and I can move switches by touching, but the cockpit still doesn’t take up the whole 1080p touchscreen. Why not?

@-Ice:

No, I think he wants to use the touchscreen both as a display device and as a way to interact with the cockpit. Therefore, he wants to look at an MFD and be able to touch the appropriate OSB and get the correct response.

my mistake.

my advice - get another screen and use Helios (Ices profile - other profiles are available) and either MFDE or YAME

If you need help with either check the forums or PM Ice - he’s a nice chap and will help you out …

Hey guys, I’ve been running Helios with ICE’s profile for a good number of months now. However, this AM I launched Helios and got Windows on-screen notification box that “HELIOS has stopped working”. I see that you did clean reinstall. But, you also mention a corrupted XML file. Which XML file are you noting? And is there something else going on here that contributes to HELIOS failing to launch.
Thanks in advance for your help.
Mike

Hehehe… thanks for the kind words! Glad that worked out for you! Enjoy!

I would recommend you place your question on the referenced thread…better results in getting your question answered.