kbowler

Hi I just attempted to purchase the new "Greek islands" training program and chose the Greek Islands option on the appropriate page, which showed the programs I had already purchased. When the payment went through Paypal, it showed on their email as Amsterdam. As I had already bought Amsterdam some time ago, it was impossible to chose that option anyway. So something is screwed up on your website. I have now paid $11.99 for the Greek Islands but it is obviously not showing it as Purchased as somehow it thinks I was buying Amsterdam. Could you please advise how this can be sorted. Keith

Hi Niklas Thanks for your reply. I have had chance to check a few more aircraft since my first post, and I have found a number of them which work OK, and others do not. I guess it just depends if the developer either decided to implement the features (or not) with his own code, or let the internal P3D code do the job.

Hi Having just re-installed Windows 10 and moved over to a clean install of P3D v4.4, I was setting up commands on my PMDG aircraft (B737, B777 and B747) and realised that the "rudder trim center" and "aileron trim center" keys I had defined do not seem to work on any of these aircraft. These commands do seem to be functional on, for example, the P3D Lockheed C69A, so I know that they do work on some other aircraft. Are these commands just not implemented on the PMDG aircraft, or is there a problem with my installation? Regards Keith

Hi I have just purchased the Falcon 50 from SimMarket and seem to have two possible zip files: one shown as v1.3, the other v1.4. Can anyone explain the difference as I can see no reference to an update to v1.4 on the Flysimware website. I am currently using P3D v4.3, so which version of the aircraft is more suitable? Thanks Keith

Thank you Kyle for your reply. In a sense, yes, I was looking to see if what I was seeing was a genuine bug, or something peculiar to my setup. Verification by others would give me ample justification for reporting it as a genuine bug. I did not want to waste the developers time by making it "official" at the outset, but in view of what you have said, I'll get in touch with official support. Regards Keith

