YAME64 suite
-
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…
-
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…
indeed, still have.
all crimson drivers above 17.1 give me a black bms window and even with lower versions I can’t force AA via AMD but need to set it in BMS -
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.Hi!, thanks for the help, but I can’t find any “.rng” file in neither of the folders… Do you know the name of it?
I think I have a problem with both programs, Helios get me artifacts when I execute the profile manager and YAME can’t mask, I have two possible solutions:
- YAME can mask
- Helios gets in front
As YAME at least displays a message saying It hasn’t been able to mask, then that’s why I’m trying with YAME first, but as I say I haven’t been able to do any of them yet…
Regards.
-
Hi!, thanks for the help, but I can’t find any “.rng” file in neither of the folders… Do you know the name of it?
I think I have a problem with both programs, Helios get me artifacts when I execute the profile manager and YAME can’t mask, I have two possible solutions:
- YAME can mask
- Helios gets in front
As YAME at least displays a message saying It hasn’t been able to mask, then that’s why I’m trying with YAME first, but as I say I haven’t been able to do any of them yet…
Regards.
Look in yame\images folder and delete the file with the name of the Windows you want to mask.
-
As YAME at least displays a message saying It hasn’t been able to mask,
Then you are not following the steps above correctly. When it does that, YAME is expecting to find a mask file but it doesn’t find any so it runs the profile without a mask.
-
Look in yame\images folder and delete the file with the name of the Windows you want to mask.
I found it and deleted it. Then I restarted YAME, same issue and file appeared again…
-
@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 testThanks for the help, I’ve done this too but when I exit the edit gauges screen it freezes, and when i select create mask before exiting it does nothing, just blinks for a moment and the same image appears…
Regards.
-
Then you are not following the steps above correctly. When it does that, YAME is expecting to find a mask file but it doesn’t find any so it runs the profile without a mask.
Thanks Ice, which steps? The installation ones?
Regards.
-
The one above in red. If you are doing exactly that (video would be great!) and YAME still comes out with no masking, then I’m at a total loss… maybe try copying what I’ve shown in my video (YAME Masking) and see if that works.
-
Hi
I have a problem with the new version, I don’t know why but the map of the CDP is not showing (totally black), it is not a problem of file (no message), and everything works fine unless the map (no option for color or night mode). This is very strange, no matter the theatre… Any idea ?
PS : OK, resolved, I don’t know why but the “showmap” option in the layout file was set on “false”, I don’t know how this happened…
-
Hello gents,
Yesterday I updated Nvidia drv to the most recent and same YAME 64 everything 64bit on 64bit win 7 BMS 433.3 IKAROS 4.1 . Afterwards only in ikaros theater any TE I make and run no MFD RWR extraction like no RTT is exported. I had no such issues with the previous version of YAME. Other theaters run just fine! I’ll install the previous version again to check if it is an NVIDIA conflict…I don’t know …Any ideas?
Best regards, -
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 300Now that you mention it I do vaguely remember reading about setting g_nKnobAccelerationDelta 300 in the falconbms.cfg file, will give that a try, but I did manage to create a working HELIOS solution for HDG/CRS knobs too without the need for editing the falconbms.cfg file per -Ices suggestion.
thanks Focaldesign
-
Hello gents,
Yesterday I updated Nvidia drv to the most recent and same YAME 64 everything 64bit on 64bit win 7 BMS 433.3 IKAROS 4.1 . Afterwards only in ikaros theater any TE I make and run no MFD RWR extraction like no RTT is exported. I had no such issues with the previous version of YAME. Other theaters run just fine! I’ll install the previous version again to check if it is an NVIDIA conflict…I don’t know …Any ideas?
Best regards,Can you post (or send me in pm) the yame log file? Tank you
-
Can you post (or send me in pm) the yame log file? Tank you
Yeap roccio, as soon as I am on PC.
Thanks -
For the mask problem: when hit rum client button, does the rgn file generate?
-
Hello guys,
A video showing YAME64 Version 1.2.1 working on second touch screen with Helios.
Is 14 minutes cause I decided to include my AAR mission with it.
Enjoy.
Pika -
For the mask problem: when hit rum client button, does the rgn file generate?
I’ll try when I get home, but look at what I have discovered…
It masks when the app is in the same screen and it doesn’t when u get the app to the other screen?
Regards
-
I’ll try when I get home, but look at what I have discovered…
It masks when the app is in the same screen and it doesn’t when u get the app to the other screen?
Regards
Thanks for the report, I will look into this.