|
|
Post by nightflight157 on Jun 2, 2020 6:58:04 GMT
Hello, I recently installed the HJG Boeing 720v7. I added to repaints (hjg_b720_boeing_1960.zip, and elton_john_b720-022_n7201u.zip). I followed the installation instructions, I got the aircraft to load in my FSX aircraft hanger.
The problem is, the engines refuse to start. I even tried selecting another aircraft in my hanger, started the engines on it, then switched the aircraft selection in FSX to the Boeing 720. The engines shut off. Has anyone else
had this issue? Any assistance would be greatly appreciated. In the past, I downloaded and installed the HJG Boeing 707 and it works great.
|
|
|
|
Post by aerofoto - HJG Admin on Jun 2, 2020 13:58:27 GMT
"IF" you're using "FSX" .... then use the default FS stated "CTRL+E" based auto engine startup procedure/commands .... since the prescribed FS2004 manual engine startup procedure (per our manual and service notes) can't work in FSX.
The only difference is the engines will then start in the FS default FS ENGINE #1/2/3/4 order .... as opposed to the recommended FS2004 based #3/4/2/1 manual engine startup order.
The engine startup procedures using the B707/620 panels we offer (and which are the only files we support) are precisely the same.
Mark C
AKL/NZ
|
|
|
|
Post by nightflight157 on Jun 2, 2020 18:58:20 GMT
Yes, I am running FSX. I have tried CTRL+E and absolutely nothing happens. The engines make no attempt to start. The aircraft is completely dead. I've noticed that the usual tip from FSX that an engine isn't started and to press CTRL+E doesn't
show up on this aircraft only. I have no other issues with my other aircraft. Any ideas?
Thanks.
|
|
|
|
Post by aerofoto - HJG Admin on Jun 2, 2020 21:44:05 GMT
The problem I have with this is .... "IF" the simulation is installed correctly .... and "IF" the files we provide haven't been edited in any way or aren't influenced by any other ad-on FS utilities/modules, then, there's no way in the world the simulation can't/won't respond to "the default FS auto engine startup commands" (same as applies to the B707's and every other simulation we provide also).
I note you say you're using our B720 (not B720-B) base pack, but, what panel are you using with it ?
Have you added or are you running any "non-HJG" supplied utilities or other FS programs with either the base pack or panel .... and .... have you edited any details at all in regard to any of the files we provide ?
Need you to tell us "precisely how you've installed what we provide" .... and also .... "precisely what you doing when you attempt to start the engines".
Mark C
AKL/NZ
|
|
|
|
Post by aerofoto - HJG Admin on Jun 5, 2020 19:19:21 GMT
As I mentioned above .... So long as files we offer haven't been modified or aren't being influenced by any other add-ons modules/utilities (some of which have been known to have adverse affect), then, there's no reason why any simulation shouldn't respond to "the default auto engine startup" commands. Different things can be experienced on different PC's/systems and with different installations though ..... and which is well documented right throughout FS, but, one small detail HJG encourages is to "start FS/any flying session by loading a "default M$FS simulation" first (such as the default CESSNA), and only after it stabilizes within FS, then, select and load one's aircraft/simulation of choice (this's recommended and even written into the engine startup procedures for some our our panels .... except in the case of the DC-10 and MERCURE 100 simulations we offer and with which this procedure is unnecessary). Following this procedure simply ensures that all systems, associated with any simulation (panels primarily), are set to the "default" configuration for ease of initial operation. Again .... and whilst "not essential" on more than by far the majority of PC systems .... this seems to have a positive influence with a few/some PC systems/installations/simulations in rare cases where issues have been reported .... although once more this's never been proven, nor ever reported to have been the case (so far as I can recall since 2006), with any of the HJG supplied B707/720/C-135 SERIES simulations. As confirmed with our following linked FS compatibilities statement .... WHAT IS AND IS NOT FSX COMPATIBLEtonymadgehjg.proboards.com/thread/8910/fsx-compatible-portable.... our B707/720/C-135 SERIES simulations, and their supporting/recommended panels, are FS2004 native, but, FSX portable .... although our recommended manual engine startup procedure/s for these panels can't work in FSX and which is why one must resort to the "default FSX auto engine startup procedure" (using keyboard commands) .... and which works perfectly fine albeit without the ground assistance/compressed air and associated cockpit to ground audio dialogue. Once more .... the default FSX auto engine startup procedure works fine with these, and all of our other, simulations .... using the panels we offer or M$FS assignments  Mark C AKL/NZ |
|
|
|
Post by nightflight157 on Jun 8, 2020 21:49:30 GMT
Thanks for all the replies. Sorry I haven't responded before now. I've had other more urgent things to tend to that have taken up a lot of my time. I initially installed the HJG Boeing 720 v7.zip folder by unzipping and copying and pasting it in my FSX\Sim Objects|Airplane folder. I checked the aircraft.cfg folder and found an incorrect entry I had made and fixed it. The engines still wouldn't start. I tried uninstalling and reinstalling the HJG Boeing 720 v7 folder and still no success. The aircraft lights work, the gauges seemed to be working, and the main door opens and closes.
Then, I did some more searching on the HJG website and found the "Easiest Way At Installing HJG aircraft into FSX by Dan Hansen (which is very helpful). I read it thoroughly, re-read it, and then followed all the steps one by one. I created an
HJG folder in the FSX\Sim Objects folder and the appropriate sub-folders. I now have the HJG B720 v 7 installed in the HJG folder, the HJG b707_core_files_v1.6 installed, the HJG_b720_boeing_1960.zip installed, the HJG elton_john_b720_boeing-022_n7201u_1974.zip installed, and the HJG b720-020_panel_1959 (that is more 'original' for the B720) installed. Both repaints show up in my aircraft hanger, with the gauges working, aircraft lights working, and the main door opens and closes. But the engines still won't start. I haven't modified any of the folders (except as instructed to when running FSX). The only thing I can think of is maybe like you mentioned that they "aren't influenced by any other ad-on FS utilities/modules". I'm about to raise the white flag as they say!
|
|
|
|
Post by aerofoto - HJG Admin on Jun 9, 2020 2:21:41 GMT
The installation process/s can't affect the engine startup procedures .... unless something's been installed radically wrongly in the first instance, but which, and in FSX, would then likely result in your entire simulation not being recognized or displayed by FSX. You seem to have installed everything correctly .... by virtue of the fact it "IS" all apparently displaying and is otherwise working. As mentioned within my earlier reply .... the prescribed manual engine startup procedure (per our manual) for these panels/simulations can't work in FSX .... it'll only work in FS2004, so, don't try to apply this particular procedure in FSX. "In FSX" .... the default MSFS auto-startup procedure (only) must be used .... and which, I assume, is (in FSX) triggered by keyboard commands CTRL+E. If everything's installed and displaying correctly .... then .... there's no way in hell the default auto-engine startup procedure can't work .... unless something else you have installed is preventing it from doing so .... and which is something we may never be able to get to the bottom of  The same auto-start procedure (CTRL+E) works perfectly in FS2004 also .... for those whom wish to use it in preference to the manual procedure with all the bells and whistles ! By default .... these, in fact all of our simulations, load into FS2004, and FSX too, with the engines already running. Keyboard commands CTRL+SHIFT+F1 automatically shut down the engine/s .... and again .... keyboard commands CTRL+E automatically start the engine/s .... in numerical sequence. It should be as simple as that What you need to do is as follows .... Tell us "precisely what you're doing" prior to .... and during .... your engine startup procedure .... and step by step please. As I hinted earlier .... you may fall into the category of those whom may "need to" load a default FSX aircraft (not a 3rd party add-on aircraft like ours) into your FSX at the very start of each flying session .... and only after letting it stabilize for several moments .... shut it's engine down "automatically" (as prescribed .... this auto-shutdown procedure is akin to closing the fuel valves and forcing the engine/s to stop .... and which I'll comment further in regard to in a moment because it could also be part of your problem) .... "then" .... pause FS, and select and load your FS aircraft of choice .... then once its stabilizes within FS use the precribed auto-startup procedure. "IF" .... you've performed an auto-shutdown procedure (CTRL+SHIFT+F1) .... then .... before attempting to restart the engines automatically it may (possibly) help your case to select keyboard commands CTRL+SHIFT+F4 (this's akin to opening the fuel valves in order to enable fuel flow to the engine/s during startup) .... and only after doing so then apply the CTRL+ E auto-start commands Ordinarily in FS .... selecting CTRL+E should automatically open the fuel valves too, but, for some reason and with some simulations (although I've never experienced this in regard to our B707/720 panels .... since all functions within these panels are programmed to work identically) it's known that CTRL+SHIFT+F4 must be applied in to manually open the fuel valves and in advance of selecting CTRL+E in order be able to start the engine/s. So try that ! If this last advice doesn't work for you .... then .... I'm "buggered if I know" what's going on .... if fact it'll fall into the category of one of very few issues I've not been able to resolve for people Mark C AKL/NZ |
|
|
|
Post by aerofoto - HJG Admin on Jun 9, 2020 5:06:44 GMT
Just as a further quick acknowledgment ....
I've just this moment completed a B720 test .... out of "pure curiosity".
I loaded the default MSFS CESSNA .... first.
I then shut its engine down .... using keyboard commands CTRL+SHIFT+F1 (as expected the engine shutdown).
Without leaving FS/abandoning that same FS session I then paused FS .... and selected a B720 .... and loaded it into FS.
It loaded .... with the engines shutdown (as expected).
I then employed the MSFS auto-start procedure .... using keyboard commands CTRL+E .... and all 4 engine on the B720 started fine and individually, in the numerical and FS sequence of #1, #2, #3, and then #4.
No problem/s whatsoever were experienced.
I did not need to employ keyboard command CTRL+SHIFT+F4 in order to open the fuel valves prior to engine start .... but .... you should still try doing this (as recommended within my mlast reply) anyway.
Mark C
AKL/NZ
|
|
|
|
Post by Falcon on Jun 9, 2020 14:27:16 GMT
I've had this problem in many aircraft in the past in FSX. And it was all a matter of making sure the Fuel Valves were open. Even after I did the same as Mark and started with default FSX aircraft.
|
|
|
|
Post by nightflight157 on Jun 9, 2020 18:22:26 GMT
Success! I loaded a default aircraft, let it stabilize for a moment; selected CTRL+SHIFT+F1; paused FSX and selected the Boeing 720; selected CTRL+SHIFT+F4; then selected CTRL+E and the engines started. Problem solved. Thank you very much for all your assistance. I really appreciate it. Happy Flying
Jim
|
|
|
|
Post by aerofoto - HJG Admin on Jun 9, 2020 20:10:21 GMT
You'll likely be among the very few whom might ever need to do that then Jim (using CTRL+SHIFT+F4 to open the fuel valves again after an CTRL+SHIFT+F1 induced auto-shutdown .... and prior to then using the CTRL+E auto-startup procedure) since most others likely wont need to, but, I'm glad you've finally achieved success. Bear in mind you may need to employ this same recommended engine startup procedure for other simulation too .... ours and those by other groups possibly too. And always remember .... it's best to load a default MSFS aircraft first "before" transitioning to your intended aircraft type of choice. This is recommended for all HJG simulation (and others too) .... but .... is not necessary for the HJG offered DC-10's or MERCURE 100 simulations, Just been revising the panel selections to communicated earlier. This's what you should be using for the HJG B707's/B720's and C-135 SERIES simulations .... HJG B707 - WHAT PANEL WHICH PLANE ? tonymadgehjg.proboards.com/thread/1558/hjg-b707-panel-which-planeHJG C135 - WHAT PANEL WHICH PLANE ? tonymadgehjg.proboards.com/thread/1560/hjg-c135-panel-which-planeAlways use the correct/recommended panels with each of our B707's/B720's and C-135 SERIES simulations. Never use just any panel or whatever looks best or may be one's favourate. These panels are tied into the FDE for these simulation .... MEANING .... only the recommended panel versions should be used with each simulation. Some can't function correctly if assigned to just any of these simulations. Similar applies also in respect of the B707/B720 and C-135 SERIES sound packs HJG offer too .... our recommendations for which are as follows .... HJG B707 - WHAT SOUND WHICH PLANE ? tonymadgehjg.proboards.com/thread/1561/hjg-b707-sound-which-planeHJG C135 - WHAT SOUND WHICH PLANE ? tonymadgehjg.proboards.com/thread/1562/hjg-c135-sound-which-planeThe latter (assignments) portion of this reply is simply "a reminder" and for general consumption  Mark C AKL/NZ |
|
