Phil Chimbolo

I have the same issue. Would appreciate a reply to this thread if you solve the issue. Thanks!

Thanks for the insights on this Hawker guys! Carenado is notorious for needing quick & early SP1 releases. Knowing that, I waited. Disappointing to see to comments here because they usually do a good job fixing the major issues with their SP1 releases. However, I rarely ever see a release of an SP2 or patch otherwise. I'll keep an eye on this aircraft to improve with further releases. I'd like to think they will. For now, my credit card stays in my wallet.

Not in your case. It solved my "freezing indexer" problem. Yay for me, and not for everyone else, I guess. If my suggestion works for others, glad I could help. If not, they can keep digging through the forums.

DO you have FSUIPC autosave enabled? if so, disable it. Those pauses can be seen if/when FSUIPC saves the current flight. Depending on your PC specs this will either be more or less noticeable. That solved my freezing issues.

Mr. Randazzo and the rest of the PMDG team, Regarding all your efforts and endurance around the P3D legal headaches, development investment and quality release... THANK YOU! (And Thank you BETA testers!!!) What was once a complete experience in FSX is now an even better experience in P3D. My life is whole, and fully satisfied again.

I had this solved a while ago. Sorry I didn't see this topic sooner. I stumbled upon this subject while looking for something else today. When I researched it and didn't find anything in the forums I thought I was on my own, so I did some comparisons between FSX and P3D cfg files. SOLUTION: The VOXATC indexer is looking for the following entries in the "[Main]" section of your Prepar3d.cfg file: SimObjectPaths.0=SimObjects\Airplanes SimObjectPaths.1=SimObjects\Rotorcraft SimObjectPaths.2=SimObjects\GroundVehicles SimObjectPaths.3=SimObjects\Boats SimObjectPaths.4=SimObjects\Animals SimObjectPaths.5=SimObjects\Misc For some reason, the latest P3D.cfg file no longer has them. As we all know, VOXATC needs to research the available aircraft you have installed. Without these (or at least the first entry) it cannot successfully do that. I hope this works for you guys. It worked great for me. No issues since. BTW - Although I love VOXATC, Tegwyn should have been able to see this. And, although this would seem to be the fault of LM, if P3D doesn't need these entries itself... then this ends up being Tegwyn's issue with VOXATC having to rely on such entries. (I'm a software developer, that's how I see it).

Thanks Andy! I will contact tegwyn. I can restart vox, but I still see the same message. Interestingly, I can fly the same flight plan and if I unpause quickly (versus having the flight sit there for an hour until I return) I can continue with normal ATC communications. So the comms seem to be functioning from pushback to shutdown under normal conditions. I just sent tegwyn a support email. Hoping he has some insight into the reasons for the message after pause.

I read a number of posts around this issue, none help. This is a situation where I already have been in contact with VOXATC atc controllers and lose them when I pause the simulator (specifically P3D v2.3). SITUATION: - I depart from ANY airport, ANY aircraft using an IFR flight plan. - VOXATC works great all the way until I pause the flight -- usually just before TOD when I'm at cruise altitude. - At the time it paused I was in contact with "Center" controlling the airspace I was in. So all was fine before I paused. - When I unpause the flight VOXATC tries to reconnect and seems to fail with the message "No ATC Unit Found". Why will VOXATC not recognize the "Center" controller I was in contact with prior to pausing and reconnecting to it? Anyone have this problem and/or solve it already? #immersionkiller

Wow! I just posted this as I didn't see your problem. See mine, I have an example (on video) of what happens. At least I think it's the same issue as my left GEN light never goes off while waiting. http://forum.avsim.net/topic/420650-engine-1-freezing-after-startup/ Sorry if it's not the same. Sounds close.

