aerofoto

Try loading a default aircraft (any AP featured default M$FS simulation). Let it load and stabilize in FS. Ensure the AP is "OFF" .... and none of the AP NAV items are engaged. Then .... select your B757 of choice and similarly let it load and stabilize in FS (AP and all AP NAv items "OFF") before getting under way. An see if that has any positive impact. Sometimes little idiosyncrasies, such as you describe, can be resolved through loading a default M$FS simulation .... in advance of the simulation you actually intend flying. In fact producers of some add-on simulations (including HJG) do recommend this as a standard practice. It may sound as "boring and pointless as hell", but, it's actually a known and recommended FS remedy "in some cases" .... as it simply ensures "everything" is set up in accordance with its default configuration "from the start". MRC

That figures because the DMFS simulations are (and have always been) provided as "separate aircraft base pack, panel, and sound pack folders" .... with their panel and sound folders aliased outside the base packs. If the base pack sub folder "aliasing process" can't find a panel or sound folder according to where it's directed (due to installation errors or these other assignments being non-existent), then, the entire simulation simply "IS NOT" going to be displayed by FSX. In the case of updated files mentioned earlier within this thread. The updates provided by HJG should only be used with the DMFS file versions offered by HJG. What HJG offer is the "original/last release version" DMFS aircraft base packs .... with "fixed" panels, both "original and new" sound pack options, and separate FDE updates (for the TRIDENT's and VC10's only at this stage). "DO NOT" apply any of the HJG supplied updates to other updated versions of the DMFS files though as what HJG offer may not be compatible with other updated versions of these files (and vice-versa). One may end up in a mess trying to do so. MRC

I hasten to add .... HJG have recently fixed all known issues associated with each of the original DMFS panels (primarily APU and engine startup faults), and have added a few extra details not previously included as well as making each of these panel FSX portable too .... whilst at the same time ensuring the look, and functionality, of each DMFS panel remains "COMPLETELY UNCHANGED". These updates were released last December (2021). The "ORIENTATION NOTES" .... within following the linked HJG announcement .... clarify some of the applied updates/improvements .... https://tonymadgehjg.proboards.com/thread/10055/website-update-december-20th-2021 A suit of FDE improvements (for the TRIDENT's, and VC10's only at this stage) were also released by HJG last December .... along with Benoit PLAMONDON's "NEWEST" (2021 produced and HJG exclusive) sound packs for the DMFS BAC ONE-ELEVEN, DH COMET, HS TRIDENT, and VC10/SUPER VC10/C1K and which have been "customized" for each of these simulations .... as explained within the above-linked thread. MRC

You'd do better to post this query at HJG since that's where most of the DMFS support is now provided (it's awkward to try'n offer support on more than one forum), but, in doing so you also need to state "precisely what you've done, step-by-step, in order to install everything". The principle DMFS aircraft base pack files remain as originally compiled by DM .... "AUTO-INSTALLERS" .... HJG have altered nothing in this regard. The only exception to this rule is the "NEW" TRIDENT 1C, -1E, SUPER 3B, and SUPER VC10 1154 base packs which are manual installers compiled by HJG and in accordance with established DMFS installation protocols In the case of FSX a "manual install" is encouraged though .... since the DMFS auto-installer process is engineered in favor of FS2004. Again you need to state you case at HJG .... but briefly .... the following applies (as already hinted by "ANAISMITH") .... You need to ensure you have a "DMFS Shared Files" folder created inside your Sim Objects folder (I think it is in FSX) and into which both Panels and Sounds are each installed. The CFG's, inside default Panel and Sound folders accompanying the base pack, are each aliased to the said DMFS Shared Files folder .... so .... if you don't have the above recommended configuration, then, it's likely you'll be confronted with an FSX "No Show" .... by virtue of the fact the simulation can't find the files it needs in order for the simulation to be displayed. Also .... you need to open the "Replacement Files For FSX" folder (inside each panel folder) and copy & paste its contents (usually a single file and an FSX specific PANEL CFG .... from memory) inside each principal Panel folder and overwrite the FS9 files there by the same name. That is how DM compiled everything .... nothing has changed. MRC

"PRECISELY" :) .... and very well stated too "CLAWSONA" ;) MRC

