YAME64 suite
-
Hi
Hello
I’ve got an issue with Yame64 on Irakos theater
I got 50% chances to get black MFDs on on this theater on first launch (IRC with HAF F-16).
If I restart BMS the issue disappears.
On other theaters i got no issue
Any ideas ?
Thanks in advanceNever tested Ikaros theater, but next time you have the issue try to save the yame logs (found in yame install folder \logs) and send to me. Plus it would be great if you can add more informations. Like are you using yame in server/client or client only, are you using dll hook or default extraction.
Thank you
-
I’m running on Client Only
Reproduced today, the log files are below :
client_log :09/01/2018 19:05:26: *************************************************** 09/01/2018 19:05:26: * YAME client START * 09/01/2018 19:05:26: *************************************************** 09/01/2018 19:05:26: Data extraction: true 09/01/2018 19:05:26: Texture extraction: hook 09/01/2018 19:07:06: Unable to load briefing file. ```log :
09/01/2018 19:07:06: 33U1x64
Screenshot : ![](https://img15.hostingpics.net/pics/710658IMG20180109191602453.jpg) Thanks
-
Hi
Hello
I’ve got an issue with Yame64 on Irakos theater
I got 50% chances to get black MFDs on on this theater on first launch (IRC with HAF F-16).
If I restart BMS the issue disappears.
On other theaters i got no issue
Any ideas ?
Thanks in advanceI have the same prob since last YAME upgrade and I didn’t figure it out yet. It happens only with all HAF F16 models. All other models have no issues. Yame logs don’t point the issue. That’s why I don’t use YAME with Ikaros. Maybe it’s a model’s graphics issue…
-
I have the same prob since last YAME upgrade and I didn’t figure it out yet. It happens only with all HAF F16 models. All other models have no issues. Yame logs don’t point the issue. That’s why I don’t use YAME with Ikaros. Maybe it’s a model’s graphics issue…
could be the extraction coordinates that are hot round for that particular Aircraft. i should install ikaros to test.
-
ddoc,
Thanks for the reply. I looked in the YAME /conf/ subfolder like you directed me to and neither of the files they told me to copy were in there. I uninstalled YAME, completely deleted everything YAME related, and redownloaded it. I set it up like last time, though this time everything works just fine! I can launch BMS from YAME without any problem. Awesome, one more baby step complete! Some day I’ll have the mini pit put together and running correct.
Thank you for your time!
-Crow -
EDIT: I found the AVTR light, apparently it’s not on the “others” tab. It’s still weird that YAME64 crashes when clicking the “others” tab on my end.
Thanks for this excellent tool!
Cheers, Uwe
-
could be the extraction coordinates that are hot round for that particular Aircraft. i should install ikaros to test.
rttTarget not 600 i think, looks like YAME works with 600
i saw this in NORDIC EF2K with 1024, i changed it to 600, but still floating with TrackIR in the EF.
-
EDIT: I found the AVTR light, apparently it’s not on the “others” tab. It’s still weird that YAME64 crashes when clicking the “others” tab on my end.
Thanks for this excellent tool!
Cheers, Uwe
If the ‘other’ tab makes it crash, there’s something wrong with a gauge in the xml that is part of the other tab.
Might want to open your config xml and delete all gauges that are set via the other tab and try to set them again then via the UI. -
rttTarget not 600 i think, looks like YAME works with 600
i saw this in NORDIC EF2K with 1024, i changed it to 600, but still floating with TrackIR in the EF.
YAME will work with everyrttTarget size specified in aircraft data file. The problem is with DLL hook that will work with only 600 (or 1200 if you set double rttExtraction size). Try not using hook (if enabled).
-
Sorry if this has been asked before, didn’t want to read 127 pages
Does anyone have the issue where you start yame, and it immediately and forever uses 50% cpu? Seems a bit high, even when it’s not doing anything yet.
-
Hi Xtacy,
Yes. Read my first post on page 117, followed by Ice’s and others. It seems to be a combination of issues between Nvidia drivers and the latest version of WIN10.
Johan
-
I’ll try rolling my nvidia driver back, but im on win7 so i’ll just be hopeful
-
It will work till Windows updates you again…… I’ve done everything I can think of to turn it off even in registry. It will reboot, BSOD then reboot again with Windows update turned back on… Do I own this software or not? TOTAL BS.
Sorry, ranting. -
Hi Wicked,
I was able to disable Windows updates in WIN10 by going into “Services”, then to “Windows Updates” which you can disable in the menu. Nothing has been installing automatically on my system since then, and YAME works great.
-
I did the same thing but it blue screened and changed the setting after a reboot. But! I will try again.
-
No Joy! The service is turned off and has been. I uninstalled all the recent updates (it would let me) and rebooted. I went back to the updates page to try and get the last one and as I was watching it the updates previously uninstalled popped back up as installed again….
-
that s strange. i have Windows 10 1079 and latest Nvidia driver and no issue for me. if you open the process Explorer (ctrl alt del) what it says about yame cpu and gpu usage?
-
Yeah, this issue seems to be hit and miss… not everyone is affected.
-
Greetings. Would like to thank everyone involved for this great piece of software.
Have been a long time user of the MFDE tool in conjunction with the BMS display extractor. I’ve started to use YAME also for MFD extraction and it works great. Perfect alternative to the BMS extractor tool.
Again, a great big thanks.
Kind regards. J. -
Around 40% on CPU usage when it is running. The mouse lags and basically everything lags… Hate windows.