YAME64 suite
-
Ok, managed to get hook working (still a bug in client that it wont receive hook data unless you tick it in Server tab - then it becomes visible in client tab).
No fps impact, that’s good.
But i can’t get the smoothness. The MFD is jerky, especially on TGP etc.
I tried 60fps both s and c - more lags.
What should i try next based on the collective experience?
Server is yame64 -> 100mbps ether -> yame32 client.edit: one more thing - may be unrelated, but tests indicate otherwise at the moment. on a bms ‘server’ machine i experience random in-flight keypresses while yame’s running (keyserver DISABLED, xml value FALSE). ‘n’ (nightvision) activated about 3 times randomly, and other times something ‘clicks’ in the cockpit as well without any obvious effect… only addition i made to the fully working rig (with U1) is the yame64 server with hook. thanks
No immediate idea on the performance I’m afraid. I can get a solid 30FPS on my client in Belgium when getting textures send through by someone in Poland.
Maybe it has something todo with 32bit client. Or with the specs/gpu/drivers on the client machine, just guessing here.On the in flight keypresses I have no idea. Never experienced it up till now. If the key server is not on, it shouldn’t be translating anything and client/server by default don’t generate keypresses. I’m not entirely sure it’s a YAME cause on that one.
PS: in next release we will have a right click (or tab & hold on touchscreens) on all client windows to close them
-
@mikemadmax, please send me the following files:
- YAME config (/yame64/config/yame64.xml)
- layout file (/yame64/layouts/<yourlayout>.xml)
- a screenshot and/or description of your screen setup so I can determine what you secondary screen is where you wish to run the YAME client on</yourlayout>
-
Thanks for the right click fix!!!
Ok, i kinda tweaked it for performance - server fps is 20, client fps is 40 and smoothing off. Almost no lag. Good.
Continuing to hunt down the random keypress culprit. Will try recording acmi. But from about 20 attmpts at Landing TE about a minute in a have NVG on and sometimes gear lowers (or alt gear). When i fly no-yame - none of that. VERY strange. I will even swap usb ports for my controllers to hunt it down. And yes, with my setup there can be numerous keystroke culprits (x55, g13, mfds).
Thanks agaiN!!! -
Sys Specs: Win 10 Pro [64], MSI Game Pro MOBO, i7 CPU, 32GB Memory, 2 (x) ASUS Nvidia 970 GPU’s w/ SLI bridge, WD 500Gb SSD, WD 2Tb SATA HHD, Toshiba 2Tb SATA HHD, Samsung 23" Curved Mon, ASUS 19" Touchscreen Mon, MIMO USB 7" Touchsreen Mon, TM Cougar TQS w/ TUSBA, TM Warthog SSC, TM Rudder, TM MFD’s, Track IRv5, Air Force Game Seat, Gametrix Jetseat, Corsair Head Phones.
Mike, I see you have 2x 970’s, are you by chance forcing SLI AFR2 for BMS?
If so, turn it off or select SFR and it should work.
I had the same issue when running SLI AFR2.
Hope it helps. -
Hey Guys:
Just returned from some Honeydo mandates. But man what a response. Reminds me of my days back in the Corp. When the rounds were kicking up dirt and whizzing by your ears - you felt alone until you looked around to see your brother grunts sending heat down range. Thanks a bunch guys for your outreach. Focal, your read is correct, I can’t extract MFDs, RWR or DED from within BMS either. And ICE I’ll look into whether I’ve place my extractions behind my main display. However to all, as I’ve been communicating with ICE, my system crashed a couple of weeks ago and I couldn’t even get a hard boot. I tried everything, including recovery software. Got fedup and went out and purchased new SSD and SATA drives along with an upgrade from Win 8.1 to Win 10 Pro. Naturally, I had to do a fresh install of BMS U1 through U3. From the start I couldn’t even load BMS without a CTD situation, never mind extract from within BMS’ Cockpit Display Extraction. With great assistance from ICE, Cloud 9 and, other members, I’ve been able to launch BMS as a stand alone and, from YAME64. Give me a bit of time and I’ll compile config and layout files along with screenshots and send them along in short order. Let me get to work and I’ll be back.
Thanks again and chat soon.
You guys are the best.
Mike
-
TxMtb thanks for your insight. Yep, I am running 2x 970’s with an SLI bridge. I’ll check out your recommendation and get back with my findings in short order.
-
Ice: You very well may be right. Allow me to ask a noob question. As we discussed, I have three monitors: (1) Samsung 23" Curved Screen at 1920x1080; (2) Asus 19" Touchscreen at 1600x900 and; (3) MIMO 7" Touchscreen at 1024x600. Should I add all these figures together to get a combined total of 4544x2580 and apply this number as my total display real estate? For example in YAME’s "CLient>Windows> Width & Height boxes. Or should I set the width and height to my secondary screen resolution where I’ve placed my instruments (see attached screenshot)? By the way all my gauges are working in-flight.
-
TxMtb: I’ve disabled SLI. No joy. But thanks for the suggestion.
-
Ice: You very well may be right. Allow me to ask a noob question. As we discussed, I have three monitors: (1) Samsung 23" Curved Screen at 1920x1080; (2) Asus 19" Touchscreen at 1600x900 and; (3) MIMO 7" Touchscreen at 1024x600. Should I add all these figures together to get a combined total of 4544x2580 and apply this number as my total display real estate? For example in YAME’s "CLient>Windows> Width & Height boxes. Or should I set the width and height to my secondary screen resolution where I’ve placed my instruments (see attached screenshot)? By the way all my gauges are working in-flight.
No. First, post a screenshot of your display setup. Like so:
To get this, right-click on your desktop and click on DISPLAY SETTINGS. Show us what you’re working with.
As for YAME, you can specify any height and width. I like my window to be FULLSCREEN, so I set it up as 1920 and 1080. If I want it to be displayed in Monitor 1 (see above), then it’ll be Pos X -1920, Pos Y 0. To get it to show on Monitor 3, it’ll be Pos X -3840, Pos Y 0. I then just position the gauges and stuff within that window as needed. If I wanted a new window that I can turn on and off, I can make it a smaller size, but then it’ll be tricky to position it along the X and Y properly. Note that my two monitors are at NEGATIVE X coordinates since my main screen (#2) is on the right side and it’s upper-left corner is 0, 0.
I hope that made sense. Also note that it is strongly advised to have your main screen on the right side and have your secondary screens on the left.
-
Hi Folcal: As requested I’ve attached my YAME64 Config.xml, layouts.xml along with a screen shot of my display setup. Hope these can me get these extractions working. Again, please note that all my my guages are working while in-flight.
-
See the attached:
-
See the attached:
That is unnecesarrily complicated. I suggest you line them up with the smallest at the left, middle-sized in the middle, and main screen on the right.
-
Yep it made sense. I’ve had my displays setup as depicted for about five years now - although I’ve swapped out monitors over the years to upgrade to touchscreen displays. I’ve also been using BMS for quite awhile. As I think I mentioned, I have the original boxed Falcon 4 as well as Allied Force. I dropped them when BMS entered the market. The reason I asked for your thoughts on totaling combined screen resolutions was because years ago when I was setting up multiple monitors (I think for Janes’ F/A-18 Simulator or Graphsims F/A-18 Operation Iraqi Freedom) it was required. I still have Janes’ and Graphsims original disks. Now that I’ve retired, I have the time and resources to get back into simming with devotion. While I’ve been tempted to get on my separate and dedicated civilian flt sim PC (running X-Plane, P3D and FSX Gold as well as the Steam edition), I can’t give up my BMS. So I’ve got to tackle this problem. And again, I thank you and the others in the Falcon community for lending a hand. Your advise, expertise and passion are invaluable.
-
Will do.
-
ICE: Would you do me a kindness and send me a thumbnail of your BMS File structure. I’m beginning to think I’ve got a corrupt 4.33 download and as a result I’m missing some critical files. Thanks for your patience.
-
I can’t give up my BMS.
I know the feeling, bro…
So I’ve got to tackle this problem. And again, I thank you and the others in the Falcon community for lending a hand. Your advise, expertise and passion are invaluable.
I can only say thank you for the kind words. My “expertise” is built upon the knowledge and help shared to me by OTHERS in this community, so it is my duty and pleasure to pay it forward
ICE: Would you do me a kindness and send me a thumbnail of your BMS File structure. I’m beginning to think I’ve got a corrupt 4.33 download and as a result I’m missing some critical files. Thanks for your patience.
I’d advise you to read this post and move forward from there.
-
Okay, weird issue just now. I’ve returned to the v1.1 install that is publicly available and had a few flights with it working. All of a sudden, when testing out something for another forum member (-Pv-'s IDM issue), I noticed my MFDs and DED were blank. Weird. So I went back to the YAME suite and ticked TRANSPARENT BACKGROUND for these and I got an image back…. but with a gray background (Block 15 had green MFDs). I immediately knew something was up. I set the left MFD as unticked TRANSPARENT BACKGROUND and the right MFD as ticked. Both MFDs worked but the left one was exactly how it appeared on the cockpit (black background) while the right one had a gray background. So I unticked all TRANSPARENT BACKGROUND options (except RWR), saved my profile, and started again.
No image. Closed YAME, started it up again. No image. Very annoying.
The fix? Rebooted the computer. Without changing anything on YAME, I started it up, images there and working.
Lesson – turn it off then turn it on again.
-
Happened again. Set TRANSPARENT BACKGROUND for DED, start up YAME, no image on all extractions. Shut down YAME, start it again, still no image. Restart computer, start YAME, everything works. Set TRANSPARENT BACKGROUND for PFL, start up YAME, everything works.
So it is an error that is reproducible, but doesn’t occur all the time. But I wouldn’t bother about investigating this as the beta versions we have doesn’t seem to have this issue and the release version seems to behave itself once setup is done and YAME is just “used” rather than fiddled with. Just posting it here for others to know about and what the “fix” is.
-
Hi, thanks for this great tool.
I use single PC with only 01 monitor. Is it possible to use CP60 as texture overlay? I know MFD, DED and RWR does.
If not could it be implemented in the future?Thanks.
-
That’s an interesting development with the v1.1 install. As you may recall, I had to do a fresh install (after setting up my new SSD and SATA drives) downloaded from the BMS thread announcing its new release of U3 which pointed to the U1 setup as a first step. Remember, after the fresh install (even after repeated uninstalls/re-installs) it would CTD every time I tried to launch BMS. Cloud 9 advised that I check to see if dx9display.dsp was in my user/config file - it wasn’t and I had to add it and then delete as I understand it regenerates whenever you restart BMS. In addition, Cloud9 advised me to add -Mono -window to my BMS Target Launch.exe path. Only then was I able to get BMS to Launch. It’s not YAME because all of this was happening before I loaded YAME64.
You know what, I just remembered that I also have Falcon BMS 4.33 installed on my civilian flight sim PC (dating back to 10/18/2015). It started right-up with MFD’s, RWR and, DED along with Helios gauges rendering with no problems. I’m going to cross reference both system files and see if I’m missing any of them.