Do an FS>COM search as follows .... CLS world airways DC-10 or .... Kevin Alexander Do that and it'll turn up a number of WA (and other) DC-10 textures for the CLS product. MRC

I believe you're right Tom .... in regard to all of the above. HJG do occasionally undertake what some people refer to as "FAKE" (WHAT IF) liveries. Some people just like a certain airline livery, on a particular aircraft type, despite the fact such equipment was never flown by an operator. The group doesn't go out of its way to do this though simply because representing "FAKE" (WHAT IF) subjects can be a right royal "pain-a-place-where-the-sun-don't-shine" since its focused on historic reality primarily, but again, it does occasionally venture into the realms of "BS" .... usually as the result of requests that have been made to it as per the following -linked subjects .... https://simviation.com/hjg/fantasy/fantasy.htm I perhaps need to say most of (but not all of) the above linked "FAKE" (WHAT IF) livery subjects are aircraft types that were actually planned/considered (acquired i some cases too), but, ultimately never eventuated or entered service .... or .... it's been done just to see how the identity of a particular airline/operator might have looked on an certain aircraft type. People are "welcome to ask" .... if they wish .... but .... HJG don't guarantee such requests will be honored (technically speaking the group isn't a repaint service) given its primary focus on "real world history". MRC

"THIS" thread's almost a year old now :) FSX requires strict adherence to precise FSX specific installation protocols. Depart from these .... or make the slightest mistake .... and one's then exposed to potential for FS aircraft recognition and display related issues .... which HJG loosely term as "FS NO SHOWS". It's important to remember all HJG aircraft base packs download configured for FS2004 use .... MEANING .... all PANEL and SOUND folder CFG's are aliased to the default FS2004 PANEL assignment (usually the B737-400 or B747-400) and also to the default FS2004 SOUND assignment (the B737-400). Using these files "in FSX" the CFG's for both PANEL and SOUND assignments need to be manually edited to read in accordance with "FSX SPECIFIC" default aircraft PANEL and SOUND assignments .... usually the B737_800 in the case of twin-engine aircraft types. If these aren't edited correctly then FSX simply wil not recognize and display the installed aircraft subject. As for FLTSIM.XX data. The installation instructions for all HJG textures clearly states the very first entry must always start at "0" .... or "FLTSIM.0" .... with all subsequent entries then being edited to read "in strict numerical sequence". A particular detail I'm aware of though that can also cause "NO SHOW" related issues is in regard to the TITLE= data line within FLTSIM.XX data .... as is evident per the following variations which were recently discovered within a community members installation of over 50X B737-300's assigned to the very same FSX base pack .... title=HJG_737-300 title=HJG_737-3T5 title=HJG B737-3Y0 title=HJG B737-300 title=Boeing 737-3Y0 title=B737-3Y0 The above "lack of uniformity" among these entries (as can clearly be seen) caused some of this community members add-on textures to "not display at all". The basic aircraft type/product description within the TITLE= data line of FLTSIM.XX/ADD TO AIRCRAFT data really needs be/is advised to be "completely uniform" for all additional texture installations .... as follows .... [fltsim.0] title=HJG B737-300 [fltsim.1] title=HJG B737-300 [fltsim.2] title=HJG B737-300 [fltsim.3] title=HJG B737-300 [fltsim.4] title=HJG B737-300 If this data isn't "uniform" .... MEANING .... if too many variations appear among this data .... then .... it seems to confuse FS and some texture additions simply "will not display at all" ..... despite otherwise having been edited in accordance with correct numerical sequencing and no other basic errors having been committed. WHY DO I KNOW THIS ? 1. Because it's happened to me (in FS2004) :) 2. Because of it's also happened to 3 or 4 other people (in FSX) too and since since 2017 .... each of whom I "successfully" resolved FS aircraft recognition and display problems for on the HJG forum ;) I'll be the first to acknowledge that "prior to" 2017 our then system in use actually allowed for the existence of this sort of "non standardization among FLTSIM.XX data to occur and did promote the possibility for FS recognition and display problems. Having since become aware of this particular issue though our current system in use, since 2017 (that's in regard data uploaded since this time), limits potential for this sort of problem .... and since 2019 has "almost eradicated" .... barring any undetected typos prior to release and which still happen to even the very best of us. In respect of the SIM= data lines within each FLTSIM.XX data. This data .... which relates to the AIR.FILE name for each aircraft type base pack .... should be completely "error free". It's essential though that each texture is used with the correct aircraft base pack for which a texture subject is intended. The SIM=/AIR.FILE name within FLTSIM.XX data accompanying each aircraft type texture is different .... being named for the specific aircraft type/sub version it's intended to represent. Having to rename any FLTSIM.XX based SIM= data line in relation to an AIR.FILE name is an absolute sure indication that a texture "isn't" being used with the correct/intended aircraft base pack/model .... and that will lead to other than FS recognition and display issues. If using HJG panels and sound packs it'd also be a grave mistake to swap an AIR.FILE (FDE suite generally) too. The weight and engine thrust statements within HJG FDE's varies among aircraft types both intentionally and by necessity. Swapping an AIR.FILE/FDE will affect the performance of some simulations .... and their audio too .... either positively or negatively. The correct/recommended texture, base pack/FDE, and panel configurations for everything HJG offers are clearly stated within the forum based manuals for all of its simulations. 9 out of 10 problems occur only when instructions aren't read or are otherwise misunderstood .... but .... which HJG are also quite happy to assist resolutions for .... preferably on it's own forum though and by virtue of the fact that's where all of its accumulated resource and expertise is located. Some of this this may seem complex to read, but, it's not by any means .... provided people simply install data correctly/precisely and as HJG advises it should be installed :) MRC

