Hi,I've been corresponding with Pete Dowson recently, because we have tried to correct the reverser problem, that many of us (incl. me) are encountering, but to no avail. The only way to get the reversers deploy for me after touchdown is to EITHER manually touch the throttles to get the engines to ground idle, OR in FSUIPC settings program a yoke button for FS CONTROL to do "THROTTLE CUT" (from FSUIPC list. After getting the throttles to ground idle the reverser works fine. Feel free to experiment with your settings, and please report back here!Now, to the actual topic :). Pete suggested I try the PIC v1.3 patch, that I _thought_ was ONLY meant for the people using PFC or other external hardware (aerosoft MCP for example). I upgraded, because Pete himself wasn't having the reverser issue, and he was using v1.3. Pete also suggested, that the patch is NOT just an external HW compatibility upgrade!I didn't get the patch to help there, but rather discovered at least one new thing:* The N1 (and others as well) readings are slightly different for each engine. I know it's true to life to be that way, but is this intentional ?I know there was some talk here at the PIC forum back when the 1.3 patch came out, that it might have some "easter eggs" or improved features in it, other than the compatibility things. I wonder why Wade or any other team member hasn't set the record straight. I don't understand what is it that prevents the WELP from telling how it really is. ARE there any additional BUGFIXES/FEATURES implemented in the 1.3, OTHER THAN the external device compatibility ?Also, I have TRIED to contact Wade Chafe to get his take on the PFC.DLL, which supposedly has DIRECT contact with PIC autopilot, to get my own homemade MCP work. But I have never received any reply whatsoever. I wonder why???Feel free to comment!Tero

You are right Tero, there are other things included into the 1.3 patch. What they all are is a "mystery" to be found out by us. Why? Who knows, but if they are important we will notice them...... Infact I am going to reinstall it tonight because I don't save my flights {which is a PROBLEM} with this patch but am curious to find the easter eggs!Best Wishes,Randy J. [email protected]" A little learning is a dangerous thing"AMD XP 2100 |MUNCHKIN 512 DDR RAM |ECS[/b ] K7S5A MB |[b]GF3 64 MEG |WIN XP PRO |MITSUBISHI DIAMOND PLUS 91 19"

1.3 also gives you an APU which fires up in about 8 seconds, an EIACS message when you open the exit doors -POSKY does not model-, fuel burn imbalance disappears (unrealistic), can't save flights, etc, etc. If you don't have a piece of 3rd party hardware (MCP), then don't bother. There is no uninstall, you have to un/re-install the PIC to go back to the FS2k2 patch level.Rob.

>not model-, fuel burn imbalance disappears (unrealistic)Well, the uneven fuel burn was a bug in the first place. The imbalance was quite exaggerated compared today's airliners with well-maintained modern engines (but what can you expect from a bug? ;-)).I agree with you on the rest, and I have one thing to add: When disconnecting the A/P with the joystick using the 1.3 patch, the CMD light on the MCP stays on. If I remember correctly, the A/P does disengage though. But the only way to make the CMD light go out is to cycle the A/P disengage bar.Martin767 fetishistIt's a lot like life and that's what's appealing

:-)For the record,there are NO "bugs" in the PIC767, only "Features".Yes, the fuel imbalance may be a little exaggerated, but having both engines burn identical amounts of fuel I would suggest is also unrealistic.The other 'feature' is the self testing of the warning lights on the panel..every so often they light up...I say it is an automatic peridic 'self-test' :-)Long Rule the PIC.Right, enough silliness, it's time for "...up, up, and awayyyyyy"

Seeing that there is much against this patch, I will stay away and wait for easter for my eggs :)Best Wishes,Randy J. [email protected]" A little learning is a dangerous thing"AMD XP 2100 |MUNCHKIN 512 DDR RAM |ECS[/b ] K7S5A MB |[b]GF3 64 MEG |WIN XP PRO |MITSUBISHI DIAMOND PLUS 91 19"

