YAME64 suite
-
Great Tool, i love it :-).
One Question:
are there Plans to add support for DX Key´s ?Thx!
Yes, DX binding is present in our 1.2 beta’s. -
-
Got an IBM X200T around and thought I give it a shot. Sadly the program crashes at multiple points:
leaving the client->windows tab
closing and saving the gauge layout editor
starting the client (YAME window pops up fine, then crashes)Last entry in the logfile reads “FD/Texture connecting to server”, depending on which options I use. Tried multiple combinations and settings with no luck.
VC, DX and drivers are up to date, AV and Firewall should not be a factor, system is Win 7 64bit
If it wouldn’t crash by navigating the UI I’d simply blame it on the old hardware and move on. -
Got an IBM X200T around and thought I give it a shot. Sadly the program crashes at multiple points:
leaving the client->windows tab
closing and saving the gauge layout editor
starting the client (YAME window pops up fine, then crashes)Last entry in the logfile reads “FD/Texture connecting to server”, depending on which options I use. Tried multiple combinations and settings with no luck.
VC, DX and drivers are up to date, AV and Firewall should not be a factor, system is Win 7 64bit
If it wouldn’t crash by navigating the UI I’d simply blame it on the old hardware and move on.Can you check one of the following is applicable to your setup?
- Windows aeroglass disabled might cause issues
- enabling “trama S3TC” in OpenGl Texture compression might cause issues
- reported SLI issues
- AFR - Crappy FPS (not really sure why)
- AFR2 - Good FPS - No left MFD & RWR
- SFR- Good FPS - YAME rendering fine
-
Hi there, thx for the quick response.
- Windows Aero is enabled
- Never heard of “Trama S3TC”, never touched any graphics related settings. afaik C4D uses OGL and it’s working fine out of the box.
- It’s a laptop with integrated graphics, SLI shouldn’t be a factor
The only major difference in software would be some Lenovo tools for better accessibility when used as a tablet. After 20 years of PCs I should have thought of this earlier, even though they run mostly quiet in the background.
Will do some tinkering with that and see what happens. If it helps I’m gonna report back, if not I’m gonna wait for some more suggestions. -
My YAME just stopped showing up on the monitor! It opens fine, but just populates in the task manager. I was using it for a flight, went to run some errands and when I came back and opened it again, this happened.:(
Does anyone have any ideas as to the culprit of this problem?
Thanks -
@usafpga:
My YAME just stopped showing up on the monitor! It opens fine, but just populates in the task manager. I was using it for a flight, went to run some errands and when I came back and opened it again, this happened.:(
Does anyone have any ideas as to the culprit of this problem?
ThanksOne of your monitors went into sleep mode?
Are you talking about the gauges or the main UI.
In case of gauges: Open you layout xml file (/layouts folder) and check to see what x/y coords the window(s) have and see if they are still located on the correct position.
In case of UI: open yame64.xml file (/config folder) and also check x/y coordinates. -
One of your monitors went into sleep mode?
Are you talking about the gauges or the main UI.
In case of gauges: Open you layout xml file (/layouts folder) and check to see what x/y coords the window(s) have and see if they are still located on the correct position.
In case of UI: open yame64.xml file (/config folder) and also check x/y coordinates.Main UI. Is the .xml file in the client folder? If so, I opened it and this is what I got. Did I go to the right place?
Only one top level element is allowed in an XML document. Error processing resource 'file:///D:/Yame64/YAME64/YAME64_client…
-
@usafpga:
Main UI. Is the .xml file in the client folder? If so, I opened it and this is what I got. Did I go to the right place?
Only one top level element is allowed in an XML document. Error processing resource 'file:///D:/Yame64/YAME64/YAME64_client…
No the xml is in the /config folder, named yame64.xml
-
In yame64.xml in conf folder you will find a section like this:
probably the values are set to -32000, change to 0 and all should work. It’s a known and resolved bug for the next update.
-
No the xml is in the /config folder, named yame64.xml
Ok, found it. my x/y coordinates are 32000/32000. Is there anything else I should be looking for?
-
In yame64.xml in conf folder you will find a section like this:
probably the values are set to -32000, change to 0 and all should work. It’s a known and resolved bug for the next update.
Yes, that’s what I’m showing. How do I change the values? It won’t let me change them in the config folder.
-
@usafpga:
Yes, that’s what I’m showing. How do I change the values? It won’t let me change them in the config folder.
That’s strange. Try saving it as another file like yame64NEW.xml, then delete the original yame64.xml and then replacing it by the new file by changing the filename to yame64.xml again
-
@usafpga:
Yes, that’s what I’m showing. How do I change the values? It won’t let me change them in the config folder.
Maybe you have installed YAME in a system folder (as program files) and you don’t have write permissions. Copy the YAME64.xml to your desktop, change the values and try to copy back in it’s folder.
-
In the YAME64 manual, page 33, second paragraph concerning the moving map, it states: “Next to the ownship, if your DTC was saved in 2D correctly and pointed to in the UI, ……” I am just getting back into BMS after a few years and still trying to rap my head around WDP and this program and I am confused as to the what the quoted language means and what UI is it referring to. Could someone explain the procedure for getting the moving map into the CP. I searched this thread but to no avail.
Thanks -
Maybe you have installed YAME in a system folder (as program files) and you don’t have write permissions. Copy the YAME64.xml to your desktop, change the values and try to copy back in it’s folder.
Thanks, will give that a try when I get home from work. Thanks for all the help gentlemen, its greatly appreciated!!
edit: got it sorted, I was trying to edit the values in the .xml format. Had to open it in notepad……DUH!!:rolleyes:
Thanks again gentlemen!
-
In the YAME64 manual, page 33, second paragraph concerning the moving map, it states: “Next to the ownship, if your DTC was saved in 2D correctly and pointed to in the UI, ……” I am just getting back into BMS after a few years and still trying to rap my head around WDP and this program and I am confused as to the what the quoted language means and what UI is it referring to. Could someone explain the procedure for getting the moving map into the CP. I searched this thread but to no avail.
ThanksHi,
WDP has nothing to do with this.
UI stands for User Interface and refers to the grey YAME window where all the settings are done, so not the windows that show the actual gauges.
You understand it doesn’t add a moving map into BMS CP right? It extracts data from the sim and shows you custom gauges and moving map on a different window outside of BMS.1/ if your DTC was saved: see manual section 3.2 first run:
The first run needs a little setup, so go to the Globals tab and set your preferred folders (see in detail in “globals tab” section).
Normally at first run the application will automatically warn the user he/she has to configure some initial settings and bring you to the globals tab. When you chose “yes” it will automatically bring you to tab where to set those. If you chose “no” (e.g. because it’s the one for running in server mode on another pc), it won’t ask again next time.If you didn’t set it at first run, see manual section 8 Globals tab for a screenshot.
You can set the path to Falcon BMS (in this way you can have multiple installations of FALCON), set the user DTC file that will be used once running BMS (it’s used to retrieve steerpoint s & preplanned threat circles), set the keyfile BMS will use (this is used by the callback server to send the correct key to FALCON).
-
@usafpga:
My YAME just stopped showing up on the monitor! It opens fine, but just populates in the task manager. I was using it for a flight, went to run some errands and when I came back and opened it again, this happened.:(
Does anyone have any ideas as to the culprit of this problem?
ThanksAnother way without to change YAME64.XML file is to use Window application menu (the menu usually used when the app icon on the top right corner is mouse right button clicked.
1- Select the application on the task bar with left mouse button
2- press in sequence (not together) these buttons
ALT (enable application menu bar)
LEFT ARROW (select system menu - app icon)
DOWN ARROW (open or drop down system menu)
DOWN ARROW (move down selection bar on ‘MOVE’ option - you can use also the ‘M’ but it depends on your regional setting)
ENTER (Select ‘MOVE’ option)
LEFT OR RIGHT ARROW (This it moves your window in the arrow direction… if you know where the windows is - The first ARROW depress tie mouse pointer to the window then you can use it to move window but you need almost one arrow press)you can first try the sequence with a visible window
with Win 10 and thumbnail window preview (small application window displayed when mouse is on taskbar app icon) you can right click directly on the sall app icon on the top left icon in the thumbnail window and the select move in the opened menu.
The mouse pointer is positioned over the invisible window keep left mouse button clicked and move it towards the centre of the screen.
If you don’t know where window is move left and right until the windows is moved in visible area -
For anyone having trouble getting texture overlay to work, make sure you have the hook enabled on the client tab, then in the hook tab choose texture overlay and enable what you want and put in the necessary values. Hit apply when you are finished, then go to the conf file in the yame install, and copy the yame_d3d.cfg from here into the bms install bin/64x folder replacing the old file (if there is one). Then close yame, and launch bms from the default exe in the /64x folder, dont lauch from yame. If you apply any changes in client tab or server tab after doing this or launch from yame it will overwrite the cfg. You don’t have to open yame again doing this, or have yame open, it works automatically. Good work guys, really enjoy it thanks.
-
For anyone having trouble getting texture overlay to work, make sure you have the hook enabled on the client tab, then in the hook tab choose texture overlay and enable what you want and put in the necessary values. Hit apply when you are finished, then go to the conf file in the yame install, and copy the yame_d3d.cfg from here into the bms install bin/64x folder replacing the old file (if there is one). Then close yame, and launch bms from the default exe in the /64x folder, dont lauch from yame. If you apply any changes in client tab or server tab after doing this or launch from yame it will overwrite the cfg. You don’t have to open yame again doing this, or have yame open, it works automatically. Good work guys, really enjoy it thanks.
Wow, didn’t know that someone is using the overlay extraction….