The one I like best is his L-18 LODESTAR :) MRC

HJG forum's the best place to pose this sort of query (such can easily be missed here by those "in the know or otherwise responsible" for the groups offerings) since any required information can be gotten more quickly, directly, and accurately right from over there :) FYI .... HJG's entire flight line of C-135 simulations were all superseded by "V6.1" files late last year and which were released as announced on the HJG forum on "December 16th 2020 .... https://tonymadgehjg.proboards.com/thread/9862/website-update-december-16th-2020 .... and as also publicized per the following FS.COM Community News item presented around the same time .... https://www.flightsim.com/vbfs/content.php?21800-HJG-2020-Christmas-Website-Update Much needed "FDE enhancements" constitute the upgrading of all HJG supplied C-135 TYPE simulations .... among which a few new aircraft base packs were also released .... along with entirely new customized B707 sound packs (dependent on the new FDE and also used by the HJG C-135 line) .... as well as a small number of panel edits supported by a new panels/gauges core files suite too. Same time these new V6.1 C-135 files were released .... HJG's entire B707 flight line was also upgraded to "V7.1" based on the same upgrading and benefiting from the very same panel/gauge/ and audio enhancements too. HJG V5.0 (and earlier) C-135 and HJG V6.0 (and earlier) B707 simulations are now "old hat" and been made "redundant" by these "NEW" files. More concerning the development of these new files may be reviewed per the following links .... C-135 SERIES https://tonymadgehjg.proboards.com/thread/9817/135-modifications B707 SERIES https://tonymadgehjg.proboards.com/thread/9822/b707-720-modifications MRC

That's correct .... in regard to both the ENVMAP and some people liking, or disliking, it's influence over metal finishes. Guess the result depends largely upon how FS artists compile their representation/s of natural metal surfaces .... since not everyone (including HJG artists too ... whom have been modifying their finishes only since around 2008/9) works according to the same theory. Re the ENVIMAPI .... I replaced my own FS2004 ENVMAP years ago .... back around 2008 (I think it was downloadable from FS.COM) ..... and have, myself, been very pleased with the way in which it influences what I use in FS .... of course it's influence isn't over just metal finishes along, but, everything generally. A few more images of metal finishes base on my above, and earlier, comments .... and using what I like to fly in FS .... MRC

But definitely not chrome .... in the RW image I mean. Your images of the HJG offered texture/s better demonstrate the groups "preferred finish/metal treatment" better than my own images do And "YES" .... the "FS time of day and season" aspect of environmental influences will always dictate what's ultimately viewed .... and quite significantly too. MRC

