YAME64 suite
-
Problem solved but as usual, whatever fixed it is unclear. After your suggestion I moved the touch panel below the main in Windows settings which is how it’s set up, coordinates 1080x1080. It didn’t fix it and would crash when I ran the client. Then I put it back to side by side and moved the window around the main monitor to see if it would work on it. It did. Then I set coordinate back to 3840x0 and it worked one time but never would again. While looking in my Nvidia settings I noticed the surround option they have. It recommended I use certain ports on the video card. I was using the intel video of my board for the touch panel because that’s how I’ve usually done it in the past. So I decided to disable the onboard graphics, switch the main monitor port on my 2080ti and plug the touch panel into it as well. I created a brand new layout for Ice’s Helios 16S profile, put the touch panel beneath the main in Windows settings and set the coordinates to X 1080 Y 1080 and BAM! Worked like a champ! Why it wasn’t working before is unclear though. Using the onboard graphics for the TP and the video card for the main has always worked before. I leaning towards it being a video card issue. Oh well, it’s fixed.
-
Problem solved but as usual, whatever fixed it is unclear. After your suggestion I moved the touch panel below the main in Windows settings which is how it’s set up, coordinates 1080x1080. It didn’t fix it and would crash when I ran the client. Then I put it back to side by side and moved the window around the main monitor to see if it would work on it. It did. Then I set coordinate back to 3840x0 and it worked one time but never would again. While looking in my Nvidia settings I noticed the surround option they have. It recommended I use certain ports on the video card. I was using the intel video of my board for the touch panel because that’s how I’ve usually done it in the past. So I decided to disable the onboard graphics, switch the main monitor port on my 2080ti and plug the touch panel into it as well. I created a brand new layout for Ice’s Helios 16S profile, put the touch panel beneath the main in Windows settings and set the coordinates to X 1080 Y 1080 and BAM! Worked like a champ! Why it wasn’t working before is unclear though. Using the onboard graphics for the TP and the video card for the main has always worked before. I leaning towards it being a video card issue. Oh well, it’s fixed.
That’s definitely the way you want to do it, technically and performance wise. Glad you got it working!!
Running such a powerful gfx card and then forcing your CPU to deal with a second monitor when your gfx card can handle 3-4 really big monitors without issue is not the way to go. You GFX card will take no serious performance hit by running two monitors, but your CPU would definitely take a hit running the second touchscreen monitor. Might only see such issues in some serious testing like 3DMark, etc. but why not do it the right way? You should only ever plug a monitor directly into your motherboard for troubleshooting if that 2080ti goes bad and will not send any info to it’s display(s).
Are you using MFD’s on your touchscreen setup? I’m still wondering if other people have issues with OSB 2, 3, and 4 (for left and right MFD’s) – mine are slaved to non-OSB functions per my post above… Would love to know if others deal with this, too.
-
Well, today was a very frustrating day. The problem is not fixed. After putting both monitors on the card and disabling the onboard graphics it works occasionally. Usually I have to start the client on the main monitor a couple times and then move it down to the touch panel for it to work. One thing I noticed is that when YAME is running with BMS, the YAME app gets moved off the main window even when minimized to the touch panel. After shutting down BMS if I don’t move YAME back to the main monitor and close the program on the touch panel, it will no longer work. When I try to launch it, it will lock up forcing me to shut it down with task manager. At his point I have to uninstall/re-install to have it work again. Other oddities, are when I get a successful start of the client and minimize the YAME app, I get a weird screen freeze for a second. Also, YAME is seeing my second monitor at X 970 instead of 1080 which places the center of the YAME window in alignment with the main monitor which has a a width of 3840. Also when I fire up Helios YAME shifts and occasionally doesn’t shift back. Typically this is a scaling issue but I’m not using any ATM because it really jacks it up. Both the main and the TP have a 1080 height. I’m wondering if the issue are the different refresh rates of the monitors at this point. My previous setup was with a 49" 4K Ultra HD tv @ 3840x2160 60hz I believe. The TP is locked at 60hz while the monitor is at 144…… man I hate MFDE… it’s not working correctly either though lol.
-
I’ve ruled out refresh rates and scaling. Might try using a different HDMI cable for the TP. I’m using an older one now. If that doesn’t work I’ll try my 27" TP with higher res. And finally, if all else fails I’ll set up the 4K tv again. If that fixes it I’ll be pissed lol. I paid a grand for the damn monitor.
-
Helios still works? I haven’t been able to get it to dance for a long time, figured Win10 broke it’s legs…
Okay – so you’re using MFDE, YAME64, and Helios? Wondering if they are not playing nice together. Windows does not care what monitors have which refresh rates, but if you are pushing any sort of sync through your GFX card control panel, you can turn it off to test. Varying refresh rates should not present an issue unless you’re trying to span a 3D scene across multiple monitors (like eyefinity). Don’t waste too much time on refresh rates, etc.
Cables are cables – if the endpoints have become disconnected, it will have problems or just won’t work. You can try another cable to see if something changes, but issues with a cable will NOT be subtle. There is no difference in cables unless one is very, very long (in which case a booster could be added to maintain signal strength and deal with noise). On that note, when it comes to adapters between formats like HMDI-to-DisplayPort for example, there are raw cable-to-cable types, or active types that ensure the receiving end views the cable as the adapted type and not the type that was adapted to fit. Be sure you have the correct one(s) for your setup if you use these. Even gold tips adds nothing to the function/ability of the cable, and if you get very scientific, should be avoided.
Make sure you cross your T’s and dot your i’s : start at step one with that new monitor by ensuring any necessary drivers are installed, that it is set up properly in the Windows settings AND in your nVidia Control Panel. Check and double check. So many times over the years I have hit myself over the head for missing some small detail. Moving forward, if it’s not that, definitely bring back an old monitor to troubleshoot - be very methodical tracking down the source issue and only change one thing at a time as you test! Make notes if it helps, if you’re busy with other things around the house, so you can be sure you’re not missing anything.
Google questions about monitor issues with the name of your monitor to be sure there is not some issue that other users have when using it for gaming applications, etc. Anything you can do to find out why your new monitor is not behaving like the old one will help. I don’t envy you, I used to have a in-home PC troubleshooting business at @$100/hour – I don’t do it anymore because it drove me crazy. Money was good, but repeat business to the same people started to get to me, even though they were happy to pay every few months. lol
-
Ok, it’s fixed and I know why. First off I don’t use YAME and MFDE at the same time. I don’t care for MFDE (though I appreciate it greatly) and it’s a last resort when YAME isn’t working but they essentially do the same thing. Second, Luckily I’ve had zero issues with Helios using Ice’s 16S profile for a couple of years and three computers. My setup issue with it is I don’t like Ice’s .key file as he does not use a Warthog. I’ve used Morphine’s profile for about 4 years now and I usually have to do some tweaks to get Helios to recognize the key presses. Third, THANK THE LORD IT’S NOT THE MONITOR! lol.
So it seems that YAME does not like having a window size that is exactly the same size as the monitor resolution it will be running on. I think it’s always been this way, at least for my setup because I’ve had these exact same issues from the beginning. In the past I’ve somehow gotten it to work by magic fairy dust or blowing on it just right. Who knows. Usually I would make scaling changes in the windows settings but this time around it didn’t work.
The main thing that caught my attention was how YAME would get moved when I fired up Helios. No matter where my coordinates placed the window, the moment I launched Helios YAME would shift left. So, I decided to take the YAME profile window size from 1920x1080 to 1919x1079…… It fired right up. It fired up multiple time and no longer shifted when firing up Helios or starting BMS. The coordinates to center the window on the touch panel ended up being x 1050 y 1080. I then made a few changes of the gauges back to the left and it’s good to go.
So if you’re having the kind of issues I’m having, namely, using YAME in full screen mode without borders to move the window, set the window size one tick smaller than the monitor resolution and all should be well.
YAME is still finicky about starting and stopping, editing and running the client without shutting down first. It will still crash occasionally but not in game and not if I take steps to prevent it. All in all, problem solved. -
I’ve had YAME running on my other computer for several years now with no issues. Well a couple issues but they’ve been fixed. On my new system I have a Samsung 49" 3840x1080 main monitor and a 1920x1080 touch screen. YAME works fine anywhere on the main screen but the minute I try to move it to the second monitor by putting 3840 for the X starting position it locks up and splats. In windows settings the touchscreen is to the right of the main wide screen so these coordinates are correct. Can I assume that YAME doesn’t like wide screen/non 10/9 format monitors? And if so, does anyone have a work around?
Thanks!
Didn’t catch this the first time I read it until you posted the solution you found.
If you have a main monitor of 3840, your X starting position for the next monitor would be 3841 not not 3840, maybe give that a try and see what happens just for testing sake.
My main monitor is 5910x1080 (bezel correction) and start the YAME monitor at 5911. -
I think I did try 3841 at one point but I’ll do it now to be sure. What’s odd is that even now I should be setting it to 1080x1081 but in order to get it to look right I have to use 1050x1080. I’ll try 1081 as well with the new layout.
-
Hello Wicked,
a question, how would this support of the second monitor, your photo is not very readable.
Thank you, for any information !!!
Take Care !! -
I’m not sure I’m understanding your question but YAME is exporting all the gauges and MFD to the touch panel. Helios overlays YAME with a touch activated representation of the cockpit. This pic is of my previous setup.
-
I’m not sure I’m understanding your question but YAME is exporting all the gauges and MFD to the touch panel. Helios overlays YAME with a touch activated representation of the cockpit. This pic is of my previous setup.
Good morning, Wicked!
I have a 19 "monitor, how to attach it to the desk, how is the stand you use, in its current configuration, I could see that it is a little inclined on the table, and does not take your view from the main monitor.
Thank you !! -
Hello everyone,
I have a question. Is YAME compatable with Saitek Instrument Panel? https://www.amazon.com/Saitek-PZ46-Flight-Instrument-Panel/dp/B000VLNXRU
It is probably not possible but I wanted to ask. Also what do you think about instrument panel’s compability with Falcon?
-
Not unless there is some sort of hack for it – they display pre-set guages for FSX, and you can “purchase” more… As it’s the most overpriced flight sim controller I’ve ever seen, I wouldn’t waste the money to find out.
YAME64 works by addressing monitor space, so if it’s not recognized as a tiny monitor attached to your desktop space, YAME64 won’t be able to do anything with it. My advice: don’t waste the money!!
@Wicked: I shared your pic on the facebag, got mobbed by a bunch of people asking questions about which monitor you own – I replied with Samsung C49HG90 49" 3840x1080 144Hz – if that’s not correct, please let me know
-
Not unless there is some sort of hack for it – they display pre-set guages for FSX, and you can “purchase” more… As it’s the most overpriced flight sim controller I’ve ever seen, I wouldn’t waste the money to find out.
YAME64 works by addressing monitor space, so if it’s not recognized as a tiny monitor attached to your desktop space, YAME64 won’t be able to do anything with it. My advice: don’t waste the money!!
@Wicked: I shared your pic on the facebag, got mobbed by a bunch of people asking questions about which monitor you own – I replied with Samsung C49HG90 49" 3840x1080 144Hz – if that’s not correct, please let me know
Haha! That’s awesome! Yeah that’s the one. Going to it from a 49" tv you’re losing a lot of height but as close as I am to it, it doesn’t matter. It’s by far the most immersive experience I’ve had using a monitor with Falcon or BMS and its silky smooth at 120hz. I haven’t tried 144hz again yet but I will tomorrow. I know the card and monitor can handle it so I think BMS has an issue with it.
-
@mhm:
Hello everyone,
I have a question. Is YAME compatable with Saitek Instrument Panel? https://www.amazon.com/Saitek-PZ46-Flight-Instrument-Panel/dp/B000VLNXRU
It is probably not possible but I wanted to ask. Also what do you think about instrument panel’s compability with Falcon?
As SimlerPDX said, YAME has to see it as a monitor in windows display settings.
-
Good morning, Wicked!
I have a 19 "monitor, how to attach it to the desk, how is the stand you use, in its current configuration, I could see that it is a little inclined on the table, and does not take your view from the main monitor.
Thank you !!This is the mount that holds the touchscreen WALI Premium Single LCD Monitor Desk Mount Fully Adjustable Gas Spring Stand for one screen up to 32", 17.6lbs Capacity (GSDM001), Black https://www.amazon.com/dp/B0779JSRH5/ref=cm_sw_r_cp_tai_5zCdDbJ8CRKVC Or close to it anyway. There is a post that clamps to the desk and the articulating arm slides on the post and can be positioned from there. In my current configuration it is clamped onto the desk but upside down and underneath the desk. I have 2 of these and they work well to position the touch screen underneath the main monitor. The stand I used to use is a standard flat panel TV rolling office stand. It has a tray for DVD players, cable boxes and what not that clamps onto the two uprights. I mounted the touchpanel post the that with a 3/4" block of wood to help strengthen the tray as it’s not meant to support that much weight. This, I think is the stand or close to it. The pic is when I ran two touchscreens… wasn’t worth the hassle.
Yaheetech 32 to 65 Inch Mobile TV Cart Universal Flat Screen Rolling TV Stand Trolley Console Stand with Mount for LED LCD Plasma Flat Panels on Wheels https://www.amazon.com/dp/B06Y27JM4F/ref=cm_sw_r_cp_tai_ZGCdDbGEW3SP4 -
This pic shows the tv stand setup a little better. I’m also using the 27" touchscreen and not the 23" I’m using now. One problem with this setup is rudder placement. The rudders will only go so far back before they hit the legs of the stand limiting how close you can get to the TV. Also, you end up having to put the TrackIR on the touchscreen which blocks parts of your view. Even backed away and putting the TrackIR on the TV is problematic. Unless you were the bill of your hat really high you won’t get full motion up and down.
-
… its silky smooth at 120hz. I haven’t tried 144hz again yet but I will tomorrow. I know the card and monitor can handle it so I think BMS has an issue with it.
I use a 144Hz monitor, and it’s very hard to go back to anything lower for just regular desktop use. Spent some time with at my father’s house and was missing it hardcore. Got a chance to try out a few projectors with BMS, but couldn’t wait to get home to my 144Hz gaming monitor.
Just a note, HDMI cables can’t do 144Hz, so it’s Display Port cable or USB-C for that, for those following along. Best wishes and good luck to you!! Thanks for the pics!
-
It’s running 144hz now like a champ.
-
Trying to get the YAME64 Kneeboard gauge to work. I can point to the 8019.dds file in YAME64 and display it in another YAME window without issue but it seems that the YAME Callback Kneeboard_Change does nothing for me. The doc says its suppose to switch between one of two data cards within the 8019.dds file.
Has anyone else got this to work?