YAME64 suite
-
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.
-
I don’t know what else to suggest at this point. I’m not a newbie, but I’m no guru either. Again, I tried every possible reset action before frustration got the best of me. And frankly, no one in the community had a real working fix. It wasn’t until I completely wiped my main drive that I was able to restore YAME after reloading BMS Base 1 thru 4.33U5. Helios seems ready to go as well - although I haven’t started to repopulate yet. I’m hopeful in that regard. I’ve got five display devices (32" main display, 27" secondary and, Lilliput 8" Touchscreen for Yame gauges, a 19" Touchscreen for Helios, along with an Android Tablet for moving maps) and they all seem to be working well. So, IMHO, I don’t think its the touchscreens. But rather - in my gut - I just feel that it’s the Windows or Nvidia auto updates (possibly both). I was reluctant to start all over again because I had so many associated apps on my system, including DCS. Hell, I just went through changes reloading qBittorent and WinZip, not to mention Hardware Drivers, TM Target GUI, Calibration, Voice Attack, Gametrix Jet Seat, TrackIR and others (devil of a time trying to locate the registry keys for all my apps). Note that I’m only mid-way through the rebuild process. I’m dreading having to restore DCS - I know it’s going to be a mind blowing trip. In any event - good luck. Let me know of your results.
Best,
Mike -
An update. I recently loaded a brand new copy of Win10 Pro, reloaded Falcon and DCS and changed boards. I also have a Rift and that’s a PITA as well to load so I decided to try something else. I’ve pretty much swapped all of my hardware that may have caused an issue with new parts. The only thing I haven’t changed in all my issues with YAME is my 27" touch panel. So I decided to swap the 27" with my original Dell 23". I had had some issues with my new video card but blamed it on the driver at the time and after the reformat it worked as normal. One of the reasons I upgraded was I thought that my processor or board overheated and was causing other issues. I had used Realbench from Asus to check my performance but one day it would not make it through the bench and even after swapping all the parts it still wouldn’t work.
Back to yesterday. I swapped out the touch panels and fired up YAME. When I say I fired up YAME I have a process now that occasionally will get me one session on Falcon. I start YAME and make sure it’s set to extract to the main monitor at coordinates 0,0. Then I run it and it always pops up with no problem. Then I stop it, then I start it, then stop it lol about 4 times. I stop it once more and then change the coordinates to x3840 y0 which should place it neatly on my touch screen. Low and behold it worked! Rather than waste time testing I flew a nice long Day 1 campaign mission for about 40 mins. NO PROBLEMS. Afterward I shut everything down and then tried to start YAME again… NO GO. SUPRISE SUPRISE. Rather than start kicking shit all over the man cave I instead when through my YAME dance and low and behold it worked again! Now that doesn’t necessarily mean that the monitor was at fault but there was one more clue to it possibly being A culprit. That Realbench Asus program magically began working like a champ again. In the past I’ve had other issues I attributed to a bad HDMI or DP cable but I now think it’s been the damn monitor the whole time. Great.
However, after saying all that. Why the hell do I have to start and stop YAME 4 times to get it to work on the extended monitor. Unfortunately, Windows updates are a way of life now that I have a Rift so I would really like to find the issue. Until then at least I can fly again! Who says the Falcon dance is dead??? -
I don’t know what else to suggest at this point. I’m not a newbie, but I’m no guru either. Again, I tried every possible reset action before frustration got the best of me. And frankly, no one in the community had a real working fix. It wasn’t until I completely wiped my main drive that I was able to restore YAME after reloading BMS Base 1 thru 4.33U5. Helios seems ready to go as well - although I haven’t started to repopulate yet. I’m hopeful in that regard. I’ve got five display devices (32" main display, 27" secondary and, Lilliput 8" Touchscreen for Yame gauges, a 19" Touchscreen for Helios, along with an Android Tablet for moving maps) and they all seem to be working well. So, IMHO, I don’t think its the touchscreens. But rather - in my gut - I just feel that it’s the Windows or Nvidia auto updates (possibly both). I was reluctant to start all over again because I had so many associated apps on my system, including DCS. Hell, I just went through changes reloading qBittorent and WinZip, not to mention Hardware Drivers, TM Target GUI, Calibration, Voice Attack, Gametrix Jet Seat, TrackIR and others (devil of a time trying to locate the registry keys for all my apps). Note that I’m only mid-way through the rebuild process. I’m dreading having to restore DCS - I know it’s going to be a mind blowing trip. In any event - good luck. Let me know of your results.
Best,
MikeMake sure you deactivate your modules before wiping DCS. If not no worries but once you use your allotted installs, you get new ones once a month… Where’d all the trust in the world go?
-
Just to better understand. When all of you with YAME problems say that it does not work, what do you mean?
It crashes or it does do nothing (have you checked in process explorer if it’s runnig in background)?
When does the problem occour? Launching YAME UI or when hitting the START CLIENT button?Thanks to all, just trying to figure out what the problem can be, keep in mind that YAME is just a (quite) simple OpenGL application.
Another thing to try is the 32 bit version.
-
Wicked: Thanks for the advice. Will do. However, I backed up everything on my Drive to my & E: 1 and 2 Tb Drives as a safety net before I purged my main Drive. Hopefully, I can fully restore DCS from one of those without too much hassle. I did run into issues restoring some of my prior apps using the copy feature and decided to reload those apps from scratch - ergo the registry key hunt. But, after reading your posts I’ve got to say I admire your resolve. Me too. I’m not going let the gremlins get the best of me either. Only problem is, I’m spending more time troubleshooting than flying. Well in the immortal words of whoever it was that termed the phrase: “Keep em Flying”.
-
Hi Roccio:
As I mentioned in my previous posts on this subject, I don’t think YAME is the problem. Again, I’m convinced its the recent Windows and/or Nvidia auto updates that’s at issue. YAME, as well as, Helios were working fine on my system until these updates kicked in. -
Hi Roccio:
As I mentioned in my previous posts on this subject, I don’t think YAME is the problem. Again, I’m convinced its the recent Windows and/or Nvidia auto updates that’s at issue. YAME, as well as, Helios were working fine on my system until these updates kicked in.I am just wondering what the problem could be. I am not on my Falcon pc right now, but I keep it up to date (windows-wise and nvidia diriver-wise) just to test. What I miss is a touch screen and a high DPI monitor. I know that there can be problems with antialias and masking, so just remove those settings if you have and try again.
-
Roccio: Have you ever considered replicating Helios so that YAME is an all-in-one application. The reason I’m asking is because after Helios went south on me a few months back, I reached out to Gadroc’s Workshop for a fix and didn’t receive a reply. I was left with the impression that the shop is closed.
-
I never had antialasing or masking ticked. And when YAME was up and working before IT stopped working, I didn’t have a problem with my two touchscreens. They responded to touch as expected.
-
Roccio: Have you ever considered replicating Helios so that YAME is an all-in-one application. The reason I’m asking is because after Helios went south on me a few months back, I reached out to Gadroc’s Workshop for a fix and didn’t receive a reply. I was left with the impression that the shop is closed.
In the next version there will be much more functions to interact with YAME. I’m not going to replicate all the Helios functionalities (that would require a lot of time), but what I have now (in my development version) I can get a full working cockpit. This part need a lot of testing and I don’t have a touch screen …
-
Understood. YAME is awesome right now but, what you’re projecting for the next YAME version would be beyond fantastic. I’m a YAME fan and I wish I had the expertise to pitch in and lend a helping hand. When Helios crapped out on me, I was vexed. When YAME stopped working, I freaked the hell out. On behalf of myself and, I would hope everyone else in the BMS community running YAME, you’re the best. My deepest and sincere thanks for your continuing great work.
-
Due to personal time problems, we’re in shortage of some serious testing. Since Roccio doesn’t have a touchscreen, maybe you can pitch in as tester?
Do keep in mind, the current alpha version is again a very big change so the first things that actually need testing, is all the basic stuff already available in the current release, in all its aspects (client only, client+server, 3D hook, RTT, all gauges, all variations of gauges like mlu, electronic etc, with and without masking, with and without background color and background images, multiple windows on multiple monitors, key server, touchscreen etc etc). -
I’d be honored to give it a shot - as time permits. However, understand that I’d be learning as I go and would need guidance…
-
Roccio has generously aloud me to test the new version and that is what I have been running the last few days. To answer Roccio’s question, when I say it won’t work, I mean the program itself starts up and functions properly (all three versions). The problem happens when I try to run the extraction to my second monitor. I can drag and drop it when I have it bordered with no issue. When I try and input the coordinates and then run the extraction it hangs up and I have to go to task manager and kill it. When it’s hanging, it is only using maybe 34mb of memory and 18% processor utilization. So the issue isn’t like what was happening with masking turned on where it would run the CPU up to 80% utilization. The odd thing is, it will run the extraction with no problems on the main monitor at coordinates 0,0. Then if I stop and start the extraction around 4 times I can then go back to window tab and change the settings to x3840 y 0 and it will finally extract it on the second touch panel. IT MAKES NO SENSE! lol. I do not think that it’s YAME necessarily causing the issue because once it’s running it’s smooth as silk.
It’s like YAME has to tell Windows the monitor configuration if that makes sense. In other words, when I simply run the extraction to X3840 Y0 Windows doesn’t understand the total resolution of my monitor configuration and by running YAME at 0,0 several times Windows see the overall resolution and finally puts the extractions at X3840. Man, that’s convoluted! -
Wicked: I hear what your saying. When I laid out my monitors in Display Settings as ICE suggested I was having the same problems. However, when I laid them out in their physical placement configuration I was able to set the coordinates to get my YAME gauges to populate my second monitor just as I wanted them using the drag feature. I don’t know if the following pics will be helpful, but its what I did to get my layout setup and I’m not experiencing a start and stop extraction problem. A you coined it - its running as smooth as silk.
Display Settings.
YAME Settings.
Gauge Layout.
-
Madmax, I will try setting the display setting as my monitors physically are laid out. However, how would Windows or YAME know where the monitor is in the real world?? lol To my knowledge it only knows it’s plugged in. What arranging the monitors in settings does is define how your mouse will traverse from one monitor to another…… hmm… I’m going to try it. Now I have to figure out the coordinates for it… Actually, I think I can use yours as my touch screen is below my main monitor. Nice setup BTW!
-
So mates, if someone wish to help let me know via private message.