Where "metal finishes" are concerned (among other things .... including the like dirt and weathering too) different people like different things .... appreciably ;) HJG artists each use their own "non-chrome-like" metal texturing (since 2006 at least) though to aim for/replicate a more natural polished metal appearance .... http://i.imgur.com/SIKqNEu.jpg .... BUT .... they completely avoid the "Chrome Look" .... simply because whilst aircraft surfaces tend to be shiny/reflective after polishing (these dull down quickly whilst in service though) they're certainly not chrome or chrome-like in appearance. The Chrome look is probably over doing things IMHO .... but again .... people like different things :) Reflective metal textures really started coming into vogue with FS2002 .... one of the first (I recall) being a BAe 146 in AA livery but which was horrendously chrome-like in its appearance. People liked it at the time ... .probably because it was vastly different than anything else that's been done previously, but, I recall a lengthy debate about this sort of texturing on the HJG forum during 2002 (log lost given the changes of sever and forum transition prior to 2006) .... and most eventually agreed that whilst it "looked impressive" from an artistic standpoint it also tended to appear "un-natural" too .... so .... HJG artists have done what they've done, and they way they do it, since 2006 MRC MRC

"YES" .... they are FS9 Paul .... but also FSX portable too .... as are their supporting panels/gauges as well. HJG's "NEW" and customized B707/720/C-135 sounds packs (released last Christmas) are offered as separate FS9 and FSX specific versions also. MRC

That could happen if you'd set and activated a restore point dated/timed "prior to" the installation of the said simulation/s. HJG currently offer 3 B-CAL B707 subjects as follows .... The short fuselage B707-120B G-TJAA 1979 .... And the standard fuselage B707-320C G-AYEX 1981 .... And the standard fuselage B707-320C G-AYZZ 1971 (leased from AMERICAN AIRLINES during the BUA/B-CAL era) .... All supported by customized panels for each aircraft type .... and "BRAND NEW" (just recently released) customized P&W JT3D (series) fanjet sound packs also. MRC

No problem :) .... and Tom should be included in that thanks too since his knowledge tends to parallel my own ;) The double lobe of the B707 fuselage is probably a bit less distinct than is the case with the DC-8 .... and from memory it's probably a little exaggerated/over scale within the 1/144 AIRFIX B707-420 kit, but, is pretty well/better proportioned within the much more recent 1/144 scale MINICRAFT B707-320, -320B/C, and -420 kits. Mark

