YAME64 suite
-
Hi Roccio:
As I mentioned in my previous posts on this subject, I don’t think YAME is the problem. Again, I’m convinced its the recent Windows and/or Nvidia auto updates that’s at issue. YAME, as well as, Helios were working fine on my system until these updates kicked in. -
Hi Roccio:
As I mentioned in my previous posts on this subject, I don’t think YAME is the problem. Again, I’m convinced its the recent Windows and/or Nvidia auto updates that’s at issue. YAME, as well as, Helios were working fine on my system until these updates kicked in.I am just wondering what the problem could be. I am not on my Falcon pc right now, but I keep it up to date (windows-wise and nvidia diriver-wise) just to test. What I miss is a touch screen and a high DPI monitor. I know that there can be problems with antialias and masking, so just remove those settings if you have and try again.
-
Roccio: Have you ever considered replicating Helios so that YAME is an all-in-one application. The reason I’m asking is because after Helios went south on me a few months back, I reached out to Gadroc’s Workshop for a fix and didn’t receive a reply. I was left with the impression that the shop is closed.
-
I never had antialasing or masking ticked. And when YAME was up and working before IT stopped working, I didn’t have a problem with my two touchscreens. They responded to touch as expected.
-
Roccio: Have you ever considered replicating Helios so that YAME is an all-in-one application. The reason I’m asking is because after Helios went south on me a few months back, I reached out to Gadroc’s Workshop for a fix and didn’t receive a reply. I was left with the impression that the shop is closed.
In the next version there will be much more functions to interact with YAME. I’m not going to replicate all the Helios functionalities (that would require a lot of time), but what I have now (in my development version) I can get a full working cockpit. This part need a lot of testing and I don’t have a touch screen …
-
Understood. YAME is awesome right now but, what you’re projecting for the next YAME version would be beyond fantastic. I’m a YAME fan and I wish I had the expertise to pitch in and lend a helping hand. When Helios crapped out on me, I was vexed. When YAME stopped working, I freaked the hell out. On behalf of myself and, I would hope everyone else in the BMS community running YAME, you’re the best. My deepest and sincere thanks for your continuing great work.
-
Due to personal time problems, we’re in shortage of some serious testing. Since Roccio doesn’t have a touchscreen, maybe you can pitch in as tester?
Do keep in mind, the current alpha version is again a very big change so the first things that actually need testing, is all the basic stuff already available in the current release, in all its aspects (client only, client+server, 3D hook, RTT, all gauges, all variations of gauges like mlu, electronic etc, with and without masking, with and without background color and background images, multiple windows on multiple monitors, key server, touchscreen etc etc). -
I’d be honored to give it a shot - as time permits. However, understand that I’d be learning as I go and would need guidance…
-
Roccio has generously aloud me to test the new version and that is what I have been running the last few days. To answer Roccio’s question, when I say it won’t work, I mean the program itself starts up and functions properly (all three versions). The problem happens when I try to run the extraction to my second monitor. I can drag and drop it when I have it bordered with no issue. When I try and input the coordinates and then run the extraction it hangs up and I have to go to task manager and kill it. When it’s hanging, it is only using maybe 34mb of memory and 18% processor utilization. So the issue isn’t like what was happening with masking turned on where it would run the CPU up to 80% utilization. The odd thing is, it will run the extraction with no problems on the main monitor at coordinates 0,0. Then if I stop and start the extraction around 4 times I can then go back to window tab and change the settings to x3840 y 0 and it will finally extract it on the second touch panel. IT MAKES NO SENSE! lol. I do not think that it’s YAME necessarily causing the issue because once it’s running it’s smooth as silk.
It’s like YAME has to tell Windows the monitor configuration if that makes sense. In other words, when I simply run the extraction to X3840 Y0 Windows doesn’t understand the total resolution of my monitor configuration and by running YAME at 0,0 several times Windows see the overall resolution and finally puts the extractions at X3840. Man, that’s convoluted! -
Wicked: I hear what your saying. When I laid out my monitors in Display Settings as ICE suggested I was having the same problems. However, when I laid them out in their physical placement configuration I was able to set the coordinates to get my YAME gauges to populate my second monitor just as I wanted them using the drag feature. I don’t know if the following pics will be helpful, but its what I did to get my layout setup and I’m not experiencing a start and stop extraction problem. A you coined it - its running as smooth as silk.
Display Settings.
YAME Settings.
Gauge Layout.
-
Madmax, I will try setting the display setting as my monitors physically are laid out. However, how would Windows or YAME know where the monitor is in the real world?? lol To my knowledge it only knows it’s plugged in. What arranging the monitors in settings does is define how your mouse will traverse from one monitor to another…… hmm… I’m going to try it. Now I have to figure out the coordinates for it… Actually, I think I can use yours as my touch screen is below my main monitor. Nice setup BTW!
-
So mates, if someone wish to help let me know via private message.
-
So I’ve been reading and searching this tread and the manual, but I cannot seem to find any information on how to get YAME to overlay like it does in the second screenshot of the opening post. I can get YAME to run with the MFD and RWR in position, but it is behind the 3D window of BMS. Any hints or pointers are much appreciated!
Thanks!
-
So after moving the touch screen monitor in display settings to be positioned below my main monitor and setting those coordinates nothing changed. In fact, my YAME dance of starting and stopping the extraction 4 times on the main monitor at 0,0 and then switching the coordinates to put it on my touch screen no longer works.
Something else I noticed. If I set the coordinates to say x -1920 y 0 even though the monitor is on the right side at X 3840 in Windows settings, YAME will start and run the extraction. It will not put it on the monitor because that isn’t where Windows says it is. However, if I run my mouse over the YAME icon on the task bar, it shows the extracted layout and will stop and start without hanging up. The minute I set the coordinates to where the monitor actually is, regardless of which side of the main monitor (left, right, top or bottom of the main) I tell Windows it’s on, it hangs up. Windows will not allow YAME to move the layout to an active monitor other than the main unless it’s dragged over.I know many here are using the same version and build of Windows I am but there is something different I can’t find with mine keeping YAME from placing the layout somewhere other than the main monitor.
-
Hey Wicked,
Give a try with this.
Use the MFDE extractor for your MFDS DED PFD and Caution panel
with 60 ms in performance settings, and the yame64 for the rest
of your gauges. Be sure to have the Hook option ticked and put 6
refresh rate in the client window.
After many tries i find this is to be the best solution for a smooth BMS experience. -
Hey Wicked,
Give a try with this.
Use the MFDE extractor for your MFDS DED PFD and Caution panel
with 60 ms in performance settings, and the yame64 for the rest
of your gauges. Be sure to have the Hook option ticked and put 6
refresh rate in the client window.
After many tries i find this is to be the best solution for a smooth BMS experience.I you use MFDE for extractions related to texture (MFD, DED, PFD, RWR) you have no need to tick the Hook checkbox as this is only relevant for those kind of extractions.
6 as refresh rate seems a bit small, maybe 60? -
Hey Roccio,
I find 6 to be the magic number for me since anything above it cause the
bms to be really unplayable. I had above 150 FPS in the air and it seemed like having
a 20 years old graphic card. Same thing with the frames capped at 60 with the nvidia inspector.
As for the Hook option u are right. I forgot to remove it.
All these problems started with the latest nvidia and windows updates. Even rolling back
to 385.69 driver as ice suggested didn’t solve anything.By the way I didn’t had a chance before to thank you and your team for your magnificent software.
Keep up the great work guys. We are all waiting for the next big update. -
Hi again Wicked: I don’t know if the following provides a solution for you. Hell, I don’t even know if it even makes any sense (whether its intuitive or counter-intuitive).
Obviously YAME will layout your grid and gauges you’ve selected to run based on the X, Y coordinates you’ve set in YAME’s Client/Windows/Edit screen. Now, I ran into the same problem you describe when I set YAME’s Width to 3440 and Height to 1440 (mirroring that of my main display - Dell 34" Curved 3440x1440) and the x coordinate to 3440 and y coordinate to 0. What I encountered was that, when I set the x coordinate to 3440 and y coordinate to 0, it was only picking up my main display(edge-to-edge and not my other three (3) displays and Android Tablet (Left to Right as in ICE’s Window’s Display Settings layout). Initially what I didn’t account for, was the combined Width and Height of my other displays. I also noted that if I set my y coordinate to 0 and, populated the gauges I selected, dragging from the main display and placing them in position on my second display (LG 32" 1920x1080), when I ran YAME and then Launched BMS I was getting a black screen on all of my displays (no gauges at all on any of my displays). )
This result stumped me for a bit. Then I ran Client/Windows/Edit again but, this time I ticked Border with Visible also ticked (I left Fullscreen, Masked and, Antialiasing un-ticked). I then dragged the White Boarder showing at the top of my main display down to the bottom of the main display (just about the top of my second display below the main) and dragged/placed my gauges on the second screen accordingly. When I ran YAME and Launched BMS, the gauges were pretty much close to where I wanted them and, BMS was showing fullscreen on my Main display. A little tinkering was needed (moving, resizing the gauges and, un-ticking Boraders) but, I got what I wanted. Note, that YAME changed the On Monitor window (in the Clent/Windows/Edit interface) from On Monitor 1 to, 2. At first, I had tried making the change manually but it wouldn’t take. I also had to putz around with my Width and Height settings. I still have to troubleshoot these setting because only a fraction of the YAME Grid is showing on my third display (set up as Portrait and Inverted in Win 10 Desktop Display Settings).
Whether you call it intuitive or counter-intuitive, what I’ve concluded is that, if you set YAME’s y coordinate to 0, YAME is going treat the Top of your main display as its uppermost point of reference and its going overlay and mask BMS from showing up on that main screen (single, extended double or, triple main screen setups). BMS will be running but, its running underneath YAME on the main screen. If you review my Pos Y coordinate in my #1443 Post above, you’ll see that I changed it from 0 to 1403 (just a few digits under my Main display’s pixel height of 1440). So what I would suggest is that you set your Y coordinate to whatever your Main displays pixel height is and make adjustments from that number up or down. In short, you want your main display to run BMS’s graphical renderings independent of your YAME gauge layout which would be dedicated to your second, third and/or fourth monitor(s).
Per the YAME start and stop extraction issue. I don’t have a clue about what’s happing there. Way above my pay-grade. However, I would consider Varhn’s advice regarding BMS’s MFDE extractions. I’d try anything once, twice, thrice, ad-infinitum, if it’ll make this sucker work as desired.
Let me know how this quest turns out. I’m sure we can help each other in this effort.
Best regards,
Mike -
Hey Roccio,
I find 6 to be the magic number for me since anything above it cause the
bms to be really unplayable. I had above 150 FPS in the air and it seemed like having
a 20 years old graphic card. Same thing with the frames capped at 60 with the nvidia inspector.
As for the Hook option u are right. I forgot to remove it.
All these problems started with the latest nvidia and windows updates. Even rolling back
to 385.69 driver as ice suggested didn’t solve anything.By the way I didn’t had a chance before to thank you and your team for your magnificent software.
Keep up the great work guys. We are all waiting for the next big update.do yoy have window mask enabled? if yes try to disable it
-
As Roccio said, if you’re using any of Ice’s layouts uncheck masking on the windows tab. It will make you assign a background color and I usually choose black. Helios will cover it up anyway.