YAME64 suite
-
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
-
i had to alter screen dimensions as I added a 1080 monitor in place of a 760 - - plus I had my system zoomed in (it was not native) and that completely messed things up - live and Learn - If you read this make SURE your Windows system is not zoomed in - you can easily do this by right clicking and under display settings and move that slider –- that will “”#@%$# up YAME big Time - make sure it is at 100% - if you ever change that it changes all of your coordinates on your screens
-
Exactly my point –-- if you have two screens, [1] 1920x1080 (main screen) and [2] 1695x1050 (gauges) and you arrange them in this order - [1][2] - then your YAME screens will be at coordinates X = 1920 and Y = 0. If you change your [1] screen to, say, a 2560x1080, then you will have to change your YAME coordinates to X = 2560. If you change your [1] screen again to a different resolution, you’ll have to change your YAME X coordinates again. Not to mention that BMS will put your extractions and other things on your [2] screen out of whack when you’re in the 2D menu and you have set BMS to fullscreen.
On the other hand, if you arrange your screens in this order - [2][1] - then your YAME screens will be at coordinates X = -1695 and Y = 0. If you change your [1] screen to 2560x1080, your YAME coordinates will still be X = -1695. If you change your [1] screen again to a different resolution, your YAME coordinates will still be X = -1695. This is because your main screen [1] determines where coordinates 0, 0 are and each time you change the [1] screen resolution, you change everything to the right of that monitor…… but everything to the left of it will stay the same.
Hope that made sense
-
it makes total sense Ice ! what messed my system up was the zooming in that windows does. Once i got it all back to normal 100" zoom rate all is Good.
And i understand your coordinate explanation thanks…. thats what these forums are good for so people can read this and fix their issues…great post
-
Glad that made sense. Obviously, nothing wrong with putting your screens in whatever position you want; I was merely trying to make you aware that while it may seem counter-intuitive, putting the YAME screen on the LEFT side of your main screen may be less of a hassle
That zoom issue catches a lot of people out –- BTW, what’s the resolution on your new screen?
-
Guys. Beware !
The latest windows 10 update and nvidia drivers mess up
badly with yame64. The moment u start the client u notice a
constant high usage of the cpu up to 90% -
My last update for WIN 10 is 1709 NVIDIA 388.31, GLOBAL CPU usage is around 15% max
-
My last update for WIN 10 is 1709 NVIDIA 388.31, GLOBAL CPU usage is around 15% max
I have the same versions of all (except YAME, I’m testing the new version) and no problems for me.
-
As a temporary measure, I have rolled back Win10 from the Fall creation to the prior update and have rolled back my Nvidia driver from 388.13 to 385.69 and all is well with Yama–-back to 60+ FPS. So now I just have to watch out for some forced updates from MS and Nvidia. Not an easy task.
-
Interesting that it affects some but not all…
-
Hi,
I have the same problem, Win 10, and YAME useless since last update, the CPU usage is too high… Too bad
-
I have the same problem, Win 10, and YAME useless since last update, the CPU usage is too high… Too bad
Too bad for Windows indeed! Just roll back to Windows 1703 and get back to enjoying YAME. No sense in being a Windows beta tester
-
Just updated to v1.2 and have a couple questions.
1) Texture Overlay.
Previously, I had my MFDs extracted to the bottom left and right corners of my screen, slightly transparent. Is this no longer supported? I don’t see a Hook tab anymore, or a place to select Texture Overlay. Nevertheless, I tried copying the yame_d3d.cfg file to the /bin/64x folder, but I get no overlays.2) Browser gauge output
Is it possible to output things other than the ICP to a browser? For example, can I output both MFD’s to a browser? If so, how would I go about this?
If I can get the MFD’s extracted and opened on a browser in my kindle fire (would prefer an app, but it doesn’t look like this is supported atm), I may have found the cheapest MFD display solution ever (low end Kindle Fire units go for ~$20). -
Wanted to see if anyone is running a similar config and has had any issues.
Have 3 monitors running surround on GTX-970’s and a 4th running on integrated HD-4500.
Had no issues extracting to the 4th monitor before but when I fired up YAME this weekend there was no display.
Moved the YAME window back to the main displays and it worked fine. Tried to drag it back to the 4th monitor and it starts flickering in/out on that monitor and then just disappears.
Same thing happens when trying to Edit Gauges. There’s just no display.
Made sure drivers were up to date and created a 2nd window to test with, it does the same thing.
Can drag anything else but YAME to that monitor and it functions fine. Kinda stumped. -
Wanted to see if anyone is running a similar config and has had any issues.
Similar config, yes, issues, no.
See above for issues with drivers, might be the “latest drivers” causing issues, but just a guess.
-
Similar config, yes, issues, no.
See above for issues with drivers, might be the “latest drivers” causing issues, but just a guess.
Thanks Ice, been digging around and hopefully will figure something out. Nothing has changed on the driver front that I could tell, no issues with CPU % either.