adi518

It's Simconnect halting it. Since P3D, unlike FSX, does not install this component. That's why latest Ezdok update includes the setup file for it.

I'm running 970 SLI too. I do not recommend getting a 970 since the Nvidia fiasco bursted out. Without getting into too much debate, you're getting a 3.5GB card, instead of 4GB. Read more about it in various articles. SLI will not be efficient until LM overhaul their code, while working close with Nvidia. Looks like it's going to take time. I do expect them to accomplish that way before DX12 becomes mainstream.

It's auto initiated when the sim boots.

That's because dx11 tech provides faster rendering techniques. It's all about efficiency.

Guys, this product is the answer to the old 2d clouds tech. No more spinning clouds artifacts. This is utilizing the volumetric tech enabled by DX11. It's an inevitable move into something new and better. This may also pose as a bypass solution to clouds hammering performance in p3d.

I can't stress enough that SFX is becoming more and more incompatible with p3d as new versions of p3d are released. This is something that we don't have much control of. If you want to get it running again, then go back to Win 7 or wait for the developers to come out with a new SFX, or, for the unlikely to happen, which is LM changing something in their code to make it work correctly. The stuff you can find on my site was only good for up-to Win 7 and P3D 2.2. As you can see I state that a Win 8 version is offered as beta only , and therefore not guaranteed to work. Since I'm on Win 8 now, me too, can't use SFX properly now. It's an annoyance, I agree, but again, not much we can do about it.

I'll update that. Thanks.

LM is yet to implement water in all it's glory. The whitecaps 'issue' was raised some time ago and it was told that LM will improve the water and bring back the whitecaps effect. Of course, it won't be looking the same as FSX DX9, because this is a new tech, supposed to be looking MUCH better and act a lot more realistic. I think 2.4 water already look way better than previous versions so definitely, LM is stepping in the right direction, just give 'em time.

You can try the beta package from my website. Basically, with each p3d 2 update, SFX will have more and more issues. Especially, if you use WIN 8 like me. The people who made SFX are working on a new effects framework that will be much more compatible with DX11 titles. I think we can expect it in 2015 as the developers are progressing very slowly, mostly because current SFX works for many, many other titles, meaning they are not rushing to release the new version.

Hmm, I can't recall this problem. Happens with certain aircraft add-on or a global artifact?

Yes, do not confuse SweetFX with Shader. They may resemble each other, but they're two different purposes. As for DSR. With some tweaking it may be able to replace SFX sharpening, but I haven't really tested it to tell. DSR is basically a new method of down-sampling, a mean to reduce jaggies instead of using an AA method like MSAA, SGSS etc'.

Nope. Basically, YMMV when it comes to P3D 2 and SFX. On Win 8, it's even worse because P3D2 will crash upon bringing up the menu bar. There's a totally new effects framework coming soon and that should solve plenty of trouble, including for P3D 2 users. When that happens, I will update this forum and my site accordingly.

Until SLI isn't cleared, we're going to see bad performance in some heavy scenarios. However, I still think single gpu is way unoptimized.

I think this means there's no need for that notebook driver hack anymore.

It has no alternative atm. Nothing even comes close as far as I know.

It's now out: http://library.avsim.net/download.php?DLID=187387 After many months of beta testing, bug-fixes and new features constantly being added, the awesome Maarten Boelens has released the new version of his freeware tool - SimLauncherX. This a complete game changer. No more default FSX/P3D2 interfaces! Just two cool features that pop to mind: - Automatically add Ezdok entries to your aircraft (lens flare enabled!). No more Estonia migration tool or Ezca CFG tool. - C&D ANY aircraft. Never again will you start a flight with your engine running... The list of features is LONG so just grab your copy asap and check it out! Edit by Maarten: replaced the download link by a link to the Avsim library

So aggravating. The controls section is so buggy.. I know there are other, much more pressing issues, but still. It's such a time wasting, agonizing process of re-assigning all keys / deleting conflicting default assignments after a new update (by conflicting, I refer to assignments holding keys preserved for Ezdok). I'm looking at the xml controls file and I can't, for the love of god, figure out how to tweak this thing to a clean state. One thing I noticed, if you damage it somehow.. incorrect syntax or whatever, p3d will call it corrupt and re-create a new one with all default assignments. Searching the controls is even more painful since you can only search for actions, but not for keys, which is far more important. So that's it? no way to remove all keys at once? Mods: looks like a forum bug caused a duplicate. Would you kindly remove the other thread? Thanks.

The right man for the job!

EMT is only required in order to fool ezca cfg to add the camera entries to aircraft folders in p3d.

I noticed the fps counter keeps coming back although I have hideinfotext=1. :\

Ok.. some rumors de-mystified: 1.17 works perfectly fine under p3d 2.3 and win 8.1. However, this is the situation.. a lot of people are installing p3d on a fresh win 8.1, meaning without installing fsx first. What does it do? it creates a problem, where simconnect isn't installed nor gets installed by the p3d installer. Therefore, LM has included a few simconnect setup files in a folder called 'redist' in p3d root folder. Inside of it, there are few versions of simconnect. You have to install the latest one (sp2) in order to regain functionality for Ezdok, but wait that's not all. You also need to create a simconnect.xml file and put it where your dll.xml and exe.xml are. Then, your Ezdok will work. Look for my thread with detailed explanation.

From what I understand the improvement in 980 is mostly power usage. So, pretty much same performance, using less wattage. Cool, but not enough to replace my watercooled SLI.

Sweet, thanks for the heads up.

Oh well. Turns out I found the solution to the "mystery". Apparently, sometimes, P3D2 installer won't install SimConnect, god knows why (?). As a result, things like Trackir and Ezdok just won't work. Unfortunately, I had to go through perils until I found the solution. Here goes: 1. Install latest SimConnect from p3d root/redist. The one inside FSX SP2 (there's a lib folder in there, inside it an msi installer file). This will fix your Trackir. 2. Open Notepad and copy-paste this into it: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect Server Configuration</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv4</Protocol> <Scope>Global</Scope> <MaxClients>64</MaxClients> <Address>0.0.0.0</Address> <Port>9017</Port> </SimConnect.Comm> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>Auto</Protocol> <Scope>local</Scope> </SimConnect.Comm> </SimBase.Document> Save as 'SimConnect.xml'. Throw this file into 'C:\Users\<user>\AppData\Roaming\Lockheed Martin\Prepar3D v2'. This will fix your Ezdok. Enjoy, thank me later. Shame the "geniuses" over at F1 "support" forum couldn't figure this out. In their entire forum this solution is not mentioned once. Only bits of information that never helps. Also, Oleg said he will be back to support his add-on by September 7th and never came back. 0 credibility, 0 reliability.

Last time I checked 2.2 on win 7, it was working great. Aside for slowing down when navigating through the menu bar, which was no-biggy. This time around, I'm on 2.3 and win 8.1.. now you have to make the difference between win 8 and 8.1, since 8.1 is dx12 and 8 is dx11, similar to win 7, which means less problems. I'm tracking the sfx developers to see if they're about to release their new injector. They're working on a new solution with much better compatibility.