|
Post by gary42127 on Apr 16, 2008 6:34:09 GMT
I think I may edit the panel and install a different set of flap indicators and a different autopilot, and see if that fixes it.
|
|
|
Post by aerofoto - HJG Admin on Apr 16, 2008 8:04:01 GMT
Before you do anything as drastic as that ....
I want you to start you FS flying session with the default MSFS CESSNA .... then .... transfer to your B707/720/C135 of choice .... and see if that results in any change.
I want you to do the following as a 2nd separate/individual test ....
Start the CESSNA/B707/720/C135 with an engines running situation .... shut down the CESSNA engine when FS has loaded and is stable .... then select your B707/720/C135 aircraft of choice .... you will then need to go through the complete engine startup procedure with your BOEING aircraft to get the engines started .... and see if this results in any difference.
Make sure you shutdown and restart FS between each of these checks/tests
I also want you to locate each of the 3 B707 gauges in you FS "GAUGES" folder .... right click on each of the individually .... select "PROPERTIES" .... then check that they are not showing with the "READ ONLY" option ticked/selected.
These are long shots .... VERY LONG SHOTS INDEED.... but .... they are also the last fundamental type checks I can think of.
It's just "EXTREMLY ODD" you are experiencing this problem with just the HJG B707/720/C135 aircraft, FDE, and panels .... but .... all you other FS aircraft remain functioning fine .... REALLY ODD INDEED !!!! Mark C AKL/NZ
|
|
|
Post by Dan K. Hansen on Apr 16, 2008 8:35:40 GMT
OK, just fired up FSX (SP1+SP2) on WinXPsp1
B707-420 in BAW panel: panel.b707-420 sound: B707_RRCONWAY
CTRL-E for startup... F7 for giving the flap just one notch ... indicators moves just nicely F7 again, nice movements again. F6 a couple of times ... very nice movement back to zero.
Turned the Heading indicator, first some 30 degress one way then 30 degrees the other way... no problems here either...
In flight the heading indicator had no problems what so ever.
I'm sorry, I can't reproduce your problem.
|
|
|
Post by gary42127 on Apr 16, 2008 9:00:49 GMT
Before you do anything as drastic as that .... I want you to start you FS flying session with the default MSFS CESSNA .... then .... transfer to your B707/720/C135 of choice .... and see if that results in any change. I want you to do the following as a 2nd separate/individual test .... Start the CESSNA/B707/720/C135 with an engines running situation .... shut down the CESSNA engine when FS has loaded and is stable .... then select your B707/720/C135 aircraft of choice .... you will then need to go through the complete engine startup procedure with your BOEING aircraft to get the engines started .... and see if this results in any difference. Make sure you shutdown and restart FS between each of these checks/testsI also want you to locate each of the 3 B707 gauges in you FS "GAUGES" folder .... right click on each of the individually .... select "PROPERTIES" .... then check that they are not showing with the "READ ONLY" option ticked/selected. These are long shots .... VERY LONG SHOTS INDEED.... but .... they are also the last fundamental type checks I can think of. It's just "EXTREMLY ODD" you are experiencing this problem with just the HJG B707/720/C135 aircraft, FDE, and panels .... but .... all you other FS aircraft remain functioning fine .... REALLY ODD INDEED !!!!Mark C AKL/NZ I know it's odd....but all the other aircraft seem to be working fine. I'll do all those tests and let you know the results.
|
|
|
Post by aerofoto - HJG Admin on Apr 16, 2008 11:38:20 GMT
Just a comment regarding FS engine startup procedures with our aircraft .... and I'm not suggesting there's anything wrong with following DAN's preferred CNTRL E method of engine start ....
Try to use the intended engine startup methods for each of our aircraft .... as detailed in my PANEL INSTALLATION & HANDLING NOTES (for each of our principal aircraft types) and as appears on the ABOUT HJG AIRCRAFT forum page. These do require precision .... and a bit of knob/lever clicking .... but .... also give users a basic impression of what and how things are done during engine startup procedures on any aircraft.
I urge folk not to think these methods are too difficult or time consuming .... because they're most certainly not. With time and practice these procedures will become intuitive .... and only add more to your enjoyment/appreciation of all the panels/aircraft we currently offer.
OH .... and BTW .... would you mind confirming "here" the "LAST MODIFIED DATES" for each of the 3 B707 gauges you currently have installed.
This's the only way we can check that what you've got there (in terms of gauges) is indeed what you should have and be using in relation to the currently downloadable panels/PANEL.CFG data.
It's another "LONG" .... but .... "LAST SHOT" !!!!
Mark C AKL/NZ
|
|
|
Post by gary42127 on Apr 16, 2008 12:39:04 GMT
I checked the three 707 gauge files, and none of them are marked as "read only".
The last modified dates are as follows.... 707-120, 11/13/2007 707-320, 11/22/2007 707-LATE, 11/22/2007
I'll do the other tests and let you know the results.
|
|
|
Post by gary42127 on Apr 16, 2008 14:35:57 GMT
Well.....I did the tests as requested, but am still having the same problems. I took a screenshot...sort of a split-screenshot showing the plane externally with the flaps down, and at the same time showing the panel. As you can see, while the flaps are down and the green "flaps extended" lights are on, the flap indicators show that the flaps are still up. Maybe the picture will help.....maybe not. I'm kinda clueless at this point.
|
|
|
Post by Dan K. Hansen on Apr 16, 2008 17:13:05 GMT
I've never doubted you, but I'm equally baffled by your problem!
I've tried very hard to recreate your problem, but failed every attempt...
And by judging on your shot, everything else seems to be working, and that kind of rules out the possibilities that you had accidentally placed the wrong files in the wrong folders. (or should that be the right files in the wrong folders .... or vice verse....)
Please check also that you have the FSX-version of the panel active and not the fs9 version (default) You see, there is not only a aircraft_fsx.cfg but also a panel_fsx.cfg .... but I'm sure you have read the install guide forward and reverse by now.... I'm very sorry that I'm not able to help you more...
|
|
|
Post by gary42127 on Apr 16, 2008 21:59:03 GMT
I checked, and both the panel and aircraft config files are the FSX versions.
Is there a particular version of FSUIPC that you recommend? I'm running version 4.26 which I believe is the latest version.
|
|
|
Post by Dan K. Hansen on Apr 16, 2008 22:32:21 GMT
Me too, no I don't think that FSUIPC has anything to do with it at all, I'm afraid.....
Could you (by PM) give me a full description of where and how you have installed it? Which folders, and which corrections you have made etc. etc.
I say by PM, as I don't see this thread gains anything. But if I/we find the solution, I will of course post the reason here....
|
|
|
Post by gary42127 on Apr 28, 2008 11:19:56 GMT
Just wanted to thank everyone who tried to help with my problems, especially Dan who has been going back and forth with me via email for a couple weeks. Unfortunately, this nut doesn't appear to be one that we're going to be able to crack, and I believe we've tried everything that can be tried. The strange thing is that these issues don't manifest themselves in FS9. Everything works exactly as it should. Thanks again.
|
|
|
Post by Dan K. Hansen on Apr 28, 2008 12:23:39 GMT
Have you tried the joystick re-configuring thing I talked about? That is more or less the last thing I can come up with (ref. the Too Low flaps thread elsewhere on the forum)
And btw. Please don't call me a nut ;-) ....
|
|