YAME64 suite
-
is it possible to change the map ?
I tried to use a map with airfield and strips 2048*2048 no joySure, you can. The maps are in gauges/cp60/maps
If you want to use a new korea map (for example) just replace the korea.png with the one you have made. It must be a 32 bit png. If you still have problems try send me the image, I will convert to a working one.
-
Tested overlapping gauges and got some rather interesting results. First off, here’s my overlapped YAME gauges:
So that’s all gauges overlapping at least one other gauge. I have the TRIM, DED, RWR, and CPD stuff even going OUTSIDE the screen borders to test that as well. I got an average of 48.42fps when combined with my Helios profile. Does this mean that overlapped gauges are better? I don’t think so. I think what’s happening is because the PC doesn’t have to “draw” parts of the gauges that are covered by other gauges or covered by my Helios profile, it saves some workload resulting in better framerates. I think this is also why my previous testing had an average of 48.11fps vs. a lower 47.xxfps in today’s tests…. I had the TRIM gauges covered by my Helios profile before whereas now I’ve fixed it so that they’re seen in the Helios profile.
I then tested again, same YAME profile as above (note: AA off), but without Helios this time… average of 48.36233fps. Not sure exactly what’s going on there as Helios was no longer a factor, but 0.05767fps difference… meh. So, 47.2185fps on a “correct” Helios + YAME setup, AA on, 47.528fps on the same but with AA off, 48.42fps on Helios + overlapping YAME gauges, and 48.36233fps on overlapping YAME gauges only. Not really much difference between AA on/off and overlapping gauges doesn’t affect performance negatively, it seems!
Just decided to test this for fun as I don’t think people will intentionally overlap gauges to save FPS. I just wanted to know if overlapping had any effect, if any.
-
From your website…
“possible fix for tearing in networked setup”
I reported this, but I’m just curious about whether some other people have reported it as well and/or you have encountered it on your internal tests.
It would mean it’s not only a problem on my end (which is good for me but bad for the community)
Thanks
-
From your website…
“possible fix for tearing in networked setup”
I reported this, but I’m just curious about whether some other people have reported it as well and/or you have encountered it on your internal tests.
It would mean it’s not only a problem on my end (which is good for me but bad for the community)
Thanks
Do you use hook extraction or default BMS texture extraction?
-
Do you use hook extraction or default BMS texture extraction?
Hook. In the end I didn’t check with RTT as I said I would do. I’ll try to do it tonight and report back if the problem persists with RTT extraction
-
Sure, you can. The maps are in gauges/cp60/maps
If you want to use a new korea map (for example) just replace the korea.png with the one you have made. It must be a 32 bit png. If you still have problems try send me the image, I will convert to a working one.
Thanks Roccio the 32 bit did it.
-
From your website…
“possible fix for tearing in networked setup”
I reported this, but I’m just curious about whether some other people have reported it as well and/or you have encountered it on your internal tests.
It would mean it’s not only a problem on my end (which is good for me but bad for the community)
Thanks
Keep in mind, that’s the roadmap valid starting from the next release. Viewed from the initial release there’s a lot more of course
-
My client screen freezes whenever I use edit gauges or windows being dragged over top of each other. The ghost window sticks to the main window and prevents further use. I have to shut down program via task manager. And it is using 40% cpu while the window sits there. The client just keeps freezing on me whenever I move stuff to other monitors. Its a real mess on my client computer.
Also, is it possible to have all the gauges show before BMS starts. I don’t want to wait until I am in the seat to see there is a problem with placing and such.
Client computer: [email protected] Ghz 8gb ram GTX 580 3gb
-
Also, is it possible to have all the gauges show before BMS starts. I don’t want to wait until I am in the seat to see there is a problem with placing and such.
It sure is!! Go to CLIENT > WINDOWS, select the window you want to show, click EDIT, then make sure VISIBLE is checked. You can also click on EDIT GAUGES to see and fine-tune your gauges.
-
It sure is!! Go to CLIENT > WINDOWS, select the window you want to show, click EDIT, then make sure VISIBLE is checked. You can also click on EDIT GAUGES to see and fine-tune your gauges.
Yes I have done that, but each window needs to be done separately…no? Is it possible to have all the gauges from all the separate windows all show in place before entering BMS, like MFDE does? I have 7 different monitors and 7+ windows and I don’t want to check each one individually before I fly.
-
Each window will have to have VISIBLE ticked, yes. Then when you run YAME, it will show all of those windows (and the contents therein)…
For example, I have two windows, one for each of my touchscreens. Both have VISIBLE ticked.
-
Ahh, good. Now if I can just get it to stop freezing when I move gauges.
-
roccio, small issue I encountered this evening with YAME. I currently have my profile saved, under “version 6” and I have “version 5” before that. When making my “overlap test,” I saved a “overlap version” profile.
Now whenever I load “version 6,” I still get the “overlap profile” layout. I need to load up “version 5” to return to my normal-sized screens. I save that layout under “version 5” and “version 6” and clicking YES when it asks me if I want to overwrite, but when I run it, it’ll show the “overlap profile” layout. I’ve even loaded up “version 5” and overwrote it on “version 6” and “overlap profile” but if I load up those two profiles, it’ll still show the “overlap profile,” not the “version 5” profile.
-
Yes, when the windows are set to visible, they should show up, with the gauges, from the moment you hit the “start client” button on the first ‘run’ tab.
Ahh, good. Now if I can just get it to stop freezing when I move gauges.
Strange, cannot replicate this issue. Not the freezing and not the high CPU usage…
-
roccio, small issue I encountered this evening with YAME. I currently have my profile saved, under “version 6” and I have “version 5” before that. When making my “overlap test,” I saved a “overlap version” profile.
Now whenever I load “version 6,” I still get the “overlap profile” layout. I need to load up “version 5” to return to my normal-sized screens. I save that layout under “version 5” and “version 6” and clicking YES when it asks me if I want to overwrite, but when I run it, it’ll show the “overlap profile” layout. I’ve even loaded up “version 5” and overwrote it on “version 6” and “overlap profile” but if I load up those two profiles, it’ll still show the “overlap profile,” not the “version 5” profile.
Known issue. When you change stuff in the tabs, and hit apply, it gets automatically written to the currently active layout file. So say you load v5, change settings in the gauges, it will get saved into the v5 file. If you then do save and save as v6, you have v5 and v6 as identical layout files.
It’s a task I have in the backlog for a while now, but it’s low priority. For now, the save layout button acts more like a “make a copy of my current layout file and save it under a new name” -
Yes, when the windows are set to visible, they should show up, with the gauges, from the moment you hit the “start client” button on the first ‘run’ tab.
Strange, cannot replicate this issue. Not the freezing and not the high CPU usage…
When I press run I get all blank screens until entering pit. They only show up with edit gauges and then the YAME window freezes every time I press edit button. I’ve tried reinstalling YAME, no change.
-
When I press run I get all blank screens until entering pit. They only show up with edit gauges and then the YAME window freezes every time I press edit button. I’ve tried reinstalling YAME, no change.
that’s very strange. First report of that kind so far. Have you tried uninstalling first, ànd deleting eventual files/folders left over after uninstall before reinstalling to make sure you are not using compromised config or layout files from the previous version or something?
-
That’s not what I’m doing at all.
I have v5 all set up.
I go to the CLIENT > MISC page, click SAVE LAYOUT, and select v6.
It asks me if I want to overwrite, I say yes. I also click APPLY.
For lolz, I click SAVE LAYOUT again, and select “overlap version”.
It asks me again if I want to overwrite, I say yes. I also click APPLY.
I go to the RUN page and start YAME client.It shows me the overlap version layout.
I stop the profile, go to CLIENT > MISC page again, click LOAD LAYOUT, and select v6. I click APPLY.
I go to the RUN page and start YAME client.Same deal, it shows me the overlap version layout.
I stop the profile, go to CLIENT > MISC page, click LOAD LAYOUT, and select v5. I click APPLY.
I go tot he RUN page and start YAME client.It shows me v5 layout.
Note that I don’t change any settings or anything at all, I’m just overwriting v5 into v6 and “overlap version” but this doesn’t seem to be the case.
Interestingly, I seem to have stumbled upon the solution. I noticed that when loading v6, it gives me a wonky picture of the gauges. I started up the sim and noticed that the gauges worked but the picture was not right. The issue was that under v6, it saves the gauges similar to v5, but it had the masking properties of “overlap version.” I had to nudge one gauge on RIGHT WINDOW and one gauge on LEFT WINDOW to force YAME to re-calculate masking values for both windows, then save the profile.
I love how YAME is mimicing the program it was designed to help out…. there’s the Falcon dance, now there’s also a YAME dance…
-
Uninstalling via Control Panel throws an error that it is already uninstalled. Which it is not.
YAME uninstall works though. -
Icarus, check PM.