YAME64 suite
-
Hi folks,
thanks for the update, good to see the F-18 being supported.
Do I need to uninstall the previous version first before updating?
All the best,
Uwe
Normally you don’t. Just run the installer and will update and keep your config & custom layouts.
-
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.
Same thing for me. I had this issue with the original version too. Everything worked apart from the mfd’s. After being in touch with roccio, the only way I could get the mfd’s to show was to install bms on my client pic, and click the hook box, then the mfd’s worked. Cleared out all the version 1 stuff and tried the new one tonight and with nothing else but the ip settings etc the problem persists - all gauges work ok, but mfd’s are blank. I will look into it more tomorrow evening and post my results.
-
I figured out what the problem was with my client computer. I think it was that YAME did not play well with Windows basic. The YAME windows would get corrupt (washed out and or smeared) when moving from monitor to monitor. I needed to reinstall Windows because I could not turn Aero back on for some reason.
-
I ended up installing BMS on my slave PC as well, just to get rid of the annoying prompts at the start then I realized I could click the HOOK option as well…
-
I’m running YAME client on a laptop without BMS, displaying all gauges and MFDs/DED via the 3D hook. So there should be no need for a BMS install on the client side.
-
Normally you don’t. Just run the installer and will update and keep your config & custom layouts.
I tried this and all the new installer offers is to create a desktop icon
All the best, Uwe
-
I tried this and all the new installer offers is to create a desktop icon
All the best, Uwe
Yes, that should be enough. The rest it just uses from the previous install (location to be installed etc).
Just check the last tab in the program where you can see the version number. If it shows 1.1.0 it’s all good. -
I ended up installing BMS on my slave PC as well, just to get rid of the annoying prompts at the start then I realized I could click the HOOK option as well…
One of the changes in v1.1.0 by request is that it will only promote you once for the BMS path, DTC & keyfile location. If you click no to that message, it won’t ask again.
-
Yeah, I was referring to back when it was an issue in v1.0
-
Update to 1.1.0 seems to have worked fine, however on the first flight I had no mfds (other gauges worked fine).
I checked the settings and it looks like the 3d hook extraction method had been disabled, and all of a sudden I had RTT_Export…. set to 1 again in Falcon BMS,.cfg which I am pretty sure I had not enabled once I got v. 1.0.0 running.
Anyway, editing Falcon BMS.cfg and setting the RTT_ExportTextures back to 0 brought the mfds up again using the 3dhook method.
Thanks again for this great tool and the even greater support you guys provide to the community!
Uwe
-
Is the V1.1.0 an incremental installer? I’ve already installed Yame 64 on my PC. What will happen to my profile? Do i have to make a backup, than restore it into profile folder? Thank you guys, wanderful tool!!!
-
Is the V1.1.0 an incremental installer? I’ve already installed Yame 64 on my PC. What will happen to my profile? Do i have to make a backup, than restore it into profile folder? Thank you guys, wanderful tool!!!
Best to always take a Back-up of tje config file and your personal layout files.
It’s incremental. If you install over it, it will look for a config file. If there, it won’t install tje default One over it. It will overwrite all lay-outs that come with the install, but won’t delete layout files you saved under a New name. -
Perfect! Thank you!
-
Thank you very much for the 32b
A stupid question….How to Stop/Close 32b version?
-
Hey guys,
just a little heads-up if you’re also running komurcu’s excellent MFD for Android software on your tablet. AFAIK you’ll still need the RTT_ExportTextures=1 in your falcon bms.cfg or else your DEDs / RWR / MFDEs won’t display on your tablet / phone.
Maybe YAME64 could change its “warning” about the variable being set to 1 when using the 3d hook method that this setting is required for some “3rd party software”.
All the best, Uwe
-
Thank you very much for the 32b
A stupid question….How to Stop/Close 32b version?
seems to be an issue with the 32bit version. Placed in our tracker as critical bug.
-
My client screen freezes whenever I use edit gauges or windows being dragged over top of each other. The ghost window sticks to the main window and prevents further use. I have to shut down program via task manager. And it is using 40% cpu while the window sits there. The client just keeps freezing on me whenever I move stuff to other monitors. Its a real mess on my client computer.
Also, is it possible to have all the gauges show before BMS starts. I don’t want to wait until I am in the seat to see there is a problem with placing and such.
Client computer: [email protected] Ghz 8gb ram GTX 580 3gb
Hi, is this by any chance happening with the 32Bit version? Seems the x86 version has some issues with the build the x64 doesn’t have.
-
Hi, is this by any chance happening with the 32Bit version? Seems the x86 version has some issues with the build the x64 doesn’t have.
No. 64bit version. I think it has to be something to do with my Windows install, because it works fine on my main computer, but I need it to work on my secondary computer.
-
Can the HUD on client be mirrored or flipped? Just like FMFDE.
-
Can the HUD on client be mirrored or flipped? Just like FMFDE.
Not yet, but I can imagine it can be useful if you want to use it as a flat extraction to be reflected onto a real hud. Then again. I assume the screen used in the hudbox would only be used for the hud extraction and nothing else, so it’s easier to just set your screen to turn 180° in windows, or physically turn that screen around then have it as an extra feature in code