Model you built was very likely the 1/144 scale AIRFIX kit .... and which is a B707-420 version specifically .... similar to the -320, but, quite different from the -320B, -320B/SCD, -320B ADV, and -320C and each of the earlier series B707's too. "We" do a lot of plastic modelling ourselves .... https://tonymadgehjg.proboards.com/thread/7876/latest-modelling-project Have several of the said AIRFIX kit in captivity here (various releases of it) .... among several hundred other kits within "our stash" too. MINICRAFT also released the B707 in 1/144 sale too .... in -320, -320B/ADV, -320C, and -420 form, but, so far as I'm aware these never became available until the 1990's. Again your kit sounds likely to have been the AIRFIX release .... especially given you mention its BOAC (or BRITISH AIRWAYS) livery. In regard your comments .... That was a basic characteristic of all B707 and DC-8 fuselages. That was a characteristic of each of the turbojet powered B707's (from the -120 through -320 series .... and including the -420 .... as well as early B720 versions too, but, not in regard to "B" sufficed" fan-jet powered upgrades of both the -120, -138, and B720) and DC-8's .... though the type, and number of pipes (daisy petals) varied between P&W and RR type engines .... again the AIRFIX -420 kit fits this description perfectly. "YES" .... there "is" .... if you're meaning for FS use. As Tom has recommended ("THANKS" Tom ;) ) HJG offer the "complete" B707/B720 family (along with most major variations of the C-135 SERIES too .... similar to, but quite different from, the B707's) in the form of the following specific aircraft type versions .... - B367-80 - B707-120 - B707-120F - B707-120B - B707-120BF (freighter) - B707-138 - B707-138B (early production) - B707-138B (late and upgraded early production) - B707-220 - B707-320 - B707-320F - B707-320B - B707-320B ADV - B707-320B SCD - B707-320C - B707-320C (freighter) - B707-420 - B707-700 - B720-A - B720-AF (freighter) - B720-B - B720-BF (freighter) The majority of the above HJG family are represented by several models featuring each of the physical variations applicable to each version .... as related within SECTION 1 of he following-linked "NEW" HJG B707 manual .... https://tonymadgehjg.proboards.com/thread/9861/b707-installation-handling-notes Same in the case of the following-linked HJG the C135's too (just for completeness of reply) .... https://tonymadgehjg.proboards.com/thread/9860/135-series-installation-handling-notes These simulations have each recently been FDE upgraded .... as related throughout each of 2X pages within the following-linked HJG forum report .... https://tonymadgehjg.proboards.com/thread/9822/b707-720-modifications .... and also additionally supported with "NEW" sound packs as per the following-linked audio-visual presentation too .... Note you say "diorama" .... but .... if it's static AI you want, and for FS purposes only, then, not sure how the UI HJG models might impact things. Given PC and graphic resources are now far more powerful than when these models were conceived there should be any major problems though MRC

I'm pleased he's gone to the trouble of doing this .... because his doing so now confirms the panel he's using "IS NOT" the version hosted/recommended by HJG :) Although he states using HJG supplied B737 simulations I acknowledge he "DOES NOT" actually state using the panel hosted/recommended by the group, however, such couldn't be definitively ascertained from either of his earlier postings. As will be verified per imagery featured within the following-linked forum based manual for the HJG supplied B733/4/5 simulations .... https://tonymadgehjg.proboards.com/thread/8798/b737-300-installation-handling-notes .... "THIS" .... is the panel version hosted/offered/recommended by HJG .... And .... "THIS" is the OH sub panel portion (part of the MP view) of that panel and with it's AUTO-ENGINE START feature hilited accordingly .... Comparing the above imagery with his own it's evident both panels are "quite different". Some might wonder .... surely one can use any alternative add-on panel with any other simulation. The answer to which is both "YES" .... and "NO" .... because although "can" be done in "some cases" and without incurring problems in other cases such can't be done without incurring issues of various magnitudes. The reason for this's because "some" panels are dependent upon certain FDE elements associated with some simulations .... and if such elements (standard or not) are lacking then issues may arise that require alternative/customized procedures being employed. Whilst the B737 FDE offered by HJG is VL in origin .... it's also been significantly recompiled/"improved" too .... and which may (I don't say it will though) result in certain features of "some" non-HJG sanctioned panels possibly not functioning. Whether or not such applies to this particular other/non-HJG panel isn't known though .... simply because HJG didn't compile it, but, it does seem, from the evidenced provided, that such might be the case. Using the groups recommended (mostly customized) panels with HJG simulations will/should result in no issues arising at all (provided they're they're installed used correctly to start with) .... but .... if alternative panel options are employed then such can't be guaranteed .... or supported by HJG. I don't know which panel he's using .... BUT .... I'll hazard a guess and say his use of my earlier "suggested" SHIFT+CTRL+F4 (I think it is) keyboard commands, in order to engage the fuel system prior to manual engine startup, may well resolve his apparent manual engine startup issue ... both anytime , and anywhere, within FS. It's evident HJG can't assist with this query simply because the panel concerned isn't one of the groups own productions/offerings .... SO .... unless any HJG specific queries are forthcoming here, or in need of being replied to, I may not add anything further to this thread. MRC

"Seems" to be a fundamental misunderstanding of FS engineering here .... particularly in regard to "older" (key words) FS programming :) Using the "panel based" engine startup procedures .... if he's shutting-down the engines using CTRL+SHIFT+F1 keyboard commands (which essentially cuts fuel supply and forces the engines to shutdown) .... then fails/forgets to re-engage the fuel supply again "prior to" engine startup afterward but within the same FS session .... THEN .... he'll effectively be preventing the engines from restarting and which will likely explain his experience. In this particular case it may not be possible to manually restart the engines again .... until CTRL+SHIFT+F4 keyboard commands (I think it is .... and which re-engages the fuel supply) are first applied .... since FS will always remember the last configuration and apply/transfer it to the very next scenario. For the benefit of "everyone's" awareness .... 3 engine startup procedures are practiceable using the B737-300/400/500 panel hosted (not compiled) by HJG and which are as follows .... 1. Panel based fully manual procedure .... requiring fuel supply to be manually engaged at around N2 20%. 2. Panel based auto-start procedure .... which auto-re-engages the fuel supply at around N2 20%. 3. Default MSFS (2004 and FSX) keyboard induced auto-start procedure .... which also auto-re-engages the fuel supply during engine startup. Using the current HJG hosted FS2004 native panel (can't vouch for other/alternative non-HJG supplied panels though) each of the above 3 procedures work fine .... if correctly applied .... both on the ground and in the air anywhere, and at any time, within FS .... in fact they can't not work as such. :) It's called "providing a service" .... something the HJG team do "thoroughly and voluntarily" at considerable imposition upon their own personal time in order to try'n advise or correct people in need .... the purpose of which is ultimately intended to aid more than whom ever care to ask any question and from which others might also prospectively benefit ;) MRC

