YAME64 suite
-
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! -
This is not a yame problem but a windows monitor arrangement problem
Best way to set up additional monitors is up and/or left of the main monitor. That way, when any program changes your resolution of the main monitor, the others don’t get shifted.
So in Windows monitor setup, drag your second monitor above or left of your primary monitor. All coordinates for windows are relative to the top left point of the primary (x:0; y:0). If you place your second monitor below, say for example aligned with the left side of the primary, the starting coordinate of your second monitor is x:0/y:1050 (height of your primary). So e.g. YAME places a window at that coordinate. But when your primary monitor changes resolution because the 2D UI of BMS is max 1024x768 or something and you use it in full screen mode, the second monitor now starts at x:0/y:1024. So the YAME window is now 1050-1024=26 pixels lower then you anticipated.
Quick workaround, but you won’t get BMS 2D in fullscreen then, is active the ‘windowed’ checkbox on the YAME main tab above the launch bms button on the left side. -
So, I was doing a bit of housekeeping and uninstalled YAME from my BMS rig
I deleted the left over folders and used ccleaner to get rid of leftovers registry links.Later I reinstalled YAME but, as soon as I click on the shortcut to start it, it immediately stops responding.
No log is generated.Win 7 64 bit machine.
Any thoughts on what might be causing this?
-
Check yame64.xml in conf folder and set x and y in ui section to 0. Just a try
Inviato dal mio Y635-L21 utilizzando Tapatalk
-
no luck
<apps version=“1.2”><falcon><windowed>true</windowed>
<path>C:\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></apps> -
Well cleaned out my entire registry and did a fresh install…same problem.
grasping at straws, I changed compatibility to Vista service pack 2 and it worked, WTH??
I’m using Win 7
-
did you try and start the game from inside the game folder ???
-
There is no problem starting the sim.
Not sure what you’re asking -
This post is deleted! -
This is not a yame problem but a windows monitor arrangement problem
Best way to set up additional monitors is up and/or left of the main monitor. That way, when any program changes your resolution of the main monitor, the others don’t get shifted.
So in Windows monitor setup, drag your second monitor above or left of your primary monitor. All coordinates for windows are relative to the top left point of the primary (x:0; y:0). If you place your second monitor below, say for example aligned with the left side of the primary, the starting coordinate of your second monitor is x:0/y:1050 (height of your primary). So e.g. YAME places a window at that coordinate. But when your primary monitor changes resolution because the 2D UI of BMS is max 1024x768 or something and you use it in full screen mode, the second monitor now starts at x:0/y:1024. So the YAME window is now 1050-1024=26 pixels lower then you anticipated.
Quick workaround, but you won’t get BMS 2D in fullscreen then, is active the ‘windowed’ checkbox on the YAME main tab above the launch bms button on the left side.Thanks a lot!The problem solved finally after I chang my monitor to LG34UC88,it seems perfectly fit~
THX bro! -
Hello
Sorry if this has been answered before, this thread is way too long…
I installed yame64 on my win10 computer and bms runs on same computer
Everything works as expected when I launch yame64,yame client and bms
I can see the instrument being extracted and rendered normally apart from the ADI and stby ADI of wich I see only the bezels and the flags but no “adi ball” displayed
Any idea why?Thanks