YAME64 suite
-
New version 1.2.0 just released!
Go to first post for infos!Hope you enjoy this one!!
:bdance::drink:
:rtfm:
If you report issues, please mention the following:
- YAME version (x64 or x86)
- YAME configuration (local extraction, client-server, client-only, hook, nohook, …)
- YAME layout
- Falcon theater
- Instant action, dogfight, TE or campaign
- Steps to reproduce the bug
- OS version and 64 or 32 bit
- graphical card and driver versions
- VC++Res’15 version
-
OK good job guys.
Just updated my visual c++ ver. 14.0.23026 x64
I did not uninstall the previous version but just ran the YAME set up (x64), completed but, program does not start.
Have set to run as admi, tried shortcut and the exe directly. just nothing happens…Resolved:
Uninstalled previous version and reinstalled new. -
Yippee!!
-
This post is deleted! -
I had 2 strange things happen after upgrading to 1.2:
- The launcher kept setting my theatre to Israel. I had been playing Nordic, and it would repeatedly launch me back in Israel.
- None of my flight instruments were showing data, nor was I getting any textures extracted (e.g. no MFDs, no RWR)
Like Badger, I set YAME to run as an admin.
For now I have successfully reverted to 1.1. I noticed the hook log said something about failed to load configuration file, but nothing interesting other than that.
-
Can you try uninstalling v1.0 or 1.1 entirely plus check there is no more d3d9.dll hook file in the bms /bin/data/x64 or x86 folder and then install 1.2?
-
I did a clean install of 1.2, and I’m having a problem with the touchscreen. I’m running BMS in fullscreen and using YAME’s d3d extraction. When I tap on an MFD’s OSB on the touchscreen, BMS minimizes.
I’m running x64, client only, KTO, testing in the Navigation TE, with a GTX1080 (378.66 drivers), VC++ version 14.0.23026.
The layout:
<windows><window><name>YAME</name> <width>1920</width> <height>1080</height> <posx>0</posx> <posy>1080</posy> <fullscreen>true</fullscreen> <border>false</border> <visible>true</visible> <background>000000</background> <antialias>true</antialias></window></windows> <misc><version>1.2</version></misc> <left_mfd zindex="0"><width>436</width> <height>436</height> <posx>60</posx> <posy>590</posy> <visible>true</visible> <window>YAME</window> <type>default</type> <bezel>true</bezel></left_mfd>
This happens if I’m not running Helios. If I am, the transparency layer at the bottom of my profile stops it. So it looks like YAME thinks I’m clicking the desktop instead of an OSB.
-
That’s indeed unwanted behaviour. In the clients/misc tab, do you have touchscreen checked or unchecked? Try doing the opposite and see if it changes anything.
-
Hi there and first of all, BIG TIME THANKS!
I´ve experienced same isue as the already stated : not working EXE after installing on top of v1.1.0. I uninstalled (but left a backup copy of the old YAME).
With the new installation from scratch it all worked fine… and I tried to use the old YAME, and is still working (that helped me out to copy the old screen configuration by having both YAMEs opened at the same time).Finally, an interesting thing I found: both YAMEs can work with either version of the HOOK dll (d3d9.dll), but I just left the latest one.
No better performance in FPS so far… but really nice improvements on many areas.
Single bug I found: while testing the Center pedestal blk 60: I set up CP60_page_next & prev on the callbacks… and while flying, I push it next several times, wich ended showing a couple of strange pages and finally closing YAME… it just fainted. I have to test it out more times to see it in detail.
Setup:
Win8.1 x64
YAME 64, local with hook (fullscreen or windowed)
Layout: nothing fancy…just the basic engine, RWR, DED, MFDs, Alt and Mach… and also the above mentioned Center pedestal blk 60 for testing purposes.
Theater: Korea stock and Balkans 4.33.3.5 (actual)
Instant action… basicaly
Steps… just use callback NEXT for the CPedestal, passed several screens, and yame was closed.
Graph: ATI HD 7970 with Catalyst 3.251.9001.1001-140704a-173665E-ATI (pretty old, but dedicated for my old reliable ATI card with 6 screen outputs)
No clue on how to know the VC++ version.THANKS!
-
Can you try a TE instead of instant action. Officials IA is not supported in BMS anymore.
Do you have single keys, key combo’s or DX mapped to the callbacks? -
Can you try a TE instead of instant action. Officials IA is not supported in BMS anymore.
Do you have single keys, key combo’s or DX mapped to the callbacks?I thinks I did already in campaign… but have to recheck specifically again to be sure. What happened now is that doing a pae back it goes to a corrupted page with a blue box or something similar… and page next crash YAME. Sometimes it does directly without changing pages.
Callbacks are CTRL+ALT+F or CTRL+ALT+G
-
I thinks I did already in campaign… but have to recheck specifically again to be sure. What happened now is that doing a pae back it goes to a corrupted page with a blue box or something similar… and page next crash YAME. Sometimes it does directly without changing pages.
Callbacks are CTRL+ALT+F or CTRL+ALT+G
Can you send me the screenshots of the corrupt pages? I’ll try to reproduce with your key bindings.
-
That’s indeed unwanted behaviour. In the clients/misc tab, do you have touchscreen checked or unchecked? Try doing the opposite and see if it changes anything.
It was checked. I just tried it unchecked and it didn’t change anything.
-
It was checked. I just tried it unchecked and it didn’t change anything.
Will look into this. -Ice halped us a lot with the touch screens, so maybe he can point you in the right direction.
-
Thank you. I should also say that I’ve tried it with both a solid black background and with a window mask (in the clients\windows tab) and neither made a difference.
-
Ok, Used TAC is Maverick training… but this also happens in Camp and so on.
DATA screen seems OK:
After “CP60_page_prev” I go to MFD… this is the weird one with the blue corrupted box
Another “CP60_page_prev” and FUEL page is OK
Another “CP60_page_prev” and PLAN page seems OK
Between this pages I can move NEXT or PREV… no problem.
The YAME crash happens when I try to reach MAP page, whichever wat I try:Note.- Sorry, error message in Spanish equals the famous “YAME64.exe stop working…”
-
It was checked. I just tried it unchecked and it didn’t change anything.
can you also send the yame64.xml in the config folder please?
-
can you also send the yame64.xml in the config folder please?
As requested:
<apps version="1.2"><falcon><windowed>false</windowed> <path>D:\Games\Falcon 4\Falcon BMS 4.33 U1</path></falcon> <server refreshrate="30" port="53000"><texturehook>false</texturehook> <keyserver>true</keyserver></server> <client refreshrate="30" runserver="true"><texturehook>true</texturehook> <server port="53000" sync="false">local</server> <smoothtextures>true</smoothtextures> <mipmaptextures>true</mipmaptextures> <layout>rogue.xml</layout> <usetouchscreen>true</usetouchscreen></client></apps>
-
Same thing , CP60 crash when accessing map. And that blue box . Other pages are ok?.. It doesn’t depend on mission type TAC/CAM.
After cycle prev/next , (because you can’t go next to map->crash), data screen have bugged hsi also , like it copy half hsi from of old screen over new hsi.
It seems pedestal CP60 need some more work … but is 95% finished … can’t wait
Regards
-
This is quite strange. We tested a lot and have no issues.
Thank you all, we will found and fix this annoying bug.