Something I've been struggling with since I installed the T7 is that my Engine #1 does not complete it's stabilization during the startup procedure. At first I thought it was the throttle settings withing FSUIPC, so I followed everyone's recommendations to bypass FSUPIC and let FSX manage the throttle. I did that. No change. THEN... I was watching FROOGLE PETE's video "PMDG 777 - FULLY LOADED, KJFK to KDEN Part 1". Lo and behold... I see that his Engine 1 gets stuck temporarily in the exact same spot as mine... he even makes a comment about it when it finally "jumps" to its completed state of stabilization. See his video at exactly 28:13 when it jumps. The issue for me is... mine NEVER jumps to where it needs to be (EVER!). And... when I move the throttle all the cockpit controls move (throttles, center display shows power being requested) but Engine one provides no thrust. Engine 2 is fine. This link will take you to exactly 28-minutes where Froogle has already initiated Engine 1 start and he is waiting for this stabilization. http://www.youtube.com/watch?v=fMrW4O4WXYY&t=28m0s Why is mine NOT completing ? It is stuck at 21.8 N1 and 391 EGT. Any help would be immensely appreciated.

Me too! ADX, and a number of other blogs, are basically flight simulation enthusiasts -- like all of us. I'm not worried about the accuracy of their information at all. I suspect that some/most of their information (not just ADX) has some embellishment and/or guessing and assumptions that get published. So what?!?! Show me a journalist that doesn't do that to some degree as well. I simply appreciate these bloggers gathering information out there so that I can quickly get a sense of what is in development. The developers that really benefit from their blogs are the smaller ones -- those that have no real marketing presence or brand recognition yet. Companies like PMDG and Aerosoft don't benefit because they get top-billing everywhere and everyone knows what's going on with them. I think someone representing a top-tiered company like PMDG should keep their comments off of the forums if they can't be positive and supportive. I can see if a blogger has published some damaging information about a company. To strike back is legit. I've not seen ADX have anything negative to say about PMDG. Ease up Ryan!! You do what you enjoy doing, and let folks like ADX do what they enjoy doing to support the FS community. Everyone means well.

The quality of IVONA is incomparable. I tried all the free ones and the other pre-sale demos. I eventually bought the IVONA 5-pack. VOXATC does a great job randomizing multiple voices that are installed giving you a realistic sense of going from controller to controller. The $$$ was worth it!

I will try that Ryan. Thanks! I'll report back.

Strange... I've installed two liveries -- United (merger) and Delta In both cases when I go through cold and dark start-up procedures and engage throttles to taxi. At that point I either get no power/thrust in both engines OR no power/thrust in one of the two engines. BUT... the throttles move forward and the throttle indicators on my center display unit show the power being requested by the throttles. (attached pic showing one Engine 2 with power, Engine 1 without). Which engine works is random. Please keep in mind the following when responding... (1) I have successfully flown several flights (gate-to-gate) with the PMDG House livery -- no issues (2) I have tried both with and without FSUIPC axis control (3) My successful flights have been with FSUIPC control of the throttles Please help me understand why the add-on liveries I've used (and installed through the very latest Ops Center; just downloaded this evening) don't work. (I love this bird, and PMDG is great... but I don't want to just fly their livery!!!!)

Hmmmm. SDK... ugh.

If you cannot set EFIS settings on the EFIS panel, or DSP settings, it's likely because your FMC menu options for "EFIS CTL" and "DSP CTL" are set to "ON". You will find these options by clicking your MENU button on your FMC. See the EFIS CTL and DSP CTL options at LSK 1R and LSK 3R respectively. They need to be set to "OFF".

Thanks for the feedback! Sorry for my delayed response. Been on the road and just got back. Tried using DWC mode but am equally, if not more, frustrated by the incorrect wind issues at my destination airport. Regardless, I will try Jim's suggested settings. Thanks again!

