I'm using the hjg DC10-30CF, Saturn livery. FS9.1, Windows 7. Active Sky 6.0.
If I select the a/c, things appear to be okay, but if I shut down the Cessna or DC10 with the keyboard (Cntrl + Shft + F1 ) or shut down the engines with the fuel/start levers, the brakes will not release. Other a/c seem to be okay, like the default Cessna and the HJG DC8-61. Seems to be only with the DC 10. Do you know of a work-around or souton?
Post by aerofoto - HJG Admin on Mar 3, 2019 0:30:26 GMT
We offer the DC-10-30CF .... but .... we don't offer a SATURN texture for it (that airline never operated DC-10's and was absorbed into TRANS INTERNATIONAL AIRWAYS during 1976), so, we need to verify precisely what you've got and whether or not its a file obtained from this website.
We do offer SATURN DC-8-61F and DC-8-55F subjects though and for which we do provide support, but again, no SATURN DC-10's.
Not knowing what you've actually got I'll hazard the following commentary in regard to our DC-10's though ....
The brakes "do not ever" lock on, and stay on, without being able to be released .... except in the case of a GPU assisted full/and manual engine startup scenario as quoted from our forum based online DC-10 manual ....
PLEASE NOTE: It is not possible to release brakes or start remaining #3 and #1 engines until after the "clear to start other engines" dialogue is completed.
In other words .... you must complete the full cockpit-to-ground engine startup dialogue, and procedure, first .... or .... it will not be possible to release the brakes. Refer to the following section of our DC-10 manual ....
Post by aerofoto - HJG Admin on Mar 3, 2019 19:27:24 GMT
Rare instances have been recorded where commercial FS add-on products have interfered with certain aspects of programing associated our (and other) freeware simulations, but, I don't see that ACTIVE SKY should pose any such influence or threat.
"LOUROSS" .... with respect .... have you thoroughly familiarized yours our DC-10 manual ?
Particuularly in regard to "SECTION 4" .... that's sections "4.00 through 4.09" in their entirety.
There's no reference within this manual to loading the CESSNA, or any other default M$FS supplied aircraft, in advance of loading any of our DC-10 simulations .... in fact it's been stated previously that this normally adviseable procedure, for other simulations (HJG and non-HJG), "IS NOT" necessary for any of our DC-10's.
The default CESSNA senario "IS CERTAINLY" recommended, and even stated, in regard to "ALL" of the other simulations we offer .... with the exception of the MERCURE (desirable but not essential) and DC-10.
In fact our DC-10 simulations each load into FS with all essential panel systems pre/auto-configured .... save for all interior/exterior lighting, YD, anti-skid, A/B, and Pitot Static, Flaps/Slats, Elevator Trim, Radios and Navigation settings, WX Radar, V-Ref data, and AP/MCP configuration (each of which must be manually set) .... and even to the extent where they've even been "FORCED" to use the correct engine startup order (#3, #1, then #2) if the default M$FS CTRL+E assisted auto-engine startup prcedue is empoyed.
In assuming that the default M$FS CESSNA scenario should be used for our DC-10's too .... then .... you could, unwittingly, be creating your own issue.
Don't use the default M$FS CESSNA scenario with our DC-10's .... it's simply not necessary/essential .... but even if it applied then it still shoudn't result in the brakes being locked "ON".
As replied yeserday .... the only scenario that will result the brakes remaining locked "ON" is when using the GPU assisted engine startup procedure .... and only if the cockpit-to-ground dialogue ("you'll be clear to release brakes upon completion of engine startup" .... or words to similar effect) has not been triggered/completed. That's how it's inteded to work. In other wordas ... you can't release the brakes and get under way .... until you're virtually cleared to do so per the auto-dialogue
Post by aerofoto - HJG Admin on Mar 3, 2019 22:40:59 GMT
To try'n further analyse this report (lucky I have a fair bit of FS work to attend to this morning ... so this's actually quite "convenient") I've established the same scenario as described by "LOUROSS" ....
- default M$FS CESSNA loaded
- CNTRL+F1 forced engine shutdown (again loading the CESSNA "is not" necessary or prescribed as part of any procedure associated with our DC-10 simulations).
- DC-10-30CF loaded .... with DC-10-30 panel and sound pack (the sound pack can't impose any influence of course).
- APU started.
- panel manually configured for manual startup of all 3 engines.
- all 3 engines started manually .... in the order of #3, #1, and #2.
- panel manually reconfigured for normal departure.
- APU shutdown.
- brakes released (note I say "brakes released").
No problem/s, at all, were experienced with releasing the brakes .... and I taxied the full length of the default KSEA airport, stopped on the cargo ramp, applied the brakes once again, restarted the APU, manually reconfigured the panel, shudown .... and then buggered off for a coffee .... and which is precisely what I'm dong now as I sit and compile this report.
Yet again .... I can only "assume" that one, or other, of our prescribed manual engine startup procedures (namely that using the GPU as opposed to the APU) are not being applied correctly or fully completed .... and which will (intentionally) cause the brakes to remain locked "ON" .... until the dialogue (George's voice) is triggered and advises the brakes can be released after engine startup .... MEANING ... .you can't go, anywhere, until George sais you can
I confirm everything is running fine .... and once again confirm also that it "IS NOT" necessary to load the default M$FS CESSNA in advance of loading any of our simulations, but, even if this scenario is applied .... then it seems have no detrimental effect whatsoever.
Loading the default M$FS CESSNA is recommended however for each of our other simulations.
Post by Mike Monce - HJG on Mar 4, 2019 14:19:24 GMT
I've been using AS for over a decade on every flight I do and have never experienced such a problem. AS interacts with the FS weather engine not with the cfg or air file of the aircraft. AS running along side a complex sim such as the PMDG will definitely impact frame rates, especially in overcast conditions but I doubt it ever impacts aircraft systems. AND, HJG planes are notoriously frame rate friendly.
The only possible scenario is a code "bleed through" during the installation of the DC10 and/or AS. Hardrives do make mistakes sometimes in placing code. I would first totally uninstall the DC10 and reinstall. If that doesn't work uninstall both AS and the DC10 and do a complete reinstall.
Pilot reports Number 3 engine missing.
Mechanic replies: Engine found under right wing after brief search.
Post by Nathan Ford - HJG on Mar 5, 2019 9:12:57 GMT
I would have to say that I agree with the solution from Mike. Make sure you reboot your PC after uninstalling, then start FS9. Close it down, reboot your PC and install the aircraft. Reboot, then and start fs9 again. You will make sure that the registry entries for Windows are updated this way.
Well, I find it very difficult to believe that for a rather long period of time, I used the DC10 with no problems, but at exactly the same time I installed AS I started making mistakes. Way to much coincidence there. Mike and Nathan, I really want to thank you for your info. Long time ago, when an a/c didn't work right off the bat, was told it's probably a corrupted download. But, I forgot all about that. Maybe Mikes way is same thing explained differently. Anyhow, thanks a bunch, will try that. lr.
Post by aerofoto - HJG Admin on Mar 5, 2019 19:25:57 GMT
I find it very difficult to believe that for a rather long period of time, I used the DC10 with no problems
Anything can be "believable" that people go to the trouble of reporting (and we do take everyone's reports seriously) .... and over the past 19 years (ever since I first became associated with HJG) I've seen some odd issues reported that are either specific to peoples OS's, based on conflicts with other installations, or are otherwise difficult/impossible to explain .... let alone resolve.
I "suggest" (only) that your own above-quoted comment (that you had the DC-10 installed for a while and without any such issues, but, now have an issue) possibly offers a clue in itself. I held off asking the following questions previously .... but .... they've been on my mind regardless ....
1. What have you installed into FS in the form of any background programs (I think we can forget the AS though as Mike and myself have both now mentioned) .... "since installing the DC-10's ?
2. What (if any at all) edits have you applied to our DC-10 panels ? .... MEANING .... Have you altered what we provide or added any other utilities to the panel/s ?
Beyond the recommended uninstall/reinstall .... I can't offer any further advice in the face of no such issue (as has been reported) being known to exist or ever having been reported previously as well as my own not being able to replicate it.