YAME64 suite
-
I was hoping there was a setting or parameter that hooked YAME to outside the cockpit views so that the MFD’s and instruments are updated, dynamic, and in sync. Is that even possible?
So you are hoping YAME can still display MFDs and instruments and keep them working (in sync) even when you are outside the cockpit? I doubt this is possible. Like I said, even the BMS CDE exhibits this behavior so maybe the game itself just does not “draw” the MFDs/instruments when you are on an external view, and therefore there is nothing for YAME to hook on to. I could very well be wrong….
-
Hello people.
Thanks for this master piece…:)
I have running server with 64 version and client witth 32 version…and I haven´t extraction.
This is client.log form client…obviosuly
01/03/2006 12:47:14: ***************************************************
01/03/2006 12:47:14: * YAME client START *
01/03/2006 12:47:14: ***************************************************
01/03/2006 12:47:14: Data extraction: false
01/03/2006 12:47:14: Texture extraction: true
01/03/2006 12:47:14: Texture connecting to server.
01/03/2006 12:47:54: Texture extraction connected.
01/03/2006 12:48:25: Texture data extraction stop.
01/03/2006 12:48:29: Client::run ended.As I understand, I´m connected to server but there is no extraction, correct?
Any idea what is the problem?
Thank you
-
Sorry….I add I have left MFD in server Pc and is running perfectly.
-
Good morning.
Well, I have found the problem.
Is possible you don´t believe it but it´s true.
I´ve loaded Block 50 profile and I have extraction
If I deselect CMDS option in EW section, I don´t have extraction.
I don´t know if you can reproduce this issue, but I can promise you that´s was the problem.
Thank you
-
Good morning.
Well, I have found the problem.
Is possible you don´t believe it but it´s true.
I´ve loaded Block 50 profile and I have extraction
If I deselect CMDS option in EW section, I don´t have extraction.
I don´t know if you can reproduce this issue, but I can promise you that´s was the problem.
Thank you
Will look into this, thank you.
-
The last question
YAME32, how to run in no window mode?
Thx
-
The last question
YAME32, how to run in no window mode?
Thx
Sorry, but I don’t understand what you mean…
-
I´ve started Yame 32 and is in window mode.
I´ve tried to edit yame.xml with notepad++ but no results.
-
In the YAME client UI, go to CLIENT -> WINDOWS and select the appropriate window. Check/un-check BORDER as appropriate. Try running in FULLSCREEN mode or setting it to MASKED and the “window mode” top border will not appear.
-
Thank you very much
-
Hello, Now that I’m over the BMS hooks not being present within BMS so that display instruments update values while in Falcon’s #D outside views, I’d like to discuss a couple of issues that I’m hoping somebody can provide some solutions.
1.) The YAME UI is very small on my computer - which is a Windows 10, 64bit I7 CPU with 3200X1800 touchscreen display. I’ve tried all the compatibility troubleshooting steps to no avail. I also have a second 1920X1080 display/monitor connected. In trying to drag the UI to the second monitor, the display is still micro small.
2.) The touchscreen with the 3200X1800 display functions, but the OSB button positions do not seem to line up with the callbacks. Meaning when touching OSB’s, the function is offset slightly to where the button position displays.I’m really liking the capabilities of YAME especially the MFD piece - thanks so much for all of your efforts!
-
I think the actual size of the YAME UI is set, so a bigger resolution monitor = smaller UI size. On a 1920x1080 res monitor, it should be more than enough to be useful. Maybe you’ve zoomed out or changed your desktop size settings?
-
Hi
I use YAME my first time and have some problems. Google and the forum can not help me yet (at least I did not find anything).
First of all, my setup:
PC 1 for Falcon BMS with YAME64 1.2.1 server.
PC 2 for instruments (3 monitors) and YAME64 1.2.1 client.Server settings:
falcon BMS.cfg:
Client Settings:
When I start the client, the following error message appears:
My ADI looks like this:
And unfortunately, the MFDs, the RWR and the DED are not displayed at all. Otherwise, the other instruments will work as expected.
The file “d3d9.dll” did not exist in the x64 folder.
The second problem is that my CPU fan is running at full speed when I start the client …
I hope this is not a double post and someone can help me.
Regards
MadDoc
-
To All:
Around post 1108/1109, I stated that when I updated windows 10 to the new fall creation, when using yame, my FPS dropped to around 5 FPS. So on the advice of ICE, I rolled back to windows version 1709 and everything is fine. However, I keep on getting notices from MS to update to the fall creation. One day I will have to do so. Has anyone else updated to the fall creation of windows 10 without any issues with respect to the FPS loss when using Yame? Have the developers of Yame found what the issue is with DX9 games, Yame and the fall creation? -
You will remember that I’ve strongly advised against upgrading to Win10CU as I’ve had issues with CU and my touchscreens. After some time, Windows updated itself anyway and I braced for the worst. Luckily, my initial issues never happened again so whatever was missing from Win10CU must’ve got added in and fixed. Therefore, do not worry too much about Win10FCU… just delay it as much as you can so that you aren’t a beta tester… if it ain’t broke, don’t fix it! When the time comes that we’ll be forced to update to it, hopefully the initial bugs will be ironed out.
Unless there’s something in Win10FCU that you really, REALLY need?
-
Just to contribute these, in case a dev’s mind might find these useful for any possible issue escalation.
I’ve been using yame quite some time now and I am pretty pleased, moving on from Lighting’s mfd extractor (for the avionics / organs) and embedded bms extractor (for mfd’s / hud/ rwr extraction), to separate displays on my setup.
I sometimes have small glitches/lag/lower fps on the yame mfd’s and hud views, these mainly when on heavy a2g missions, including operational tfr / hud flir / tgp, but sometimes also had these on a2a engagements. Well I am still searching about optimal settings, this is not the main concern I wanted to share.
Since previously with the bms extractor I didn’t had any fps looses on the exported images, I’ve tried to disable yame’s mfd’s / hud / rwr extractions, keeping only the rest necessary organs (CP, engine etc), and enable back bms extraction for the mfd’s / hud / rwr.
Test was ok, yame extractions working good with no lag, mfd’s etc also working ok with no lag. I did however experienced some 20% fps loss in-game when running both extraction software, which is not a showstopper for my 1080 card but did not like to have.
So I’ve moved again all extraction options to yame as in the first place… But, this time, mfd’s / hud / rwr didn’t want to display at all, whatever I did with falconbms.cfg options or hooks options from within yame.
Issue was solved after completely uninstalling yame, deleting ALL files and layout profiles, installing a fresh copy of the latest version and building again from scratch my xml layout profiles… Using my old-original profiles was a no-go as again mfd’s / hud / rwr displays would turn black, so I’ve used the stored numbers to quickly set the organs to the appropriate positions etc. Another discovery was that using as the new layout profile the same name as the old profile, would again turn my mfd’s / hud / rwr displays black with no extraction at all! So using a new name was the solution for this…
Finally, another worth-mentioning find… All these “tests” where flown in only 1 specific TE mission I had build quite some time ago. Mission was originally working fine / extractions when flying the mission were ok, but after the problem appeared as described above extractions stopped working for this mission! Even after reinstalling yame and building my new options and layouts, in all other stored TE missions or any new TE missions the extractions are working ok (although with the originally mentioned lag some times), in the specific TE mission extractions did not want to work… Mission deleted, issue cannot be reproduced lol.
Back to ops.
-
Hi
I use YAME my first time and have some problems. Google and the forum can not help me yet (at least I did not find anything).
First of all, my setup:
PC 1 for Falcon BMS with YAME64 1.2.1 server.
PC 2 for instruments (3 monitors) and YAME64 1.2.1 client.Server settings:
falcon BMS.cfg:
Client Settings:
When I start the client, the following error message appears:
My ADI looks like this:
And unfortunately, the MFDs, the RWR and the DED are not displayed at all. Otherwise, the other instruments will work as expected.
The file “d3d9.dll” did not exist in the x64 folder.
The second problem is that my CPU fan is running at full speed when I start the client …
I hope this is not a double post and someone can help me.
Regards
MadDoc
According to the settings, the d3d9.dll should be there though.
And the error and ADI image suggest some images are missing (or unreadable).
The above plus high CPU makes me believe something went wrong during install. Can you try running everything as administrator? If that doesn’t help; uninstall, and delete all remaining files that might remain after that and then redownload and try again? -
Has anyone else updated to the fall creation of windows 10 without any issues with respect to the FPS loss when using Yame? Have the developers of Yame found what the issue is with DX9 games, Yame and the fall creation?
Still on Win7 here, so can’t really tell I’m afraid.
No idea if Roccio or Scorpion found something yet, but it seems more Win10 then Yame related. Or maybe some of the used libraries that give issues in Win10. -
Just to contribute these, in case a dev’s mind might find these useful for any possible issue escalation.
I’ve been using yame quite some time now and I am pretty pleased, moving on from Lighting’s mfd extractor (for the avionics / organs) and embedded bms extractor (for mfd’s / hud/ rwr extraction), to separate displays on my setup.
I sometimes have small glitches/lag/lower fps on the yame mfd’s and hud views, these mainly when on heavy a2g missions, including operational tfr / hud flir / tgp, but sometimes also had these on a2a engagements. Well I am still searching about optimal settings, this is not the main concern I wanted to share.
Since previously with the bms extractor I didn’t had any fps looses on the exported images, I’ve tried to disable yame’s mfd’s / hud / rwr extractions, keeping only the rest necessary organs (CP, engine etc), and enable back bms extraction for the mfd’s / hud / rwr.
Test was ok, yame extractions working good with no lag, mfd’s etc also working ok with no lag. I did however experienced some 20% fps loss in-game when running both extraction software, which is not a showstopper for my 1080 card but did not like to have.
So I’ve moved again all extraction options to yame as in the first place… But, this time, mfd’s / hud / rwr didn’t want to display at all, whatever I did with falconbms.cfg options or hooks options from within yame.
Issue was solved after completely uninstalling yame, deleting ALL files and layout profiles, installing a fresh copy of the latest version and building again from scratch my xml layout profiles… Using my old-original profiles was a no-go as again mfd’s / hud / rwr displays would turn black, so I’ve used the stored numbers to quickly set the organs to the appropriate positions etc. Another discovery was that using as the new layout profile the same name as the old profile, would again turn my mfd’s / hud / rwr displays black with no extraction at all! So using a new name was the solution for this…
Finally, another worth-mentioning find… All these “tests” where flown in only 1 specific TE mission I had build quite some time ago. Mission was originally working fine / extractions when flying the mission were ok, but after the problem appeared as described above extractions stopped working for this mission! Even after reinstalling yame and building my new options and layouts, in all other stored TE missions or any new TE missions the extractions are working ok (although with the originally mentioned lag some times), in the specific TE mission extractions did not want to work… Mission deleted, issue cannot be reproduced lol.
Back to ops.
Thanks for the report Raptor.
When beta testing I also had occasional all black extractions. Sometimes it helped just closing BMS and YAME, then start YAME again and reset 3Dhok or no 3D hook, and then start BMS. It seems the setting or deleting of the dll sometimes doesn’t get executed when BMS is still running.
Are you using mask option in any of the windows you use? That sometimes can cause issues too where the mask file hasn’t updated for some reason after you changed to location of certain gauges and then the moved gauge is behind a mask. -
then start YAME again and reset 3Dhok or no 3D hook, and then start BMS. It seems the setting or deleting of the dll sometimes doesn’t get executed when BMS is still running.
I’ve tried these with no success. I suspected that could be a memory / himem issue, up to temp files/config files caching, so I’ve also tried deleted temp files, killing processes, and restarting the pc between some steps, with no joy.
Are you using mask option in any of the windows you use? That sometimes can cause issues too where the mask file hasn’t updated for some reason after you changed to location of certain gauges and then the moved gauge is behind a mask.
No I am not using mask option at all.