YAME64 suite
-
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?
-
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 0.
Maybe this helps
Like me. It go well but it need to have installed BMS 4.33 U1.
-
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.
You´r right, my fault :wfish:
has to be 1 instead 0 -
I have both 4.33 and 4.34 installed, i cant get it to work fullstop, what could i be missing guys?
-
I have both 4.33 and 4.34 installed, i cant get it to work fullstop, what could i be missing guys?
Not compatible right now. They are working on it
-
I have both 4.33 and 4.34 installed, i cant get it to work fullstop, what could i be missing guys?
The selected FALCON is 4.33 U5:; ; ; .
-
I have both 4.33 and 4.34 installed, i cant get it to work fullstop, what could i be missing guys?
I could not get it to work properly either until now, but that’s what I did to get it working.
Roccio has said that 3Dhook does not work (yet), that is crystal clear.
But I got gauges and MFD via RTT texture extraction working.
To do so the key was to configure BOTH versions (4.33 and 4.34) to export the MFDs via RTT texture extraction.
That means no 3DHOOK file present on neither the :\Falcon BMS 4.33\Bin\x64 nor the :\Falcon BMS 4.34\Bin\x64 folder (where the Falcon_Bms.exe files are)
set g_bExportRTTTextures 1 on both 4.33 and 4.34 falcon_bmas.cfg files
And of course falcon cannot be launched via the big “Launch Falcon BMS” button on YAME´s Run Tab.
This way YAME is extracting the MFDs and the gauges ok on my PC (server-client config)
I do not know if this works if only BMS 4.34 is installed.
I hope it helps
-
I could not get it to work properly either until now, but that’s what I did to get it working.
I hope it helps
This helps indeed!
I’ll mention it on the website as well until v2 is released! -
Hello, Question does the YAME works in Android tablets?
I would like to have in my knee as kneeboard a tablet with colour moving map like CPD software