YAME64 suite
-
Have you tried with only u5 without New baltic theater?
And please share The Yame logs after crash occured. -
Yesterday installed U5 and flew a 3ship MP flight for 1,5h in KTO without having issues with BMS or YAME, so possibly Baltic theater issue.
Cant really check anything without config and logs. -
I flew a MP flight of ~2hrs on Balkans using YAME on multiple screens (client only).
All was fine (from the BMS 4.33U5/YAME point of view, that is…. ).No reinstall of the Yame software.
-
Ok guys need your help. I had Yame64 working great for months. Not sure what happened but here is what changed Windows 10 updated and I also installed BMS U5. Now Yame64 is crashing every time I try to launch it. Not sure if it’s a result of U5 or the windows update. When I try to launch the UI open’s a white box then immediately crashes and I get the following message. So what do you guys think? hopefully someone has seen this and knows what I am missing here. I vaguely remember this happing before but I don recall how or what fixed it lol. It doesn’t generate a log I’ve checked multiple time and the log file is empty. Any and all help is greatly appreciated.
-
Ok guys need your help. I had Yame64 working great for months. Not sure what happened but here is what changed Windows 10 updated and I also installed BMS U5. Now Yame64 is crashing every time I try to launch it. Not sure if it’s a result of U5 or the windows update. When I try to launch the UI open’s a white box then immediately crashes and I get the following message. So what do you guys think? hopefully someone has seen this and knows what I am missing here. I vaguely remember this happing before but I don recall how or what fixed it lol. It doesn’t generate a log I’ve checked multiple time and the log file is empty. Any and all help is greatly appreciated.
go to yame installation folder then in conf folder you will find yame64.xml. try to rename it to something like yame64.old and restart program.
-
ok will try that thank you Roccio
-
go to yame installation folder then in conf folder you will find yame64.xml. try to rename it to something like yame64.old and restart program.
Update: So I tried what you suggested and it didn’t work. Nothing changed that I can see. Doing that just created a new yame64.xml file. It is still crashing doesn’t get any farther then the picture above. When I go into event viewer in Win 10 this is what it says so maybe this VCRUNTIME140.dll got corrupted some how? What do you think?
Here is what the Event viewer says:Faulting application name: YAME64.exe, version: 0.0.0.0, time stamp: 0x59afa99e
Faulting module name: VCRUNTIME140.dll, version: 14.13.26020.0, time stamp: 0x5a39fee3
Exception code: 0xc0000005
Fault offset: 0x000000000000ca27
Faulting process id: 0x2e78
Faulting application start time: 0x01d3c3338db496a6
Faulting application path: D:\YAME64\YAME64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 45be4c30-fcfe-4b0f-9975-816802ddd040
Faulting package full name:
Faulting package-relative application ID: -
Update: So I tried what you suggested and it didn’t work. Nothing changed that I can see. Doing that just created a new yame64.xml file. It is still crashing doesn’t get any farther then the picture above. When I go into event viewer in Win 10 this is what it says so maybe this VCRUNTIME140.dll got corrupted some how? What do you think?
Here is what the Event viewer says:Faulting application name: YAME64.exe, version: 0.0.0.0, time stamp: 0x59afa99e
Faulting module name: VCRUNTIME140.dll, version: 14.13.26020.0, time stamp: 0x5a39fee3
Exception code: 0xc0000005
Fault offset: 0x000000000000ca27
Faulting process id: 0x2e78
Faulting application start time: 0x01d3c3338db496a6
Faulting application path: D:\YAME64\YAME64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 45be4c30-fcfe-4b0f-9975-816802ddd040
Faulting package full name:
Faulting package-relative application ID:can you post your layout xml that you are using? you will find in layiut folder
-
Hey sorry for the lack thereof and late response I was out of town for a few days. I’ve taken out any custom xml file and was just trying to get it to start stock. So I believe it loads the default xml file right. I’ve uninstalled and wiped the registry and will try to reinstall and see if something changes.
-
Hi Roccio PM sent you. Thanks man
-
Hi Guys. I’ve got the same problem. Win 10 updated 2 days ago and now I’m getting the same window as you Sleeper. M. In fact this recent Win 10 update even corrupted my mouse pointer. I rolled back to a previous restore point which I hope - fixed the pointer (will see when I shut down and restart my system), but no joy with YAME. I lost Hellios a few months back with the a similar stop working window. Now YAME - Heaven FORBID. I can’t live without my YAME. I’m running a 4 monitor setup with along with a Samsung Galaxy Tab A for my moving map and a separate ICP replica. Please help Roccio. Happy Easter to all.
-
Hi Guys. I’ve got the same problem. Win 10 updated 2 days ago and now I’m getting the same window as you Sleeper. M. In fact this recent Win 10 update even corrupted my mouse pointer. I rolled back to a previous restore point which I hope - fixed the pointer (will see when I shut down and restart my system), but no joy with YAME. I lost Hellios a few months back with the a similar stop working window. Now YAME - Heaven FORBID. I can’t live without my YAME. I’m running a 4 monitor setup with along with a Samsung Galaxy Tab A for my moving map and a separate ICP replica. Please help Roccio. Happy Easter to all.
Ok I’ve been trying to figure this out and up until this morning same issue over and over. Well I’m not sure what happened but I was able to get YAME64 to load completely by having one of the default BMS Keyfiles loaded within BMS and not my personal edited keyfile. For some reason Yame is not liking the Key file I had been using for months. (Maybe it was to much formatting going on inside the key file or a conflicting DX assignment). Try opening BMS and then loading a default applying it then closing BMS then Launch YAME64 and see what happens.
-
Hi Sleeper,
Read my first post#1179 page 117 and the subsequent discussions with Ice and others. It looks like the WIN 10 update and or Nvidia updated drivers, are part of the problem. I had the same issue, default YAME profiles would run fine, but modified ones (like Ice’s) would slow down the computer to a halt. I reverted to older WIN10 and Nvidia drivers, and everything works beautifully.
Johan
-
Hi Sleeper,
Read my first post#1179 page 117 and the subsequent discussions with Ice and others. It looks like the WIN 10 update and or Nvidia updated drivers, are part of the problem. I had the same issue, default YAME profiles would run fine, but modified ones (like Ice’s) would slow down the computer to a halt. I reverted to older WIN10 and Nvidia drivers, and everything works beautifully.
Johan
Thanks, I think I subsequently figured out the issue on my end at least. So after messing arounnd with the Keyfile and discovering that something changed either with windows or because of U5 I decided to take out any formatting that was in the Keyfile. ICE uses a lot of formatting such as ############### to add description etc to his keyfiles and a lot of ============== to make it pretty and separate the different areas of the the callbacks. Well you know how if you replace a key with in the UI with one of your own and save the file it removes any of that formatting and makes it similar to a default key file. Well that solved the issues on my end it seems. Stay tuned in case something else pops up. Again not sure if it as U5 or the creators update that caused this. I actually used DDU uninstaller to Remove any older Nvidia drivers and re-installed the latest driver which is 391.35. So far everything is working on my end. Again stay tuned ya never what will happen with Win10 and their updates.
-
Hi Sleeper,
Read my first post#1179 page 117 and the subsequent discussions with Ice and others. It looks like the WIN 10 update and or Nvidia updated drivers, are part of the problem. I had the same issue, default YAME profiles would run fine, but modified ones (like Ice’s) would slow down the computer to a halt. I reverted to older WIN10 and Nvidia drivers, and everything works beautifully.
Johan
This problem should be solved just by turning off the antialias and mask options in CLIENT\WINDOW tab
-
Thanks, I think I subsequently figured out the issue on my end at least. So after messing arounnd with the Keyfile and discovering that something changed either with windows or because of U5 I decided to take out any formatting that was in the Keyfile. ICE uses a lot of formatting such as ############### to add description etc to his keyfiles and a lot of ============== to make it pretty and separate the different areas of the the callbacks. Well you know how if you replace a key with in the UI with one of your own and save the file it removes any of that formatting and makes it similar to a default key file. Well that solved the issues on my end it seems. Stay tuned in case something else pops up. Again not sure if it as U5 or the creators update that caused this. I actually used DDU uninstaller to Remove any older Nvidia drivers and re-installed the latest driver which is 391.35. So far everything is working on my end. Again stay tuned ya never what will happen with Win10 and their updates.
I really need to have a look at those keyfile…
Can you please send me one that will crash YAME? -
Well Gentlemen. I finally got frustrated trying to get YAME to work so I wiped out my entire Drive and I’m starting out again from scratch. Going to reload my original Falcon 4 disk and take it from there. Man I’ve got some work cut out for me. Thrustmaster devices Cougar and Warthog HOTAS, Rudders and MFDs), TrackIR, Voice Attack, Jet Seat and all the rest. My head is about to explode just thinking about all this crap. DCS will have to wait because I know that’s going to be a pain. But hopefully I’ll get YAME back and maybe HELIOS as well. However, the issue I know I’m going to face is that I’m still running WIN 10 Pro Ver 1703 OS Build 15063.966 and I don’t know if I’ll be able to roll it back to a pristine state. I know one think though, I’m disabling all updates from this point forward. Wish me luck.
-
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.
-
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.