YAME64 suite
-
@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
-
Hooray!!
Now please tell us when you guys plan to release the next version…. each time I see a “new post” marker on this thread, my mind goes “IT’S HERE!!!” which is obviously not the case.
I am not a patient man
-
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.
What is the specs of the slave/client PC?
Does this tearing happen using MFDE or CDE?I suspect a low-framerate issue, hence the tearing. Have you tried INCREASING the framerates instead of decreasing it?
-
What is the specs of the slave/client PC?
Does this tearing happen using MFDE or CDE?I suspect a low-framerate issue, hence the tearing. Have you tried INCREASING the framerates instead of decreasing it?
No I did not try to increase it. i thought the maximum refresh rate for extraction was locked to 30
But a GTX580 should be enough, I think….
-
A GTX 580 powering three monitors? Not really sure of the load imposed by YAME or how compatible it is going over a VGA connection. But like I said, have you tried using MFDE or the built-in CDE? If MFDE/CDE works with no tearing, then the issue is YAME. If there is tearing on those extraction methods, then might be a hardware issue. Just my 2 cents.
-
A GTX 580 powering three monitors? Not really sure of the load imposed by YAME or how compatible it is going over a VGA connection. But like I said, have you tried using MFDE or the built-in CDE? If MFDE/CDE works with no tearing, then the issue is YAME. If there is tearing on those extraction methods, then might be a hardware issue. Just my 2 cents.
The GTX580 is connected to just two monitors. The second smaller monitor is connected to the onboard VGA and using the CPU integrated graphics.
But these are 2d grahics, right? A GTX 580 should be more than enough to get to 30 FPS.
Anyway I pumped up refresh rate to 60 and check with fraps the FPS on the YAME windows which is steady 60 with minor hick-ups on the upper 50s. So I thinks low framerate is not the problem.
At least not low display FPS on the client screens. I don’t know if the server computer is really extracting those 60FPS that the client is showing.
Some other comment. On my system, there is no noticeable FPS impact difference between extracting at 30FPS and 60FPS.
And visually,which is what counts to me, both extractions look equally smooth, with the exception of the tearing. (no numbers to support this assertion)
-
The tearing is quite strange, as it seems a vsync problem, but vsync is enabled for all windows. Try to lower texture extraction FPS in both server and client.
-
The tearing is quite strange, as it seems a vsync problem, but vsync is enabled for all windows. Try to lower texture extraction FPS in both server and client.
Tried already 20, 30 and 60. Tearing present with all refresh rates…
Funny thing is that it happens mainly on those vertical lines.
When I turn hard and the hsd is turning fast, it looks very smooth.
And so does the HUD.
-
Tried already 20, 30 and 60. Tearing present with all refresh rates…
Funny thing is that it happens mainly on those vertical lines.
When I turn hard and the hsd is turning fast, it looks very smooth.
And so does the HUD.
Ok, thank you. We will keep an eye on this and hope to fix soon.
-
Ok, thank you. We will keep an eye on this and hope to fix soon.
Thanks.
I am using right now hook extraction. I will check the RTT extraction and let you know. Also will try again with GPT.
GPT looks not so smooth overall, bit I can’t remember if I had this tearing on the radar screen too.
Maybe it’s just a problem on my end.
I’ll report back.
PS I will also try local extraction
-
-
Hooray!!
Now please tell us when you guys plan to release the next version…. each time I see a “new post” marker on this thread, my mind goes “IT’S HERE!!!” which is obviously not the case.
I am not a patient man
-
:D:D:D:D
-
I’ve been testing this out with my new MFD setup and it works great! A couple issues I’ve seen:
1. The UI is quite laggy (a second or so lag time when switching tabs, clicking buttons).
2. Some width/height settings for gauges are reset to defaults when going to the tab with that setting. In my case, the threat warning lights (right of the RWR, triangular light panel), I believe the default is 733x755 or something. I change this to 244x251 ish to work in my setup, to fit on my 800x480 monitor, next to the RWR exported by BMS. Whenever I go to the YAME64 tab with the threat warning lights panel, it resets back to the defaults of 733x755 which is quite annoying when tweaking other instruments on the same tab. I have to remember to always reset the sizes of this gauge back to what I want.Otherwise great software and I’m looking forward to updates!
-
I’ve been testing this out with my new MFD setup and it works great! A couple issues I’ve seen:
1. The UI is quite laggy (a second or so lag time when switching tabs, clicking buttons).
2. Some width/height settings for gauges are reset to defaults when going to the tab with that setting. In my case, the threat warning lights (right of the RWR, triangular light panel), I believe the default is 733x755 or something. I change this to 244x251 ish to work in my setup, to fit on my 800x480 monitor, next to the RWR exported by BMS. Whenever I go to the YAME64 tab with the threat warning lights panel, it resets back to the defaults of 733x755 which is quite annoying when tweaking other instruments on the same tab. I have to remember to always reset the sizes of this gauge back to what I want.Otherwise great software and I’m looking forward to updates!
1. Will note, but no similar reports so far. Bizar.
2. Same. Have you hit the apply button after changing the size before going to another tab? Otherwise it won’t be saved. Does it behave the same when you change the size via the “edit gauge” preview window (under tab client/windows)? -
If I learned anything useful for YAME, it’s that you should click that APPLY button… twice. And then twice more for good measure. Then you can switch tabs.
-
Hello,
Is there a possibility to change lettertype of the DED.
I prefer to have less bold letters.Thanks
-
Hello,
Is there a possibility to change lettertype of the DED.
I prefer to have less bold letters.Thanks
No,
It’s not a font we use, it’s a texture straight from BMS and 99% as in the real F-16. -
Sorry, where is YAME32 link to download?
Thank you
-