Tried this - no joy
- Sharpe
Can you show a screenshot of your YAME64 folder?
Sent from my LG-H818 using Tapatalk
Tried this - no joy
- Sharpe
Can you show a screenshot of your YAME64 folder?
Sent from my LG-H818 using Tapatalk
How about you try to run yame from the actual folder instead of the shortcut? Perhaps the shortcut points to an exe in the wrong folder.
Sent from my LG-H818 using Tapatalk
Running BMS in fullscreen or windowed mode?
What are your YAME settings for the texture extraction, 3d hook?
Have you tried toggling the antialiasing setting for YAME?
Can you specify which nvidia drivers you are using now?
Sent from my LG-H818 using Tapatalk
Which windows version are you working on?
Also, have you tried running YAME as admin?
Sent from my LG-H818 using Tapatalk
Running (a more recent version of) YAME on the creators update perfectly here.
Whether you have restore point on or not, you should be able to revert to a previous version of Windows. Start > Settings > Update & security > Recovery. Click the get started below “get back to a previous version of Windows 10”.
Not sure of it will be flawless of course
Sent from my LG-H818 using Tapatalk
Are you running BMS as administrator? There might be some user permission restrictions on the bms registry keys
Like I said, the registry is involved. Create a new calibration and follow what I explained in the post above. Just change the folder in which you will drag the file to the one you mentioned.
If you want to do it the registry way, you have to find the correct subkey and add your old calibration.
iirc, there is a registry entry created for those calibration files so just drag and drop won’t work. Easiest (no registry edits) would probably be to create a new calibration and save it. Then rename your old calibration file to the new name and drag it in C:\Program Files (x86)\HOTAS\calib and overwrite the existing file.
thanks Focaldesign,
the culprit is indeed window aeroglass.
now after turning it on, it seems to work.however, I get a lot of “BMS stopped working” appcrash quite often, and sometimes the extraction does not work, I get blank MFD instead.
If that happens, I have to restart the computer to make it works again.
are there some setting to make yame works better?
please advise.my system is i3 o/c to 4ghz.
8gb ram
gtx 970
win 7/64.
BMS runs fine without YAME?
Do you use the hook for the textures?
Sorry if this is a noob question:
I have just installed yame64 v1.1.0 and VC++Res for VS2015.I can run it and see the yame64 suite window,
then my mouse left and right button stops responding,
I can move the mouse but that is it.
And I can not close yame, now it seems my windows hangs,
even ctl-alt-del does not work.what is wrong here?
please advise.
What OS are you on?
Have you installed the 64 VC++Res 2015 package?
What hardware + drivers do you have in that system?
Iirc, particalsys.ini is per bms install, you cannot change it per theater.
Lightning has collected the definitions in the tdf file, might help you out: https://svn2.assembla.com/svn/lightningstools/trunk/F4Utils/Terrain/TheaterDotTdfFileReader.cs
Not sure if all are covered.
Lightning’s tools might help you out: http://svn.assembla.com/svn/lightningstools/trunk/F4Utils/Campaign/Save/TwxFile.cs
I fly BMS single-player mode in 64 bit; however I also enjoy flying multi-player on the VG server (32bit). I am therefore trying to install both YAME64 and YAME32 on the same client PC. Installing YAME32 after installing YAME64 corrupts both programs. Perhaps because YAME32 automatically installs in the same folder as YAME64 with no install options to choose another. YAME32 returns the following errors:
MSVCP140.dll missing from your computer
VCRUNTIME140.dll missing from your computerLog folder is empty. I tried installing YAME64, then remaming YAME64 folder, then installing YAME32. YAME64 will then run, but not YAME32. Any suggestions how to overcome this problem?
For the missing dlls for YAME32, you need to have the visual studio 2015 x86 files installed, not only x64.
Install path error between versions will be added to the issue tracker, but you should be able to run BMS 32bit with the YAME64 version.
IIRC it cant find the mouse device which will cause this crash
He can commit to 3D though so in 2D mouse device is found and in use.
Did you copy the install from a previous installation or was it a fresh install?
Also, have you gone through all the settings as input devices, graphics settings etc and made sure they are valid?
Check if the bms window is not opened off screen, via the cockpit display extraction in the bms launcher. Should be at 0,0 iirc.
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.
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.
Does you server have a sound card? If not, set up a virtual one.
Most probably it also does not have a dedicated graphics card, check this thread: https://www.benchmarksims.org/forum/showthread.php?t=24564
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.
I’m running YAME client on a laptop without BMS, displaying all gauges and MFDs/DED via the 3D hook. So there should be no need for a BMS install on the client side.