I do not know if anyone has mentioned this, but if using kg in the FMC and EFB, the WT & BALANCE value in the EFB for FUEL DENSITY (which should be in kg/l, shows up as 6.699 (i.e the lbs/gal US figure) when it should be 0.803. Using the "Read from Aircraft" button does however insert the correct value. Nevertheless for the sake of correctness, it would be nice to have this value set initially as 0.803, as at present it causes the fuel in each tank to show ridiculously high maximum figures until the button is pressed. Regards Keith

I had a similar problem this morning but a support ticket got a reply from PMDG. Apparently Navigraph did an update at their end which caused the EFB not to connect. They were made aware of this and have now fixed it. If you load the aircraft up and try again, you should find no fault message and the database recognises your airports when you do a search. My thanks to Chris Makris at PMDG customer and product support for a quick reply to my ticket and to Navigraph for a quick fix. Regards Keith

Hi Dan Thanks for the reply. After checking again this morning, I realise that the 700NGX liveries are also missing, though the 700NGX WL versions are there. I have opened a support ticket as you suggest , and sent the log.

Hi Yesterday I updated all my PMDG aircraft including the Operations Centre using the usual Operations Centre updating procedures. I got an error window when updating the P3D v3 version of the B737 NGX. Suspecting a problem, I decided to uninstall the aircraft from P3D (via the Control Panel), but also manually clean out all the other files for the P3D v3 of the aircraft. As I also have the P3D v4.0 version of the B737 as well, this also uninstalled that aircraft at the same time, though I did not manually clean any files from this version. Anyway, I downloaded the latest versions of B737 (both base pack 800/90 and 600/700) from the PMDG website, and re-installed (which installs in both P3D simulators simulataneously). Although the aircraft itself seems OK in both versions of P3D, I now cannot see any B737-600 liveries in the P3D v4 version. When I look in the livery downloader section of the OC for this version, no -600 liveries are available for download. These do, however, appear as available in the OC downloader section for the P3D v3 version of the aircraft, which I shall obviously have to re-download, having cleared out all references to liveries with my clean up procedure! When I look in the P3D v4 Simobjects folder, there is a folder for the -600 and it contains several texture files for different liveries, but I assume these are left over from the previous installation. More to the point, why is the OC not showing -600 liveries as available for download as I thought this was a function of what was available from PMDG and should be visible if the 600/700 is installed. The -700 liveries do show up in the aircraft menu, and in the downloader. Did the original updating of the Operations Centre cause this problem, and if so how do I get my -600 liveries back in operation?

Hi Scott Thanks for the reply. I am at least happy to know it is not something wrong with my particular setup. I'll just have to remember to operate a switch prior to doing anything with an aircraft. It might be embarassing to lose power or displays if you have just taken off on Vatsim! Regards Keith

Hi I have noticed with several aircraft that after loading the aircraft and then loading Linda, the first press of a button or switch on the TT panel seems to do a spurious action. This happens even when there is no action defined for that button, and if there is an action defined in Linda, it does not do that action. For example, with the PMDG B737, with engines running and ready to fly, pressing a button on the panel switches a sequence of actions on the overhead panel including switching off fuel pumps and emergency lights and blanking the screens. The engines continue to run. The button used in my test was defined to switch on VNAV, but I have used other buttons and switches with the same result. After that first press, any further button/switch presses seem to do their correct actions. With the Just Flight PA28R, for example, this first press stops the engine and switches the alternator off. Start the engine and subsequent button presses again work correctly. I have not tested every single aircraft, but the TFDi design B717 also exhibits similar weird behaviour in this way. It seems as if there is some buffer being flushed with the first button press sending rubbish to the aircraft causing a variety of weird actions depending on which aircraft is loaded. It only seems to happen with the TT panel. Buttons on the CH Yoke, Microsoft Sidewinder joystick and CH throttle quadrant are OK. Details of setup are: P3D v4.0 Linda 3.0.3 Module for the aircraft described or Default version (Just Flight PA28R). FSUIPC 5.113. Incidentally, I checked all places where TT panel buttons/switches could be alternatively defined i.e P3D native controls and FSUIPC and none of them contain commands for the TT panel. The problem only occurs if I load Linda!, and it happens whether I load Linda before or after the simulator. Regards Keith

Hi Andrew Thanks for your reply. I guessed there might be a bug somewhere in the current version as previous versions have worked so perfectly for me. I look forward to the fix. Keep up the good work. Regards Keith

Hi Further to my first post above, I have just cleared out Linda from the Modules folder, and re-installed. Again, the same issue shows up. It does not matter which aircraft are loaded, Although the chosen button action shows in red for that button slot, as soon as 'Save' is clicked, the Linda module reloads, the Linda window is refreshed, and that button definition has disappeared rather than changing to green. I have tested all such H1:x type buttons and they all fail in this way, yet I can define actions using them via FSUIPC direct or directly in the P3D v4 native Controls section, without any problems. Is the latest version of Linda blocking these types of switches from being defined? They certainly worked OK with FSX-SE and P3Dv3 in earlier Linda versions. By the way, all other non H1:x buttons are defined correctly and saved as expected! Keith

Hi I am trying to define button presses on the VRInsight TT panel for those buttons recognized as part of the Hat Switch H1:1 to H1:8. Unfortunately when I define the action and click save, the action is not saved and the H1:x slot in question remains blank. I checked similar hat switch type buttons on my Yoke and joystick, and none of this type of button definition is saved for these either. I am running P3D v4.0.28.21686, FSUIPC 5.113, and Linda 3.0.2.714. The controls work fine in my FSX-SE setup, and register correctly in the appropriate Linda slot when pressed, they are just not saved! Any ideas? Keith

Hi If I have defined switch and button definitions for an aircraft, e.g PMDG B737 in P3D v3 (or FSX-SE), which files/folders do I need to move to the Linda setup in P3D v4 so I do not have to manually define each action again in the new simulator. Thanks Keith

Hi Keven I have the solution though I feel embarrassed to tell you. In my confusion over another problem with the CRJ and Chaseplane, I must have defined the views for the CRJ700 using the already existing Bombardier profile "Bombardier CRJ 700" , which is the standard Microsoft CRJ700 in my FSX-SE installation. I had completely forgotten about that aircraft! Having defined what I thought was the correct aircraft, I then looked for the equivalent " Bombardier CRJ 900", to define that. There was obviously no aircraft of that name, which is why I must have used the former profile for that as well. The actual aircraft names for the Aerosoft aircraft are, of course, "Aerosoft CRJ-700" and "Aerosoft CRJ-900", which are in the presets list. It was staring me in the face all the time! I can now go ahead and define the correct profiles! How stupid! A case of overthinking and just being fixated on the wrong details, or just a senior moment! Anyway thanks for your help and patience. Regards Keith

Hi Keven. Perhaps I did not explain my problem well enough. The method you suggest was always the one I used when defining a new aircraft by importing similar views from another aircraft using the import button at the bottom of the page in the active preset column. I'll explain what actually happened by giving you the specific example. I was working with the Aerosoft Bombardier CRJ700, and defined inside and outside views for it from scratch. Next I loaded the Bombardier CRJ900 aircraft, and in my rush to get views to it, I used the pull down menu at the top of the preset page, and clicked on the CRJ700 I had just defined. This assigned all the views from the CRJ700 to the CRJ900 and changed the label at the top of the page to CRJ700, even the CR900 aircraft is loaded! Clearly that is a bit confusing and not ideal. I should have used the method you suggested, in which case, I believe, the label at the top of the page would still be CRJ900! My problem is now, how can I get back to the original situation, where when the CRJ900 is loaded, the aircraft label at the top of the preset page shows CRJ900 (as given by the aircraft folder names in Simobjects), and the preset page is clear of any views. I cannot just delete these views for the CRJ900, because I am effectively deleting the views for the CRJ700 (as well as the CRJ900), and in any case, I think the label at the top of the page would still read CRJ700 not CRJ900. Regards Keith

Hi Keven In defining presets for a new aircraft, (we'll call it aircraft A), I clicked on the top menu and chose the presets for aircraft B which appears to import all the latter's presets, so the "top" label shows aircraft B not aircraft A. What I would like to know is how can I get back to this top label showing the loaded aircraft A so I can manually define fresh presets from scratch for this. If I delete the current individual presets (those imported from aircraft B), it deletes them so they no longer exist in aircraft B when I load it. What I want to do is break the link between aircraft A and the imported presets for aircraft B, without losing aircraft B's presets, and get the correct name in the top label (i.e aircraft A) with a clean preset page. I had thought that the label at the top of the preset page was always the aircraft currently loaded and recognised by its folder name as appearing in the Simobjects folder, but this appears not to be the case. In the past I have imported presets individually using the arrow at the bottom of a preset section, so the aircraft label at the top has remained the name of the loaded aircraft. Now, having a different top label to the loaded aircraft is a bit confusing. I hope this makes sense. Regards Keith

Hi Keven I checked both aircraft.cfg files (for CRJ 700 and 900) with Notepad. I entered dummy info at bottom of the first one, and saved without problem. I then cleaned this dummy info out, and resaved OK. For the CRJ 900, I just saved the original on top of itself, again without problem and so both files were not locked. When I re-started P3D v4, I got the usual Chaseplane re-configuration information for these two aircraft. When I checked the inboard views, they worked perfectly for both aircraft! I rebooted, checked again, defined a new inboard view, and checked the key assignments. They all worked as they should. Do not ask me why it worked, but it obviously has. Thanks for your help. Regard Keith

Hi Keven After some further experimentation, I discovered that the inboard views can be made to work if you load a default aircraft, "Piper Cub", for example, then the CRJ. However, if you then go to an outside view (no flashing views this time) and then try to go back to an inboard view, the inboard views no longer work and we are back to the fault condition. Also, I notice that If you press "A" or "S" during the initial phase when the views work., this also causes the same problem. Normally with other aircraft, after pressing "A" or "S", you can get back to the Chaseplane internal views by choosing one of the Chaseplane inboard presets, but not with the CRJ. Any clues here? Oh, by the way, deleting the cache has no effect. Regards Keith

Hi Keven Just to add further to the same problem, after update to CRJ v1.0.1.0 today, in both P3D v3.4 and P3d v4, the Chaseplane camera system for this aircraft has gone haywire similar to previous posts. The inboard cameras views are fixed at a default value, and will not alter. When I click on the first of the outside views, the screen flashes rapidly for a second or so, then settles to the correct outside view. I can then change between outside views correctly but going back to inboard views, nothing works and I get the same default view. The other very odd thing is that if I try to use the key assignments to move around the screen, when in inboard view mode, they do not do what is defined in the Control Assignements, For example, left and right arrow keys are supposed to move left and right, but they rotate left and right instead. However, in outside view, the keys work correctly as defined in the assignments. All other aircraft appear to be unaffected, at least from the quick sample I checked. There is something weird happening with this aircraft! I think the system worked OK before the upgrades, but I did not check it out thoroughly as I have been away from this aircraft updating other items. Regards Keith

I, too, no longer have any working hat switch on my CH yoke, and the Xbox controller which I use to move Chaseplane around the cockpit is not being recognised since recent update. This applies to any of the simulators FSX-SE, P3D v3.4 and P3D v4.

Hi I am not entirely clear about current best practice when updating the B737, B747 QOTS II, and B777 with P3D. While I know it is advised that an update via a full installer release requires an uninstall, what is the current best advice on how to achieve this, particularly where P3Dv3 and P3Dv4 are both installed on the computer. The reason I ask is that I still have a document I prepared based on Kyle's earlier advice for updating the B777 and B737 which suggests uninstalling via the Control panel, but then manually removing various files ; i.e Delete any references to the NGX or 777 in the [Sim]\PMDG folder Delete any references to the NGX or777 in the [Sim]\SimObjects folder (where [Sim] is your FSX or FSX:SE directory) Delete any references to the NGX or 777 in the %AppData%\Roaming\[Developer]\[Sim]\SimObjects folder I notice this applies to the FSX or FSX-SE versions, but does it also apply if you want to update via a full install on the mentioned versions of P3D. Might it be useful to put a sticky on the forum summarising current best practice as circumstances have obviously changed with the recent release of P3Dv4 and the possibility of various mixed configurations of FS, notably FSX, FSX-SE, P3Dv3 and P3Dv4, being installed on a FS computer. Thanks Keith Bowler

Hi Mike Thanks for your reply. I agree with you. My understanding is that if FSX-SE is installed on a clean machine, with no previous version of FSX having been installed, the system installs all files on the machine as if it was FSX, and labels folders accordingly, barring of course the fact that FSX-SE is put into the Steam folder. I am therefore at a loss to understand what caused this, though I have installed a fair number of older aircraft add-ons into FSX-SE. I vaguely remember one which did not work correctly when I chose the FSX-SE installation option, so ran the installer again treating it as FSX and it seemed to work. Whether that caused an additional Flight Sim Documents folder to be produced, I have no idea. Not surprisingly, most of the usual flight files are in the "C:\Users\Owner\Documents\Flight Simulator X Files". The folder "C:\Users\Owner\Documents\Flight Simulator X - Steam Edition Files" only contains the Tutorial 2 flight files for the PMDG B7737NGX, but there is also a duplicate copy of these in the other folder. I do not particularly want to start fiddling with the registry to correct things, even supposing I knew what to alter. I did wonder whether deleting ASN and then re-installing it with the folder "C:\Users\Owner\Documents\Flight Simulator X Files" folder removed, might work. I suspect, though, that unless the relevant registry information is cleaned out, it might just re-install with the same problem. I might give ASN support folks a ticket and see if they have any ideas before doing anything too drastic. Regards Keith

Hi Thanks for your reply. I think all the paths are set correctly in ASN as the weather gets injected into FSX-SE correctly, and I have checked that they make sense. Unfortunately there is not an option to set up the location of where ASN looks for wx.pln. I'll have to keep hoping someone at ASN or a knowledgable user notices the post; failing that I suppose I could put a ticket into ASN support directly. Regards Keith