YAME64 suite
-
I started to use Yame when I downloaded Ice’s profile about a month ago. At that time I was getting about 60+ FPS. Today I updated my Win10 to the fall edition and guess what, the FPS dropped to between 4 and 10 FPS. I then reloaded the game with the only difference being that I did not use Yame and the FPS was 70. Obviously, you cannot fly at less than 10 FPS so my question is-is it me or Yame? I reloaded the driver software for the Nvideo card with no change in the FPS. Any thoughts? :mad::mad::mad::mad:
-
I started to use Yame when I downloaded Ice’s profile about a month ago. At that time I was getting about 60+ FPS. Today I updated my Win10 to the fall edition and guess what, the FPS dropped to between 4 and 10 FPS. I then reloaded the game with the only difference being that I did not use Yame and the FPS was 70. Obviously, you cannot fly at less than 10 FPS so my question is-is it me or Yame? I reloaded the driver software for the Nvideo card with no change in the FPS. Any thoughts? :mad::mad::mad::mad:
i don’t nave the fall update, bit on my dev pc with cu 1703 all Works well. the other test pc is now offline as i sas not Able to install win 10 cu
-
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
-
-
Running BMS in fullscreen or windowed mode?
The screen with the gauges on them is running in fullscreen with visable, masked and antialiasing checked. The CPO map screen only has masked and antaliasing checked.What are your YAME settings for the texture extraction, 3d hook?
YesHave you tried toggling the antialiasing setting for YAME?
Not yet. Based on another thread, I am not using any antialasing from the video card, only from the game and apparently YAME.Can you specify which nvidia drivers you are using now?
Driver Version 23.21.13.8800 dated Oct 12, 2017 from Nvidia.I just ran BMS again but this time I unchecked antialiasing within the Yame setup for the right screen (gauges) and for the CPO and still got only 6 FPS. No joy.
-
My advice is to never update to the latest version of Windows right away, unless you like testing stuff for M$. I had issues when Win10CU first came out and I had to revert to Win10AE so I’m not surprised that people are having issues with Win10CU Fall Update. If YAME was working fine before, but it isn’t now after the Fall Update, then it’s clear where the issue lies.
-
I have temporarily put YAME aside because of low FPS and reloaded MFDe and placed the gauges in ICE’s Helios profile. I am now back to 60 FPS. Of course, I have lost the use of the map in the central pedestal. So for now, its MFDe until Windows 10 fall edition and YAME can play nice together.
-
Why not just roll back the update?
-
never did that and it sounds scary.
-
As long as you’ve not installed anything important between your Windows update and now, you should be alright. Windows should’ve created a restore point when it upgraded….
-
Roccio and Focaldesign
I don’t know if I am alone with respect to the FPS slow down in YAME, but if either of you need additional info to work on this issue, please let me know.126/10/2017 16:01:41: *************************************************
26/10/2017 16:01:41: * YAME64_d3d: InitInstance called *
26/10/2017 16:01:41: *************************************************
26/10/2017 16:01:41: Loaded original dll: C:\WINDOWS\system32\d3d9.dll
26/10/2017 16:01:42: Direct3D9 created.
26/10/2017 16:02:19: Created render target
26/10/2017 16:02:19: Created offscreen surface
26/10/2017 16:02:19: StartMFDThread–------------------
26/10/2017 16:02:19: MFDThreadFunc…--------------------26/10/2017 16:02:19: Created file map
26/10/2017 16:02:19: Mapped file
26/10/2017 16:02:19: StartSendingData…
26/10/2017 16:07:16: refcount == 1
26/10/2017 16:07:16: …StopSendingData----------------------
26/10/2017 16:07:16: Texture closing handles.
26/10/2017 16:07:16: Unmapped file.
26/10/2017 16:07:16: Closed handle.
26/10/2017 16:08:46: Reset YAME D3DDevice
26/10/2017 16:19:17: YAME64_d3d: ExitInstance called.
26/10/2017 16:19:17: CloseAll-----------------------26/10/2017 14:49:21: ***************************************************
26/10/2017 14:49:21: * YAME client START *
26/10/2017 14:49:21: ***************************************************
26/10/2017 14:49:22: Data extraction: true
26/10/2017 14:49:22: Texture extraction: hook
26/10/2017 14:51:14: Unable to load briefing file.
26/10/2017 14:52:19: Client::run ended. -
Read ths on the Nvidea forum:
Microsoft is aware of isolated instances of performance impact to frame rates of some apps that utilize DirectX 9 and is working to resolve this in a future Windows Update. This post will be updated once the Windows Update solution is available.
In the meantime, you can work around this by disabling fullscreen optimization for the affected app, or by running the game in windowed mode. To disable fullscreen optimization:
1. From the Start Menu, right-click the affected app and select More > Open File Location. File Explorer will open to the app’s location.
2. In File Explorer, right-click the app and select Properties.
3. On the Compatibility tab, check the box to Disable fullscreen optimizations.However, I did this to Yame and BMS, but the FPS was still below 10. Nevertheless, maybe this is a clue to the problem?
UPDATE: I rolled back the Win10 fall update and all is now well with YAME.
-
Exactly, I wish that OSB could not be run with mouse…, this option is probably not in YAME 64?.
-
Exactly, I wish that OSB could not be run with mouse…, this option is probably not in YAME 64?.
Sorry, Idon’t understand what you are requesting…
-
Sorry, Idon’t understand what you are requesting…
Sorry, I know…, Google translator:mad:, but I already explain, touch screen - click with OSB - is OK, normal screen - mouse will not insert in - and do not click like in touch:mad:.
But ride, no?:D:D:D
Regards Maestro. -
Sorry, I know…, Google translator:mad:, but I already explain, touch screen - click with OSB - is OK, normal screen - mouse will not insert in - and do not click like in touch:mad:.
But ride, no?:D:D:D
Regards Maestro.MR. Roccio, I found, you can click the mouse, you just have to set the window mode in the BMS.
-
But does it not lose focus from BMS? Do you not notice the engine sound getting quieter?
-
yes, giù can click mouse and you should not loose focus on bms wundow
-
Confirmed, I use BMS in “-window” mode always and my touch screen with Helios works without a problem.
Only downside is that sometimes the toggle to enable/disable 3D mouse doesn’t seem to work and when I press something on my touchscreen, it also clicks where the mouse pointer is in my pit. Accidentally fired EPU because of it once -
On another note ! Is a second set of digital engine instruments (for engine two) in the future of this super program ?