YAME64 suite
-
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 -
Hey Wicked,
Using Win 10 Pro Ver 1709 Build 16299.371
Nvidia drivers are version 385.28. anything newer than 385.41 causes YAME to mess up on my machine. It runs, but flickers the entire YAME screen.
385.41 caused some issues but nothing that affected YAME. -
Hi Tweety:
Great observation. The emergency scissors are there to warn Wifey (AKA: Sylvester) that her tongue is at risk if she keeps bugging me about how much time I’m spending on trying get to my rig up and running again (sic). Thanks for your levity. Much appreciated right now.
Mike (mikemadmax) -
Hi Wicked,
I have WIN10 HOME Edition, OS Build 15063.909 and NVIDIA drivers 385.41. YAME works great with these. I have blocked all updates, but Microsoft is trying really hard everyday.
Johan
-
Hi again Wicked. I’m running Win 10 Pro Ver 1703 Build 15063.966 and Nvidia (2x970’s) driver 382.05. As I mentioned in an earlier post, when YAME pooped out on me I reset my main drive (C:) and started over - methodically reloading all my hardware and applications. As a refresh point, I loaded my original Win 10 Pro and Nvidia disks and declined any updates. I also permanently disabled the auto update features for WIN 10 and Nvidia. If your not familiar with disable process, You Tube has crap load of How To videos on disable procedures. Frankly, stuff I never knew existed. In any event, as of an hour ago, I’m back up and running YAME with no problems so far. Again, as many have noted, Win 10 and Nvidia auto updates are the likely gremlins in the mix.
-
Well, changing drivers has not worked so I’m down to two things. A windows update killed it or it no longer likes the touch panel. I’ll test the touch panel by putting my smaller dell 23" in its place. If that doesn’t work I’ll reset one last time.