After RTFM I can tell you that the suppression DOES NOT WORK! I am in "Standard" depiction mode, my "dynamic rate of change" (which is POORLY explained in the manual) is set to 0% (as recommended by HiFi), Downloads are set to "Automatic" at a 30-minute interval. I have both suppression options checked (local range suppression & suppress on ground), my ceiling suppression is 10,000ft. My local range suppression distance is 100nm. Sooo... when I'm taxiing (in or out) what about "suppress on ground" am I not understanding? I've ready plenty about "the suppression doesn't suppress downloads, only writes to FSX". However, the status of "Depiction Output Active" is displayed at the bottom of the AS2012 screen indicating that it is writing to FSX. The manual says specifically that status tells me that AS2012 is "writing" to FSX. AS2012 Manual excerpt (pg. 15) And... when I'm on final approach, what about "ceiling suppression" am I not understanding? I'm on a smooth approach and suddenly (1) the download occurs -- ok, fine --, but then again (2) "Depiction Output Active" status goes on and my FPS goes from almost 30 to about 5. I am very frustrated. I've been an ActiveSky customer since v5 and this is the first time ever I've wanted to uninstall it. How do I stop these FSX writes? And, I wouldn't mind stopping the downloads too.

After reading numerous posts from all over the web, I decided to spend my entire weekend trying to figure this out.Good news! I did!!! Thanks to the multitude of frustrated posters on this, and other forums.NOTE: This post assumes... (1) you have experience in Delphi and (2) have done work with SimConnect within Delphi before, but are just having difficulty getting SimConnect and Delphi XE2 to play nice together.1. Start by downloading the latest Delphi SimConnect files from C. Scott Hendry's web site (this is the latest FSX SimConnect):http://members.iinet...her/Delphi2.zip2. Following these instructions in editing the SimConnect.pas file to support AnsiChars and AnsiStrings:http://www.fsdevelop...52&postcount=11This is where everyone starts to lose ground because although you might be able to compile/build you FSX project, either the connection to the SimConnect.dll file fails OR calls to the SimConnect.dll file cause exceptions errors every time. Hang tight, we're almost there!3. I had to do this to make sure I got a connection with worrying about my Windows 7 path, or executable/project path where my application was running from. COPY the latest "SimConnect.dll" file on your machine to your project folder or where your application (exe or DLL) will run from. You guys can work out alterative locations later, but I was too excited to get this posted to worry about this step. (Please share your insight into NOT having to copy the DLL; I tried to place it into a global/Win7 path and it didn't work)Anyway, to find the latest DLL on Windows 7 Pro (x64) check the following location which is where I installed the SDK: (it may be installed in a different location on your PC): C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\lib\managed 4. Here is the big one... there is a file inside C. Scott Hendry's zip file (downloaded frome #1 above), under the folder "Delphi\HeaderRT" folder called "SimConnect.Pas.embed.manifest". You will need to override your project's Run-Time Theme (the what? exactly!) with this predefined manifest. To do that in Delphi XE2 you need to do the following:- Delphi menu path: Project -> Options- In the options window click on the item in the navigation tree called "Application"- On the Application settings panel (on the right) you we see "Runtime Themes". When you first see that it is likely set to "Enable runtime themes". Change it to "Use custom manifest".- After changing the runtime theme setting, select the manifest file "SimConnect.Pas.embed.manifest" mentioned above by clicking the open file dialog box using the elipsis button [...] next to the Custom Manifest edit box and navigating to the file, wherever you unzipped it to.- Once selected and the file appears it the "Custom Manifest" edit box, click "OK"- Resave your projectNow you're ready to Build and Run your project under Delphi XE2.*** Sorry, I'm not sure if/how/where this may / may not work in other versions of Delphi ***Another tip to make sure you're FSX/Delphi projects are consistently compiled... always add the following lines to "uses" clause in your main Project "program" code file (under Project -> View Source): SimConnectSupport in '<your specific path>\HeaderRT\SimConnectSupport.pas',SimConnect in '<your specific path>\HeaderRT\SimConnect.pas' Then, as usual, make sure you include these units in your "uses" clause in your main program units (where needed) for SimConnect function and constant / variable references.This just solves the environmental issues between SimConnect and Delphi XE2 causing people to not be able to build their FSX applications, or properly connect to the SimConnect.dll.... and those are the biggest hurdles people have been facing for a few years. Now, you may still have your own specific implementation / function call issues. There are other posts that can help you with those.This should work for you. Read thoroughly and carefully, apply your already established knowledge of these tools and it will all work out fine.

Dear HiFi,I found a bug in your XGauge Installation Wizard. After reading several posts here, and doing some testing of my own, I've come to this simple assessment.It would appear that when the XGauge installation wizard is run for the first time (right after ASE installation) the aircraft that were configured then are remembered somewhere. That's fine, however...If the user moves "certain" originally configured aircraft out of the \Simobjects\Airplanes folder (i.e. to retire them, or to have FSX ignore loading them) and the XGauge installation wizard is run again, the wizard falsely displays the error "Problem checking for access rights to FSX aircraft folder..." blah blah blahIn my case, I can simply put back the aircraft I've moved aside while I run the wizard for new aircraft I've added. For people who uninstall aircraft, the only way to solve the problem you created is to either uninstall ASE and reinstall it... or to reinstall the aircraft so the XGauge Wizard can see it so it can run.Interestingly, I used your "UNINSTALL" option to remove the XGAUGE panel reference from all the aircraft thinking I could then move the unwanted aircraft aside safely. Nope! I tried to run the Xgauge Wizard again, to add the gauge to only my desired aircraft remaining in the \Simobjects\Airplanes folder... and the error came back again! So I had to put all the aircraft back so the wizard would run.Not sure what happens to people that "uninstall" aircraft that were once configured by the wizard. I suspect they might have to reinstall ASE from scratch. But I have no intention of testing that for you too.Poor implementation. Please fix.

This issue existed prior to SP1, but it also came through into SP1. Did complete reinstall. All else is fine after several flights (thanks PMDG!)SITUATION: If the aircraft is loaded on the tarmac and the sound device is set to "speakers" (or "headphones"), all works well through the initial device. However, if you switch the device to another AFTER the aircraft is loaded -- at any time (before, during, after flight) -- the NGX sound no longer comes out anywhere. And, if you switch it to the original device... still no dice.Any/All other sounds from FSX comes the the correct device, just not the NGX sounds. Headphones and speakers all work fine. For what it's worth... headphones are analog 3.5mm jack (not USB).Please advise.

I had posted an "A/T disengaging" issue yesterday and thought it might have been related to the weather engine. Now, I'm not so sure. My issue of the A/T disengaging is shortly after I reach cruise altitude... and this didn't have until I installed HF4 also. If anyone on this thread has any ideas about my situation, I'd appreciate ANY assistance. My thread is here: http://forum.avsim.net/topic/350101-autothrottle-disengaging-at-cruise/

Tried different Wx engines (ASX, ASE, FSX, as well as static "clear skies" option). After all that, I'm not sure it has anything to do with the weather at all. It may be a "throttle issue" period. OBSERVED BEHAVIOR:- Climb to cruise altitude successfully, and smoothly- About 5-minutes after reaching cruise altitude Engine #1 starts to accelerate and decelerate 13+/-% up, then back down to where Engine #2 is (this cycles up and down, over and over -- gets worse and worse)- Engine #2 stays fairly consistent (+/- 1%) while Engine #1 struggles. - Reset the weather and Engine #1 came back to where Engine #2 was. - Within minutes it starts to destabilize again. - After 10+/- minutes A/T disengages. - After A/T disengages both engines stabilize again, but depending on where I left my throttle, the plane begins to accelerate or decelerate ending up in either an "overspeed" or "stall" situation. Guys -- that's the best I can do to explain it. But since hot fix 2987 -- my enjoyment of the NGX has also destabilized. Any help for here would be immensely appreciated!

I will have do gather more information during the next flight. Although, just to try it out I unloaded ASE and loaded ASX (in mid-flight) and the problem "seemed" to be resolved. I know... that doesn't tell anyone anything, since there are so many variables that can effect the flight. I will check back with more information. But... I am curious though (regardless of my specific conditions) how many people have seen the sudden increase in A/T disengages since HF 2987.

Ever since I installed the most recent hot fix (#2987) I cannot seem to fly safely on autopilot because the A/T disengages. Prior to hot fix #2987 all was well. I've seen mentions about using the ASE weather engine -- which I am -- and that it may be causing problems. However, it clearly wasn't before HF 2987 and I flew dozens of flights successfully. Is anyone else having this same problem ?