YAME64 suite
-
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
-
-
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)?A FRAPs capture of the window shows around 10fps.
Yes, this is on returning to the tab. The sizes have been reset to defaults after returning to the tab with the threat warning lights.
-
Also I just discovered the keyboard shortcuts for resizing. Brilliant!
-
Ok Thx
-
A FRAPs capture of the window shows around 10fps.
Yes, this is on returning to the tab. The sizes have been reset to defaults after returning to the tab with the threat warning lights.
1. Fraps isn’t really a good point on regular software FPS. When you look at the FPS of BMS in 2D it will even be a lot lower at points.
2. Can you send me your layout xml (in layouts folder) & yame64.xml (in config folder) via PM so I can look at it? -
Just got my first MFD working on a second display - I am so pleased that even on old geezer can get this thing working! Thank you so much for the program and the clear instructions.
-
Any updates on the next version? You guys are such a mean tease!
-
Not yet. Havent been able to test, too much work at main job.
Did make our website partialy during tje weekend. Www.yame64.com -
Website smebsite!!
@ -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 got tired of working on my Helios profile so went back to run a bit more tests. Had to run a “control” test first just in case my system ran differently from last time, maybe my new Helios profile would affect the results, etc. My default setup (AA On) ran an average of 47.2185fps on TE13. This is almost 1fps less than during my previous testing, but I’ve changed my profile slightly with more YAME gauges showing, notably the trim gauges, marker beacon, and HYD gauges. My Helios profile also has more stuff in it so that could be a factor as well. Bottom line, I did a few flights to establish a baseline with my current PC settings. Turning AA off resulted in 47.528fps. 0.3095fps gain? I’m calling AA settings NOT A FACTOR as far as framerates go.
Next test is overlapped gauges.
-
is it possible to change the map ?
I tried to use a map with airfield and strips 2048*2048 no joy -
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