YAME64 suite
-
Thanks roccio, Here you have:
<apps version=“1.2”><falcon><windowed>true</windowed>
<path>E:\Falcon en produccion\Falcon BMS 4.33 U1</path></falcon>
<server refreshrate=“30” port=“53000”><texturehook>false</texturehook>
<keyserver>false</keyserver></server>
<client refreshrate=“30” runserver=“false”><texturehook>false</texturehook>
<server port=“53000”>local</server>
<smoothtextures>true</smoothtextures>
<mipmaptextures>true</mipmaptextures>
<layout>default.xml</layout></client>
<app index=“0”><name>Target Script</name>
<path>C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETScriptEditor.exe</path>
<commandline>C:\Program Files (x86)\Thrustmaster\TARGET\scripts\warthog_BMS_Full_Paddle_swap.tmc</commandline>
<batchrun delay=“”>false</batchrun></app></apps> -
The code you have posted shows a space in the path name, \TARGETScriptEditor.e xe
-
The code you have posted shows a space in the path name, \TARGETScriptEditor.e xe
It was an error on the copy paste to show the content of the YAME64.xml . I checked and appears correct.
-
I think the problem are the spaces in C:\Program Files (x86)
I have not tested, but you could try to change the strings:<path>C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETScriptEditor.e xe</path>
<commandline>C:\Program Files (x86)\Thrustmaster\TARGET\scripts\warthog_BMS_Full _Paddle_swap.tmc</commandline>to
<path>“C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETScriptEditor.exe”</path>
<commandline>“C:\Program Files (x86)\Thrustmaster\TARGET\scripts\warthog_BMS_Full_Paddle_swap.tmc”</commandline>In the next version this is fixed in the code.
-
I think the problem are the spaces in C:\Program Files (x86)
I have not tested, but you could try to change the strings:<path>C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETScriptEditor.e xe</path>
<commandline>C:\Program Files (x86)\Thrustmaster\TARGET\scripts\warthog_BMS_Full _Paddle_swap.tmc</commandline>to
<path>“C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETScriptEditor.exe”</path>
<commandline>“C:\Program Files (x86)\Thrustmaster\TARGET\scripts\warthog_BMS_Full_Paddle_swap.tmc”</commandline>In the next version this is fixed in the code.
Thanks Roccio, seems to work now.
-
Hi all,
I just installed YAME to get a nice working Carapace (Belgian MLU RWR). Sadly, the RWR resolution appears to be rather poor (left), especially compared to what MFDE offers (right):
Is there any way to increase the resolution?
Thank you very much. -
The left images is what bms offers. Should be ok in regards of resolution and is a correct view of The carapace.
Your right image of mfde is not carapace but the ATD.
Yame has that too. With newer symbology or with carapace prio mode (bearing & distance in the box on tje bottom instead of a red line) and / or with carapace labels.
See the manual in the atd chapter for more details. -
Hi Focal
Thanks for answering.
The right image (ATD) was only to illustrate the difference in resolution.
I’m not trying to render an ATD, my aim was to render the carapace scope but in higher res. I understand I have to chose between two options:- Carapace scope in kinda low resolution (limited by BMS)
- ATD scope w/ Carapace labels
I found an atd.png file in the YAME directory. I guess I’ll try to edit it to look a bit more like a Carapace scope, then
-
Is your BMS set to double resolution? That should make the rtt extraction pretty high res.
But don’t expect too high res, I’ve seen a real Carapace scope in the BAF flight sim a few times and it wasn’t very high res eitherWhat do you mean with the ATD file?
Fr the RWR you can select a background image; there’s a real Carpace scope picture I made in there to be used.
Try to load the BAF MLU layout profile that comes with the install to see what I mean. -
Unable to use YAME after installing U5 Falcon crash and YAME freezes.
-
Any logs?
In Yame there are buttons to open server/client/overall log -
I have reinstalled on the clean version of U4 and it works. YAME stopped working when I installed the U5 version and the new Baltic Theater.
-
Have you tried with only u5 without New baltic theater?
And please share The Yame logs after crash occured. -
Yesterday installed U5 and flew a 3ship MP flight for 1,5h in KTO without having issues with BMS or YAME, so possibly Baltic theater issue.
Cant really check anything without config and logs. -
I flew a MP flight of ~2hrs on Balkans using YAME on multiple screens (client only).
All was fine (from the BMS 4.33U5/YAME point of view, that is…. ).No reinstall of the Yame software.
-
Ok guys need your help. I had Yame64 working great for months. Not sure what happened but here is what changed Windows 10 updated and I also installed BMS U5. Now Yame64 is crashing every time I try to launch it. Not sure if it’s a result of U5 or the windows update. When I try to launch the UI open’s a white box then immediately crashes and I get the following message. So what do you guys think? hopefully someone has seen this and knows what I am missing here. I vaguely remember this happing before but I don recall how or what fixed it lol. It doesn’t generate a log I’ve checked multiple time and the log file is empty. Any and all help is greatly appreciated.
-
Ok guys need your help. I had Yame64 working great for months. Not sure what happened but here is what changed Windows 10 updated and I also installed BMS U5. Now Yame64 is crashing every time I try to launch it. Not sure if it’s a result of U5 or the windows update. When I try to launch the UI open’s a white box then immediately crashes and I get the following message. So what do you guys think? hopefully someone has seen this and knows what I am missing here. I vaguely remember this happing before but I don recall how or what fixed it lol. It doesn’t generate a log I’ve checked multiple time and the log file is empty. Any and all help is greatly appreciated.
go to yame installation folder then in conf folder you will find yame64.xml. try to rename it to something like yame64.old and restart program.
-
ok will try that thank you Roccio
-
go to yame installation folder then in conf folder you will find yame64.xml. try to rename it to something like yame64.old and restart program.
Update: So I tried what you suggested and it didn’t work. Nothing changed that I can see. Doing that just created a new yame64.xml file. It is still crashing doesn’t get any farther then the picture above. When I go into event viewer in Win 10 this is what it says so maybe this VCRUNTIME140.dll got corrupted some how? What do you think?
Here is what the Event viewer says:Faulting application name: YAME64.exe, version: 0.0.0.0, time stamp: 0x59afa99e
Faulting module name: VCRUNTIME140.dll, version: 14.13.26020.0, time stamp: 0x5a39fee3
Exception code: 0xc0000005
Fault offset: 0x000000000000ca27
Faulting process id: 0x2e78
Faulting application start time: 0x01d3c3338db496a6
Faulting application path: D:\YAME64\YAME64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 45be4c30-fcfe-4b0f-9975-816802ddd040
Faulting package full name:
Faulting package-relative application ID: -
Update: So I tried what you suggested and it didn’t work. Nothing changed that I can see. Doing that just created a new yame64.xml file. It is still crashing doesn’t get any farther then the picture above. When I go into event viewer in Win 10 this is what it says so maybe this VCRUNTIME140.dll got corrupted some how? What do you think?
Here is what the Event viewer says:Faulting application name: YAME64.exe, version: 0.0.0.0, time stamp: 0x59afa99e
Faulting module name: VCRUNTIME140.dll, version: 14.13.26020.0, time stamp: 0x5a39fee3
Exception code: 0xc0000005
Fault offset: 0x000000000000ca27
Faulting process id: 0x2e78
Faulting application start time: 0x01d3c3338db496a6
Faulting application path: D:\YAME64\YAME64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 45be4c30-fcfe-4b0f-9975-816802ddd040
Faulting package full name:
Faulting package-relative application ID:can you post your layout xml that you are using? you will find in layiut folder