|
Post by Nathan Ford - HJG on Oct 23, 2018 23:38:12 GMT
Another quick question, have you updated FSX deluxe to sp2 or is it a straight install from the discs? FSX sp2 update
There are a lot of problems with the original install of FSX that where fixed, including missing scenery etc, by Microsoft with their sp2 update. Cheers, Nathan
|
|
|
Post by ssi02 on Oct 24, 2018 4:54:29 GMT
FSX is current with all updates.
|
|
|
Post by ssi02 on Oct 24, 2018 5:01:03 GMT
Tried all three startup procedures including the FSX last-ditch standby, ctrl+e. Ctrl+e only one that works, all engines start 1-2-3-4, I can even use the individual fuel valves for the engines on the pedestal, and the start buttons. Only things I do not need to touch are the battery/ground power switch and reference to the air pressure gauge. I can also set the other switches having to do with engine ignition etc, they have no effect on the startup. Engine temperature gauge needle does do not circle the gauge several times as with the other two alternatives. From what I can see I will be using ctrl+e unless something else is recommended.
|
|
|
Post by aerofoto - HJG Admin on Oct 24, 2018 17:54:38 GMT
Using the FS default CNTRL+E auto-start procedure one "does not" need to touch/manipulate any of the above-mentioed panel features following selection of these basic keyboard commands. Given what we already know works well I am "suspicious" as to your implementation of our recommended manual engine startup procedures, but, can´t fathom what´s going wrong/being done wrong in your particular case Just onme small detail though .... During the 2 manual engine startup procedures confirm you are delaying engaging the fuel ignition levers until N2 15% has first been achieved .... and not before or too far beyond this indication. As already stated a number times .... Although some acknowledge an issue using FSX SE .... and others don´t .... and yet others acknowledge an issue using FSX A .... and others don´t (as previously stated by me) .... at the end of the day, and once again, the FSX videos (showing both of prescribed manual engine startup procedures) linked within my first reply, indicate that both of these procedures do work "in FSX" and without any apparent issues at all. Failing success .... I can only "suggest" the issue you´re experiencing "may" be located on your own system or "may" be occurring through the influence of something you may have installed or running within your version of FSX. Such can can happen .... and when such does occur (very rarely though) .... then we´re aften hard-pressed to be able to poin-point/advise or resolve such issues if these are caused by untilities neiher produced or recommended by us .... despite the fact nothing would please us more (in the interest of end user enjoymemnt of what we lik to produce) than to be able to do so. The following may seem silly queries but these do need to be asked .... and I (perhaps) should have done so at the very start of this thread and in the interest of total clarity .... 1. Are the files you have installed those versions currently downloadable from "this website" ? .... Confirm they aren´t a part of someone else´s compilation (supposedly for the HJG DC-8´s) and/or aren´t part of any other(unauhorized) package that may have been uploaded elsewhere. 2. Have you made any adjustmets whatsoever to any of the files we provide ? 3. Are you running any other add-on applications/utlilities "as part our panels" (or within your FSX version) that might influence the data we provide ? I ask the above simply because we are aware of some issues having occurred in the past and which have been related to the influence/s of either points 1/2/3 above. Beyond this possibly being the case .... I´m now all out of further advice .... I regret to say ;( Mark C BOG/CO
|
|
|
Post by Falcon on Oct 25, 2018 13:24:52 GMT
I use FSX Acceleration, and have no problems with start up procedures. I did have many problems with Steam and addons though. I can't be of any help.
Falcon
|
|
|
Post by ssi02 on Oct 27, 2018 12:30:39 GMT
I tried the ctrl+e startup both with and without the switch and other control use - wanted to see if the switches changed anything and they did not, so no need to manipulate them, as you have said. I experiment on my own with these things before I contact you so I can let you know of anomalies you may not be familiar with before I contact you again. I do, however, shut the sim down completely between tries so everything after my experimentation is a fresh start.
Indeed, I don't cut in the fuel pumps until 15% N2 is reached; starter cutoff occurs at 35% as recommended.
I'm going to take a look at what you've recommended re: different models and publishing date, however, I can tell you this - this was a clean install using base packages and add-on textures off the HJG website as it is now. Panels used came off the current HJG website also. I made sure I downloaded the FSX-only sound files for each aircraft as well, also from the HJG website. I don't like putting outside materials into the mix unless extenuating circumstances (i.e., no HJG panels available) make that necessary. I should mention, however, I'm using the latest version of FSUIPC4 downloaded off the Schiratti site.
I concur with your assessment re: something in my installation just being basically incompatible with the HJG panel files on this PARTICULAR aircraft. I say that because the HJG panels for the 707 series and 727s perform flawlessly on my machine and are a great deal of fun to work with. The add-on panels I've installed for the DC-9s and MD series, as well as the 737 aircraft, are installed only if they are mentioned to be compatible with your work here. What's occurring with the DC-8 is a very minor issue that I'm convinced is due to some very arcane, almost never heard-of issue that's peculiar to my set-up. It's been the story of my computer ownership since day one, and not just on flight sims.
Right now I'm fencing with an L-1011 installation that's presenting some interesting challenges.
|
|
|
Post by aerofoto - HJG Admin on Oct 28, 2018 19:02:43 GMT
Again .... I had to ask those questions and are glad you´ve been a little more specific by answering them. It doesn´t help to solve your issue .... whatevers causing it .... BUT .... it does at least help eliminate a small number of potential possibilities. FSUIPC (in licensed or unlicended form) won´t/shouldn´t contribute to your issues simply because it´s not required "to actually run" any of our panels .... with the exception of the WX Radar in each of our panels equipped with it, as well as the DC-10 panels fuel dumping and transfer system. We can´t guaruntee that FSUIPC won´t impact what we offer though .... in the event you´ve used it to apply any major configurational changes within FS, or for your hardware device, but, as you, yourself, say .... you apparently have no difficulties running our B707 and B727 panels, despite certain elements of similarities in programmimg among these (for our B707´s at least) so, there´s no obvious reason why issues should arise with any of our DC-8 panels .... save for our awareness that different things can happen on different systems and over which we´ve no control or ability to advise in regard to. I can´t really offer anything of further value to this particular thread subject .... until something more obvious is clarified .... maybe That´fine if you´re referring to the panels we provide "HERE" (although those you mentioned within the above quote that are offered by us here "are not" FSX compatible) .... BUT .... if you´re referring to FSX panels released by other artists for (supposed) use with HJG simulations then I´d recommend "CAUTION" .... simply because we´ve had too many past reports, both on and off forum (in fact it drives me nuts sometimes), which indicate some of these alternative panels aren´t as compatible with our own projects as is implied. We´re not trying to denegrate the work of other artists .... or even push our own work for that matter .... it´s just "a simple fact" of which people should be aware. What I mean by this statement is .... there´s "a technical interelationshp" between all of the files we provide (FDE, panels/gauges, and sounds) so as to ensure their complete compatibility with our own projects .... as we provide them. FS authors whom aren´t HJG developers generally have no idea how we go about this (in all due respect to them) or the way we compile what we offer .... and that´s where, and why, some incompatibilities and defficiencies have been known to arise and cause issues. One thing we can assure folk though is .... if any file is offered by HJG, here on this website, then it "IS" .... (a) well tested .... and (b) compatible with what we offer .... or it simply wouldn´t be supplied or otherwise recommended by us. In selectig out panel offerings one simply has to check whethr or not each panel is stated to be FSX portable. I can´t imagine why you should be experiencing any challenges with our L-1011´s (apart from enjoying and learning how to fly them) since these files are all perfectly fine too .... in both FS2004 and FSX .... so .... you should start a separate thread in regard to this .... in the event any such need arises. Mark C BOG/CO
|
|