YAME64 suite
-
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.
-
yes, in some update ( don’t know if windows or video driver) we encountered a big problem with masking. i don’t think this feature is usefull as you can run helios in front of yame, so inthe next version i would prefear to remove it.
need to understand what can be the positioning problem. maybe is related to high dpi monitors? -
Hey Roccio,
I have both antialiasing and masked window disabled.
At the moment I don’t encounter any performance issues but
yame isn’t as smooth as it used to be.By the way Mike.
I had similar problems to yours. I solved them by
by right clicking into yame icon > properties > compatibility tab > display dpi settings to application.
After that the next time u run yame you drag each window to your preferred monitor. Then right click on it and then click : remove border, align to monitor, fill in monitor, save layout and then you close it. That way u get the exact coords. After you have all your windows where u want them you go on the main page and have borders antialiasing and mask disabled.I hope u get all of your problems solved real soon.
-
Hi Varhn:
That’s exactly how I had my system set before YAME crapped out on me a couple of weeks ago and, now post recovery - after reformatting my main Drive and starting over. Its funny because having I reached out to Wicked last night to offer some help on the same issue, I went into Desktop Display and moved my fourth display (dropping it down and to the right, adjacent to my other monitors) and voila, the YAME grid filled the entire 4th monitor screen as well. Its all about setting the right coordinates so that all the displays you want to use fall within the grid so that you can position the gauges wherever you please. I’ve got it running perfectly again. In fact last night, I flew my first campaign mission since getting back in the pit. I fragged a 12 ship package, an OCA Strike out of Seosan targeting NK Haeju AB. SEAD took out the SAMs, Escort dealt with MIGs and, my AI Wingmen and I dropped our GBU 24’s and obliterated Haeju. TRaclIR, Voice Attack, Jet Seat, TM MFD’s and, my recently acquired Viper Gear ICP - all worked flawlessly. It was total immersion and fantastically gratifying. I still have figure out how to fine tune my aging Cougar TQS - maybe a Hall’s update. We’ll see.To Roccio and Fd:
I really do feel Win 10 and/or Nvidia auto updates are wrecking havoc on YAME and Helios. Since reformatting my main drive and restoring to Win 10 V1703 Build 15063.966 and Nvidia Driver 382.05, I haven’t had any problems. Note that I permanently disabled future Win and Nvidia updates. FYI: although I’ve got Helios working again, I haven’t set it up. I’ve decided to table it for the time being pending release of your next YAME version. If you guys can replicate most of Helio’s extractions and, create a functional stand-alone turn-key F-16 (and F-18) pit, it would be beyond awesome. It would be a game changer. Again, I would be honored to help you test the beta. -
I don’t how that smiley popped up but, it’s the Superbug I was referring to.
-
Hi Varhn:
That’s exactly how I had my system set before YAME crapped out on me a couple of weeks ago and, now post recovery - after reformatting my main Drive and starting over. Its funny because having I reached out to Wicked last night to offer some help on the same issue, I went into Desktop Display and moved my fourth display (dropping it down and to the right, adjacent to my other monitors) and voila, the YAME grid filled the entire 4th monitor screen as well. Its all about setting the right coordinates so that all the displays you want to use fall within the grid so that you can position the gauges wherever you please. I’ve got it running perfectly again. In fact last night, I flew my first campaign mission since getting back in the pit. I fragged a 12 ship package, an OCA Strike out of Seosan targeting NK Haeju AB. SEAD took out the SAMs, Escort dealt with MIGs and, my AI Wingmen and I dropped our GBU 24’s and obliterated Haeju. TRaclIR, Voice Attack, Jet Seat, TM MFD’s and, my recently acquired Viper Gear ICP - all worked flawlessly. It was total immersion and fantastically gratifying. I still have figure out how to fine tune my aging Cougar TQS - maybe a Hall’s update. We’ll see.To Roccio and Fd:
I really do feel Win 10 and/or Nvidia auto updates are wrecking havoc on YAME and Helios. Since reformatting my main drive and restoring to Win 10 V1703 Build 15063.966 and Nvidia Driver 382.05, I haven’t had any problems. Note that I permanently disabled future Win and Nvidia updates. FYI: although I’ve got Helios working again, I haven’t set it up. I’ve decided to table it for the time being pending release of your next YAME version. If you guys can replicate most of Helio’s extractions and, create a functional stand-alone turn-key F-16 (and F-18) pit, it would be beyond awesome. It would be a game changer. Again, I would be honored to help you test the beta.YES TO THIS!
-
Hey Roccio,
I have both antialiasing and masked window disabled.
At the moment I don’t encounter any performance issues but
yame isn’t as smooth as it used to be.By the way Mike.
I had similar problems to yours. I solved them by
by right clicking into yame icon > properties > compatibility tab > display dpi settings to application.
After that the next time u run yame you drag each window to your preferred monitor. Then right click on it and then click : remove border, align to monitor, fill in monitor, save layout and then you close it. That way u get the exact coords. After you have all your windows where u want them you go on the main page and have borders antialiasing and mask disabled.I hope u get all of your problems solved real soon.
Trying this.
-
Who here has YAME running well and also uses a Rift or WMR HMD like the Samsung Odyssey or Vive? I’ve moved on from thinking YAME is causing the issue of not placing the layout on another monitor by using coordinates and not dragging. As I’ve stated in the past, YAME will load onto the second monitor after being started and stopped and the main monitor and then changing the coordinates to the second monitor. However, it will only run once like that. After the first run it will lock up upon starting and then crash…. Working on it.
-
YMMV, Windows 10 1803 update breaks YAME for me again. It comes with Nvidia 390.77 drivers.
Gonna mess around with reverting to 385.xx drivers as this fixed it before.Edit: Yep, 385.41 and everything went back to normal.
PITA that can’t figure out why newer drivers won’t work. -
i have just finished to install 1803. will see if there are problems.
-
I can not use pedestal moving map in new theaters. What are the requirements for map loading in size and format?. I tried to add maps from WDP for new theaters as Spain but when I doing ramp start, when I select map on pedestal a warning appears saying “Iberia map not loaded”, for instance. I reduced the map to 1024x1024
Any clue? -
you can check map dimension from the Korea map (2048x2048x24 PNG) i’m using 4096x4096x32 map in ISRAEL without problems.
Take care of this:file type: PNG
file location: YAME\gauges\cp60\maps –- IF YOU ARE USING REMOTE CLIENT SHOULD BE ON REMOTE CLIENT
file name: <theater name=“”>.png & <theater name=“”>White.png –- AS indicated from the error dialog!!!</theater></theater> -
Thanks Francky I think you are right.
I it does not work Chicho you can send me the map files and I will correct them for you.Now I’m busy to try to resolve a problem that the new Windows10 has with OpenGl and fullscreen windows.
-
Thanks Francky and roccio.
I have done exactly what you say but I continue with the same problem. Nordic theater works fine except BE is on left botton corner of the map all time. I have check in settings and BE posit is correct. Spain POH theater does not load the map properly named. All others theaters work fine. Thats the reason why I ask you for the correct format and size. Anyway roccio, I will send you the maps I have for theater with problems.
Regards.