|
|
Post by johnfromoz on Mar 16, 2006 18:35:45 GMT -5
This is both a spooky tale, and a question. A friend has been visiting regularly to continue a world tour using the Goose. Doing well up to a point where he bounced it off the Himalayas. Against better advice, he persisted up a valley and ended up scraping a ridge.
As a self-imposed penalty, he delayed the flight for repairs. I got to work and did a repaint with panel patches (and tour stickers). We flew another aircraft on a local tour and landed that with no problems, and changed back to the ("repaired") Goose at an airport out of the mountains. Same flight, just switched from a working aircraft back to our Goose.
Lack of ATC we put down to bad FS airport design or possibly local custom, but it turned out the electrical system had failed. Fortunately the airport had a big river beside it and we landed there.
We thought it was a good laugh. The Goose had behaved well up until the prang, and, after being repaired, developed an electrical fault. Totally appropriate. We went into "failures" and removed all failures. Continuing the long leg, we saved the flight in the air.
Next week, the same thing happened. So we turned off the failure. It kept returning, and we couldn't remove it.
Crossed our mind that Bill programmed the Goose to do that if people treated it badly by hitting the planet with it. My thoughts are that it may be a glitch which creeps in after a long tour with many saves, I have had other tours go strange well into them.
I plan to recreate the tour setup afresh from the point reached, reloading a "fresh" Goose. But has anyone any experience of such failures which refuse to be switched off?
|
|
|
|
Post by Admin on Mar 17, 2006 15:26:22 GMT -5
John-
Several people have had anomalies with the Goose since its release. I am at a loss for solutions as it has always behaved perfectly here. I do know that oddities will save when saving a flight so you might try reloading the aircraft just before saving the next time.
|
|
|
|
Post by johnfromoz on Mar 17, 2006 21:50:25 GMT -5
Tom, thanks, we tried reload from within the scenario. It's not the only time it's happened, other aircraft have done it too, and I suspect it's a matter of reproducing the scenario afresh as a new saved flight. I will be doing that this weekend, so if that's the answer I'll post here, but I wondered if we weren't alone and there was a quicker fix!
|
|
|
|
Post by bhk on Mar 17, 2006 22:08:36 GMT -5
This sort of thing has happened to me on long flights with many save-overs.
Most recent, the DH Albatross (Jens Kristensens' model) lost it's autopilot. No matter what I did, it just would not engage.
So I made a fresh "leg" of this part of the journey from New York to Venice which had been done in several saves between NY and Lisbon.
This leg is the Lisbon to Venice section.
Loaded it and no problem at all with the auto-pilot.
Bruce
|
|
|
|
Post by johnfromoz on Mar 18, 2006 21:27:50 GMT -5
Yes, I think that's going to be my answer. Just settling down to recreate the flight now. I suspect it's less of a problem with the various aircraft models than it is a Microsoft ghost in the FS machine when saving very long tours.
EDIT - for info or for a laugh, however it takes you ;D I recreated the flight setup anew. It did get rid of the power failure but the compasses are now around 90 deg off! Next step - reselect the aircraft. If that fails -reinstall the Goose!
|
|
|
|
Post by johnfromoz on Mar 26, 2006 21:40:06 GMT -5
Well folks, I'm not much wiser, having recreated the saved flight. I then made sure all failures were off. I selected "random failure" and set the number of failures to "0", which is something I had not had to do before as all the defaults have been for no failure until you choose to set one.
All went well for a couple of hours then the compasses went around 180 deg off our heading ...
|
|
|
|
Post by Admin on Mar 27, 2006 15:30:24 GMT -5
I'm baffled, I seldom make flights lasting more than an hour but once a bunch of us flew Geese from one island to another in the Marivellas and nobody reported any problems and we were in constant chat for 2 1/2 hours
|
|
|
|
Post by johnfromoz on Mar 27, 2006 17:52:42 GMT -5
I'm baffled too. I noticed the first occurrence of the compass problem went away next time I loaded the flight, have not yet checked the latest. If it doesn't vanish of its own accord I might reload the Goose, it's about the only other thing I can think of. I just have a feeling it's not the aircraft but something more general in FS.
|
|
|
|
Post by johnfromoz on Apr 22, 2006 20:42:12 GMT -5
Just to (I hope) round this off...
Last week I totally uninstalled FS9 and reinstalled it and the Goose. We then recreated the last position of our tour and started with a clean slate.
In five minutes, the compass started drifting from our southerly course to westwards, and ten minutes later, drifted back to the east.
The intriguing thing is that it appears to be a regional thing rather than the aircraft. At least I hope so.
It had begun in northern India heading for the Ganges, and persisted down the Bay of Bengal and along the Andamans and Nicobars. On reaching Indonesia it stabalised and in near an hour's flight before we finished that leg, was perfectly well behaved.
It would be interesting to try, and to hear from others who might care to, what happens in different flights with the Goose and other types in that region.
|
|
|
|
Post by Admin on Apr 22, 2006 21:10:05 GMT -5
Strange isn't it. There used to be a weird triangle in the Pacific Northwest that caused CTDs, but only in Winter. I think in a program that provides us with the whole world, the number of these oddities is remarkably small.
|
|
|
|
Post by johnfromoz on Apr 23, 2006 18:51:55 GMT -5
It is. Until you mentioned the Pacific Northwest, I almost got the impression that MS stitched together the planet and decided to put the seams in places they thought nobody would notice! Glad it didn't turn out to be Bermuda, that would be too predictable.
Looking forward to continuing our tour in a few days. I am hoping we're right and all is fine from here on.
|
|
|
|
Post by foxwolfen on Aug 18, 2006 16:10:03 GMT -5
It is a problem long familiar to designers. The only way I found to solve this (its a chaching problem I suspect) is to never overwrite the default flight (even in GW3 I leave the cessna flying in Seattle. It seem once you do so, all kinds of anomolies begin to appear, including the AP state and electrical problems. I saw both when working on my Beech project. It was driving me crazy until I realized it never started to happen until after I made a saved flight the default. As for the goose.. while it is a "hall of fame" recipient on my site, if you read my review of it... www.ascendant-online.net/en/reviews/flightsim/aircraft/cutters_goose/index.phpI love it, but there is something about my setup that it does not seem to like. Cheers Shad |
|
|
|
Post by johnfromoz on Aug 21, 2006 19:20:15 GMT -5
Shad,
Thanks for the input. Nope, never overwritten my default flight. The issues arose in regular FS9 and I must say I have not really noticed them, or tested, in GW.
We finished the world tour and still had occasional compass problems all the way from India to Australia, with the compass being way off in one direction, working its way back then deviating in the other direction. Recently I have had it in other aircraft. Best guess from various forums is that it may be AFCAD related, possibly to do with local magnetic variations in conflict between nearby fields....
But the Goose will remain among my top aircraft, and I look set to stay with FS9 and GW3 for some time - I've only just broken them in!
|
|
