YAME64 suite
-
AARRGHH!! One suggestion I can’t believe nobody’s brought up… can we be able to resize the YAME64 suite window itself? Instead of a small box and having to scroll through, we could instead resize it to fill at least the vertical space of a monitor and then see more options and less scrolling! Just realized we were all so amazed at the program that this seemed to have gone unnoticed.
A few issues with v1.1:
the HYD B gauge is still not being rendered
the display extractions (MFD, DED, etc.) no longer work
is there a way to remove the bezels from the DED and PFL? -
AARRGHH!! One suggestion I can’t believe nobody’s brought up… can we be able to resize the YAME64 suite window itself? Instead of a small box and having to scroll through, we could instead resize it to fill at least the vertical space of a monitor and then see more options and less scrolling! Just realized we were all so amazed at the program that this seemed to have gone unnoticed.
A few issues with v1.1:
the HYD B gauge is still not being rendered
the display extractions (MFD, DED, etc.) no longer work
is there a way to remove the bezels from the DED and PFL?For the resize of ui isdoable but need some time.
Wil check hyd b, it seems to me to had fixed…
For display extraction to work remove the old d3d9.dll and yamed3d.cfg located in falcondir\bin\x64 or use the new functionality in hook tab (remove hook files)
If you want bezel free gauges you have to remove them by yourown in the file located in the gauge folder. When saving remember to keep transparency info. -
Strange, see 2 Posts above. Made that With 1.1 less then an hour ago. HydB and extractions working.
Bezel of DED/PFL. Not a real option. Maybe try deleting/renaming the gauges files of those so they maybe don’t get rendered? Not sure if that will work. Not behind pc now to try. -
For the resize of ui isdoable but need some time.
Wil check hyd b, it seems to me to had fixed…
For display extraction to work remove the old d3d9.dll and yamed3d.cfg located in falcondir\bin\x64 or use the new functionality in hook tab (remove hook files)
If you want bezel free gauges you have to remove them by yourown in the file located in the gauge folder. When saving remember to keep transparency info.No d3d9 or yamed3d files in the \bin\x64 directory as I wasn’t using HOOK.
-
Interesting development…. not changed anything at all, but started Falcon via the LAUNCH button on YAME and the extraction is working again. Started Falcon again via my desktop shortcut and via my Helios button and extraction kept working. Weird, not sure what’s going on, but glad it’s working!!
Note that even though the extraction is working again, HYD B is still a gray circle. And yes, I tried nudging the gauge by 1 pixel left/right and even resizing the gauge 1 pixel, still not being rendered. It does show up in the EDIT GAUGES screen, but not when YAME is actually running.
-
I am unable to reproduce the issues with the gauges. Please send me your layout xml file and I will check.
-
Check PM!
-
If you want bezel free gauges you have to remove them by yourown in the file located in the gauge folder. When saving remember to keep transparency info.
If this is the case, can we have an option like on the RWR where we can choose a background image or no image at all please? Thanks!
-
Did another fresh download, clean and install.
The HSI has the problem only when the window it’s in is masked.
When the window is not masked the default HSI looks as it should. -
thanks to Devs for the new release, specially for taking our considerations into account. It´s super to have the F-18 extracted, bye bye GPT and Texture extraction…
I can’t make the .bat files to work properly. I have tried with three different .bat flies which work when i double click on them directly, but when run with YAME (normal or “run batch” modes) they don’t work. I performed a clean install, but problem persists.
I think i found a bug:
When adding an APP to the run menu, no matter what the state of the “Batch” check-mark is, the app is always added without the star. Editing the app, unchecking and then checking again the “batch” check-mark, solves the problem.
-
Did another fresh download, clean and install.
The HSI has the problem only when the window it’s in is masked.
When the window is not masked the default HSI looks as it should.Aha, thanks. Maybe that’s also the case with -Ice’s hydrB gauge. Taken into our bug tracker.
thanks to Devs for the new release, specially for taking our considerations into account. It´s super to have the F-18 extracted, bye bye GPT and Texture extraction…
You’re welcome.
I can’t make the .bat files to work properly. I have tried with three different .bat flies which work when i double click on them directly, but when run with YAME (normal or “run batch” modes) they don’t work. I performed a clean install, but problem persists.
I think i found a bug:
When adding an APP to the run menu, no matter what the state of the “Batch” check-mark is, the app is always added without the star. Editing the app, unchecking and then checking again the “batch” check-mark, solves the problem.
Will add those to the bug tracker aswel, can’t test at the moment to verify it’s a general problem or need more details to reproduce it.
-
-
Aha, thanks. Maybe that’s also the case with -Ice’s hydrB gauge. Taken into our bug tracker.
Bug sorted out thanks to roccio! Apparently, the HYD B gauge uses the default window name, in this case, “YAME”…. I had changed window names so I could tell which is which so the HYD A gauge was set to display in “RIGHT WINDOW” but HYD B gauge still kept the default “YAME”… changing that to “RIGHT WINDOW” sorted it out, but I had to open the layout file in Notepad++ to make the change as it can’t be done in the UI for now.
-
Getting “unable to install default configuration file” when I try to run v.1.1 of YAME on my client PC. Version 1.1 does run on my server PC however. Both machines running Windows 7 x64.
-
Do you mean when running the setup for v1.1?
Did you assign read only attributes to any of the YAME configuration files? Also, make sure to have closed all apps launched via YAME launcher prior to updating your install.You might also want to try running YAME as administrator.
-
You might also want to try running YAME as administrator.
The installation completed successfully but I wasn’t able to initially open the program. Anyway, right clicking on the shortcut and running as administrator worked - thanks Scorpion. Not sure why version 1 did not require this additional step.
-
Did a few more tests, this time testing if v1.1 had a framerate hit and whether the orientation of monitors had an effect on performance. Also tested whether fullscreen or windowed modes had any real effect on framerates. Check out my FPS testing thread to read more.
TL;DR - no FPS hit with the new version; monitor orientation does have a little effect; fullscreen vs. windowed does not have much difference, but fullscreen still out-performs windowed mode by a little bit.
-
I had hopes that the new version would solve my unique problem but it’s still present. I’m running the server on one machine and the client on a second machine. I can get MFD’s and DED to work using textures only but not hook. I’d like to figure this out because I’ve got a big framerate hit using textures only.
A thought; could the age of my client’s video card be a problem? It’s a GeForce 8500 GT and most likely not compatible with the latest Direct3D/DirectX.
-
I had hopes that the new version would solve my unique problem but it’s still present. I’m running the server on one machine and the client on a second machine. I can get MFD’s and DED to work using textures only but not hook. I’d like to figure this out because I’ve got a big framerate hit using textures only.
A thought; could the age of my client’s video card be a problem? It’s a GeForce 8500 GT and most likely not compatible with the latest Direct3D/DirectX.
Have you opened the ports of the router and checked for possible server/client firewall blocking YAME?
-
I had hopes that the new version would solve my unique problem but it’s still present. I’m running the server on one machine and the client on a second machine. I can get MFD’s and DED to work using textures only but not hook. I’d like to figure this out because I’ve got a big framerate hit using textures only.
A thought; could the age of my client’s video card be a problem? It’s a GeForce 8500 GT and most likely not compatible with the latest Direct3D/DirectX.
Could indeed be a possibility. I’ve seen non working 3D compass & ADI on an older machine, likely because it can’t handle the sphere 3D the texture is placed on. This could be a similar case.
It should work because we’ve tested even with 2 pc’s on different locations. One guy running server with hook only + BMS, and me in another country loading only client and receiving from his IP and it worked.