I was wonder if you have heard anything about RC3 disrupting the autopilot of the LDS-767? I've done 10 flights in the 767 so far, same flight, same weather etc.. 6 were disasters where the autopilot went out of control and 4 flights were uneventful. The 6 that went bad the only difference was that I used RC3 on those flights. The LDS team is blaming RC3 but my issue with that is the fact that RC3 has worked fine on ALL my other payware aircraft and I have em all.Will

>I was wonder if you have heard anything about RC3 disrupting>the autopilot of the LDS-767? I've done 10 flights in the 767>so far, same flight, same weather etc.. 6 were disasters where>the autopilot went out of control and 4 flights were>uneventful. The 6 that went bad the only difference was that>I used RC3 on those flights. The LDS team is blaming RC3 but>my issue with that is the fact that RC3 has worked fine on ALL>my other payware aircraft and I have em all.>Will,Please give us details as I suggested over in the LDS forum. I know that at least 2 of us do own the LDS 767 package so we can surely investigate this further.-michael

sorry, i try to keep it simple on my machine. i fly the default lear with the default panel.now my beta testers, they fly every plane/panel under the sun, and they have not reported any problems.not sure if they have this new plane, but i can't imagine if rc works with all these other planes, that rc would be causing a problem with this new plane.jd

Hi Michael, here are the some details about the flights.Flight- KDEN to KDFWstart time 9:00amweather: saved weather from march 1st using AS2004 (very mild)Otto is handling the commsI'm PIC with the FMC controlling the autopilot. LNAV and VNAV are engaged.RC3 and AS2004 are both running from a networked computer via widefs.all the flights are exactly the same in every respect either with RC3 or without up until it comes time for either descent or approach or somewhere between the two. The things that go wrong are this.1. the 767 flys straight through the TOD even though the MCP altitude has been changed to 10,000 feet and LNAV is engaged. And there is a waypoint that has 10,000 feet set as a crossing restriction. I also get no 767 captains announcement about starting descent. I also lose all panel sounds... i.e. seat belts, Flight attendent call bell etc.2. If I then try to start the descent with either the level change or VS the aircraft starts hunting up and down.. it ignores any input to the VS setting. The trim is going up and down out of control and vertical speed is anywhere from 5000 fpm down to 3000 fpm climb.3. I can regain control of the aircraft by completely turning OFF the autopilot and trimming by hand. at this point I can hand fly the entire rest of the flight and the 767 handles great. BUT if I re-engage the autopilot VNAV, level change or VS then I'm back on the roller coaster ride. Altitude hold does still work.Now 2 out of the 6 times that things screwed up the descent was normal but The crossing restriction was not met and in ALL 6 flights the aircraft would hold the localizer but totally ignored the glideslope as if I was on a localizer only ILS. Again, if I turned off the autopilot I could regain control of my vertical speed and easily hand fly the landing.I have read the manual.. and as far as I'm concerned if there was something wrong with my procedures then all 10 flights would have had the same type errors. That's why I did this "controlled flight experiment". I had over 1000 real time hours in PIC 767 and 700 in the PMDG 737 so I do understand boeing aircraft autopilots and fmc's...I'm now racking up the hours on the LDS trying to find out what the heck is wrong.Thanks,a copy of this post will be on the LDS forum. Will

JD Do you have RC3.1 beta testers flying LDS-767? ;-) I keep hearing that RC4 works fine with it but I'm not privy to that info... I can only tell you that I've had trouble using the LDS with RC3.1 in fact I've had no success at all with the combo of these two. I don't think it's RC fault at all as I stated before and it really rubbed me the wrong way when I saw an LDS rep suggest that autopilot problems were Radar Contacts Fault...not the 767's. Will

Gents,As I mentioned on the LDS forum, I have had four great segments with LDS and RC3 (as well as FDC, AS4 and FSNav) together. Some theorize that maybe OTTO is trying to set the AP ... I limit OTTO to comm freq changing only ..I say great segments ... the software was great ... all of it, RC3.1, FDC, AS4 and FSNav ... not necessarily so for the pilot .. but at least I had no encounters with Bill S. ... hehehehe.VERY MUCH looking forward to RC4 ... RC3 adds so much to the experience ... Maybe it is using Otto for AP that is messing things ... ?Cheers, and

Sorry Paul, as I stated in my post OTTO is handling ONLY comms. I've never let OTTO try to fly an aircraft that has an FMC. What would be the point.:-lol But..............are you running RC3 and AS4 locally or on a network using widefs like I am? Maybe it's widefs that is causing me the problems.. I just don't understand why I'm still able to use AS4 without it having any effect one way or another on the autopilot. Will

.

