YAME64 suite
-
check if you have selected masked or antialiased window in yame. if so disable those configurations
Problem solved~!Thank you,bro!
However,if I use the “Launch Falcon BMS” bar to start ,the in game resolution will drop and cant be adjusted.BMS short cut click,everythind goes fine.Any suggestion? -
Problem solved~!Thank you,bro!
However,if I use the “Launch Falcon BMS” bar to start ,the in game resolution will drop and cant be adjusted.BMS short cut click,everythind goes fine.Any suggestion?this seems related to the “full screen optimization” problem.
-
this seems related to the “full screen optimization” problem.
OK~It seems solved!THX again!:D
-
I did a fresh install of BMS and a new install of Yame64 v 1.2 64 bit on a Windows 7 Pro 64 bit system. I also have the VisualStudio 2015 redistributable files installed (both X86 and X64). When I run Yame64 (admin) it crashes with a dialog box.
Problem signature:
Problem Event Name: APPCRASH
Application Name: YAME64.exe
Application Version: 0.0.0.0
Application Timestamp: 59afa99e
Fault Module Name: ucrtbase.DLL
Fault Module Version: 10.0.14393.2247
Fault Module Timestamp: 5adc1d0b
Exception Code: c0000005
Exception Offset: 000000000000fab4
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 2021
Additional Information 2: 2021a6bb3b4d9c0739b3679462c5732e
Additional Information 3: d2d1
Additional Information 4: d2d151e1c83a1b403a9d1e6e8aabbb4dAny ideas as to why this is crashing? There was no log files
-
I did a fresh install of BMS and a new install of Yame64 v 1.2 64 bit on a Windows 7 Pro 64 bit system. I also have the VisualStudio 2015 redistributable files installed (both X86 and X64). When I run Yame64 (admin) it crashes with a dialog box.
Problem signature:
Problem Event Name: APPCRASH
Application Name: YAME64.exe
Application Version: 0.0.0.0
Application Timestamp: 59afa99e
Fault Module Name: ucrtbase.DLL
Fault Module Version: 10.0.14393.2247
Fault Module Timestamp: 5adc1d0b
Exception Code: c0000005
Exception Offset: 000000000000fab4
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 2021
Additional Information 2: 2021a6bb3b4d9c0739b3679462c5732e
Additional Information 3: d2d1
Additional Information 4: d2d151e1c83a1b403a9d1e6e8aabbb4dAny ideas as to why this is crashing? There was no log files
please give more infos of what your system is and what configuration of yame you are using. if you want you can even post your layout and yame64.xml config files
-
from the manual
New in 1.2 is the autodetection of the BMS location, user DTC (used to retrieve steerpoint s & preplanned
threat circles) and keyfile (used by the callback server to send the correct key to BMS, and for the touchable
zones on the bezels/gauges), and theater (for the CP60 moving map).
If you have multiple BMS versions installed on the same pc, you can set desired BMS version.I do have multiple BMS versions installed but, only one of them show up in the drop down box on the global page.
Is there somewhere that I can add these in manually?
-
from the manual
I do have multiple BMS versions installed but, only one of them show up in the drop down box on the global page.
Is there somewhere that I can add these in manually?
not for now. yame search installed bms on the registry, so normally it will find only the “main” installation.
in your case how do you have many installations? and how do you run one or another?
maybe i can add something for the next yame update -
Hi Roccio,
I install and run same YAME32 on a Windows7-64 bit and it works fine.
But when I try to do the same on WindowsXP, I install YAME32 successly, but then it doesn’t run. This is the error. The virtual machine runs on the same Win7 pc.Bye
-
Hi Roccio,
no idea about my problem? Someone uses Yame64 32bit Client on a WinXP S.O.?Thank You in advance
-
My system in a Windows 7 Pro 64bit system and up to date with all updates.
-
Hi Roccio,
no idea about my problem? Someone uses Yame64 32bit Client on a WinXP S.O.?Thank You in advance
sorry, but i don’t have an xp pc, so it’s quite difficult to test. i can only ask what service pack is your, maybe some of the more advanced features are not supported
-
I am using Windows XP SP3 to test YAME64 32 bit Client.
Regards
-
I’m not sure it’s Map-related or Yame-related problem, but I hope somebody can answer this.
The MFD screens is black when I fly on Ikaros map, the other instruments and screens is working perfectly.
KTO, Israel etc good too. Is there any idea, what can be the problem?Thanks in advance.
T -
I’m not sure it’s Map-related or Yame-related problem, but I hope somebody can answer this.
The MFD screens is black when I fly on Ikaros map, the other instruments and screens is working perfectly.
KTO, Israel etc good too. Is there any idea, what can be the problem?Thanks in advance.
Tcan you give more informations? mfd or cp60 is black? what yameconfiguration are you using (same machine as falcon or remote via network)
-
I’m not sure it’s Map-related or Yame-related problem, but I hope somebody can answer this.
The MFD screens is black when I fly on Ikaros map, the other instruments and screens is working perfectly.
KTO, Israel etc good too. Is there any idea, what can be the problem?Thanks in advance.
TOpen instant action and exit. Then fly your mission in Ikaros . Usually that fixes that issue.
-
Thanks guys, seems lgbomber’s trick is working , if I start a dogfigt, the MFD is working, and it will working in campaign too (if I restart the Falcon, I have to repeat this process, but that’s not a big deal). Thank you.
can you give more informations? mfd or cp60 is black? what yameconfiguration are you using (same machine as falcon or remote via network)
Hi. You made an excellent software, I use it a lot, thank you Not sure this helps to track down the error or not, if you need any other file or logfile, just tell me which one.
I have three extra monitor below my main monitor (pic), all connected to my videocard (DVI, display port and HDMI combined). I have 4K monitor, and running the Falcon in window mode.
As you see there is plenty of other instrument, and the engine and fuel gauges are on the same LCD with Right MFD. All other is working only the MFD screen is total black*.I tried to narrow the symptoms:
- this error appeared on Ikaros theatre for me, KTO and Israel work fine.
- if I start the Falcon, and start the campaign, the MFD is black.
- if I start dogfight, then go back to Campaign, the MFD will be OK.
- The CP60 seems OK even if the MFD is black (as I said every other instrument is working right), but if I switch to MFD page of CP60, the whole thing is freeze, all other instrument too. If I exit from campaign, then jump to dogfight, suddenly everything will be OK (without any restart), and will be OK if I went back to campaign.
*correction, it seems the HUD display also black. Didn’t noticed it earlier.
-
I finally got YAME64 to run on Linux / WINE (winehq-staging), everything works quite well after installing vcrun2015 (“winetricks install vcrun2015”) except for the most important bit: display & texture / data extraction
I tried various methods (client / server, 3dhook, non-hook extraction) but none of them showed anything on the extracted gauges. Does anybody know if processes are allowed to access each other’s memory (I guess that’s the method used here) when running in separate wine executables?
I would have posted this question in the Linux subforum here, but sadly we still don’t have one so I’d be happy to hear if anybody has gotten YAME64 to work with a WINE-based Falcon BMS instance. Launching BMS from within YAME64 works just fine, as does editing windows, gauges and so on.
All the best & thanks in advance for any comments!
Uwe
EDIT: Native BMS display extraction works fine within WINE, so it might be just a simple little detail I’m missing here…
-
I finally got YAME64 to run on Linux / WINE (winehq-staging), everything works quite well after installing vcrun2015 (“winetricks install vcrun2015”) except for the most important bit: display & texture / data extraction
I tried various methods (client / server, 3dhook, non-hook extraction) but none of them showed anything on the extracted gauges. Does anybody know if processes are allowed to access each other’s memory (I guess that’s the method used here) when running in separate wine executables?
I would have posted this question in the Linux subforum here, but sadly we still don’t have one so I’d be happy to hear if anybody has gotten YAME64 to work with a WINE-based Falcon BMS instance. Launching BMS from within YAME64 works just fine, as does editing windows, gauges and so on.
All the best & thanks in advance for any comments!
Uwe
EDIT: Native BMS display extraction works fine within WINE, so it might be just a simple little detail I’m missing here…
don’t really know what can be the problem, but i have yame (32 bit) running under wine on my raspberry pi 2. it works even with texture extraction…
-
Thanks for the excellent news Roccio!
Can I use a 32 bit yame64 with a 64bit BMS? Should I install yame32 (:)) into its own WINEPREFIX?
All the best, Uwe
-
New problem here …need some help!
I‘ve builded my dual monitor recently(UPPER:DELL 2209WA 1680X1050 main monitor;UDER:DELL S2240T 1920X1080 tounch screen)
and yame 64 works fine by itself
however,it shows resolution problem,I guess?
I have no ideal whats wrong with my setting,or BMS.exe problem?
THX!