YAME64 suite
-
ok i have an issue that never had before…
Start YAME ,extractions on the 2 screens are ok, but when i run 4.34 the extractions are alive, but the main screen (4.34 screen) goes black…
any ideas?
(Win7x64-ATI R7 370) -
I also made sure the Registry was changed to C:\Falcon BMS 4.34 as shown below:
Can you try reverting registry to point to 4.33 and run BMS manually instead of via the yame launch button? Uninstall and make sure all yame files are deleted first, then revert registry, then reinstall yame.
-
I can not get YAME 64 v1.2 to work on my Win 10 PC. Previously I had it working with BMS 4.34 but my windows crashed (for other reasons) so I reinstalled Win 10 on a reformatted drive. I then loaded BMS 4.33 U1-U5, BMS 4.34, and YAME64 v1.2. I also installed MS Visual C++ as shown bellow:
[…]
When I start the Client I get this error message:Same problem here - and g_bExportRTTTextures ist set to 1 in both cfgs.
Good news: I drilled this error down, but nevertheless the MFDs, etc. are no showing up.
For some reason YAME is (now?) looking for a falcon bms.cfg in C:\User\Config
Jusrt create these (sub)directories and copy the falcon bms.cfg in there and at least the error above is gone.So… Now I (we) need only help to get the MFDs & Co. to be extracted again…
-
really no one?
:noidea: -
Yame has a registry entry for where BMS is installed. So the config for 4.33 and 4.34 need to be the same regarding the RTTEXport settings. Also you’ll have to remove the DLL hook file that Yame wants to use which worked with 4.33 but not with 4.34.
-
I tired to get yame64 to run with the work around, but that seems to break everything I followed these instructions:
https://www.yame64.com/how-to/My g_bExportRTTTextures was already set to 1 for both release and everything was running fine. I then changed the registry entry voor 4.33 to point at the 4.34 folder as suggested and then I got
I changed the registry to it’s original value and still got the error. BMW won’t run anymore. Any idea what’s going wrong?Edit: 4.33.5 is still running fine
-
I tired to get yame64 to run with the work around, but that seems to break everything I followed these instructions:
https://www.yame64.com/how-to/My g_bExportRTTTextures was already set to 1 for both release and everything was running fine. I then changed the registry entry voor 4.33 to point at the 4.34 folder as suggested and then I got
https://i.postimg.cc/8cz65GWs/2019-10-28-12-37-34-Falcon-BMS-exe-Entry-Point-Not-Found.png
I changed the registry to it’s original value and still got the error. BMW won’t run anymore. Any idea what’s going wrong?Edit: 4.33.5 is still running fine
The DirectX hook is not working for 4.34. So disable it and remove the d3d9.dll from <falconbms>\bin\x64 folder</falconbms>
-
The DirectX hook is not working for 4.34. So disable it and remove the d3d9.dll from <falconbms>\bin\x64 folder</falconbms>
Thanks for the swift reply. I ended up reinstalling .34 and everything worked again.
But I just checked, there’s no such dll in the .34 bin-folder. Or will starting yame add that in the folder?
-
Thanks for the swift reply. I ended up reinstalling .34 and everything worked again.
But I just checked, there’s no such dll in the .34 bin-folder. Or will starting yame add that in the folder?
Yes, the dll is copied there by yame, so if not present no worries.
-
What do i need to modify in CPD 60 map file, in order for a/c position to be displayed properly in other theaters?
For example in EMF theater i save the map via WDP (png), then i resize it to 2048x2048 px but the a/c position is not properly displayed in map.
Any advice?
Thx in advance -
What do i need to modify in CPD 60 map file, in order for a/c position to be displayed properly in other theaters?
For example in EMF theater i save the map via WDP (png), then i resize it to 2048x2048 px but the a/c position is not properly displayed in map.
Any advice?
Thx in advanceThat map display wont work on all theaters. Will on a future update…
-
Just curious, yame64 for 4.34 is still alive? Or are we sticking with the 4.33 work around with no hook? Or waiting for the next bms update?, like i said just curious, as i check almost daily for news
-
Just curious, yame64 for 4.34 is still alive? Or are we sticking with the 4.33 work around with no hook? Or waiting for the next bms update?, like i said just curious, as i check almost daily for news
Yame is not dead, but it’s very late due to real life work. Please have patience and if someone wants to help let me know. (C++ skills required)
-
Sorry i do not even understand a++ let alone c++, however if you need somebody to put it through it paces at some point, i would gladly look for bugs/glitches problems before beta testing or beta testing, ….im happy running yame as it stands, i have no problems with it, the only down side was… running low on ssd space and looking at when i could remove 4.33 , sorry i cant help more, and happy to be patient, as i said i had not heard anything for a while, and was curious, its a great App, and i am sure others will now be relieved its still in the works …thanks HC
-
+1
-
Really wish I’d had the skills to help you Roccio
Keep up what you do, many many people truly appreciate it -
Yame is not dead, but it’s very late due to real life work. Please have patience and if someone wants to help let me know. (C++ skills required)
Curious why you haven’t made the repository public like on Github. if you need help that’s how to do it. Make it open source so others can contribute.
-
May be a dumb question. Where can I find a download for 4.33 from a trusted site? I have upgraded all my PC’s and don’t have it anymore.
-
Still download from releases and updates on this forum front page.
-