>Hi Michael, here are the some details about the flights.>>Flight- KDEN to KDFW>start time 9:00am>weather: saved weather from march 1st using AS2004 (very>mild)>Otto is handling the comms>I'm PIC with the FMC controlling the autopilot. LNAV and VNAV>are engaged.>RC3 and AS2004 are both running from a networked computer via>widefs.>>all the flights are exactly the same in every respect either>with RC3 or without up until it comes time for either descent>or approach or somewhere between the two. The things that go>wrong are this.>>1. the 767 flys straight through the TOD even though the MCP>altitude has been changed to 10,000 feet and LNAV is engaged. >And there is a waypoint that has 10,000 feet set as a crossing>restriction. I also get no 767 captains announcement about>starting descent. I also lose all panel sounds... i.e. seat>belts, Flight attendent call bell etc.>>2. If I then try to start the descent with either the level>change or VS the aircraft starts hunting up and down.. it>ignores any input to the VS setting. The trim is going up and>down out of control and vertical speed is anywhere from 5000>fpm down to 3000 fpm climb.>>3. I can regain control of the aircraft by completely turning>OFF the autopilot and trimming by hand. at this point I can>hand fly the entire rest of the flight and the 767 handles>great. BUT if I re-engage the autopilot VNAV, level change or>VS then I'm back on the roller coaster ride. Altitude hold>does still work.>>Now 2 out of the 6 times that things screwed up the descent>was normal but The crossing restriction was not met and in ALL>6 flights the aircraft would hold the localizer but totally>ignored the glideslope as if I was on a localizer only ILS. >Again, if I turned off the autopilot I could regain control of>my vertical speed and easily hand fly the landing.>>I have read the manual.. and as far as I'm concerned if there>was something wrong with my procedures then all 10 flights>would have had the same type errors. That's why I did this>"controlled flight experiment". I had over 1000 real time>hours in PIC 767 and 700 in the PMDG 737 so I do understand>boeing aircraft autopilots and fmc's...>>I'm now racking up the hours on the LDS trying to find out>what the heck is wrong.>>Thanks,>a copy of this post will be on the LDS forum.> >>Will

Just to throw my 2 cents in here, LD worked fine with RC3 with me. RC3 is the one that gave me problems...and I don't know that the problem I had was LDs fault or RC3s fault...leaning on RC3. Forum post "Turn back! You missed that VOR!!"Wilson HinesUAL004VHQCCUnited Virtual AirlinesBoard of Directorshttp://virtual.united.com --------------------------------------Proficiencies: PSS 747,777, A32x, CS 727,PMDG 737-700---------------------------------------FS2002|ActiveSky|FSRealTime|FSBuild2|FSNav|Jep SimCharts2|ACLoaderhttp://www.precisionmanuals.com/images/forum/checkcapt.jpghttp://heavylhc.com/images/av/anna.jpg

i'm just here to help. if i had the plane, i could fly it with 3.1 - but like you said, i don't think it is rc. maybe change the autopilot key sequence from ctrl-shift-m to something else. maybe something in the plane is sending that default character. maybe you have to hit that key to make the plane do something.i tried to read some of the threads in their forum, but i guess you have to pay for the plane to read their threads.keep me posted.jd

OMG, I take that back. My VNAV went NUTS with me on appr into LAS from DEN this morning. I sure hope we can get all thise things straitened out. I got LDS and RC3 the same day, hoping to have them work together! Not so!Below is my post that I put up on the LDS forum regarding these issues:Oren does have a point, although rather blunt...but blunt is ok at times.Why not LDS and RC3 developers put their heads together...don't bicker and ####! Maybe together, with their combined experience levels, can make a better experience for both of their customers AND FUTURE customers.I bought RC3 AND LD on the SAME Freak'n day! Yes I am frustrated! It would be nice to see both of them work together!Wilson HinesUAL004United Virtual AirlinesBoard of Directorshttp://virtual.united.com --------------------------------------Proficiencies: PSS 747,777, A32x, CS 727,PMDG 737-X, LevelD 767---------------------------------------FS2002|ActiveSky|FSRealTime|FSBuild2|FSNav|Jep SimCharts2|ACLoaderhttp://www.precisionmanuals.com/images/forum/checkcapt.jpghttp://www.ldsflyingclub.com/lsd1.jpg

How do we tell Otto to leave everything alone in LDS?Regretfully, I will be leaving the house for some work around my shop, then leaving for three or four days. I will try to check online, but at times it is difficult at best.ThanksWilson HinesUAL004United Virtual AirlinesBoard of Directorshttp://virtual.united.com --------------------------------------Proficiencies: PSS 747,777, A32x, CS 727,PMDG 737-X, LevelD 767---------------------------------------FS2002|ActiveSky|FSRealTime|FSBuild2|FSNav|Jep SimCharts2|ACLoaderhttp://www.precisionmanuals.com/images/forum/checkcapt.jpghttp://www.ldsflyingclub.com/lsd1.jpg

I agree with Will above...Why in the world would you even consider "shift-ctrl-M" to allow OTTO to take the reigns when you have a very capable FMC working for you with the '767. I have no problems with using the FMC, following my route and as such would not consider using OTTO. I think we are jumping to conclusions a little fast here, blaming RC3 for the problems. Being that the LDS 767 has only been out a week I would be more inclined to put the blame there. RC3 OTTO has never let me down with any other a/c, freeware or payware...Regards,Tom

This subject thread in the LDS forum seems to be going down hill fast so it will probably be a locked subject soon. My hope was that between the two developers, or three if widefs and fsuipc is involved that someone will figure out what is going wrong and we can then begin to fix the problem rather than bicker about who is at fault. It's been suggested that we try moving RC from the network computer to the sim computer but I'm not willing to do that just yet. For me having RC ATC talk to me through my headphones with my SIM sounds coming from my 5.1 speaker system is the only way to fly. I'm not giving that up just to fly a SINGLE aircraft even if it is the LDS-767. I've gone this long without it I guess I can do without it all together if need be. I'm still shaking my head in disbelief that after all that time in Beta nobody used RC and had this happen to them???????? We all know that serious simmers either use RC to fly offline or they fly online with VATSIM or something similar. Serious simmers do NOT use msfs ATC. Getting vectored into the side of a mountain just once cures that habit really fast.WillP.S. I be willing to purchase the LDS-767 for you J.D. if it would help fix the problem. :-) :-)