YAME64 suite
-
I have a problem with Yame64. Twenty four hours ago it worked, no problems at all, then tonight when I try to launch
Yame the GUI fails to load.Windows event viewer shows an applicastion error, with the following information;
Log Name: Application Source: Application Error Date: 16/11/2017 17:57:46 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: ROG Description: Faulting application name: YAME64.exe, version: 0.0.0.0, time stamp: 0x59afa99e Faulting module name: VCRUNTIME140.dll, version: 14.0.24210.0, time stamp: 0x575a4cd0 Exception code: 0xc0000005 Fault offset: 0x000000000000c260 Faulting process ID: 0x2e54 Faulting application start time: 0x01d35eeb42da1814 Faulting application path: C:\YAME64\YAME64.exe Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll Report ID: fd011b63-3b4b-48e2-bfc8-a20057a9afc4 Faulting package full name: Faulting package-relative application ID: Event Xml: <event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><system><provider name="Application Error"><eventid qualifiers="0">1000</eventid> <level>2</level> <task>100</task> <keywords>0x80000000000000</keywords> <timecreated systemtime="2017-11-16T14:57:46.500985700Z"><eventrecordid>17046</eventrecordid> <channel>Application</channel> <computer>ROG</computer></timecreated></provider></system> <eventdata><data>YAME64.exe</data> <data>0.0.0.0</data> <data>59afa99e</data> <data>VCRUNTIME140.dll</data> <data>14.0.24210.0</data> <data>575a4cd0</data> <data>c0000005</data> <data>000000000000c260</data> <data>2e54</data> <data>01d35eeb42da1814</data> <data>C:\YAME64\YAME64.exe</data> <data>C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll</data> <data>fd011b63-3b4b-48e2-bfc8-a20057a9afc4</data> <data></data> <data></data></eventdata></event>
There have been no software changes to the system, other than a re-install of YAME and both the x32 and x64 2015 Redistributables.
TIA
Steve
Have you updated your windows version?
Maybe it’s a problem with the runtime libraries (Faulting module name: VCRUNTIME140.dll, version: 14.0.24210.0, time stamp: 0x575a4cd0) -
Have you updated your windows version?
Maybe it’s a problem with the runtime libraries (Faulting module name: VCRUNTIME140.dll, version: 14.0.24210.0, time stamp: 0x575a4cd0)I’m currently running Win 10 Pro x64 1703 and there have not been any updates since yesterday when it last worked.
I will continue to dig.
-
Thanks for the report Raptor.
When beta testing I also had occasional all black extractions. Sometimes it helped just closing BMS and YAME, then start YAME again and reset 3Dhok or no 3D hook, and then start BMS. It seems the setting or deleting of the dll sometimes doesn’t get executed when BMS is still running.
Are you using mask option in any of the windows you use? That sometimes can cause issues too where the mask file hasn’t updated for some reason after you changed to location of certain gauges and then the moved gauge is behind a mask.Hey Focaldesign,
At first I’ll try to fix the Altimeter-problem.
I tried everything you told me to do. Unfortunately without success.
On another PC YAME runs as desired. So it’s on the PC, I think.My system:
AMD Phenom II x4 3.4 GHz
4 GB RAM
Win 7, 64 bit
1x ATI Radeon 5700 Series
1x NVIDIA GeForce 8800 GTIt is my “instrument-PC” with 3 monitors
Regards
MadDoc
-
Just want to report to avoid installing the new Nvidia 388.13 (disable automatic driver upgrade in W10)…YAME doesn’t like it at all, especially when loading Ice’s profile…
Johan
-
Just want to report to avoid installing the new Nvidia 388.13 (disable automatic driver upgrade in W10)…YAME doesn’t like it at all, especially when loading Ice’s profile…
Did you mean to say 388.31? +1 to that statement… just tried a flight tonight and my CPU usage went from around 4-12% to a constant 75%+ despite only having Helios, TARGET, and YAME on. Turning YAME off (Helios and TARGET still on) went back to 12% CPU usage.
-
I had a very bad slow down of my FPS with Yama when I updated to Windows 10 fall creation. So on the advice of ICE, I rolled back windows and all was fine until now. I seem to using Nvidia 388.13 and have the same slow down issue. A check with Nvidia driver support indicates a number of older drivers available: 388.00, 387.92, 385.69, 385.41. Does anyone have a suggestion on which one of the older drivers I should use to get by FPS back up to 60 and how do you rollback to an older driver IF THE ROLLBACK DRIVER TAB IN THE DEVICE MANAGER IS GREYED OUT?
PS The auto update feature for Nvidia was not checked on my system so why did it update?
-
I’ve not updated my nVidia drivers for a while and the Win10 FCU fiasco seems to have borked something so I decided to update my nVidia driver but haven’t flown since a few nights ago… the latest version as of today is 388.31 and that’s a no go. Tried older versions 388.13 and 388.00 and the issue persists. Unfortunately, I can’t remember what drivers I had prior so I can’t just go directly back to those. Can anyone chime in what version they’re using at the moment?
I’ll try older drivers but I don’t really want to be installing each and every one… sigh… it’s gonna be a long night…
damn upgrades. What’s going on with Win10 and nVidia???
@ sobe: get older drivers HERE
-
That’s what I have installed back and it works fine:
NVIDIA GeForce GTX 1080 Graphics Driver version 22.21.13.8205.
Johan
-
juyttewall
Which one of the drivers below is Driver version 22.21.13.8205? The first number below is the driver version number and the second number is the date of release so 30.10.2017 means that driver version 388.13 was released on Oct. 30, 2017.GeForce Game Ready Driver WHQL 388.13 30.10.2017
GeForce Game Ready Driver WHQL 388.00 23.10.2017
GeForce Game Ready Driver WHQL 387.92 9.10.2017
GeForce Game Ready Driver WHQL 385.69 21.9.2017
GeForce Game Ready Driver WHQL 385.41 24.8.2017
GeForce Game Ready Driver WHQL 385.28 14.8.2017
GeForce 385.12 Driver BETA 385.12 31.7.2017
GeForce Game Ready Driver WHQL 384.94 24.7.2017
GeForce Game Ready Driver WHQL 384.76 29.6.2017
GeForce Game Ready Driver WHQL 382.53 9.6.2017
GeForce Game Ready Driver WHQL 382.33 22.5.2017 -
Hi Sobe,
Mine was released on May 10, 2017, so it’s prior to all the ones you are showing. It’s not easy to find the equivalence between the 2 numbering systems.
-
Version 385.69 seems to be fine…. my CPU does not get pegged at 75% or so and I’m usually at 30-40% with just Helios, TARGET, and YAME running.
-
juttewaal
It would appear that you are using 382.05 that were released on May 4, 2017. The next release was on May 22, 2017. If you can, go to the add/remove tab in the control panel and look for the version number of the nvidia graphics driver. Mine says 388.13. -
To find your driver version number:
Right click on desktop, select NVIDIA Control Panel
On the bottom-left, click System Information
On the window that pops up, it’ll show you your driver version -
Sorry for the confusion, but my Control Panel tells me that I have the NVIDIA GeForce Experience 3.9.0.61 and it was installed on 9/8/2017.
It seems to correspond to the 385.41 WHQL which is not too far from the one Ice is mentioning above (385.69). Either one should work fine.Johan
-
ICE
to go backwards on the driver, should I uninstall what I have now and then reinstall 385.69 rather than install it over 388.13? -
I have been using YAME foR quite some time now and IT IS AMAZING–-- NO Problems ever… I just had a 27 inch TV (MaiN SCREEN) blow out on me and put a 39 inch LG in place of it — the transition WAS FLAWLESS… YOU JUST NEED TO KNOW CARTESIAN COORDINATES (AND YOU SAID MATH WAS NOT IMPORTANT)
i USE 2 SCREENS AND HAD IT SET UP IN 10 MINUTES… THANX AGAIN ROCCIIO for this amazing utility…
the first pic attachment was with track ir on it was no lined up and was never meant to be ---- wow
-
Sorry for the confusion, but my Control Panel tells me that I have the NVIDIA GeForce Experience 3.9.0.61 and it was installed on 9/8/2017.
It seems to correspond to the 385.41 WHQL which is not too far from the one Ice is mentioning above (385.69). Either one should work fine.My guess is that the GeForce Experience is one version, the actual GPU drivers is another version.
to go backwards on the driver, should I uninstall what I have now and then reinstall 385.69 rather than install it over 388.13?
I just downloaded the driver version from the website and installed it.
I have been using YAME foR quite some time now and IT IS AMAZING–-- NO Problems ever… I just had a 27 inch TV (MaiN SCREEN) blow out on me and put a 39 inch LG in place of it — the transition WAS FLAWLESS… YOU JUST NEED TO KNOW CARTESIAN COORDINATES (AND YOU SAID MATH WAS NOT IMPORTANT)
i USE 2 SCREENS AND HAD IT SET UP IN 10 MINUTES… THANX AGAIN ROCCIIO for this amazing utility…
There seems to be an issue with your attachment…. also, transitioning from one main screen to another should not be an issue at all. Provided you have your YAME screen to the LEFT side of your main screen in Windows Display Settings (no matter where the screen is physically), then you can go from a 1280x786 screen to a 1920x1080 screen to a 3440x1440 to a 4096x2160 without editing a thing on your YAME profile
-
i have no idea what you are talking about ice - i have no issues at all never have cheers
going to go play some electric guitars …… -
You just mentioned coordinates and I assumed you had to adjust these when transitioning from your 27" to 39" monitor? My point was that if you had your YAME screen to the LEFT side of your main display screen as set up in Windows Display Settings, there would be no need to adjust these coordinates. See my pic above… my main screen is #1, but my YAME screens are #2 and #3 and they are to the LEFT side of my main screen, even though they are physically below the main screen in reality.
I didn’t mean to say you were having issues, just making a suggestion
BTW, awesome setup there! How did you attach those Cougar MFDs? Did you stick them directly on the monitor?
-
I attached the MFDS with velcro stickers… same with the UFC control pad in the middle…
The screen had now changed sizes so everything has changed and all is good-
The bottom screen (which is actually the right screen #2) has a start coordinate of X1620 and y62 with a size for the pallet of 1695X1050 for the gauges screen
and your setup looks pretty awesome i must say - one day i might have a 3 screen setup - that looks very nice and it should with all the effort put into it — nice