YAME64 suite
-
This is a weird issue and I think I’ve come across this in testing. What roccio suggested was to change port; we were Skyping at that time and he suspected Skype might be interfering with the program. Sure enough, I changed the ports and it worked!
Thanks Ice. I’ll try that too.
-
Thanks Roccio. The yame_d3d.cfg port displays 53100. That is the hook port I set (by default). Which config files should I send? Should I send via PM or post here?
You can send me your YAME64.xml and the layout you use in pm is better.
-
After about two weeks of use one fact and two request…
Fact: MFDE is uninstalled for BMS 4.33 (still using 5.7 for 4.32)
YAME 64 proves to be stable, consistent and as elementary as the HOTAS when flying.
The moving map…no words!Request 1: PFD display when it’s clear.
I guess it’s not active unless a fault happens and therefore it shows black with no textures or color.
Can you impose the PFD green screen and bezel on top of it?
Request 2: Map window…is it possible for it to remember its last state when re opening (eg for example map view aircraft heading)?Hope you managed to find the fix for the VVI and AOA gauges.
Well Done and thank you !!!
-
Thx for the kind words polaris!
Ded/pfd bezels are already includes for newt release.
Remembered moving map options I will add to the feature request list.
VVi/aoa we’ve included extra Logic so it will use smaller texture when gauge size is small, hope that will fix it.
Stay tuned -
Beautyful! Thank you Roccio and Focaldesign
-
Dear Roccio and Focaldesign,
thanks a lot for sharing your nice utility, my good friend BlackGio pointed me out about how it’s useful.
I’m still mastering how to use it, but if all things will go out as in your premises… and your manual is clear and full detailed to, I’m glad to add.With best compliments and regards,
-
After days of testing, I’ve finally had the time to compile and look at the results and I’m quite pleased at how everything turned out. Check out my FPS testing thread to read more.
Bottom line: MFDE seems to be the one with the least fps loss, but the issues I’m having with it (gauges moving to the wrong screen sometimes, a pain to setup gauges, DED display is wrong/different) makes it less attractive. YAME loses a few more fps, nothing significant especially when compared to the built-in Cockpit Display Extractor, but with the correct DED extraction and being able to be pixel-accurate in terms of gauge size and location, it becomes a clear winner in my book!
Once again, thanks to roccio and Focaldesign for working on this great mod and for even taking community requests!
-
After days of testing, I’ve finally had the time to compile and look at the results and I’m quite pleased at how everything turned out. Check out my FPS testing thread to read more.
Bottom line: MFDE seems to be the one with the least fps loss, but the issues I’m having with it (gauges moving to the wrong screen sometimes, a pain to setup gauges, DED display is wrong/different) makes it less attractive. YAME loses a few more fps, nothing significant especially when compared to the built-in Cockpit Display Extractor, but with the correct DED extraction and being able to be pixel-accurate in terms of gauge size and location, it becomes a clear winner in my book!
Once again, thanks to roccio and Focaldesign for working on this great mod and for even taking community requests!
Thank you Ice for the more controlled testing. I’m sorry to see the FPS increase on your end compared to BMS or MFDE seems to be very little to none. OK for you I’ll place a link to this post in the YAME manual for the next release?
In that post you also note the following:
YAME’s gauges doesn’t really look out of place, but I hope there’s an option to tweak the look later on (I think there is, but I’ll need to learn how to do this). I also like the ability to specify gauge sizes to-the-pixel, adjust gauge position to-the-pixel, and the ability to save gauge layout in YAME. I look forward to roccio implementing feature requests into YAME so in the end, that may be the better program to work with.
What do you want to tweak? All images can be found in the /gauges/ folder so you can edit them at will. All images, except the ATD & CP60 are either taken from TomCatz high res cockpit pictures or are real pictures, but you can tweak them at your liking of course.
Adjust gauge sizes to the pixel is already possible via 2 ways: by entering exact width & height in the UI, or by using the mouse scroll wheel in the window edit gauges mode when the mouse is hovering over the gauge you wish to resize.
Adjust gauge position to the pixel is currently present in the UI by enter the exact x/y position, and in the next release it will also be possible to move a gauge in the window edit gauges mode by use of the arrow keys.
What do you mean with save gauge layout? In the Client/Misc tab of the UI you can save the layout as a new xml. The XML’s are saved in the /layouts/ folder. -
Thank you Ice for the more controlled testing. I’m sorry to see the FPS increase on your end compared to BMS or MFDE seems to be very little to none. OK for you I’ll place a link to this post in the YAME manual for the next release?
I hope you can now see why I was a bit nitpicky when I asked about your testing methods?
As for placing a link in the next YAME manual, it would be my pleasure to be featured in your documentation!As for “very little to none,” remember that I am running 5760x1080 resolution for my main display plus two more 1920x1080 screens for gauges and Helios. I would think that a 1fps gain on my setup would be 3-5fps gain for someone running on a single 1920x1080 display plus a single 1920x1080 screen for gauges, simply because their setup is pushing less pixels overall. Also remember that this test was done in very bad weather conditions with both Maverick and TGP pictures rendered on-screen and on my secondary monitor. A 1fps gain under these conditions could well be a 3-5fps gain in different weather conditions even with the same monitor/hardware setup.
What did surprise me was that MFDE performed better than YAME…. again, you may say “but it’s only 1-2fps difference” but I make the same argument as above. I would’ve expected them to have the same performance impact or even YAME to be better so it’s curious as to why there is a difference.
What do you want to tweak? All images can be found in the /gauges/ folder so you can edit them at will. All images, except the ATD & CP60 are either taken from TomCatz high res cockpit pictures or are real pictures, but you can tweak them at your liking of course.
That is exactly what I am talking about. Is it really just a copy-paste replacement of images? Basically, I wonder if I can get the “MFDE look” using YAME. I presume “yes,” but I also presume it’s not easy as I’m hoping it is.
Adjust gauge sizes to the pixel is already possible via 2 ways: by entering exact width & height in the UI, or by using the mouse scroll wheel in the window edit gauges mode when the mouse is hovering over the gauge you wish to resize.
Adjust gauge position to the pixel is currently present in the UI by enter the exact x/y position, and in the next release it will also be possible to move a gauge in the window edit gauges mode by use of the arrow keys.
What do you mean with save gauge layout? In the Client/Misc tab of the UI you can save the layout as a new xml. The XML’s are saved in the /layouts/ folder.As I said, I love the ability to specify gauge size to-the-pixel and I have Fullscreen, Visible, Masked, and Antialiasing ticked for each windows. Making any change to any gauge means that YAME will re-calculate the masking bits the first time it is run with the new changes and for the main screen, it takes quite a while. Obviously, fine-tuning will mean a bit of time is spent waiting, but as this is only really done during the setup phase of the “Falcon dance,” I’m not too bothered about it. I tend to guesstimate size and location initially using some of my pre-made guides, but I still spend a bit of time fine-tuning.
As for adjusting gauge position by using the arrow keys, you will remember that this is my suggestion in the first place! Can’t wait for that to be implemented, but like I said, it’s only really on the setup phase so I understand if it’s not a priority especially as there is the workaround I mentioned above.
With regards to saving the gauge layout, again, that is exactly what I meant! I love the ability to save my layout and copy it somewhere else for safekeeping! MFDE has the annoying quirk of moving the entire gauge layout to my main screen, which means I’ll have to drag each gauge to their old position and deal with an aching wrist and palm after a while. If that were to happen in YAME, I’d just need to specify the adjusted coordinates for the windows, and BOOM!! Done, sorted, and all the gauges are back in alignment!
Like I said above, bottom line is that although MFDE performs better, YAME’s performance is not far behind and with features that are lacking in MFDE, and ongoing development and active involvement from roccio and yourself, YAME becomes a clear winner in my scenario.
-
Thx, I know you were doing such elaborate FPS tests in the past, so I knew what you were asking of me in regards of information, which I couldn’t give you. Glad you have taken your time in trying it yourself.
Als glad to see it did have a positive impact to make windows for each physical screen.Didn’t occur to me that indeed a couple of frames on your setup could result in more gain on lesser intense setups.
The link has been incorporated into the manual with some other new stuff.
Indeed, the mask calculation takes a while. And as you say, it’s kinda a one time deal and only a time consuming issue when you are fine tuning the size/alignment.
It makes Roccio and myself happy to see the positive comments.
Stay tuned in the near future for a small update. Manual has been updated to reflect new included features. All tests are done and only 1 known new bug remaining at the moment… -
That is exactly what I am talking about. Is it really just a copy-paste replacement of images? Basically, I wonder if I can get the “MFDE look” using YAME. I presume “yes,” but I also presume it’s not easy as I’m hoping it is.
Yes it is, only thing you need to take into account is that the image you use as replacement needs the exact same dimensions (not just the ratio, there’s no scaling in that part) and textures with parts like needles etc need to have the new versions in the exact same place.
As for adjusting gauge position by using the arrow keys, you will remember that this is my suggestion in the first place! Can’t wait for that to be implemented, but like I said, it’s only really on the setup phase so I understand if it’s not a priority especially as there is the workaround I mentioned above.
Jup, I always place a link to the original request topic in our bug/feature tracker so I was aware
It’s implemented and in the next release. -
Thx, I know you were doing such elaborate FPS tests in the past, so I knew what you were asking of me in regards of information, which I couldn’t give you. Glad you have taken your time in trying it yourself.
Hehehe… like I said, I didn’t know what info you did or did not have so I had to ask. I was always going to try anyway… heck, I was in the middle of “trying” that’s why I noticed the difference.
Als glad to see it did have a positive impact to make windows for each physical screen.
See??!??!? That’s why I ask!! I would not have thought to make this change by myself! So if you could think of any other variables I could test in YAME, feel free to point them out!
My next experiment is to have gauges overlap in each window, see if that affects results at all. In my YAME profile, my speedbrake image overlapped my Landing Gear image….
Indeed, the mask calculation takes a while. And as you say, it’s kinda a one time deal and only a time consuming issue when you are fine tuning the size/alignment.
Well, it’s quite a few “one-time-deal-only” instances as a user fine-tunes… but as I said, I just consider it part of the “dance.” I would presume that once I got that sorted and should I wish to distribute my Helios profile, I can simply include my YAME layout file and that would take a big chunk out of the “dance” for the end-user. DING!! Another point for YAME!
It makes Roccio and myself happy to see the positive comments.
How could one put a negative comment in??!!? Unless the reader mis-reads? Hehehehe…
Like I said before, awesome work and I owe both of you a few beers!All tests are done and only 1 known new bug remaining at the moment…
Looking forward to the next version! Please tell me you’ve implemented the “YAME window remembers it’s location”…. for some reason, when I start up YAME, it’s on my main screen. As I play BMS and the resolution goes out of whack due to the smaller 2D menu screen, the YAME window now migrates to one of my touchscreens. In comparison, my Helios control panel stays in the same place all the time.
Also, someone mentioned (can’t locate post now) a bug with the HYD gauges. Both A and B show up in the CLIENT -> WINDOWS -> EDIT GAUGES screen but when the client is started, only A shows up as a gauge, B shows us as a gray circle.
Yes it is, only thing you need to take into account is that the image you use as replacement needs the exact same dimensions (not just the ratio, there’s no scaling in that part) and textures with parts like needles etc need to have the new versions in the exact same place.
I read the words but my brain does not absorb. I’ll have to try this to find out.
It’s implemented and in the next release.
Whoohoo!!
-
Please tell me you’ve implemented the “YAME window remembers it’s location”…. for some reason, when I start up YAME, it’s on my main screen. As I play BMS and the resolution goes out of whack due to the smaller 2D menu screen, the YAME window now migrates to one of my touchscreens. In comparison, my Helios control panel stays in the same place all the time.
Also, someone mentioned (can’t locate post now) a bug with the HYD gauges. Both A and B show up in the CLIENT -> WINDOWS -> EDIT GAUGES screen but when the client is started, only A shows up as a gauge, B shows us as a gray circle.
all implemented/fixed
-
Awesomesauce!!
Now if we could just add to the RUN window:
Do the laundry
Wash the dishes
Walk the dog
Buy flowers for the wife
Get beer/coffee/tea/water
Get piddle packWe’d be all set!
-
love is in the air….
[emoji2] [emoji2] [emoji2] [emoji2]Sorry, I couldn’t resist it…
-
Awesomesauce!!
Now if we could just add to the RUN window:
Do the laundry
Wash the dishes
Walk the dog
Buy flowers for the wife
Get beer/coffee/tea/water
Get piddle packWe’d be all set!
Done
-
So…I guess that with that last wish granted we shall have the next version shortly?
Sorry…can’t wait lol. -
So…I guess that with that last wish granted we shall have the next version shortly?
Sorry…can’t wait lol.2 bugs currently open for next release.
Manual & changelog done. -
Mind telling us which bugs are pending?
-
Mind telling us which bugs are pending?
One specific gauge is causing the UI to crash when disabling it and trying to save.
Other one is trivial.