KevinHuser

if you are an FSUIPC user check that the middle mouse options are Off in the settings kevin

keyboard combination. ctrl + shift + R should set the typhoon in ready to fly state. If not, maybe try a re-install

you should have received an update notification ? your version is a bit old. update first then check zoom again link to 0.62 https://drive.google.com/file/d/1Z91Tvc9xZ0lN6Y8T0cmFo5J57pKIVENa/view

Good, thanks it is helpful to know ch product does work ok The user seemed pretty familiar with ezdok so it would be odd if they had forgot to add it In v1- after a new install a hat as pan button often required a sim/ezdok closure after adding a controller followed by a rerun of the config tool - running sim/ezdok again usually sorted this and fhat panning was fully functional. In testing I had to do this after a re-install. With v2. I have tried (including all plugged in and connected via daisy-chained powered USB 2 hub To one pc USB 2 port ) saitek x52 Hotas x55 Hotas thrustmaster warthog Hotas saitek Cessna yoke So far all are recognised - None have presented any issues with buttons or hat panning or hat as buttons in ezdok

For info -from the ezdok forum

I believe ch yoke hat may still be an issue in v2 - it Was reported on the ezdok forum as an issue with v2 but I don't think the user has responded to my suggestion regards a possible "fix" It don't leave the original exe.xml entry for v1 in the sim EXE.xml file - but if you must - ensure it is disabled - the v1 ez config adds it back in if you revert to v1 - so why leave it in there if currently using v2 - Btw - v2 has a different install path to v1

Couple of things - the Hotkeyselect is still not acceptable in the a2a aircraft.cfg V2 will remove it For operational reasons - as you rightly point out - the aircraft.cfg will always be given priority within sim code so it has to be removed from the definition relating to fthe walkaround It should work if done in reverse All beta testers were Russian as far as I know. It is amazing some of the oddities they never picked up in testing and missing features they thought were acceptable - The Accufeel addon and in stand alone planes could be a problem - so far I have not had time to test a2a by installing them I have the c172 / c182, the Cherokee etc, probably check them over the weekend

I had some discussion with Oleg regards p3d world camera before v2 was announced, it always was a headache from V2.5 onwards -- the flight1 webpage shows ezdok v1 was never sold as P3d compatible so far creating world cameras in V2 have been successful - no issues also p3d updates that require changes to ezdok are now part of the update function in v2 - no ini file replacement needed kevin H

regards using - hat as button - did a test setup - used update camera - did a full restart of sim and the setup still worked I'm using both a pre-release build and currently released build of win 10 in testing and it works OK under both plus no more stupid appcrash reports that need clearing up periodically - seems to be gone with ezdok v2

I would suggest re-naming the EZCA folders in c:/program files (x86) and more importantly c:/users/(username)/Appdata/roaming to retain the old version 1 The exe.xml entry for v1 should be removed when using v2 If reverting to v1 -delete the v2 entry the ez config tool would add the correct v1 back in the first time you run the v1 config tool The cameras.cfg file is the same -apart from the title name - again the ezconfig tool for v1 actually deletes the existing EZCA definitions and adds them back in each time the ez config tool is run so the v1 titles would appear on screen Kevin H

Horizon hold Check it out in this video the idea is to replicate to some extent what the human brain tries to do where we try to retain the horizon in view https://m.youtube.com/watch?v=7y6NtxKmxAg

I believe the intention is to provide links to tutorial videos with English sub titles rather than do a PDF manual. It's a different approach, I like viewing a video on a subject so not having a manual doesn't bother me. I don't like the fact it doesn't autosave settings but I'm sure it will become second nature after awhile of using the new gui

