denali

I won't have time to look at it, but Windows 10 Game Mode will be available in an insider preview released sometime today. Apparently, it pushes background tasks to a couple of cores and leaving the bulk of the cores 100% dedicated to the game. Reports are a 3 to 5% framerate improvement and smoothing. Sounds very promising. Techradar gives info on how to sign up for insider previews. Keep in mind if you install a preview, to go back you may have to completely reinstall Windows. Game Mode will not be in general release until sometime in spring. http://www.techradar.com/news/windows-10-game-mode-6-of-your-burning-questions-answered https://www.rockpapershotgun.com/2017/01/25/windows-10-game-mode-explained/ http://www.windowscentral.com/windows-10-game-mode http://www.theverge.com/2017/1/25/14390990/microsoft-windows-10-game-mode-explanation

Any particular areas of SoCal, Arizona, or Colorado you'd like to see, those are the areas I have. I also have Utah and New Mexico in an older night lighting format, and all of California in the new lighting method over home grown photoscenery. (Pssst, california scenery subsections come with complete lighting for California).

https://store.ultimatevfr.com/ UltimateVFR is 1m satellite photoscenery color corrected by a professional videographer (B Movie Credits). Night lighting is excellent and enjoyable, shows up at a distance, and is aligned up-to-date with roadways. It also includes aligned autogen. And vegetation aligned with the vegetation in the photoscenery. Water maps based on USDA maps. Nobody else has all of it in the same place. I recommend trying out California Central or SoCal. He is currently working on rolling out Version 2.0 of the US. In fact, let me know if there is something you would like me to screen shot and I'll get them up here.

Or, game mode might be implementing directx 12 capabilities in previous directx versions ... which I'd heard about from a good source.

I have been using Process Lasso manually to put P3D in higher CPU and memory priorities, and to take away CPU 0 and 1 from other programs so P3D can run it's thread management with plenty of room. Placebo? I'm wondering if Windows game mode might have something to do with Windows legacy of very poor fiber management. They promised all kinds of changes with Windows 10 that did not materialize. The "game mode" market label is just a way to bring attention to the fact they may have finally fixed it. I keep dreaming.

Love LM's thoughtfulness and responsiveness (yes, i see them as very responsible). by Beau Hollis » Thu Jan 12, 2017 7:29 pm All the known SLI issues are specific to Alternate Frame Rendering (AFR). If SLI is on, but AFR is not being used, you will likely not encounter the issues. Beau Hollis Prepar3D Rendering System Lead Now to refresh my understanding of different SLI modes, and AFR.

I am on driver 376.33. and P3D Professional 3.4.18.19475. Windows 10 Pro v1607 Build 14393.576. i3770k @ 4.4GHz and 2x EVGA GTX 780 SC. 32GB RAM/12GB Ramdrive using Primocache. EVGA Precision X v.6 is showing both cards being utilized. However, on only one monitor at 1080 I am only getting a very steady 30fps. GPU usage between 65 and 85 percent equalized to both cards, both of them getting hot in parallel graphs. Going to 3 monitors at 5760 I get a kinda stuttery 28fps, I don't know why. I start AS16 with ASCA and the stutter goes away. These are not my best framerates; I can usually get 45fps on 3 screens. *shrug*. But it's smooth, and until now I didn't notice the decreased framerate. I have most things maxed, I'm in over Santa Barbara in a Carenado TBM, over Ultimate VFR Southern California (AWESOME! especially NIGHT LIGHTING) late afternoon, scattered clouds, a front in the distance. So maybe I am seeing a performance hit. I see waves lapping photoscenery as I'd expect. Just restarted after entering ShowDeviceLostWarning=0 in the P3D.cfg, same startup situation, my current default. Visibility much less now, <5nm I think, same framerate. little bit of stutter. hrmmnnn Looks like that front moved in on top of me. Looking at wundermap, yep it did. I'm wondering where I'm being frame limited now. Out of the front, smooth again. only 30fps though.

Just to chime in. I'm on 2x 780s and an ol' 3770k cpu. I had issues, including the flashing and wave problems. Then I reinstalled everything, including windows, and on all current OS, drivers, and P3D, everything is smoother than it's ever been and without issues. I say this not to create conflict with those that are having issues, But to offer HOPE that somehow those having issues can resolve them. And cherry on top, LM IS listening and doing what they can. Good luck everyone. Also, all the chatter about Nvidia dropping SLI support is just nonsense. They are not droppling dual SLI support, not even for their newer cards. They are dropping the capabilities for more than 2 cards in SLI, and it's not just them. There is actually little to be gained in 3x SLI or more and the market for it is tiny. It's a failed experiment, and the direction for development is not longer to explore that path. Mobo manufacturers are following. It's not just NVidia, it's also Microsoft. But dual SLI will still be very much supported, and in fact in 3 different modes, which my feeble busied mind has no clarity to write about now, but shows promise, and is what they actually need to do to reach their goals in VR development. You'll need SLI in the future for top of the line VR, the demands ... demand it. So SLI is NOT going away. Even if XPlane isn't supporting it. (BTW, the new XPlane runs like crap on my old system ... No SLI)

There is a tool that will allow one to test an upgrade before committing it. It installs the software in a "sandbox", where the executable and all processes ran in it are isolated from all other processes and files so that you can see what is installed and what happens. Once you're comfortable you can commit those changes. But if anything is wrong the installation you made is safely separate. You can keep that installation, all the changes that were made, and still go back to the before state. I haven't tried any other's, for windows anyways, but the one I use is Sandboxie. https://sandboxie.com/ They have a "free" version, to try, where you are only allowed to run one process from each sandbox/ all sandboxes you've created at a time. If you're considering testing an update, this might be the way to go. I haven't tried it with driver updates, I wonder if it would work.

