YAME64 suite
-
As Roccio said, if you’re using any of Ice’s layouts uncheck masking on the windows tab. It will make you assign a background color and I usually choose black. Helios will cover it up anyway.
-
yes, in some update ( don’t know if windows or video driver) we encountered a big problem with masking. i don’t think this feature is usefull as you can run helios in front of yame, so inthe next version i would prefear to remove it.
need to understand what can be the positioning problem. maybe is related to high dpi monitors? -
Hey Roccio,
I have both antialiasing and masked window disabled.
At the moment I don’t encounter any performance issues but
yame isn’t as smooth as it used to be.By the way Mike.
I had similar problems to yours. I solved them by
by right clicking into yame icon > properties > compatibility tab > display dpi settings to application.
After that the next time u run yame you drag each window to your preferred monitor. Then right click on it and then click : remove border, align to monitor, fill in monitor, save layout and then you close it. That way u get the exact coords. After you have all your windows where u want them you go on the main page and have borders antialiasing and mask disabled.I hope u get all of your problems solved real soon.
-
Hi Varhn:
That’s exactly how I had my system set before YAME crapped out on me a couple of weeks ago and, now post recovery - after reformatting my main Drive and starting over. Its funny because having I reached out to Wicked last night to offer some help on the same issue, I went into Desktop Display and moved my fourth display (dropping it down and to the right, adjacent to my other monitors) and voila, the YAME grid filled the entire 4th monitor screen as well. Its all about setting the right coordinates so that all the displays you want to use fall within the grid so that you can position the gauges wherever you please. I’ve got it running perfectly again. In fact last night, I flew my first campaign mission since getting back in the pit. I fragged a 12 ship package, an OCA Strike out of Seosan targeting NK Haeju AB. SEAD took out the SAMs, Escort dealt with MIGs and, my AI Wingmen and I dropped our GBU 24’s and obliterated Haeju. TRaclIR, Voice Attack, Jet Seat, TM MFD’s and, my recently acquired Viper Gear ICP - all worked flawlessly. It was total immersion and fantastically gratifying. I still have figure out how to fine tune my aging Cougar TQS - maybe a Hall’s update. We’ll see.To Roccio and Fd:
I really do feel Win 10 and/or Nvidia auto updates are wrecking havoc on YAME and Helios. Since reformatting my main drive and restoring to Win 10 V1703 Build 15063.966 and Nvidia Driver 382.05, I haven’t had any problems. Note that I permanently disabled future Win and Nvidia updates. FYI: although I’ve got Helios working again, I haven’t set it up. I’ve decided to table it for the time being pending release of your next YAME version. If you guys can replicate most of Helio’s extractions and, create a functional stand-alone turn-key F-16 (and F-18) pit, it would be beyond awesome. It would be a game changer. Again, I would be honored to help you test the beta. -
I don’t how that smiley popped up but, it’s the Superbug I was referring to.
-
Hi Varhn:
That’s exactly how I had my system set before YAME crapped out on me a couple of weeks ago and, now post recovery - after reformatting my main Drive and starting over. Its funny because having I reached out to Wicked last night to offer some help on the same issue, I went into Desktop Display and moved my fourth display (dropping it down and to the right, adjacent to my other monitors) and voila, the YAME grid filled the entire 4th monitor screen as well. Its all about setting the right coordinates so that all the displays you want to use fall within the grid so that you can position the gauges wherever you please. I’ve got it running perfectly again. In fact last night, I flew my first campaign mission since getting back in the pit. I fragged a 12 ship package, an OCA Strike out of Seosan targeting NK Haeju AB. SEAD took out the SAMs, Escort dealt with MIGs and, my AI Wingmen and I dropped our GBU 24’s and obliterated Haeju. TRaclIR, Voice Attack, Jet Seat, TM MFD’s and, my recently acquired Viper Gear ICP - all worked flawlessly. It was total immersion and fantastically gratifying. I still have figure out how to fine tune my aging Cougar TQS - maybe a Hall’s update. We’ll see.To Roccio and Fd:
I really do feel Win 10 and/or Nvidia auto updates are wrecking havoc on YAME and Helios. Since reformatting my main drive and restoring to Win 10 V1703 Build 15063.966 and Nvidia Driver 382.05, I haven’t had any problems. Note that I permanently disabled future Win and Nvidia updates. FYI: although I’ve got Helios working again, I haven’t set it up. I’ve decided to table it for the time being pending release of your next YAME version. If you guys can replicate most of Helio’s extractions and, create a functional stand-alone turn-key F-16 (and F-18) pit, it would be beyond awesome. It would be a game changer. Again, I would be honored to help you test the beta.YES TO THIS!
-
Hey Roccio,
I have both antialiasing and masked window disabled.
At the moment I don’t encounter any performance issues but
yame isn’t as smooth as it used to be.By the way Mike.
I had similar problems to yours. I solved them by
by right clicking into yame icon > properties > compatibility tab > display dpi settings to application.
After that the next time u run yame you drag each window to your preferred monitor. Then right click on it and then click : remove border, align to monitor, fill in monitor, save layout and then you close it. That way u get the exact coords. After you have all your windows where u want them you go on the main page and have borders antialiasing and mask disabled.I hope u get all of your problems solved real soon.
Trying this.
-
Who here has YAME running well and also uses a Rift or WMR HMD like the Samsung Odyssey or Vive? I’ve moved on from thinking YAME is causing the issue of not placing the layout on another monitor by using coordinates and not dragging. As I’ve stated in the past, YAME will load onto the second monitor after being started and stopped and the main monitor and then changing the coordinates to the second monitor. However, it will only run once like that. After the first run it will lock up upon starting and then crash…. Working on it.
-
YMMV, Windows 10 1803 update breaks YAME for me again. It comes with Nvidia 390.77 drivers.
Gonna mess around with reverting to 385.xx drivers as this fixed it before.Edit: Yep, 385.41 and everything went back to normal.
PITA that can’t figure out why newer drivers won’t work. -
i have just finished to install 1803. will see if there are problems.
-
I can not use pedestal moving map in new theaters. What are the requirements for map loading in size and format?. I tried to add maps from WDP for new theaters as Spain but when I doing ramp start, when I select map on pedestal a warning appears saying “Iberia map not loaded”, for instance. I reduced the map to 1024x1024
Any clue? -
you can check map dimension from the Korea map (2048x2048x24 PNG) i’m using 4096x4096x32 map in ISRAEL without problems.
Take care of this:file type: PNG
file location: YAME\gauges\cp60\maps –- IF YOU ARE USING REMOTE CLIENT SHOULD BE ON REMOTE CLIENT
file name: <theater name=“”>.png & <theater name=“”>White.png –- AS indicated from the error dialog!!!</theater></theater> -
Thanks Francky I think you are right.
I it does not work Chicho you can send me the map files and I will correct them for you.Now I’m busy to try to resolve a problem that the new Windows10 has with OpenGl and fullscreen windows.
-
Thanks Francky and roccio.
I have done exactly what you say but I continue with the same problem. Nordic theater works fine except BE is on left botton corner of the map all time. I have check in settings and BE posit is correct. Spain POH theater does not load the map properly named. All others theaters work fine. Thats the reason why I ask you for the correct format and size. Anyway roccio, I will send you the maps I have for theater with problems.
Regards. -
You’ve got to roll back WIN 10 and Nvidia drivers and, then permanently disable future updates until there’s a suitable fix.
-
Did you get only “map not loaded” message?
If you try to copy and rename the Korean map as Spain map do you get the same warning? -
Did you get only “map not loaded” message?
If you try to copy and rename the Korean map as Spain map do you get the same warning?I will test
-
Forgive me for asking
I also asked this question on the VP forumHope that someone can help me with this,
I have two pcs
One with BMS and YAME64
Other just YAME64
Both are connected with a crossover cableWhen I click the server tab on the first pc it shows the local and public ip as: 0.0.0.0
What could be the reason that YAME64 does not see those?
Both pc have differend ip’s and they see each other.Maybe I have to add more detail, but mainly it is the server ip question.
Both are W7 64bit and main does work as a client when I test that optionThanks in advance
-
Forgive me for asking
I also asked this question on the VP forumHope that someone can help me with this,
I have two pcs
One with BMS and YAME64
Other just YAME64
Both are connected with a crossover cableWhen I click the server tab on the first pc it shows the local and public ip as: 0.0.0.0
What could be the reason that YAME64 does not see those?
Both pc have differend ip’s and they see each other.Maybe I have to add more detail, but mainly it is the server ip question.
Both are W7 64bit and main does work as a client when I test that optionThanks in advance
No idea on why it shows all zero’s. Roccio will be more suited to reply on that.
But if you know the correct IP, you can just use that in the client exe -
No idea on why it shows all zero’s. Roccio will be more suited to reply on that.
But if you know the correct IP, you can just use that in the client exeHave you configured static (and hopefully different :)) IPs on both PCs? Do both PCs have a single network card / connection?
All the best, Uwe