Hi, sorry I've been busy with Holiday preparations, did not pick up on this thread until now under windows 10 You do not need to run compatibility settings except run as administrator on prepar3d.exe ezdok gains Admin/elevated status from P3d. however it does no harm to add it to EZCA.exe too ezdok config it should only be run when a. you add a new plane b. when you add a new controller device - joystick etc - avoid running the ez config restore option - it can damage your cameras.cfg file. AI traffic this can be a factor in delaying sim load times resulting in ezdok simconnect timeouts FSUIPC4 can defer ezdok opening until a flight is loaded, to avoid it. FSUIPC4 always check you have the latest version 4.958 -: http://fsuipc.simflight.com/beta/FSUIPC4.zip your existing purchase details can be re-used but the [programs] feature does not require users to have a paid licence. Just download it and run the installer after you unzip the download file You must run the sim at least once to create the FSUIPC.ini file the command "ready" is the key, without it ezdok will start exactly as it does using Exe.xml so a timeout would still be likely READY delays loading and running the program until sim is up and ready to fly, and FSUIPC4 can supply valid data through its IPC interface. EXE.xml file FSUIPC4 cannot overide the sim Exe.xml file entry for ezdok,it must therefore be disabled - Location c:\users\(your username)\appdata\roaming\Lockheed Martin\Prepar3D v3 it is disabled by altering the line <Disabled>False</Disabled> to True example <Launch.Addon> <Name>EZdok camera addon</Name> <Disabled>True</Disabled> <Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path> </Launch.Addon> Prepar3d.cfg I would suggest deleting your Prepar3d.cfg file as the section [uSERINTERFACE] line SITUATION=C:\Users\(your username)\Documents\Prepar3D v3 Files\xx may be the issue it seems the sim cannot read the files needed for your default flight and reverts to using the Prepar3D_Default.fxml and Prepar3D_Default.wx files P3d wil generate a new cfg file when run I hope this helps you - O.Eker

Gabster are your posts of feb 2016 and yesterday related ?? are you using v1.187 a this is the only supported version for p3d V3 ? are you using the dual function - joystick hat as buttons and hat /panning ? also what outside view are you referring to - ezca aircraft or ezca world cam I will need more info on what hat switch/buttons are assigned to in ezdok

Ezca version 2 is on the horizon (mid December approx.) - A new world camera variables.ini file is available for p3d v3.4 (pre and post hotfix versions) over on the ezdok forum you will find the download world camera/p3d has an identified bug that I am led to believe has been fixed in ver2 I hope this helps explain the issue you are having There are two view systems in-sim - ezdok and P3d default - the function keys F9 F11 F12 are assigned in p3d controls to give access to the default view system If you use F11 (locked spot view) ezdok may not recognise you have switched to a default view ( I was able to replicate this very easily) and does not release control of the mouse and Hat/pan functions correctly This can be avoided if you add F9 / F11 in the ezdok studio assignment options - define keys and buttons and the main studio shortcut box for specific VC views typical example - in ezdok define keys and buttons - default section - next category = F11 (locked spot view) will switch you to the default view and the joystick/pan or space bar plus mouse look function will apply normally another assignment in -- next in current category -- (default is the A key) will cycle views within the view category to return to VC add F9 to the shortcut box for your specified VC view ( I would not recommend F12 - too many other add-ons use that key) The point I am making is that if users allow Ezdok to control all view switching anomilies like this can be avoided. I would also recommend removing the F9 F11 and F12 assignments in p3d controls to avoid conflicts regards Kevin H

The next step after naming a new world camera view and then OK is to click on any VC view Then click on the world cam view created You should be inside the aircraft model at the defauit view co-ordinates (which looks odd but is OK) If edit mode (Num key 2) is not sounding press it and use the arrow keys etc to move the camera away from the external aircrsft model to where you want it- When done press edit key to save the changes There is a new world camera update available for P3d v3.4 - it covers pre hotfix and post hotfix Also the long awaited ezcav2 is in closed betatest and due around mid December with the P3d bug fixed and an updated database. I don't know if any of the features in previews will be implemented. Preview vids on youtube can be accessed at this link. https://m.youtube.com/watch?v=GFcyHOe-vEs

A number of ezdok camera users use the FSUIPC4 -Program -feature to load ezdok after a flight is loaded If you have FSUIPC4 installed Open your sim install folder/modules open the file FSUIPC4.ini Remove the section [Programs] completely or add // to start of the line for ezdok to disable it

How about this option instead I deliberately altered p3d to cause a sim crash and the following stopped auto solution finder/restart of the sim it changes the maintenance option - check for solutions to problem reports from ON to OFF Open Regedit. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting Find the value named "Disabled" or add a new DWORD value with this name if it doesn't exist. I I added it) The default value of this key is 0. Double click it to edit, change the value to 1 and save. This disables the automatic appearance of the dialogue where Windows is searching online to try to find a solution. You are instead shown a dialogue stating that the application has crashed, giving you the option to Debug. However, unlike previous versions of Windows, no error code is provided in this dialogue. The specifics of the error must be accessed through: Control Panel\All Control Panel Items\Security and Maintenance Under the tab "Maintenance", you can click "View reliability history", which will show a list of all app crashes. You can then click "View technical details" beside each crash to get more detailed information, such as a the error code(s) thrown from the application on crash.) Kevin H

