YAME64 suite
-
Hi,
I know that yame is not yet compatible with 4.34, but if you are in the process in making it compatible, here are some of my struggles. Maybe related to incompatibility or maybe my configuration.
After installing Yale 1.2 I tested it with my 4.33 install and I have no problems. When I place the hook DLL d3d9.dll in my x64 folder besides FalconBMS.exe 4.34 installation and try to start BMS manually (using the launcher) it directly gives the error:
“The procedure entry point Direct3DCreateEx could not be located in the dynamic link library d3d9.dll“.When I remove the hook file I can start BMS normally. But even when i’m Unchecking use hook in yame. It still gives no extracted mfds.
I think it’s something on my system. I installed the Vs2015 dependencies.
I also have the same problem.
-
After installing the required Windows Platform update for Windows 7, you could copy the d3d9.dll from the c:/windows/system32 folder and copy it over de “old” d3d9.dll in your falcon BMS bin folder.
This solves the error, but not the extraction of my mfds. So it maybe part of the solution. Just have to wait on the new release.
Darkman
Part of the performance tuning in 4.34 includes migration from Direct3D9 (XPDM) to Direct3D9Ex (WDDM) - this is why Windows 7 SP1 requires the “platform update” (KB2670838) to be installed. RTT export to shared memory now uses the Direct3D9Ex “Texture Creation in System Memory” feature, which increases FPS with “RTT export” enabled significantly.
If “RTT export” is enabled (set g_bExportRTTTextures 1), but it is not being used to display exported textures anywhere, FPS will be the same as if “RTT export” was disabled.
-
-
ITS AMAZING HOW I EVER FLEW WITHOUT YAME …NOW I CANT USE IT I’M LOST, IM LOOKING AT BLANK MONITORS THAT WOULD NORMALLY BE MY COCKPIT…ITS ALMOST LIKE HOW DID I MANAGE WHEN WE DID NOT HAVE CELL PHONES, HOPE IT GETS SORTED SOON?
-
While Roccio is doing his good work you could try RTTRemote by dunc in the meantime if you only use yame for mfd extraction. It’s in the tools directory and really neat and basic to setup especially if you have your yame settings at hand. It utilizes RTT export, don’t know if that’s still a performance factor in 4.34 though.
-
I use different monitors for all dials, mfd’s with cougers warning lights ect, i just feel a little lost without them all, yame is a great asset
-
we are beta testing. now works with .34.
-
Roccio, whoop whoop, feels like Christmas is coming, i feel like a little girl waiting for that new barbie Doll… i mean cough cough er boy waiting for is new football,
Cheers for all your efforts and a great app -
Roccio, whoop whoop, feels like Christmas is coming, i feel like a little girl waiting for that new barbie Doll… i mean cough cough er boy waiting for is new football,
Cheers for all your efforts and a great appWHoa! :shock: I can’t say I’m this excited, but I am impressed with such a quick response time! :thumb:
Cheers
-
Looking forward to the new release. YAME just gives me such a better overall FPS compare to the built in display extraction, although I wasn’t aware of RTTRemote, may have to do some fps testing again
-
Looking forward to see YAME for 4.34.
I was using YAME in 4.33 because in D3D hook mode it has no visible performance impact, the resolution of exported MFDs is also fine.Just wonder if you gonna fix (or maybe you already did it?) the bug with D3D hook mode getting sometimes stuck (textures somehow freezes and stops to refresh so i get the static picture). This was sometimes happening to me, especially when exiting campaign and starting instant action and vice versa.
-
I know an update for 4.34 is due shortly, but just to be clear; were some of you able to get YAME to run in server mode on the same PC as 4.34?
-
I know an update for 4.34 is due shortly, but just to be clear; were some of you able to get YAME to run in server mode on the same PC as 4.34?
Gauge extraction, yes. Display extraction, no.
Server-client on two different PCs.
Enviado desde mi H8324 mediante Tapatalk
-
It works for me, but i did not try out the Direct3D hook. I have Yame64 server on the PC running Falcon BMS 4.33 and 4.34. It works for both without having to change any configuration. My client YAME32 runs on Linux wine on a Notebook connected by ethernet cable. Client and server on the same PC works as well on both BMS versions.
Only problem is that YAME always checks at the configuration file from BMS 4.33 which is not really a problem for me as the required configuration parts are the same for me.
-
Working hard to have a working 4.34 version. The hook is not working at the moment, so you have to be a little patient…
-
Hi roccio if you put a dual install of BMS with falcon bms 4.33 and falcon bms 4.34 and run yame64 and then starting “yame client”, launching 4.34 with your own launcher it go well. At the moment its a temporal solution until you release the new version.
-
Hi roccio if you put a dual install of BMS with falcon bms 4.33 and falcon bms 4.34 and run yame64 and then starting “yame client”, launching 4.34 with your own launcher it go well. At the moment its a temporal solution until you release the new version.
Strangly this doesn’t work for me. I get nothing, no texture extractions and no pull from shared mem for other gauges.
-
Strangly this doesn’t work for me. I get nothing, no texture extractions and no pull from shared mem for other gauges.
Did you use 3Dhook in 4.33 ?
Problem is that Yame is pointing to the 4.33 Folder (no way to change it). so the Hook file is only availabe in 4.33. Copying the hook file to the 4.34 folder didnt work.I got it working in 4.34 it when i disabled the 3Dhook option and changed the "exportRTT texture option in the BMS config to 1.
Maybe this helps
Edit: Changes in RED
-
Also without 3Dook but g_bExportRTTTextures has to be “1” for me. As it says in the config file:
// This enables the shared texture memory area for HUD/MFDs/HMS/RWR/DED/PFL. This is independent from BMS external window usage
if it is “0” YAME server starts with an error dialogue.
-
Works with the 3D handle off, but I do not know how to move the cursor from the Facon screen to the YAME screen, “alt tab” does not help?