Jump to content

Paull57

Members
 View Profile  See their activity

  • Content Count

    14

  • Donations

    $0.00 

  • Joined

  • Last visited

Posts posted by Paull57

  1. Posted

    I am posting this in case anyone else has been having this problem.

    I did what was in the thread below for the 402, 441, and MU2 and all worked with the autopilot except Glide slope coupling on LPV approaches. All 3 airplanes would not couple until I added the Connect GPS to VOR1 indicator setting in the RXP settings for the airplanes. I also changed the VLOC source to VOR1 instead of Auto. Until I did that the airplanes would not couple and cause the Flight Director to command a descent on the Glideslope on LPV approaches. It would just continue flying inbound at the intercept altitude with the APR staying on ARM. I never saw this setting mentioned as being needed but I tried it anyway and now all 3 airplanes are doing what they are supposed to do in the testing that I have done so far. This worked on P3D V4 and original FSX SP2.

    I also have the Falcon 50 and Lear 35A and since they have the explicit settings for RXP GTN750, they both have been working fine.

     

  2. Posted · Edited by Paull57

    Jevon,

    I installed It in P3DV4.4 only.

    I got the mod that you sent and it works now but I had a strange problem with the PANEL.CFG file that was included. I could not get the autopilot popup to happen with the shift +3 key. Nothing would happen. Everything else was okay. So I compared the [Window02] section with the original and they looked exactly the same. So I thought that maybe even though they both looked the same, maybe there was some stray character that was not visible to Notepad in the PANEL.CFG that you sent in that  [Window02] section that was causing the problem so I just copied only that [Window02] section of the original PANEL.CFG to the new one and saved it and then the autopilot showed up like it should. 

    I also tried re-downloading the zip file from the dropbox, unzipping it, and using the new unzipped file before I did the copy and paste but it still did the same thing. Maybe it is something that happened in the zipping and unzipping process caused this, don't really know, but it works fine now after the copying and pasting that I did.  I am a retired Associate degree Electrical Engineer and programmer and I have seen stray characters that were not visible show up in files that caused problems before so in my experience it is possible. We called things like this a SANRD (Scientific Anomaly Not Readily Discernible). We pronounced it like Saynerd. 😀

    Thank you for your hard work and I wish you and your family health and safety now and in the future in these strange times.

    Paul

    • Like 1

  3. Posted

    Since I started this topic, I thank all that replied. Here is a quick summary of my experience so far.

    I just looked at PCaviator and it does show 1.9H on their web site and when I downloaded and installed it the last time and installed it, the programs list showed that it was already 1.9H as flyblueskies posted on Feb 22, even though the PCaviator web site was calling it 1.9G when I downloaded it. I have since made 5 flights all using P3DV4.5 and I haven't seen any problems so far. I have not used the FSX version at all since I tend to have crash to desktop in FSX too often. Very frustrating after a long flight to find myself getting knocked out of FSX just as I start my approach, as we all have probably experienced. So I basically use FSX only when I want to fly an airplane that only installs in FSX.

    • Upvote 1

  4. Posted

    Thanks for all of the replies. I sent a request to Pcaviator for the latest version shortly after starting this topic and I got a reply email yesterday that it was updated to 1.9G. I do agree that Pcaviator has been a bit slow in getting new versions made available on their website. I downloaded and uninstalled and reinstalled and it appears to be working okay although I have only made 1 short flight so far. 

    Paul

  7. Posted

    I also sent contact info to Flysimware thru their web page ad receive an email back in about 10 hours (I consider that very good response time). They suggested that it might be a faulty installation of Prepare3D 4.4 because they did not see it. So I tried further testing.

    After doing further testing on this effect, I have tried some different sequences of loading the Conquest after starting up Prepare3D. I had been loading it after loading the Mooney Bravo at KHVN. So, I was loading the Bravo first, then loading load the Conquest. In this situation, I got the strobe effect on left prop. So, I tried another airport (KEYW) and did the same sequence and no strobe effect. Moved the airplane (still running) to KHVN and no strobe effect. 

    Then I tried, after a restart, starting up in KHVN loading directly with the Conquest in KHVN. After starting engines, no strobe effect. Flew around with no strobe effect. 

    So I my best guess is that there might be some type of conflict with a texture that loads under some circumstances (like location or previously loaded plane) that causes this effect. So I when I want to fly the 441, I just make sure that I load it first, before any other airplanes. So far that has worked in all of the starting airports that I have tried.

    As Flysimware support suggested, I may have a faulty installation of Prepare3D that is behind this effect that I see. At this point, I am not going to re-install it since I have found something that works to avoid this effect so I will not at this point. Like I said in my first post, I really love this airplane (kind of partial to turboprops in general but this and the MU-2 are really at top of my list).

     

     

     

  8. Posted

    I have been flying the Conquest in FSX for a couple of years now in FSX and I love this airplane. The problem that I am describing does not happen in this airplane in FSX.

    I just bought Prepare3D V4.4 and when I tried the Conquest v2.3a in that sim I get a strange strobe effect on the left prop both during startup and when completely up and running. It just keeps flashing such that I see the prop in the blurr like a strobe light was shining on it. Day and night. It happens on the ground and in the air and is visible from both inside the airplane and outside views. It does not seem to have any effect on the flight characteristics or gauges. It does this with both versions of the prop on left side only. Right prop looks like normal blurred prop. Since it has to different versions of the props, I tried both and it does the same thing with either, only on the left side. Operationally it is not a problem, but it is a distraction.

    I uninstalled and re-installed and still does the same thing after reinstall.

    I have the Flysimware MU-2 and the 402C and neither of those have this prop effect on either side.

    I searched this forum and it I did not see any reports on this. Anyone else seeing this effect?

  10. Posted

    I did get notified from Carenado a while after submitting a ticket that it needed a fix in the installer that would fix the CTD. I was notified in an email from PCAviator yesterday the a new version was available for download since that is where I bought it. I downloaded it and it is now working. No CTD. This is on FSX boxed. So far no problems.

  11. Posted

    Tres,

    I also asked for help directly from Carenado for a crash to desktop everytime that I loaded the Premier. They asked me to delete the Carenavigraph.dll and try it. I did that and it still crashed FSX. Then I received an email on 7-3 saying that they were going to update the install package to fix it.

    Here is the info that was sent to me.

    "We've found the problem, but it's not solve-able by the customer, we're preparing the new installers to correct this issue, should be done by the end of the week."

    Paul

×
×
  • Create New...