YAME64 suite
-
HI Ice and Rocci:
I’ve downloaded YAME64 and have customized my instruments configured for my muti-display setup. Its a fantastic utility and all the gauges are working perfectly. What a beautiful application you guys have put together. However, one problem. I can’t get the MFD’s, RWR and, DED to extract when I run the program. I’ve read your release manual over and over and have tried a number of different variations. I still cant get these important extractions to display. I’m running the layout on a second touchscreen monitor wit TM Cougar MFD’s velcro’d to the screen. I’ve been in touch with ICE on this extraction problem since I can’t extract the MFD, RWR and, DED from within BMS’ Cockpit and Display extractor either. I’m beginning to think that maybe my copy of BMS Falcon 4.33 (U1, U2 and U3) is missing a file for extracting these items. I could really you guys help and expertise. I’ve included a few screen shots of my settings below hoping you guys can make some sense of where I’m going wrong. Thanks again for your assistance.
Mike
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.
-
ICE and ROCCI:
Please also note the additional screen shot below:
Mike
-
First, thanks for the kind words, but I have nothing to do with this program aside from flooding the devs with feature requests. Credit goes to Roccio, Focal, and Scorpion for their hard work!
Is there any reason you are using HOOK? Under the SERVER tab, try having EXPORT FLIGHT DATA and EXPORT TEXTURE DATA ticked, and that’s it. Max clients 1, unless you have a reason for having 4. Under the CLIENT tab, just have ENABLE FLIGHT DATA and ENABLE TEXTURE DATA ticked, no need for the hook.
Give that a go.
-
Again, thanks for getting back to me Ice. For some reason I was under the impression that you were prominently involved in the YAME64 development. In any event, your a man of honor for pointing to where the credit is richly deserved. For the past year or so, before my system crashed, I spent a good amount of time with HELIOS with some great success. But, pardon my New Yorker parlance - “YAME is the Joint”.
My hat’s off to Roccio, Focal and, Scorpion for creating such a fantastic product. The realistic textures of the instrument gauges are absolutely phenominal. And ease of layout creation dramatically flattens the learning curve.However, I’m still plagued with the same problem. I can’t extract the MFD’s, RWR and DED. I hope I’m not becoming a pest. But this problem has me licked and I can’t figure out why these items are not rendering - either in BMS’ Display Extraction or in YAME. As I mentioned, I’m thinking something is missing in my BMS config file or some other file. I say this because I’m able to extract these items in DCS. Although I don’t know if its of any relevance. I’m attaching my User/config file for your review. Maybe you can see something that’s causing the problem. If you need anything else please let me know.
I know this is an arduous process that puts the beg on your time and energy. Understand, that this guy from across the pond really appreciates your efforts in helping the BMS brothers in arms.
By the way, I followed your instructions and made the changes as advised.
Best regards,
Mike
-
Again, thanks for the kind words! I am only involved in the sense that I bombard them with feature requests and help out on the forums when I can. Like I said, the heavy lifting is done by those guys and so the credit is due to them.
I think you are confusing Helios and YAME. Helios has a little overlap with YAME as you can use Helios for gauge display but I’ve never used Helios for that. For me, Helios is just for switches/knobs/buttons and YAME (and MFDE before it) is for gauges and display extractions, so there is no overlap as far as my usage goes. YAME has more features than MFDE and thus improves on the function immensely.
Are you getting response from the YAME gauges? If so, that means YAME is getting data from the sharedmem. You do NOT have to enable cockpit extraction. Take a look at my BMS Config setup here and you’ll notice that COCKPIT DISPLAYS TO EXTERNAL WINDOWS is un-ticked.
-
When you go to CLIENT -> WINDOWS -> YAME -> EDIT GAUGES, do you see your MFDs and are they placed correctly?
Go to your Falcon\Bin\x64 folder and remove any HOOK files (d3d9.dll, hooklog.txt, yame_d3d.cfg) present.
-
Thx for the kind words.
If you are also experiencing problems with bms extractions I’m guessing something got porked. Yame gets extractions from bms so if bms itself doesnt show it, Yame won’t be able to either.
My best advice would be to uninstall bms and reinstall completely. But maybe there are less drastic options too I’m unaware of. -
I don’t think that’s it Focal… his pic above shows the in-pit MFDs working, but nothing on his secondary screen extractions, so BMS does show the MFD images…
-
I don’t think that’s it Focal… his pic above shows the in-pit MFDs working, but nothing on his secondary screen extractions, so BMS does show the MFD images…
If I understand his explanation correctly, he tried extracting them
With bms built in extractions and that also didnt work. -
any ideas re my problem (parformance, random keypresses)?
-
If I understand his explanation correctly, he tried extracting them
With bms built in extractions and that also didnt work.I’ve got a sneaky feeling that he extracted those gauges BEHIND his main display.
-
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.