YAME64 suite
-
To ALL and a shout to ICE. I’ve got YAME back for now. Haven’t populated it yet, but hope I won’t encounter any stop working notices like before. I’ve also got HELIOS back as well. I’m not Irish (actually a mut with a a bit of Scot in me) but, I’m dancing the jig. Note that I encountered two probs from the onset: missing msvcp140.dll and vcruntime140.dll. Once I downloaded these items and placed them in my sys32 folder - all was well. At least so far. Don’t know why these two items were left out of the mix after a reset. But again, so far, so good. As noted earlier - no more WIN 10 or Nvidia auto updates for me. Castrated those suckers.
good to hear this!
-
roccio: thanks for reach out. Going to re-populating YAME and Helios now. Spent the morning pouring through You Tube How To vids. There’s a plethora of support info available - a great resource to find out to apply a bunch of fixes. I’ll send a pic of my modest pit when I’m done.
-
To ALL and a shout to ICE. I’ve got YAME back for now. Haven’t populated it yet, but hope I won’t encounter any stop working notices like before. I’ve also got HELIOS back as well. I’m not Irish (actually a mut with a a bit of Scot in me) but, I’m dancing the jig. Note that I encountered two probs from the onset: missing msvcp140.dll and vcruntime140.dll. Once I downloaded these items and placed them in my sys32 folder - all was well. At least so far. Don’t know why these two items were left out of the mix after a reset. But again, so far, so good. As noted earlier - no more WIN 10 or Nvidia auto updates for me. Castrated those suckers.
Unfortunately I’ve given up on making YAME work for now. I’ve reset and reformatted my computer, I’ve upgraded my graphics card to 1080ti. I’ve upgraded processor, board and memory and YAME is still unstable for no reason I can understand. It all started with the Windows Fall Creators update where it would draw tons of computing power. I fixed that by turning off masking. Then not a month later it wouldn’t load the gauges to the monitor anymore and would freeze. Then it wouldn’t even start. I fixed the non start issue by renaming the YAME file in the config folder. Now it still will not load onto my second monitor without first allowing it to load on my main monitor at 0,0, stopping and starting the client at least three times and the changing the coordinates back to 3840. I can fly maybe one mission before it crashes and then I have to do the dance again. It does this with stock, included layouts and Ice’s layout.
It will work if I leave borders on and drag it over but Ice’s Helios profiles aren’t meant to work with borders so the border pushes the top gauges down too far to size properly.
So I’ve pretty much stepped away from Falcon until a fix is found. MFDE does the job but looks terrible to me now.
YAME obviously works on other systems but I’m baffled as to why it will no longer work on mine. -
This problem should be solved just by turning off the antialias and mask options in CLIENT\WINDOW tab
I’ll try this tomorrow.
-
Wicked: Those are some wicked issues you describe. I also had the exact same problems which prompted me to wipe my main SSD drive and start all over. Reading your thread just scared the shit out of me as I’m in the process of reinstalling/reconfiguring all of my apps and hardware. FYI: my system worked great with YAME and Helios for about 4 or 5 months after installation and setup before Helios and then YAME STOPPED WORKING. However, I believe the issue is with WIN 10 and Nvidia auto updates and, not with YAME or Helios. I’ve spent the last few days disabling every potential auto update possible. I now have YAME and HELIOS working again - although I’m still in the programming process. Gee wiz I hope it gets me back up and running. If not, I’ve got to step back myself. A whole lot of time, effort and, coin of the realm has been poured into this project. I wish you luck - wish me luck ass well.
-
Roccio: Do you suggest using YAME’s MFD extractions or BMS’
-
Roccio and Ice:
Could you do me a solid and recommend the best Block to load in YAME. -
Roccio: Do you suggest using YAME’s MFD extractions or BMS’
I vote for YAME extraction
Roccio and Ice:
Could you do me a solid and recommend the best Block to load in YAME.Sorry, but I don’t fully understand your request…
-
Quick question…
Until now, M2000 and F-18 were not supported for MFD extraction on YAME, is it still the case?
Cheers
-
Quick question…
Until now, M2000 and F-18 were not supported for MFD extraction on YAME, is it still the case?
Cheers
next version will provide almost full f18 cockpit gauges.
if i have time, information and hires images i can do the mirage ones -
Roccio and Ice:
Could you do me a solid and recommend the best Block to load in YAME.If you’re going to use a default YAME layout, use the block 50. However, if you’re using Ice’s Helios profiles it will not work. What I would suggest you do is what I have done. Get the latest Ice Helios profile and layout for one monitor which I believe is 21S. Don’t copy the layout into the YAME layout folder but instead use it to create a new layout. You’d do this by obviously starting a new layout and name it whatever you like. It will default the window name to YAME so change that. Next click on the new window and then click edit gauges and also open Ice’s layout in Notepad ++. Right click on the grid and select gauges and add one gauge at a time using Ice’s layout to get the coordinates and gauge size and repeat for all gauges until finished. I would leave out the CP and map for now and just get all the base gauges to fill the Helios profile then save it. Where I am having the issue is telling YAME which monitor I want the layout to go to. I can put a border on it, set it to 0,0 on the main monitor and drag it to my touch panel but I can no longer simply input the monitor coordinates and have it work. I am working with Roccio to try and figure out why and once I get it I’ll let you know. All I can tell is that something has changed in Windows that is keeping YAME from understanding the coordinates of my monitor configuration. I run a 50" 4KUHD TV with native 3840x2160 res and a 27" touch panel with @1920x1080. I put the touch panel to the right of the TV in display settings aligned across the top or Y,0. This would make my starting coordinate for the touch panel X,3840 and Y,0. It has always worked before but no longer.
-
Right on. In my last iteration, I was using BMS’ MFD extraction. I’ll go with YAME this go round. In respect to which Block you recommend. I was referring to YAME’s Load Layout. I was running the default.xml layout before YAME crapped out on me. Now that I’m reconfiguring my sys, I just wanted to tap into your wisdom.
-
Hi Wicked: Thanks for sharing your how to advice. We’re pretty much on the same page. Before Helios and, then YAME failed, I was running the default Block. Now that I’ve started again from scratch, I’ll load YAME’s Block 50. In my previous build I also used a good bit of Ices’ profile. In any event, your recommendations are valuable. I’ve attached a few pics of my modest pit to give everyone an idea of what I’m working with. Again, thanks for your help.
-
Hello mikemadmax,
I like the emergency scissors in your pit
Thanks for sharing and have a great day,
Tweety -
In my pit I have 2 bodnar BU0836A DX cards. Both cards are named BU0836A in the game controller list in W7. One for my ATD panel and one for my CPD. In YAME I set the push buttons of my CPD to the corresponding YAME keystrokes. The problem I am facing is that in BMS, when I push a button of the CPD, it doesn’t respond. When I press a button of the ATD the CPD display (YAME) responds. The buttons of the ATD are set in BMS to the corresponding BMS TWP keystrokes.
It seems YAME does have problems with multiple USB controllers if they have the same name.Anyone with the same kind of problems?
Is there any solution for this problem?Doc
-
In my pit I have 2 bodnar BU0836A DX cards. Both cards are named BU0836A in the game controller list in W7. One for my ATD panel and one for my CPD. In YAME I set the push buttons of my CPD to the corresponding YAME keystrokes. The problem I am facing is that in BMS, when I push a button of the CPD, it doesn’t respond. When I press a button of the ATD the CPD display (YAME) responds. The buttons of the ATD are set in BMS to the corresponding BMS TWP keystrokes.
It seems YAME does have problems with multiple USB controllers if they have the same name.Anyone with the same kind of problems?
Is there any solution for this problem?Doc
never tested multiple devices with same name, but in the next version i have rewritten all the input sysyem.
-
I hope this issue is solved with the next version. I really like this piece of software!!
-
Can you give them different names? To alleviate the duplicity?
-
-
Those of you for whom YAME is working flawlessly, can you post your Win10 build number and Nvidia driver? I have eliminated YAME settings, hardware settings and layout settings as the cause of YAME not working on my system. Obviously many of you are able to run it with no issues and the only thing I haven’t tried is Nvidia drivers and compared Windows builds.16299.371 version 1709 is my Windows build and version number and 391.24 is the Nvidia driver I’m using.
Thanks,
Wicked