YAME64 suite
-
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. -
@ -Ice:
Thank you for your testing. I have one question: do all the YAME windows you have setup have the antialias flag on or off? If are on, try your tests with it off. -
Running 6 screens with Helios ,rtt server-client for mfd and mfd extact for the gauges etc.
I can use YAME to do that.
But is it possible to toggle the centre pedestal-map on/off on top of it ?Like i do in helios with a static map ?
Map on top
-
No because de CP60 is suppose to replace the analog machmeter, altimeter, vvi, aoa, adi & hsi gauges in the real jet (see http://www.elbitsystems-us.com/sites/default/files/F-16%20Center%20Pedestal%20Display.pdf or http://www.elbitsystems-us.com/airborne-solutions/fixed-wing-systems/f-16/f-16-center-display-unit-cdu). You can’t toggle the map on of in there either, only switch between flight data (replacing analog center pedestal gauges) and moving map.
-
@ -Ice:
Thank you for your testing. I have one question: do all the YAME windows you have setup have the antialias flag on or off? If are on, try your tests with it off.I have both windows Antialias on, but even with it, I notice jaggies on the gauges. I’ll try with it off and see. Thanks!
As with mantaray’s suggestion, it would be nice to be able to toggle gauges on/off… for example, in my Helios profile, I can call up the left console or hide it with a push of a button. Would be cool if we could put the TRIM gauges there and show/hide it along with the left console. I also have the Data Card output from WDP on a hidden panel that I can show/hide with a push of a button. It would be so awesome if we could integrate the moving map so that it can be set up to show and cover a large part of the screen, but can be hidden for when it’s not needed.
-
You can add the CP60, or the kneeboard with a map image instead of a datacard for example, onto a separate window. Windows can be toggled on/of. Ref section 6.3 in the manual, most bottom field when editing a window lets you set the toggle key.
-
….nosebleed…
I wonder if “hidden” gauges will have a performance impact…
-
….nosebleed…
I wonder if “hidden” gauges will have a performance impact…
Probably, because they are still rendered or in memory or something (I’m not the developer here :D)
-
You can add the CP60, or the kneeboard with a map image instead of a datacard for example, onto a separate window. Windows can be toggled on/of. Ref section 6.3 in the manual, most bottom field when editing a window lets you set the toggle key.
Yep i just managed to toggle a window named Map in the centre of my screen
Thanks -
….nosebleed…
I wonder if “hidden” gauges will have a performance impact…
No impact for hidden gauges, just memory (as they are loaded).
-
@DEVs
I would like to show you a little issue I am having with YAME. As I stated in my earlier posts, on my rig YAME itself works and performs very well in general and, besides, gives me a performance boost for BMS.
As you can see on the videos, MFDs and HUD look quite smooth with the exception of the blue vertical radar scan limit lines and, to a lesser extent, on the radar cursor and radar scan coverage lines on the HSD.
The visual effect (not saying this is the isue) is like the lines were suffering from vertical sync tearing.
My config:
Server-Client PC configuration over wired LAN.
Client PC (the one displaying the MFDs)i3 (don´t remember the number)
GTX 580
Three monitors-
1x 1920x1200 (displays HUD and the gauges above the MFDs) - connected to GTX580 via Analog VGA- MAIN Display
1x 800x600 (LFMD+RWR) - Connected to to GTX580 via Analog VGA
1x 800x600 (RMFD+Eng. instr.) - Connected to the on-board VGA and using CPU graphic processor.Each monitor is displaying a different YAME window.
Default YAME refresh rate of 30Recorded with BANDICAM
Recorded with the cellphone
I made a check and moved the RDR MFD to the main monitor, but the tearing problem happens on all the screen with no noticeable difference.
What I have tried so FAR.
Enable the Vsync Adaptive as default nvidia 3D profile and also specifically for YAME.
Lower the server extraction refresh rate to 20.
Run all the instruments and MFDs on a single YAME window.Nothing worked so far.
As I said, the overall quality is awesome, but I know you guys are aiming for excellence….
Thank you