HJG no show in FSX fix

Just thought I'd share this. I was having a huge problem in getting HJG aircraft to show in FSX. Following the install instructions got me nowhere, the aircraft were not showing.

It's all down to the panel in the liveries you add to the base aircraft.

Just substitute a panel from another aircraft that does show up in FSX and the HJG planes will now appear. You will still need to rename the cfg files as instructed but it's the panel swap that will then sort it all out.

Hope that helps some from tearing their hair out.

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

I had to reinstall FSX a couple of days ago but backed up a mirror image of everything first. HJG aircraft had all been working, every one of them.

I did the reinstall and copied each aircraft folder, including other 3rd party aircraft, back into the new install. They all worked...except for the HJG aircraft which did not show. I even tried installing them fresh from the zip files. No luck.

I have installed HJG zips many times over the years without issue in FS9 and FSX. This time was different.

By trial and error, a 3rd party panel did the trick for me so I just thought I'd share that to help anyone out. The same was true for the HJG Caravelles despite them having an .exe installer.

For all of them, the default panel folder was the issue.

You mention that many HJG aircraft have two cfg files within the panel and sound folders but I only encountered that once. I think it was the DC-9; the Boeing 707s and DC-8s only had the one cfg. As I say, this had never been a problem for me before until yesterday.

For me, FSX without HJG aircraft just isn't complete....

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

I also found this problem of HJG aeroplanes not showing up in my most recent FSX installation after carefully following all instructions and previous installation success in another computer.

I am running FSX SE now and what fixed it for me is:

Change all texture entries in the aircraft.cfg from [fltsim.00] ... 01 ... 02..... to [fltsim.0] ... .1 ... .2

So, remove the first 0 for each entry.

Also make sure that the entry following "sim=" matches the name for the ".air" file exactly.

"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