CoolP wrote on Nov 28^th, 2011 at 5:53pm:


Thanks indeed for clarifying this CoolP!  I was confused about that until now! 

No problem, Morten. Brian, I haven't checked the tweaked settings, but the 21.0 setting helped a lot in 1.4.
Edited:


Find a ton of info (additional to the one in the manuals) regarding the planes here if you like. http://www.smartcockpit.com/plane/boeing/B767/ Or here. http://www.biggles-software.com/software/757_tech/main/sitemap.htm
757 and 767 are very similar on the basic stuff and philosophy, so you can always look at both planes.

The good news about 1.5:  I flew the 767 from Taipei to VHHH at FL310; the bird was rock steady on course and altitude even with a 56-60 kt crosswind at altitude and through higher than normal winds during descent to 2000 ft for the approach.
The bad news:  no one else has reported the problem, so maybe it's just my system.  During the approach to VHHH I selected LOC and then APP at the appropriate times.  The 767 began the descent exactly on GP and localizer.  On short final the 3 green autoland lights came on--and the plane started making S turns just like the 757 before the latest update.  At minimums I had to disconnect the AP and land manually because the rolls L and R were becoming more severe.  I uninstalled 1.5 and all the other files as Markoz suggested in his posting, downloaded a fresh file of 1.5 and installed it.  I then flew a test flight from KRSW to KMIA.  All went well until short final (wind 181/17kts) to rwy 27 and then the rolling started again and I again had to land manually.  I tried the flight again with weather set to fine rather than actual, wind on short final 006/3 kts and the rolling again occurred.
Has anyone else had a problem?  If not, I'll submit a ticket.
One other question:  I know v4.6 for the 757 does not use FSUIPC, but does the 767 still use it?

NaMcO wrote on Nov 26^th, 2011 at 1:51pm:


No ideas anyone? It's still happening and it's driving me nuts 

Sounds are ok, had checked and double checked now.

There's only one entry in the DLL.XML file, as follows:

<Launch.Addon>
           <Name>Captain Sim 767 Sound</Name>
           <Disabled>False</Disabled>
           <Path>Captain_Sim\767\cs.sound.dll</Path>
</Launch.Addon>

I have taken the old 1.4 version off and reloaded the 1.5 and restarted the computer and the following didn't work, I then uninstalled it and reinstalled it and the problem still persists. If I am honest, I have had this product nearly 2 years and there has always been something wrong with it. Why is it me who seems to have these problems and no one else does, I'm so frustrated with it, and hope that someone can finally help me to resolve the problems but I'm sure there will be some more underlying problems !!
Thanks withers96.

>LNAV doesn't work
>VNAV doesn't work
>Speed control knob doesn't turn
>When TCAS switch is switched to TA/RA, it goes to TCAS FAIL on the ND which should've been fixed!!
>When the TEST button is pressed on the TCAS knob, it doesn't say 'TCAS SYSTEM TEST OK'
>ADI doesn't work ( stops after about 5 mins and the IRS is aligned etc!!)
>Autopilot doesn't work, i.e no light appears on the button!

tomwithers wrote on Nov 30^th, 2011 at 9:45pm:

All of those problems, except the 4th one, sound like they are because your Avionics have stopped working. Two ways I can think that might verify this are:
1. Press CTRL+E (default engine start) as this turns the Avionics Master Switch on as part of the engine start procedure.
2. create a keyboard command for the Avionics Master switch (if not already done), and use it a couple of times to see if it is On or OFF. I use CTRL+SHIFT+A as my keyboard command.

I did a test by starting with the default C172 (cold-n-dark, including the Avionics Master Switch being OFF), and when I loaded the CS767 (v1.5), the Avionics Master Switch must have been turned ON during the loading, because I had the Radio set to receive the ATIS message at the airport I was at, and as soon as I turned on the Master Battery, the ATIS message came up. This didn't happen in v1.4, I would have had to turn my Avionics ON use one of the two methods above.

As for this one: When TCAS switch is switched to TA/RA, it goes to TCAS FAIL on the ND which should've been fixed!!
That is still happening in v1.5, but what I like about it is that if I see that message, I know that is is turned to TA/RA before I line up for takeoff. I use it as a hint (or part of a confirmation of the "before takeoff checklist"), and if I see TCAS TEST, I know it is in standby mode. This applies to v1.4 and v1.5.

Mark