I have touched on this subject before some time ago but have not been able to correct the issue. With the HJG 707-120\220\320\320B\C Panels installed in FSX Steam Edition, as soon as the aircraft loads I get a CTD. The Panel cfg file has been changed as outlined in the install instructions.
After some trouble shooting I have traced the problem to two Gauge Files
707-120.GAU and 707-320.GAU.
When I remove those files, the aircraft and panel load OK, but of course with a few panel gauges missing. My OS is Windows 10.
Any ideas\suggestions on correcting this issues would be appreciated, as the HJG supplied panels would be my prefference.
I assume you've not altered either the AIRCRAFT.CFG or PANEL.FG data in any way.
I also assume you've "NOT" added, or are attempting to run, any other FS utilities with your B707 simulations. If you have .... or are .... then .... we'll likely be hard-pressed to even guess what might be the cause of your particular issue since it has, in the past, been noted that some FS utilities and programs "MAY" (possibly) uniquely adversely influence some simulations.
For starters I need to remind the following ....
We can't guarantree every file we produce or offer is going to run perfectly on everyone's system/configuration or OS (nobody ever can with either freeware or payware productions .... since some things simply don't run well on some systems and which has been a well established fact over the years) .... AND .... consideration must also be given to the fact that the programming for these panels was undertaken "during 2006" (it has been edited a couple times between 2006 and 2018 but the applied edits have only been extremely minor) and long before WIN 10 ever entered the market.
Whether or not WIN 10 presents any issues for the older gauge programing associated these panels or to what extent (if any) the issue ("you say") you've been experiencing may be localized to just your system/configuration only .... I can't say .... BUT .... such may very well be the case .... "in your particular case".
The other CTD issue reported near the end of the above linked thread .... and resolved by me .... was determined to have been caused by "texture formatting" and which can be applicable to some systems/configurations yet not others.
Only questions I can pose are ....
1. When did you last update/replace your aircraft base packs (FDE file content) ? .... and .... Have you activated the FSX version AIRCRAFT.CFG files in those base packs that have these (only the -700 doesn't require this) ?
2. When did you last update/replace your panel files ? .... and .... Have you activated the FSX version PANEL.CFG files in these ?
3. When did you last update/replace your panel gauges/core files ? .... and .... Are you running the gauges files inside the panels or the FS GAUGES folder ? .... and .... Are your panel folders installed inside another FS folder and to which the default PANEL.CFG (inside your aircraft base pack PANEL folder/s) is aliased ? .... or .... Are your actual panel folders each installed "inside the aircraft base pack folders ?
4. Have you at any stage deleted your original FS CFG file then allowed FS to build another ?
Those are the only questions on my mind at this time .... based on the successful conclusion of past reported issues.
Otherwise all I can reply at this time is .... "UNABLE TO REPLICATE PROBLEM"
First, Thank you Mark for your reply and all the numerous questions and suggestions regarding this issue.
Then, I must apologize for not thinking about this one thing that I had not tried, mainly because I have never had to use this particular troubleshooting step before, and which just came to mind early this morning, and that is, to load a different airplane to start and than choose the aircraft one wishes to fly. When I did this, the aircraft, a 707-320, and associated panel displayed OK.
I know that in your Installation Instruction Manuals you specifically make reference to this method,but as I said, I had never had to use it previously with any of the other ( except the 707\720) HJG aircraft.
Post by aerofoto - HJG Admin on Mar 7, 2020 20:06:54 GMT
It's always wise (recommended) to load a default FS aircraft "FIRST" .... and only once it's loaded and has stabilized in FS then select one's intended aircraft of choice.
It's always wise (recommended) to use the same procedure again (loading a default aircraft first) when/if switching from one's intended aircraft choice to yet another "different" aircraft within the same FS session also.
This procedure is "recommended" regardless whether or nor past experience indicates it may not be necessary .... in fact the programing of some panels/gauges "requires it" (Fraser McKAY (among others as well) makes reference to this among notes accompanying his panel data for Rick PIPER's HS-748 files).
This procedure simply ensures "everything" associated with the intended add-on aircraft (particularly in regard to it's panel/gauges and utilities) is set to the "default configuration" .... by virtue of a "default aircraft" having first been loaded into any FS session .... since FS will always transfer the first/current scenario to the next within the same FS session and which might otherwise not be in the best interests of operational stability for the panels/gauges of some/other add-on aircraft.
This procedure might also be more relevant in regard to some systems/configurations rather than others (for whatever reason .... ?) .... given what we've observed per reports in regard to different peoples past experiences concerning these sorts of matters.
Whilst on this particular subject too ....
We also know "some" newer OS's might not like our long recommended panel installation procedure (creating an FSFSCONV file for HJG panels .... and then aliasing the PANEL.CFG inside default/base pack PANEL folders to this other panel source) .... instead preferring panels being installed inside aircraft base packs. There "IS" .... so we've noted .... "a bit of variation" in terms of peoples past experiences in regard to these matters too (possibly imposed by the huge variation among system configurations available today) .... BUT .... in respect of whatever we recommend versus other established/more common procedures, we, at the end of the day, will only endorse what we know, from our own experience, works or has otherwise been "proven to work well" in regard to the simulations "we offer here".
The only simulations HJG currently offer that don't (from our experience) require a default aircraft priority loading in advance of selecting any intended aircraft are the DC-10's (if used with the panels we offer) and the AMD MERCURE 100 .... despite the fact we still say this can be done if desired. This may, in part, be based on the fact that the panels/gauges/utilities for these particular simulations represent far more recent programming in comparison to some of our others .... and which are now approaching 20 odd years.
Whenever issues are experienced people "DO" need to/should experiment though .... to some extent and just as you appear to have done .... given the literally multitudes of possibilities now that could now be applicable to some reported issues.