That's because it's Not A Game!

From what I've read, if you delid the 7700k, add a dab of liquid metal, temps can be lowered by 30C, and OC's on water can get over 5.2 stable, and that's out of the gate, just getting started. Since the current P3D is thread manager limited on Core 1, The only thing that's gonna help Scotty's "moar power!" orders is GigahUrtz, and this CPU is very promising in that way. I am considering it.

I'm sorry I don't have time to look into why my SLI works at the moment. I am being completely honest. I had an issue with SLI about 3 weeks ago. I posted here about it, it was in a thread about Nvidia's driver release at the beginning of December; it killed my SLI. About a week or 10 days ago I made a clean Windows installation, Installed NVidia Drivers and the latest Prepar3d, and now SLI works. With my "data", please understand that I do not see the reason for all the griping about Prepar3d software, when from my "SLI functioning perspective", the evidence that Prepar3d has an issue with SLI does not hold up 100%. Now my debugging eye might point to that I am on an older 3770 and Maxwell 780 chipsets ... and it makes me wonder if Prepar3d maybe did something in "stub code" that affects the latest Nvidia cards, or latest CPUs .... In other words i see a differentiation between my experience and what others *may* be. But the chance of Prepar3d code being ruinous for SLI is no more than that of Intel (chipset drivers ... updated by Intel through Windows update) Microsoft, or Nvidia updates. There needs to be further differentiating by the Administrator of Prepar3d on the various differentiated platforms before we automatically incriminate Lockheed Martin. IM-HO. FYI, my debugging "instincts" are actually pointing to the chipset updates. No evidence other than the chain of experiences ... Microsoft did a big update before Nvidia did, where things borked. I don't actually know anything about the update, just a sense of how my system felt, with the 3 or 4 vms I run on it, immediately after. I find that getting into feelings about who to blame don't really help me focus on what actually happened and how to fix it. It's not very motivating to work solutions with that method either. I just simply made a pot of coffee one day, looked for notes on how to do a Windows clean install, and got to work. Sucks, but so does farming (unless you're just a nephew visiting ... or really like farming. Sometimes I think I really would).

I have a clean Windows and P3D build. Before this I was having an SLI issue after installing Nvidia's latest. 2 GTX 780's, fyi. Everything is fine in the new build for me.

Rottweilers or Dobermans?

I'm wondering if those that are having SLI issues are on Windows 10, thus bringing in a DX12 factor, if LM has been tinkering with DX12 enhancements in their updates but not yet turned them on completely. Would that break a less than Windows 10 SLI?

For those of you whose SLI is borked, there is a new NVidia hotfix released 22, Dec v.376.48. I would try it but based on the issues others are reporting I have the willies about installing it. I think Battlefield series has been related to P3D in the past IIRC, and this update does fix something for BF. I'll report back if I take the dive. http://nvidia.custhelp.com/app/answers/detail/a_id/4288

I had an issue with SLI *BEFORE* installing the latest P3D. My problem started after installing Nvidia's new driver. But I was also having issues with Windows, chipset drivers specifically, and bus issues regarding data transfer between drives. After a clean install of Windows 10, latest (same as before) Nvidia drivers, and latest P3D, the SLI issue seems resolved. Please remember the third leg of the stool is Microsoft. I will take a look again when I get a chance to be sure I wasn't hallucinating my problems going away. I'll ask Santa for clarity.

I have a clean installation with 2 780 and looking at GPU Z as well as a EVGA precision X it looks to me like both cards are sharing the load with this version. Is there any other way I can test? Frame rates and fluidity are great.

Maybe I'm laying out an idea here that would allow working with older addons. Not looking to make a general DLL translator, but one at lest specific to one addon, if not P3D only. In other words, the API expects a certain format for the responses in a DLL. If a 64bit module can figure out where the responses are coming from in the 32bit module, a data file, then maybe it is possible for the 64bit module to make the connection to the data itself.

The addons that do burrow into P3D memory space for data or to change anything are the ones that you will have to repurchase, for certain. I am still not sure that it is impossible to open a 32bit DLL for a specific 32bit api, if it follows the rules and keeps within the menu of the 64bit api (I wouldn't expect that many changes), and use it in a 64bit memory space, using a 64bit "translator" for the DLL (every time I read about this I think about what a solution may look like). At any rate, if a scenery company is still alive and wants to keep being relevant it surely won't be that painful for them to recompile a few files, not very wise for them not to IMHO. (I don't like boxes or rules, especially when all the rules in software are made-up by somebody to begin with). To elaborate. Would it be possible to have a 64bit dll that interfaces with a 32bit dll, not to connect to a running version of the 32bit dll, but to port the available calls to 64bit, and run that in the vast 64bit space. This would be done on the load, but speed at runtime would not be affected.

Strange. I have a completely new build: Windows, Nvidia, and P3D up to yesterday. I had a problem with SLI not working before, but now I am getting amazing smoothness. Placebo because of new system? But missing SLI is very noticeable. And the waves issue went away too. You know, MS is a big cog in this machine too ... In fact I am noticing other "stutters" in the Windows itself in this brand new build. Windows itself is not as fluid, and chrome is particularly sticky. *shrug*

I have a clean Windows 10 and most recent NVidia driver on 2 GTX 780s, running 5760 x 1080, and it's smoother than it's ever been. I don't have a display telling me SLI is on yet, but it's the best it's ever been, like butter sliding down glass.

You're awesome!

The MD5 on all of the files, scenery included, are different than the MD5 on the files I downloaded a few days ago. Are we sure the client is all that is needed?

Wait Ed. That's not this newly released version of P3D. I'm sorry yes it is. Got confused with the '19' in there somewhere.