YAME64 suite
-
Hi Focaldesign:
Every thing is available in the extraction and globals tabs. Now, a lot of work ahead using this fantastic product along with ICE’s layouts. You guys are the best. Tell Roccio he’s in my thoughts and, to get well and come back soon.
It’s been an adventure.
Mike
-
Hi fjp:
I believe Focaldesign found a fix for our problem. Please read our recent posts for a blow-by-blow. But, as Folcaldesign suggested: Go into YAME’s directory and open YAME64.XML with notepad editor and change the <clientonly>true <clientonly>line from true to “false”. That’s assuming its your problem as well.
Let me know if its fix for you as well. Best of luck.
Mike</clientonly></clientonly>
-
Thanks very much for all your help !!!
-
Hello mikemadmax, can you share your YAME Config file so I can see what you did. Its still not working for me : (
-
I keep getting an error (yame has stopped responding etc,) and it names VCRUNTIME 140.dll
I have replaced it, now it tells me the application cannot start correctly,
This started when I exited the game, and YAME was still minimized. The "stopped responding " error ccame up while it was still minimized, and from that point forward it would never run again. Initially it would act like it had loaded, but remain minimized, and useless - I couldn’t start it or the client - I then reinstalled it (after uninstalling it and all of the folders that it needed.) and that is when the Stopped Responding error began. 10 hours so far and no gain.
Need some more help please,
I7 920 @3.2, 6 gig ram, 660ti, 27 main, 24 Dell touch. -
I keep getting an error (yame has stopped responding etc,) and it names VCRUNTIME 140.dll
I have replaced it, now it tells me the application cannot start correctly,
This started when I exited the game, and YAME was still minimized. The "stopped responding " error ccame up while it was still minimized, and from that point forward it would never run again. Initially it would act like it had loaded, but remain minimized, and useless - I couldn’t start it or the client - I then reinstalled it (after uninstalling it and all of the folders that it needed.) and that is when the Stopped Responding error began. 10 hours so far and no gain.
Need some more help please,
I7 920 @3.2, 6 gig ram, 660ti, 27 main, 24 Dell touch.Can you check recent program updates? I’ve had a similar issues about 6 months ago and it was due to a recent VisualStudio 2015 redistributable 64 bit update. Rolling back to a previous version fixed it, and a later update a month or so later didn’t have the issue.
-
I suspect that its something like what happened to yours. Issue I’m having is that there is a problem registering the .dll
First off, I didn’t realize that 32bit .dlls go into syswow64 bit folder, and 64 bit dlls go in system32
Once I figured that out I made a bit more progress, but not over the hump.
Trying system restore now, fingers crossed. -
Hi guys!
I’m trying to run YAME with Helios but I can’t get YAME masked, program says it is unable to do it first time and the next times it goes unmasked but doesn’t display any messages, just the loading mask message…
I can’t also get Helios in front of YAME, so it doesn’t matter that I start YAME and then Helios (with the always on top option enabled) it gets back and can’t see Helios…
You can see an example of this here…
Can anyone help me?
Thanks. Best regards
-
Is it possible for the YAME64 F-16 analog HSI indicator to have the HDG CRS knobs increment/decrement in 5-degree units in addition to the current 1-degree units without creating a workaround button solution via HELIOS?
I looked at the ‘HSI.xml’ file in the ‘YAME64/gauges’ folder and the HDG/CRS buttons listed have these callbacks: SimHsiHdgDecBy1, SimHsiHdgIncBy1, SimHsiCrsDecBy1, SimHsiCrsIncBy1.
As a test, I tried editing the ‘HSI.xml’ to overwrite the original …By1 callbacks with the 5-degree incr/decr callbacks: SimHsiHeadingDec, SimHsiHeadingInc, SimHsiCourseDec, and SimHsiCourseInc.
But then when I test the HDG/CRS knobs in game the knobs still will only incr/dec in 1-degree units.
I can probably comeup with a workaround solution using HELIOS but would like to know if a YAME solution is available for 5-degree incr/decr of the HDG/CRS knobs.
-
@Greyfox-111sqn
not sure if this will work for you:open YAME CLIENT>WINDOWS tab
select RIGHT SCREEN window and then click EDIT GAUGES button
when gauges show, right-click on any blank area of gauge desktop to show menu,
select CREATE MASK menu option
right-click once more, then select CLOSE then YES to save changes,
Close YAME
Restart YAME
then launch Start YAME Client to test -
Can you check recent program updates? I’ve had a similar issues about 6 months ago and it was due to a recent VisualStudio 2015 redistributable 64 bit update. Rolling back to a previous version fixed it, and a later update a month or so later didn’t have the issue.
Well that didn’t work. If it is the c++ library it brings up a question. The version of c++ that I have installed is 14.0.24215. Could you tell me what version you have? I am getting the same error, vcruntime140.dll = although the verbage is different now
-
So along the path of a jacked up vb 2015, I went to control panel and selected to “REPAIR” it.
It’s working now, but I’m afraid to reboot.
BTW, somehow the version I have is newer than the version available via google search and a MS search.
14.0.24215 vs 14.0.24212
Well, off to scorch some clouds - fingers crossed -
There’s something funny going on with Greyfox’s setup. There are weird graphics issues with the Helios Profile Editor, his Helios profile does not appear on top of YAME even when YAME is started first, and it seems like he has issues with masking as well.
Here was the instructions I’ve given, which was the old-school way of forcing a mask:
@-Ice:Here’s how you force YAME to create masking:
Start YAME
On the UI, go to CLIENT -> MISC -> LOAD LAYOUT and load my Ice1ScreenSetup-v121.xml file
Click APPLY
Go to CLIENT -> GAUGES -> FLIGHT INSTRUMENTS
Click APPLY
Go to RUN and click START YAME CLIENTThere will be a small window that will come up with some %% numbers as YAME makes the masks. Windows may even report YAME as not responding, just tell it to wait for YAME to respond. As soon as YAME finishes its voodoo black magic mumbo-jumbo, you should see the gauges come up.
I’ve created a short video showing my YAME profile going from masked to no-mask (with orange/red background) then back to masked. I’ve also shown the %% numbers that I was talking about and you will note that my touchscreen went black…. once masking is complete, any subsequent activation of the profile will be quicker, no need to calculate masking with the && number window. This will persist until the profile is changed in some way, forcing YAME to create a new mask.
-
That didn’t work. A couple of starts then back to the same error. I may just put this off for a couple of weeks and do it on a fresh install on a new puter, but I’d like to find out why and what the fix is now so if it happens on my new box I’ll know what to do about it.
If anyone would check and report on the version of VisualStudio 2015 they have, and whether or not it is giving them problems it might help a lot.
Cheers
Tril -
Hi guys!
I’m trying to run YAME with Helios but I can’t get YAME masked, program says it is unable to do it first time and the next times it goes unmasked but doesn’t display any messages, just the loading mask message…
I can’t also get Helios in front of YAME, so it doesn’t matter that I start YAME and then Helios (with the always on top option enabled) it gets back and can’t see Helios…
You can see an example of this here…
Can anyone help me?
Thanks. Best regards
Hi mate,
I would point my main attention onto why Helios can’t go “always on top” because that should work and also fix the issue for the Yame background then.
Other then that, can you check the images or gauges folder (forgot which one) for an “.rng” file? That’s the mask file Yame generates. Try deleting that, then try moving one gauge 1px or so in the edit gauge mode so the layout is not exactly the same as before anymore. Then try checking mask again and start client, see f that helps. -
Is it possible for the YAME64 F-16 analog HSI indicator to have the HDG CRS knobs increment/decrement in 5-degree units in addition to the current 1-degree units without creating a workaround button solution via HELIOS?
I looked at the ‘HSI.xml’ file in the ‘YAME64/gauges’ folder and the HDG/CRS buttons listed have these callbacks: SimHsiHdgDecBy1, SimHsiHdgIncBy1, SimHsiCrsDecBy1, SimHsiCrsIncBy1.
As a test, I tried editing the ‘HSI.xml’ to overwrite the original …By1 callbacks with the 5-degree incr/decr callbacks: SimHsiHeadingDec, SimHsiHeadingInc, SimHsiCourseDec, and SimHsiCourseInc.
But then when I test the HDG/CRS knobs in game the knobs still will only incr/dec in 1-degree units.
I can probably comeup with a workaround solution using HELIOS but would like to know if a YAME solution is available for 5-degree incr/decr of the HDG/CRS knobs.
Hi Fletch, that would indeed be an option, to change the mapped callbacks in the HSI.xml
The reason why it still won’t work then, is not YAME’s fault but a BMS setting you need to set.
Also see -Ice’s explanation on his blog: For the Altimeter and HSI functions to work, the falcon bms.cfg file must be edited and this entry added at the first space at the top: set g_nKnobAccelerationDelta 300 -
So along the path of a jacked up vb 2015, I went to control panel and selected to “REPAIR” it.
It’s working now, but I’m afraid to reboot.
BTW, somehow the version I have is newer than the version available via google search and a MS search.
14.0.24215 vs 14.0.24212
Well, off to scorch some clouds - fingers crossedI had exactly the same issue for a while. Repair fixed it, after reboot shit hit the fan again. Drove me nuts and brought me really close to throwing it all through my window.
After an update few weeks later, all kept working all of a sudden… -
Like I said, something funny going on with his setup and I can’t put my finger on it…. he’s using two different AMD GPUs, not Crossfired, but he’s having consistent artifacts when using Helios Profile Editor on his touchscreen and he needs to drag the window to his other screen then back to his touchscreen to “refres” the Helios window. Dragging the mouse around over the Helios window produces weird artifacts as well. Maybe a GPU driver issue? Or GPU incompatibility?
He sent me his Helios profile and all parameters regarding “always on top” was correct, loaded his profile on my PC and tested it, Helios does stay on top. I initially kept saying it’s not a YAME issue and I still doubt that it is… but even if he can set a mask on the YAME profile, it’s only a workaround and he really can’t use the Helios profile in it’s full purpose as all other panels (side consoles, system panel, comms, etc.) will all appear UNDER YAME so they won’t be very useful.
-
Like I said, something funny going on with his setup and I can’t put my finger on it…. he’s using two different AMD GPUs, not Crossfired, but he’s having consistent artifacts when using Helios Profile Editor on his touchscreen and he needs to drag the window to his other screen then back to his touchscreen to “refres” the Helios window. Dragging the mouse around over the Helios window produces weird artifacts as well. Maybe a GPU driver issue? Or GPU incompatibility?
He sent me his Helios profile and all parameters regarding “always on top” was correct, loaded his profile on my PC and tested it, Helios does stay on top. I initially kept saying it’s not a YAME issue and I still doubt that it is… but even if he can set a mask on the YAME profile, it’s only a workaround and he really can’t use the Helios profile in it’s full purpose as all other panels (side consoles, system panel, comms, etc.) will all appear UNDER YAME so they won’t be very useful.
That sounds like a possible GPU driver issue indeed, regarding the artefacts. But would surprise me that such issues could also be responsible for not allowing a mask or having a certain application always on top. Strange stuff indeed :s
-
Well, I did have temperamental results with my monitor setup which depended on my cable connection from monitor-to-PC… they didn’t like HDMI connections and would sometimes show up and sometimes Windows would have no clue one or both monitors were there at all… changing to DVI-to-DP and my Targus docking station and it works reliably 100%!! And we’re not even talking about driver issues or the like here… plus I also had lower framerate results when I tried my 2GPU setup.
However, he’s working with AMD cards so I couldn’t help him much with that… I remember some people (was it you, Focal?) had issues with certain AMD drivers and had to use older drivers…