YAME64 suite
-
I have a second instance of YAME stopped working.
When double clicked the main window shows for a split second > disappears > program is active in the background but does nothing and can not be approached.
Only solution is uninstall > install.
There was nothing special about when or what caused it to behave like that after working without a problem for a few days.
I have seen similar behaviors when an antivirus is triggered, but my Kaspersky gave no notice and doesn’t have any log about it. -
I have a second instance of YAME stopped working.
When double clicked the main window shows for a split second > disappears > program is active in the background but does nothing and can not be approached.
Only solution is uninstall > install.
There was nothing special about when or what caused it to behave like that after working without a problem for a few days.
I have seen similar behaviors when an antivirus is triggered, but my Kaspersky gave no notice and doesn’t have any log about it.Check yame64.xml in cfg folder that windows pos is valid. Sometimes it goes to -32000 and so it is not visible
-
I had a virus warning and download abort by Avast for the 64 bit version. Now I cannot even reach the download file from the Yame Download Page
False positive I guess (just like virus scanners leave the user with a false sense of security IMHO, so at least there’s symmetry :D)
Can you whitelist the file in your AV software? If you download with chromium / chrome the file will be v-checked automatically, and even if it thinks the zip / exe contains a virus you can restore the download using a browser function.
All the best, Uwe
-
I’m noticing a stutter in my MFD displays every few seconds. I’m running the MFD’s on a second client machine (using hook method), and using two USB 2.0 to VGA adapter dongles to drive the MFD screens. Are these likely the cause of the stutter and would an upgrade to USB 3.0 dongles solve this (or switching to additional video cards)? My client PC motherboard is not USB 3.0 compatible, but I assume there are PCI-E cards out there that could provide the USB 3.0 capability.
I’m afraid I can’t give you a useful answer. I have never used USB monitors so I can’t tell if that’s the cause or not.
-
Stupid question, but can YAME be made to start stuff like TARGET where the program itself has to be started, a profile loaded, then “ran” to combine the stick and throttle into one virtual controller? Or stuff like FRAPS that has the UAC pop-up?
If you mean you want to start target from within Yame, that’s indeed possible.
If you mean you want to start Target and have it automatically load a profile and have it run, I don’t know because I don’t use Target. Maybe is the exe supports commands, like BMS does by having a link to “bms.exe -window -ef”, then it should be possible.
I don’t understand what you mean with FRAPS UAC pop-up. I just start Fraps from the run tab and then minimize it. -
Check yame64.xml in cfg folder that windows pos is valid. Sometimes it goes to -32000 and so it is not visible
Just checked the yame64.xml I kept before I uninstalled and that is exactly what it shows.
Thank you.
-
I’m noticing a stutter in my MFD displays every few seconds. I’m running the MFD’s on a second client machine (using hook method), and using two USB 2.0 to VGA adapter dongles to drive the MFD screens. Are these likely the cause of the stutter and would an upgrade to USB 3.0 dongles solve this (or switching to additional video cards)? My client PC motherboard is not USB 3.0 compatible, but I assume there are PCI-E cards out there that could provide the USB 3.0 capability.
Do you also notice the stutters when running anything else on those mfd screens? Like when playing a movie or something?
Also, as far as I remember those USB vga adapters tend to use cpu resources, maybe this is worth checking as well. Cpu throttling might cause some stutters too.
If you have plenty of bandwidth left on those USB 2.0 ports, switching to USB 3.0 won’t make a big difference with USB 2.0 adapters. -
False positive I guess (just like virus scanners leave the user with a false sense of security IMHO, so at least there’s symmetry :D)
Can you whitelist the file in your AV software? If you download with chromium / chrome the file will be v-checked automatically, and even if it thinks the zip / exe contains a virus you can restore the download using a browser function.
All the best, Uwe
Thanks Uwe, used Chrome to download and switched off Avast as a precaution!
-
Do you also notice the stutters when running anything else on those mfd screens? Like when playing a movie or something?
Also, as far as I remember those USB vga adapters tend to use cpu resources, maybe this is worth checking as well. Cpu throttling might cause some stutters too.
If you have plenty of bandwidth left on those USB 2.0 ports, switching to USB 3.0 won’t make a big difference with USB 2.0 adapters.I just installed a second video card and decided against the USB 3.0 dongle resolution, and indeed resolved the MFD stutter. So at least for me, multiple video cards are a better solution than USB video dongles for this software.
-
If you mean you want to start target from within Yame, that’s indeed possible.
If you mean you want to start Target and have it automatically load a profile and have it run, I don’t know because I don’t use Target. Maybe is the exe supports commands, like BMS does by having a link to “bms.exe -window -ef”, then it should be possible.
I don’t understand what you mean with FRAPS UAC pop-up. I just start Fraps from the run tab and then minimize it.Yes, I want it to start TARGET, I’ve already figured out how to keep my profile loaded at TARGET startup, but I still have to press the green “play” button to run my TARGET script. I’ve looked at the manuals and there’s nothing about command-line parameters for TARGET. As for FRAPS, it does a UAC pop-up for me each time I start it…
Another option then: is there a way to start the YAME suite and have it start the client automatically? And maybe even minimize the YAME suite window automatically?
-
A request regarding the current HSI:
The HSI has the right cardinal white line obscured by the flag’s arm making it very difficult to put the RMI needle at 90° when performing an IFR right arc during an approach. -
A request regarding the current HSI:
The HSI has the right cardinal white line obscured by the flag’s arm making it very difficult to put the RMI needle at 90° when performing an IFR right arc during an approach.Can you explain with the words used in Red Dogs chart tutorial and BMS manual? I don’t understand “right cardinal white line” and “RMI”. Do you mean the course deviation indicator and station bearing pointer?
-
Can you explain with the words used in Red Dogs chart tutorial and BMS manual? I don’t understand “right cardinal white line” and “RMI”. Do you mean the course deviation indicator and station bearing pointer?
1. On the outer bezel of the HSI there are 8 small white lines spaced every 45° that point towards the major/ cardinal directions.
The one that points towards 90° (to the right) is obscured when the engine is on in the YAME HSI version.2. RMI = Radio Magnetic Indicator = station bearing pointer.
The small arrow head at the outer ring of the HSI that points towards the TCN station when the instrument mode knob is on TCN.As for its importance…there are two ways to do an arc:
1. turn the HSI towards the station > fly straight until CDI moves > move needle 10° > fly straight > 10°…
2. Keep the RMI at 90° or 270° all the time. The easiest and simplest. -
1. On the outer bezel of the HSI there are 8 small white lines spaced every 45° that point towards the major/ cardinal directions.
The one that points towards 90° (to the right) is obscured when the engine is on in the YAME HSI version.2. RMI = Radio Magnetic Indicator = station bearing pointer.
The small arrow head at the outer ring of the HSI that points towards the TCN station when the instrument mode knob is on TCN.As for its importance…there are two ways to do an arc:
1. turn the HSI towards the station > fly straight until CDI moves > move needle 10° > fly straight > 10°…
2. Keep the RMI at 90° or 270° all the time. The easiest and simplest.I fly arcs the same, just place the SBP on 3 or 9 o’clock. That works even with the analog HSI for me.
I’ll add it to the todo list though to try and get the flag a bit more to the side. Do note, this is based on a real picture, so on some HSI’s it must be the real case that the flag arm is obscuring that part a bit. Although IRL you can look at it a bit from an angle to see the line behind it maybe. -
Hey, thx for the nice tool
and im happy with the 32bit clinent, so i can use the CPD on my tablet W10/32bit.
Here my CPD background testso now i need some buttons … hehehe, 22 and 4 rocker… (The virtual keybord will not work)
I played little with the ICP files, but i will not send to BMS, i will send to the CPD
for the MISC(INSTR/FUEL) section we can use your “ICP-thingy”. MBY in a extra frame.What is your cpd resulution? i worked on 600x800(900x1200) my BG is in 1050x1680 for a 900x1200cpd.
THX
Mapi -
Just bumping my question:
@-Ice:Another option then: is there a way to start the YAME suite and have it start the client automatically? And maybe even minimize the YAME suite window automatically?
Also, I would like to request a new feature: the ability to start the YAME Client vie command line parameter or via hotkey. I’d like to be able to put a button on my Helios profile that’ll start YAME and display gauges straight away. Thanks!
-
Need some help. My system is as follows. Win10 64, i7 6700 @ 4Ghz, GTX1060 6gb mem, 16Gb system mem, Vizio 4K UHD @ 4096x2160, ACER 27" Touchscreen @ 1920x1080. I finally got everything working using Ice’s layout as I use his Helios profile. When I say I got it working it worked sporadically. My main screen is on the left and my touchscreen is on the right. The left screen is set to x:0 y:4096 and the right is set to x:4096 y:0. After making these changes I was able to see the layout on the right screen and fly with it using regular extraction. I then went to move the guages around because the original Helios is a little different from mine and then had it fill the monitor which changed to right monitors position y: to 14. Once again it worked, however the next time I ran it it would no longer display the layout on the second monitor. So I went back in to set the right monitor y: position back to y:0 and no joy, setting it back to y:14 brought it back once. Since then it will no longer display on the right monitor.
Obviously many people have it working and I’ve had hell with Helios as well so I’m sure it’s my system causing the issues but I have no clue how to resolve it. Any help is appreciated.Update: I’ve got it working but I have to apply all the gauges before I can adjust them and after that I have to apply them again before I run the client. If I shut it off I have to apply them again upon start up. Are the layouts ever saved? Can I make the file read only?
It looks great though! -
Another option then: is there a way to start the YAME suite and have it start the client automatically? And maybe even minimize the YAME suite window automatically?
Has been noted in the tracker.
-
Need some help. My system is as follows. Win10 64, i7 6700 @ 4Ghz, GTX1060 6gb mem, 16Gb system mem, Vizio 4K UHD @ 4096x2160, ACER 27" Touchscreen @ 1920x1080. I finally got everything working using Ice’s layout as I use his Helios profile. When I say I got it working it worked sporadically. My main screen is on the left and my touchscreen is on the right. The left screen is set to x:0 y:4096 and the right is set to x:4096 y:0. After making these changes I was able to see the layout on the right screen and fly with it using regular extraction. I then went to move the guages around because the original Helios is a little different from mine and then had it fill the monitor which changed to right monitors position y: to 14. Once again it worked, however the next time I ran it it would no longer display the layout on the second monitor. So I went back in to set the right monitor y: position back to y:0 and no joy, setting it back to y:14 brought it back once. Since then it will no longer display on the right monitor.
Obviously many people have it working and I’ve had hell with Helios as well so I’m sure it’s my system causing the issues but I have no clue how to resolve it. Any help is appreciated.Update: I’ve got it working but I have to apply all the gauges before I can adjust them and after that I have to apply them again before I run the client. If I shut it off I have to apply them again upon start up. Are the layouts ever saved? Can I make the file read only?
It looks great though!Can you check if anything is saved to the xml file in your YAME/conf folder when you hit the apply button?
Try running YAME as administrator. -
Very nice tool. Combined with Helios you can have good staff with very good performance. With GTX 1060 and BMS aplication maximum settings no FPS hit.