I reverted back to the initial patch via reinstalling PIC and then the patch as I found Lee's new IVSI/TCAS gauge was having problems with the shading and sometimes the shading would even get stuck and would not update even when the hidden click spot was used to force a shading update. Since I've reverted back to the original patch I haven't had any problems at all with shading on Lee's gauge, so I would really try and stick with the original patch if at all possible.Regards,Van LatendresseYeoDesigns Panel/FDE Designer

Ok people,I have tried the v1.3 and discovered that:- the APU does NOT fire up in 8 seconds, but in ~ 30-35 seconds which is perfectly normal- the CMD text DOES go away when disconnecting autopilot even with joystick- I have no problems with shading with Lee's TCAS- I had no problems with fuel burn before, and I don't have any problems now with the 1.3 either- also someone told me earlier that the EEC works erratically with 1.3, haven't seen this happen ever. Other than these problems that I don't have, I DO have sometimes a little imbalance in engine readings, which is true to life behaviour.I'm happy that I upgraded.I'd be interested to hear other observations about the 1.3 too, just to see if I don't have them either :).cheersTero

Well I can always reinstall if things go bad so I will give her a shot and get back to you. Hey Tero, I know you don't like the "PIC look" for the VFR panel, but why not try it out? You might like it :) and of course you can always uninstall it too!Best Wishes, Randy J. Smith [h3]" A little learning is a dangerous thing"[/h3]AMD XP 2100 |MUNCHKIN 512 DDR RAM |ECS[/b ][i] K7S5A MB[/i] |GF3 64 MEG |WIN XP PRO |MITSUBISHI DIAMOND PLUS 91 19"

Randy :). I didn't tell you to install it heheh. Just kidding, I'm sure it will work just fine for you as well.Regarding the landing view. I'm SOOOO disappointed that I can't get the landing lights into the cockpit. I suspect that it's got something to do with my display adapter Gainward gf4 Ti-4200 or the drivers themselves. I'm currently running the 29.42s because the performance boost is amazing with them. Earlier I had the 41.09s but they aren't really that good... image quality & performance is a LOT better with the older ones. Also Randy, I use almost explicitly your older landing view for instrument approaches. Phil's view is mainly used for visual approaches. I also tend to use those views for departures as well. They give a spectacular view out of the cockpit. And the FEELING of actually being in a cockpit is awesome, and that is just the reason I use the old view; the new view can't capture that feeling, it just doesn't feel & look like I was sitting in the left seat of an airliner. :(.cheersTero

Hi Tero.>- the CMD text DOES go away when disconnecting autopilot >even with joystick The CMD/FD annunciation on the EADI changes as it should when I disengage the A/P with the joystick, but the switches on the MCP stay lit. Do you mean that the lights on the MCP go out for you when you disengage using the joystick?>- I have no problems with shading with Lee's TCAS This is most likely a video card issue then...>- I had no problems with fuel burn before, and I don't have >any problems now with the 1.3 either The fuel burn is actually slightly unbalanced even with the latest patch, but not as much as it was before (I think). But as you said there is now also slightly different engine readings (but I thought there was before the patch too...?).Are you able to use autosave? And does the panel and FMC status get saved properly when you save flight, and loaded properly when loading a saved flight? Becasuse this doesn't work for me... Saving the panel state doesn't seem to be possible at all, and when loading older saved flights the panel state is sometimes loaded correctly, and sometimes not.Martin767 fetishistIt's a lot like life and that's what's appealing

Martin,The CMD lights on MCP go out just like they should, regardless of where I turn the AP off from.The flight saving has a bug though. The panel positions are saved as they should (I have 3 monitors), but the switch positions are not saved. The engines are running when I load a saved flight, even if the cockpit was cold&dark when saving. That's a bug for sure...Tero

>The CMD lights on MCP go out just like they should, >regardless of where I turn the AP off from. Hmm, I guess I'll have to dig around then...Martin767 fetishistIt's a lot like life and that's what's appealing