Jump to content

andyb_1972

Frozen-Inactivity
  • Content Count

    32
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by andyb_1972


  1. Hello everyone - and a Happy 2016!

     

    I've been using the MU-2 (v2.0 purchased from Just Flight) for a couple of weeks now, absolutely love it to bits and use it as often as I can when I get some free time to sim. Unfortunately, I've having a little problem with the Cabin Pressurisation controls and possibly one or two of the other gauges...

     

    I'm using P3DV2.5 (Version 2.5.12943.0, SImConnect Version 2.5.0.0) on Windows 7 x64

     

    I have noticed if I'm a little over-enthusiastic spinning the CABIN ALT knob and I hit the lower or upper CABIN ALT dial limits the dial/knob gets stuck, after which I am unable to make any further adjustements to the cabin pressure. If I exit the flight without saving and start over again, the knob will be free again and the dial moves - but if I save the flight, quit and and resume the same flight (i.e. try to build up some history with the aircraft) the knob and dial remain stuck.

     

    I've tried uninstalling the MU-2, deleting the aircraft folder, re-downloading and re-installing but the problem persists. The first time I installed the aircraft, I had Roland's Weather Radar gauge for ASN installed and working fine. The second time I tried without the weather radar to see if it made any difference but it didn't.

     

    This is more of a question - when I spin the RATE MIN-MAX dial, is the climb rate gauge for the cabin pressure (the one above the hourmeter) supposed to move accordingly? In my MU-2, the dial doesn't move and this is regardless of whether or not CABIN ALT dial is stuck. I have the other switches set to 'BOTH ENG',  and and 'AUTO' (not sure the others matter but for what it's worth I have them at 'FLOOR' and 'COLD'.

     

    Lastly, probably unrelated, but I noticed that when using course selection knob on the co-pilot's HSI, it seems to be inoperative - at least on my MU-2. The heading bug works though.

     

    Hope someone can help me with my queries - or set me straight if I'm doing something wrong. I'm by no means an expert and this is the most complex aircraft I've tried to get to grips with in P3D so far. Please let me know if you need any more info from me.

     

    Regards,

     

    Andy


  2. I have found a solution that works for me. 

    The first step is to replace the the Original Ezca.exe with the P3d beta exe.

    Second step is the entry in the exe.xml like the description above.

    Third step: In your P3d Main Folder you will find a folder named redist /interface.These folder contains 5 subfolders.Each of this subfolders contains  a folder named retail / lic.

    In every of these lib folders is a simconnect.exe file. I have installed all 5 files and Ezca was running at once. You can see the files  in your control panel . 

    Thank-you Casco04 - that is what finally got EZdok working for me.

     

    In case it helps anyone else, I thought I would share my experience:

     

    I had a 'clean' install of P3Dv2.4 and was waiting for the release of FSUIPC v4.937 before I installed any add-ons. I did not have FSX installed on the machine or any remnants of FSX as this was a fresh Windows install on a reformatted SSD.

     

    Once I installed the updated FSUIPC, the next thing I did was install EZdok 1.5 with EMT, then the 1.7 update. Finally I ran EZdok config tool. This all appeared to run without any problems. Previously, that was all I had to do to get EZdok to work in P3Dv2.3 - but it was not enough to get it to work for P3Dv2.4 as EZdok would show up on the task bar but not in the 'Add-Ons' drop down menu.

     

    Next I tried editing the exe.xml to add the lines relating to EZdok but the situation remained the same.

     

    Finally, I tried using the 'beta' P3D-aware EZdok.exe file - but this did nothing to improve the situation either. 

     

    More out of hope than expectation, I tried Casco04's suggestion of installing the 5 simconnect.exe files. I came across similar advice on another thread that suggested this would only work if EMT was activated - so for me, virtual FSX was enabled. During the process, 2 of the installations aborted because I think they were just different language versions of files that had previously been installed. To my surprise, next time I launched P3D, EZdok auto-started and was present and working as before in the 'Add-Ons' drop down menu. I even loaded up an old .ecs file I created for the Carenado Beechcraft Baron in FSX and used the camera views for the default P3D Bonanza. Fantastic! I should point out that I installed all 5 of the simconnect.exe files. I tried it once after installing only one of them (can't remember which one) but EZdok still didn't appear in the 'Add-Ons' menu.

     

    I don't really know why it worked - maybe some of the things I did were not required - but that's what I did and now I am in the very happy position of having EZdok working with P3Dv2.4. Happy days!

     

    Thanks again Casco04!

     

    Andy

    There is one mistake in EZCA itself that might cause an error during the launch of the sim, though. If you have quotation marks (") on the aircraft title, EZCA will fail because it tries to write .ini file based on the title name to its directory concerning the aircraft specific camera setups. Because quotation marks are illegal in Windows file name, .ini file also fails and EZCA most likely crashes.

     

     

     

    TheGrunt - I was wondering if you have been able to fix that problem? I got that issue with the CR-1 Software Ford Trimotor when I used to fly it in FSX. Whenever I launched a flight with that aircraft, there would be a 'bong' error sound and I'd get an error window with "Unable to write to C:UsersAndy BlairAppDataRoamingEZCAdbvirtual_cockpitCR-1 Software.Ltd "Ford Tri-Motor 4AT-B Standard Ford Delivery"_.ini" and then EZdok would close. It broke my heart as I really love that plane but I don't really enjoy flying without EZdok.

     

  3. Would just like to echo the sentiment of dandimm in that I was very reluctant to get involved with tweaking P3D but I had the worst case of the blurries which would within a few minutes affect almost every ground texture regardless of aircraft speed. After two weeks of messing about with settings and not a single completed flight, it really was the last throw of the dice for me and I was prepared to walk away from FSX and P3D altogether and look elsewhere. I can confirm the AffinityMask=15 tweak worked for my i5 4670k. Confidence in P3Dv2 now slowly being restored. 


  4. Hello Tom and everyone else. Thanks for the kind welcome to your forum. I'm a 'seasoned beginner' at FSX having bought it middle of last year. I've probably spent most of that time trying to get the software looking and running the way I want it to instead of learning to fly properly - but I'm getting there slowly. I don't have any real-world aviation experience, so between learning how to improve FSX through tweaking and various add-ons, to actually learning how to 'fly' properly, it's been quite a severe learning curve. Hope you'll be patient with me as I find my feet in your forum (I have so many questions!) and I look forward to being a member of your community.

    Regards,

    Andy 

×
×
  • Create New...