Interesting, thanks.I don't do reinstallations!I had a feeling that something was corrupted in this particular situation because when I re-load the flight--and it's a night departure--not all of the lights come back on automatically as they should. Also, one or two items in the FMC have not been saved properly either such as the THR LIM settings. So I think this is a corruption specific to this one flight situation because various other saved situations with the PMDG 744 that I have saved previously still work normally. FS is funny how it sometimes fails to do things exactly right. But never mind. I find work arounds. In this case I changed the departing waypoint to DOMSE as I want to turn east before hitting the Potomac river.The PRYME2 SID worked for me as well -- at least the last time I tried it!Thanks again for your efforts and posts.Jonathan

Hi,this 360 orbit during a SID departure happens to me as well from time to time (in my case a WOBUN2G from EGLL (between BUR and WOBUN), i.e. well after passing the first waypoint (BUR) of the departure.I've the impression that it might be caused by having some fixes defined in the SID with different coordinates than the FMC NAV database.As you, I'm just selecting heading sel mode to go through and resuming LNAV after next waypoint.(see http://forums.avsim.net/dcboard.php?az=sho...ng_type=search)

I think there was some kind of corruption within the saved situation rather than within any SID or whatever. Today, I rebuilt the situation from scratch starting with the FS9 opening screen but just to check on something (which I outline below), I set everything to 12 hours earlier, i.e., by daylight.I then reloaded the flightplan that I'd built previously with RINKS/RAYEE, etc., and saved the whole situation. I then reloaded it and flew it and it worked perfectly. LNAV was perfect (as it usually is.)When I reloaded the daytime situation, I observed that the cockpit light switches for landing lights and some other lights did not activate as they should have done because I had saved them previously within the situation to ON. I have wondered therefore whether corruption might have been caused by the light switches themselves when saving the situation in the very first instance at night time with all lights set to ON. In that case too, a number of lights did not come on normally when I reloaded the situation, and also some of the settings within the FMC for the flight did not re-activate normally either.On my first attempt to rebuild the situation from scratch, after I changed the FS9 wx settings, for reasons beyond my comprehension, suddenly something went wrong with the hydraulics of engine no. 3. Why? "Because it's FS!" that's why. Why some situations and flights work flawlessly while others do not is beyond me. However, sometimes I do actually wonder whether some add-ons are so complex that something is just bound to go wrong from time to time for no apparently good reason. In addition, I have about 15 pieces of hardware for FS2004 so maybe it's a miracle quite frankly that any of this stuff works at all!Jonathan