JayBirdski

The Isolation valve would be your culprit.

Have never tried what you are attempting. Given that SOP is to start with entering PPOS and align, I suspect you're attemting a procedure it cannot handle. And, the INS remembers where it was last, which is why it will give you an error that must be cleared after enter PPOS if you have teleported to another airport somewhere. Sounds like something whacky in loading saved states. You might check at the simufly forums and ask them directly there.

Well the saga continues. I did get an email from my CC company saying a credit had been issued but no correspondence from PCA at all. Plane still flies. When I pulled up account info in control panel, it said I was in pending verification. Pretty sure I would be screwed were I try to re-install. Unfortunate they're actively trying to void those purchases but I think we all knew this was likely a mistake within their system we took advantage of. Perhaps it was just a bit too big of a hit to take even for the very short time it was on sale.

Same. Just tested again and it appears my activation is still valid in that the aircraft still loaded. I guess we'll have to see if they start forcefully de-activating if such a thing is even possible after its already installed.

Been waffling about this for awhile but at this price it was a no brainer. Thanks for the heads up. And yes it looks like the price got jacked up back up to $59.95US again but my original download link still appears to work.

4 out of 5 dentists recommend Simbrief as do I. http://www.simbrief.com/

+1

Its been quite some time since I used INS (Think back to RFP, but thats a different and sad story) and it was the CIVA which what I think you are probably are using although I am not a ConcordeX user so excuse me if my assumtions are incorrect. You could check present position against your flight plan, as you progress are they getting closer to your next waypoint coordinates? When originally entered did you verify waypoint distances in the INS against your FP? As far as I am aware, there are no offsets when using INS, its point A to B to C, etc. If a mistake was made at the gate, you might be in deep yogurt although I think you would've noticed that pretty quickly if your jet turned to an unexpected heading when you engaged INS nav. As for a quick way, Can you see yourself on some sort of moving map like VatSpy or an equivalent and are you where you think you are? INS also has a tendency to drift over time, an enroute update periodically is recommended but you must be within distance of a VOR for several minutes in order to do so. Here is my cheat sheet for that procedure, I think you might also have to have at least dual INS in order for this to work though. +++++++++++++++++++ CIVA INS Update Procedure Tune Nav2 to VORDME selector (on INS 1 or 2 only) to Waypoint select WP # rt click 7 then 9 to enter Longitude key enter coordinates then Insert Rt click 3 then 9 to enter Alt Press 2 then alt insert (1.5 = 1500) selector to dis/time, check distance with vor selector to WP, waypoint chg then WP# insert ins update flag should light and PI should decrease +++++++++++++++++++++ The CIVA INS was both the most satisfying and at times the most frustrating gauge I have ever used and is not user friendly whatsoever. I hope this helps in answering your questions.

You're not alone Heronjr. I pretty much as SOP must do a save before TOD and reload FSX and the flight, that gets me to the gate.

Might be unrelated but I had a lot of boot issues with a Samsung on a new install not too long ago that magically went away after I installed the Samsung Magician software..

Might I suggest you take a look at Simbrief and let it create your desired flight plans in any number of different formats, PMDG included. Highly recomended by 4 out of 5 dentists. http://www.simbrief.com/

You're a good egg Kyle, we still like you and appreciate your insights. Keep on squashing the FUD.

Download the 300 base installer again and run it.

That seems to have done the trick, thanks for pointing out the solution Mike. It was rather unintuitive though in that http://forum.avsim.net/topic/448775-08aug14-sp1b-for-pmdg-777-200lrf-and-300er-released/ says SP1b should update the 300 as well. But there is the little paragraph below that does say: +++ UPDATE YOUR 300ER AS WELL: We made a few minor cosmetic changes to the 300ER models and textures as well, and updated the 300ER installer that is inside your account at our ecommerce system. These updates are mostly really minor, but if you want the very latest please feel free to grab another copy of the 300ER from your download account. +++ Was really suprised the 300 base installer was required again and still available to me as I did not purchase the extended dowload.

I am in agreement with KrazyK, something is amiss here. I get the same version warning within OC. Have re-downloaded and installed SP1b, it of course said I already had it but re-installed anyhow. Restarted OC (Run as administrator of course) and it still says the 300ER is only at 6036 and that a new update is available, however, clicking ok to install update doesn't apparently do anything. When I load FSX, go to the CDU>PMDG Setup>About. It just shows v1.1 so not enough detail there to really say exactly what version of the 300ER I have. And as an aside I still do VAS out regularly with the 300 as well towards the end of long hauls which is what I typically fly but exiting FSX and loading an autosave from fsuipc towards the tail end of these flights gets me back in pristine shape so I can finish my flights without incident. The symptoms I hear when I know it's likely going to bomb out on me is what sounds like a repeating cabin chime every few seconds but no other visual cues. Win7 Pro x64 SP1 3770K 8GB GTX 560 (314.22) Asus P8Z77-V Pro/Thunderbolt

Yes, a -200 would be most welcomed.

Encouraging sign anyhow, one could assume it is now close to release.

Sorry to bring this up again but it does indeed seem to still be a problem with the navdata or the NGX's ability to interpret it. I'm currently on 1309 and got the same errors when using the FRDMM2 star. Changing it to NUMMY2 seems to have worked, vnav operational again. Is it the consensus that this is a Navigraph issue?

Never, Other than to jump in the default Cessna and investigate a new scenery or afcad install before I load a real tubeliner and go flying.

That would be a 75757 good sir.

The short answer is yes, an INS can be added to most any aircraft, at least those that don't replace bypass MS AP functions and instead use their own, For instance I would never try to shoe horn an INS into a PMDG package. What you're looking for is Civa INS, it is unfortunately not as easy as running setup and being done with it though. There is some panel config customizations that must be done. I'm not however a CLS user, I've only used it on on the RFP742 and DF727 back when I ran FS9. I cant offer you much more than this other than to say yes it is almost certainly possible. Hope you get it working, it is a fantastic gauge and an entirely different and very rewarding flying experience once you know what you're doing. There is a learning curve so be warned. http://www.simufly.com/ins/

One more item that might save you some frustration so near the end of a long haul is to make use of autosave, I believe fsuipc does it. I think mine saves every 15 minutes or so. Some planes are more receptive of this than others as far as saving their panel state.

Gerry is correct. I believe all the NGX panels alias back to this file. I use 3.000, tastes great and less filling too. \Microsoft Flight Simulator X\SimObjects\Airplanes\PMDG 737-800NGX\panel\panel.cfg [VIEWS] VIEW_FORWARD_WINDOWS=MAIN_PANEL,MINIPANEL VIEW_FORWARD_DIR=3.000, 0.000, 0.000 VIEW_FORWARD_ZOOM=0.8

I use Keepass which is by default a password manager but is also good at storing keys, notes, account names and passwords, you name it.

I have high hopes for BBS, I remember the PSS 777 when first released was head and shoulders above anything else at the time functionality wise. The bar is much higher now though.