I am unable to get this thing to work. Thought it was a problem with EZdok. After installing the 767, I get some simconnect warnings and FSX just hangs and refuses to start up (everything is properly in the DLL.xml). Re-ran the Ezdok configurator. I installed all three of the simconnects. Problem still persists.

 

If I uninstall the 767, this problem goes away and the sim starts up fine.

 

I am on a standalone FSX:SE. No original boxed installation.

So I have since been able to install it and start the sim. However, the sim takes much longer to load up, and the menus are impossibly sluggish to navigate. When I finally have everything set up and hit "fly now" (after 30 minutes of click....wait....select aircraft....OK....wait..........click....select location....etc) I just have an eternal freeze.

 

When I look in my process manager, I noticed there is a second fsx process. What is this, and maybe it's having some effect?

 

http://puu.sh/pbzQI/b9218550a1.png

 

When I look in my process manager, I noticed there is a second fsx process. What is this, and maybe it's having some effect?

 

http://puu.sh/pbzQI/b9218550a1.png

 

 

What's OS do you use? If it's Windows 10, there's a known issue with LvlD security protocols and Windows 10s...

   

 

What's OS do you use? If it's Windows 10, there's a known issue with LvlD security protocols and Windows 10s...

Yep, using W10.

 

Seems futile to ask, but is there a way around those problems? I just wonder because apparently some people have this plane working?

Quick update, after sifting through the registered Level D forums, somebody suggested disabling windows error reporting. That seems to have worked.

 

Quick update, after sifting through the registered Level D forums, somebody suggested disabling windows error reporting. That seems to have worked.

 

 

Yep, I was going to point you to that thread. That "fix" doesn't work for all users though; read thru the thread so you understand what you're disabling...