Pete , I wonder if this might help - if you type in the Cortana search box - services.msc select from the list > windows error reporting > right mouse click > select properties the Recovery Tab has a number of options e.g take NO action on first fail or restart one of these is also run a program. with your expertise this may be useful Kevin H

I also found a fix for Keyboard users using a registered version of FSUIPC4 using the key press function - basically you set the key (all keys for ez aircraft views assigned in ezdok) to send to sim - View camera select 4 - when key pressed & when key released as to the View system - I did a quick check of the following and it seems to be OK - basically it prevents the View - thumbnail etc window from appearing on screen make a backup copy of the panel.cfg file and make this change to the original - add // to [window 10] horizontal setting and/or //[window 11] for vertical bar setting //[Window10] size_mm=331,39 BACKGROUND_COLOR=0,0,0 position=0 visible=1 ident=2016 nomenu=1 you must leave the view system ON to allow the info bar This needs to be repeated for each variant of the airbus - on first opening the aircraft I found the view went to cp fmc panel view after a few seconds - but selecting the ezdok view for the FMC view fixed it and it did not come up again Kevin

D Quixote I have bought this Plane and really am enjoying it too - excellent add-on and great value for money the canopy needs an assignment added in p3d controls for spoilers ON (open canopy) spoilers OFF (close canopy) - you can use the existing spoiler assignments or your own choice I don't have any issues with ezdok - all three effects are applied normally nothing unusually harsh in the preference popup you can reduce the engine sound it may be masking the touchdown effect - but I agree it is not as pronounced as in other aircraft Kevin

Spent some time on this and may have a workaround - however - it is ONLY for users that access the external ezdok aircraft view using a joystick button in the main ezdok studio - shortcut box I would be grateful if someone else could try it and feedback if it works for them. step 1 remove the // mod from the airbus panel.cfg file and in sim set airbus view system to ON step 2 add to P3d controls - define keys and buttons views - View camera 4 (select) - YOUR j/button assignment to switch to ezdok aircraft view list and slide the slider - Full Right step 3 run the sim and try the view system - I tried it with a saitek yoke and saitek x55 (stick and throttle buttons) which have different button polling speeds - switching from ezca to P3d default etc and it seems to bypass the airbus view by performing the equivelant of a a long press/double press of the button regards Kevin H

I re-installed the a320 321 extd versions and checked - With tye panel.cfg mod - the checklist itself works but the text on screen does not appear It looks like the view system is linked directly to the text bar - view system off /text off - bummer I'm taking a further look at this at the moment Kevin

https://www.reddit.com/r/flightsim/comments/33e05g/ezdok_problem_with_aerosofts_a320321/

darn, As I understand it - the pagefile really comes in when programs run out of actual memory - with 16 gigs installed and 4 reserved solely for FSX I can't see how the pagefile is relevant- However you might want to check it in the system section control panel > advance system settings > advance > performance section > advanced > virtual memory - change I have mine set to custom - windows recommended - 2937 mb (2.937 gigs) for c:\drive ( I have 16 gigs installed) which means a pagefile of 3 gigs is overkill really but I have the space so I'm ok with it did you just update win 7 to win 10 keeping all programs installed or have you done a full re-install of win 10 and clean install of FSX - to be honest the update only is fraught with issues and just doesn't work out on some Pc setups you could try deleting the shaders folder in C:\Users\your username)\AppData\Local\Microsoft\FSX - if you have Steve's dx 10 fixer installed then the shaders10 folder also should be deleted FSX will rebuild it for you on next sim start also if you have saved flights in your documents folder /Flight Simulator X Files - try moving them to a new folder as backup - so fsx resets to the default flight ( if no fix you can move the saves back) edit - just thought of graphics driver - is it up to date - ​are you using ezdok camera - the licence can fail. win 10 is seen as new PC - that requires a refresh using the flight1 installer/purchase file ( re-install only option)