KevinHuser

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)

I have the file in my link in FSX classic Gold edition on my win 10 test pc and it is same file also provided by dovetail in Steam edition on my sim pc Fsx classic will ctd without it on my setup, so far it is has been ok for months with no ctd As I see it you have nothing to lose by renaming the version suggested by pmdg and trying the version in the link ?

This may seem obvious, generally fsx users have already done these but worth checking anyway to eliminate them as potential fixes Have you added the file - UIAutomationCore.dl- provided with Win 32 bit to your main FSX install folder - it should fix the ctds. On accessing menus. UIAutomationCore.dll version 6.0.6001.1800 file: http://download772.mediafire.com/yxms3tzmwjug/mik2mlqdz1w/UIAutomationCore.zip it was discovered as a cure for several FSX crash issues and is from 32 bit windows because FSX being 32 bit was unhappy using the x64 bit version in c:\windows\system32 The low memory - fsx can only use 4gigs (ever) so microsoft Did a patch to improve memory management - do you have Either fsx sp1 plus sp2 installed or fsx acceleration Your FSX.cfg file should also have an entry in the section [Graphics] HighmemFix=1 Regards Kevin

Glad to hear you have resolved the problem. The location of ezdok is not locked to the default folder for those users familiar with how it operates and able to make the appropriate adjustment to the sim EXE.xml file In testing I have not found there to be any operational benefit to using an alternate location if anyone is thinking it may be worth trying. The problem with the current beta v1.187 version of ezdok is that it is an amalgamation of very old elements from earlier editions with no flexibility hence your issue when installing ezdok on your E:/drive Unfortunately given the history of ezdok development I don't expect any updating of the code But you never know ... Lol Kevin

Hi Elaine Yes it is me. Thanx, i do my best - seems it's not so great in this instance, hopefully we can resolve the issue for the OP. I'm very impressed with your knowledge base, Avsim has excellent contributors, your guides are excellent. Kevin

Ezdok should be allowed to install the various files and folders it chooses - users should not select Alternative locations The ez config tool is responsible for adding the entry for ezdok to your sim EXE.xml file - it does not check the install path for ezdok and it will not recognise a path other than C:/Program Files (x86)/EZCA It won't auto open If you have installed ezdok anywhere else - just move the folder EZCA to that location The lic fiile and ezdok -setup v1.187.exe file should be in C:/Ezdok Software Kevin

the issue described is almost always related to a permission mismatch being read by windows when opening the software Have you added exclusions for ezdok camera - EZCA.exe and folder location within your Anti virus software and UAC slider set to - never notify The Ezdok camera wrapper/installer has a limited number of activations (3 or 4 attempts) before the Licence fails and a reset is needed Have you used the automated process before - on the flight1 website > support > - there is an Option - re-activate my order I use it regulalry due to problem solving ezdok often messing up the install /licence you add your ezdok order number - E-mail used for the purchase and password - then an automated e-mail is sent (inside is a click link) click on the link to reset the licence - Then try running the ez config tool from the desktop shortcut using - right mouse button - select run as admin don't run the registry option in the config tool then run the sim as normal

Where did you get v1.187 - if you updated using the zip from the forum it may be your problem. It is better to 1. delete the primary ezdok folder EZCA in C:/Program Files (x86) and the ezdokcam1 lic File in c:/ezdok software 2. Download the latest all in one installer from the flight1 website and run it This will replace the deleted files and reset the licence to rescan your PC hardware 3. do NOT use - run as administrator - on file EzCA.exe - try it without first 4 DO use - run as administrator on Prepar3d.exe. This allows the sim to control ezdok permission level when running the sim Kevin H

I have UT2 installed in P3d v3.3 and did a test set p3d to seattle Tacoma set A1 traffic to 65% set simulation rate to x 4 and waited, not much happened, I then opened the ATC window and selected - ATIS - then Ground - bingo - over the next few minutes a regular stream of A1 traffic moved from stands to takeoff Btw - I used the LM option to install UT2 into my separate add-on objects folder outside the sim install folder (I'm using this for add on aircraft as well if the option is available) KH

Theflightsimguy I'm not a regular AVsim user but by chance saw my post being quoted the author of ezdok has been quick to update previous versions - but this time there is still no variables update for p3d v3.2 Unfortunately when the author has been quiet in the past it has been years before an update occured - for example compatibility for steam FSX and P3d I doubt the author expected the constant updates that have been occuring with P3d - each new build version requires a new set of variables for world camera ( Pretty sure Lockheed Martin are comitted to all updates using new build versions so this won't end with v3.2 - if LM release an update v3.3 the issue of a variables update will occur again) Kevin H