Tom .... and his team .... have made a beautiful job of what they offer .... and with a multitude of period airport scenery to further enhance authenticity too ;) MRC

Thanks for that also "PILOTPOSER" Glad you're enjoying what HJG does .... as well as what Tom does too ;) And enjoy the virtual Cook Islands (my old stamping ground along with both Tahiti and Niue Island too) .... and "KIA ORANA KOE .... KIA MANUIA .... and MERRY KIRITIMITI/MOUNIA E KILISIMASI ;) MRC AKL/NZ

From what you've replied .... the following definitively statements can be made .... The HJG B707/720/C-135 (about to be re-released with new new/upgraded FDE's, gauges, and sound packs), DC-8, and DC-9 simulations/aircraft base packs are each composed of 2X separate CFG.FILE's .... the active version which is for FS9 .... and a separate "FSX specific version" (suffixed _FSX) which needs being manually activated. This's necessary for the Smoke Effects to work given the CFG based data supporting these effects is "different" for both FS versions .... and which is the only factor dictating necessity for 2 separate FS version specific CFG FILES .... otherwise both CFG's are identical. The only HJG supplied B707/C-135 and DC-8 simulations that feature "a single and dual FS9/FSX CFG.FILe" are those for the B707-700, each of the 5X CFM-56 powered C-135's, and the DC-8-71's, -72's, and 73's .... simply because the engines that power these aircraft types are "virtually smokeless" .... hence an FSX specific Smoke Effects adjusted CFG "IS NOT" necessary. The HJG B707/720/C-135's "DO" feature both FS9 and "FSX specific PANEL.CFG files. The active file is the FS9 version, so again, the FSX version needs to be manually activated .... this's necessary for some panel/sub panel view perspectives to work correctly in FSX. The HJG DC-8 panels "DO NOT" require an FSX specific PANEL.CFG though. Both of these aircraft type panel series panels were produced in accordance with the preferences of 2 entirely different HJG developers .... hence this minor variation between them. PLEASE NOTE .... the CARAVELLE's "ARE NOT" an HJG product. They're AFG's. HJG only hosts and supports these simulations on behalf of AFG. HJG "DOES NOT" market these simulations as being FSX portable .... simply because it's not been cleared to do so despite the fact its aware these simulations may function quite well "in FSX" although it's not known what, if any, incompatibilities may exist. The HJG supplied B707/720/C-135 and DC-8 panels "ARE INDEED" FSX portable and without any known incompatibilities .... other than the their supporting interior panel/FD side views can't display 'in FSX". Here's a few videos showing the HJG DC-8's panels working "in FSX" .... DC-8-10 DC-8-20/30 DC-8-40 DC-8-50 (with a nasty wind shear and aborted landing) DC-8-62/63 DC-8-70 SERIES No B707/720/C-135 panel videos exist .... yet .... to be able to demonstrate their FSX portability. These "ARE" being produced at the moment and in support of HJG's re-release of these simulations (not yet publicly available though) and which is documented as follows .... [bB707/720[/b (all imagery FS9 but these simulations "are" FSX portable) https://tonymadgehjg.proboards.com/thread/9822/b707-720-modifications C-135 SERIES[/b (all imagery FS9 but these simulations "are" FSX portable) https://tonymadgehjg.proboards.com/thread/9817/135-modifications PLEASE NOTE .... the HJG supplied DC-9 simulations "ARE" FSX portable, but, their supporting HJG offered panel series .... "IS NOT" FSX portable/compatible though. Whilst some alternative panels are available for HJG simulations it "DOES NOT", and "CANNOT", provide technical support for these .... and some (not all) of these alternatives are known to not be entirely compatible with HJG's simulations anyway. "IF" .... you've been experiencing difficulty installing any of HJG's FSX portable panels then "I suspect" such could only arise through a particular installation step (maybe the FSFSCONV alias instruction) "possibly" not having being been performed correctly. Suggest you post regarding you difficulty/ties .... "on the HJG forum" .... where it's resident FSX specialist should be able to successfully advise/guide you. - State precisely what you're trying to install. - Explain precisely how you've gone about trying to install it .... and what's happening or not happening as a result. - Information in regard to OS and PC specifications is often helpful too .... if not crucial in regard to these matters. Again .... and beyond basic advice such as this HJG prefers "not to" conduct product support on FS forums other than it own (it's too awkward to monitor all other forums and otherwise results in both experience and resolutions becoming isolated .... in any case your posting here, like a few others recently too, was simply "chanced upon :) ). All postings and replies on its own forum are intended to form part of the accumulating and considerable wealth of resource/information concerning each of its simulations .... and which is ultimately intended to aid more folk coming to the home of these simulations than whom may care to ask any question in the first instance. MRC

FSX is "very sensitive" in regard to installation protocols for add-on files .... the slightest mistake usually results in a file not then being recognized and displayed by FSX. Unless one's attempting to install a "non-FSX compatible panel or file" .... in FSX .... then no problem/s should ever occur .... provided everything's installed correctly and strictly in accordance with FSX installation protocols Most of .... but not all of .... the panels HJG offer are "FSX PORTABLE" .... but .... none are "FSX NATIVE" .... although everything that's marketed as being FSX portable is known/proven to work perfectly fine in FSX. What is .... and isn't .... FSX portable is clearly stated within the following-linked permanent HJG forum posting .... WHAT IS AND IS NOT FSX COMPATIBLE/PORTABLE https://tonymadgehjg.proboards.com/thread/8910/fsx-compatible-portable Among the CUSTOM PANELS offered by HJG and that are FSX portable an error most commonly made by some is .... the active PANEL.CFG file in these PANELS is the FS9 version .... for FSX use the FSX specific PANEL.CFG (named "PANEL_FSX") must be manually activated (renamed PANEL.CFG .... with the FS9 version being deleted first so as to avoid conflict). Among the AIRCRAFT BASE PACKS offered by HJG aircraft and that are FSX portable a similar error most commonly made by some is .... the active PANEL.CFG and SOUND.CFG files within the default base pack supplied PANEL and SOUND folders are aliased to the FS9 B737-400 PANEL and SOUND assignments .... whereas FSX specific PANEL.CFG and SOUND.CFG files (named PANEL_FSX and SOUND_FSX) are also provided and aliased to the FSX B737-800 (I think it is) and which also need to be manually activated. Installation instructions provided within HJG files are necessarily brief and to the point, but, very extensive and step-by-step FSX specific installation instructions/tutorials are also provided by HJG and per the following-linked permant HJG forum postings .... One way of installing HJG aircraft in FSX https://tonymadgehjg.proboards.com/thread/1662/installing-hjg-aircraft-fsx The easiest way at installing into FSX https://tonymadgehjg.proboards.com/thread/2081/easiest-installing-fsx-imho Even a third way to do it https://tonymadgehjg.proboards.com/thread/3033/third OTHER HJG SUPPLIED FSX SPECIFIC INFORMATION/AIDS https://tonymadgehjg.proboards.com/board/22/fsx-support-hjg-aircraft Anyone experiencing any issues, at all, with any HJG offered file needs to register and post in regard to these "on the HJG forum". It's impractical for HJG to monitor and conduct technical support on other forums. HJG will only provide support though for the files it provides on it's own website. The knowledge base which understands and has brought each of HJG offered simulation into existence and which is best able to provide support for these files can only be found "THERE" .... at HJG. HJG's aware of many files for its offerings that are available from other websites .... some of which are known to contain any number of errors that do lead to problems and for which HJG's not responsible :) MRC