Do you mean the GSX shortvuts or the EZdok shortcuts?

 

After assigning CTRL+F12 in the "Couatl"-menu to Shift+X everything works fine now, GSX and EZdok.

 

I mean the EZdok shortcuts.

 

I'm not sure if the conflict is with the F keys or the opening of the GSX menu itself. Will give it a try thanks.

Anyone know of EZdok works with V  3.2 of P3D. I asked a couple of times on the V 3.2 thread, and have yet to get an answer. Looks like nobody that installed 3.2  uses Ezdok, which I find hard to believe.  

I am trying to use EZDOK in version 3.2, but so far all attempts have failed.

Anyone know of EZdok works with V  3.2 of P3D. I asked a couple of times on the V 3.2 thread, and have yet to get an answer. Looks like nobody that installed 3.2  uses Ezdok, which I find hard to believe.  

Bob,

 

Posts #52, #238 and #249 in the very thread where you asked the question all confirm that it works - post 192 has partly negative feedback.

Just a warning: EZDok still for some unknown reason insists on setting clipmode=minimum for the VC view.

 

clipmode = minimum should only be used on external views. The default P3D - non ezdok vc view does NOT use this.

 

While using clipmode=minimum does provide a slight FPS boost it is at the cost of Z accuracy. It causes all kinds of z-fighting and texture issues on distant objects (like cloud/mountain intersections)

 

quick fix is to delete that line from your cameras.cfg for the ezdok vc view( you will have to do this each time you run the configurator because it will add it back)

Anyone know of EZdok works with V  3.2 of P3D. I asked a couple of times on the V 3.2 thread, and have yet to get an answer. Looks like nobody that installed 3.2  uses Ezdok, which I find hard to believe.  

 

Bob it probably needs an updated offsets file like it did for other versions or there will be issues with the world camera , otherwise the other cameras should work ok.

Just a warning: EZDok still for some unknown reason insists on setting clipmode=minimum for the VC view.

 

clipmode = minimum should only be used on external views. The default P3D - non ezdok vc view does NOT use this.

 

While using clipmode=minimum does provide a slight FPS boost it is at the cost of Z accuracy. It causes all kinds of z-fighting and texture issues on distant objects (like cloud/mountain intersections)

 

quick fix is to delete that line from your cameras.cfg for the ezdok vc view( you will have to do this each time you run the configurator because it will add it back)

 

Bob it probably needs an updated offsets file like it did for other versions or there will be issues with the world camera , otherwise the other cameras should work ok.

 

Is this a new problem with EZdok, because I haven't noticed any problem before with VC views.  In addition, where is the camera .cfg view, is this for each individual aircraft? 

Bobsk8, on 09 Mar 2016 - 07:18 AM, said:

Anyone know of EZdok works with V 3.2 of P3D. I asked a couple of times on the V 3.2 thread, and have yet to get an answer. Looks like nobody that installed 3.2 uses Ezdok, which I find hard to believe.

I use it. I had no problems last night with Ezdok after install of P3D v3.2 client and content.

Is this a new problem with EZdok, because I haven't noticed any problem before with VC views.  In addition, where is the camera .cfg view, is this for each individual aircraft? 

 

It's in \AppData\Roaming\Lockheed Martin\Prepar3D v3 (It's a global setting)

 

It's been a problem for a while and has been pointed out to the developer several times in their forum , no explanation has been given as to why he would add that to the VC view.

 

I made a video about a year ago illustrating the problem.

 

 

clipmode=normal is the same as removing the line entirely as was pointed out to me by Rob at a later point.

Anyone got World Camera working in PD v3.x?

 

If so how do we do it?

Anyone got World Camera working in PD v3.x?

 

If so how do we do it?

 

Word of warning. I tried for hours to fix it, never could. 

Word of warning. I tried for hours to fix it, never could. 

Download the updating variables.ini... fixed

Download the updating variables.ini... fixed

 

No. Its not. Downloaded the variables. Multiple times. Nothing. The reinstalled per support, then started in the cockpit then created a world cam, and did all kinds of back and forth switching hoping it would stick, and nothing. The list goes on and on with troubleshooting steps and youtube videos watched trying to fix it. 

 

Infact go on the flight 1 forums and you will find a bunch of folks with P3D v3 who cant get the global camera out of the ocean. Just because it worked for you, doesnt mean its fixed in the slightest for the rest of its users. That kind of archaic disregard to support the program properly is exactly why people are flocking to FSFX right now.

No. Its not. Downloaded the variables. Multiple times. Nothing. The reinstalled per support, then started in the cockpit then created a world cam, and did all kinds of back and forth switching hoping it would stick, and nothing. The list goes on and on with troubleshooting steps and youtube videos watched trying to fix it. 

 

Infact go on the flight 1 forums and you will find a bunch of folks with P3D v3 who cant get the global camera out of the ocean. Just because it worked for you, doesnt mean its fixed in the slightest for the rest of its users. That kind of archaic disregard to support the program properly is exactly why people are flocking to FSFX right now.

 

I think that many users will just uninstall Ezdok once Chase Plane gets out of beta. Even now, in Alpha many people have bought it and stopped using Ezdok. 

That kind of archaic disregard to support the program properly is exactly why people are flocking to FSFX right now.

 

What do you think I did?

There's a very quick fix for EzDok with P3D v3... called Chase Plane from FSFX, just bought it even in Alpha version, much better than EZDOK and give you some free VAS space