The first time I used FSP with FLogger I had a "Engine started without the beacon on" penalty when I was at cruise level and without even touching the panel.
The second time was last Friday night attempting to fly EHM5205 from Madrid to Amsterdam.
While getting prep to pushback I clicked the hatswitch for left side view and the FS froze. Since I cannot see any relationship between FSP and FLL I am certain that this is a recurrent problem with my 3-year old laptop.
Restarted everything and while just getting at cruise level, I minimized FS to load Navigraph. Then the screen went black and the mouse icon started to titillate (I don't know if this is ancient English) and after a couple of minutes I just re-booted and started all over again.
This time I loaded everything (Navigraph, Servinfo, Real Time) BEFORE even the FS. Tookoff, cruised and started to descend at about 110NM to Schipol. This time I clicked on the Servinfo icon and the same thing happened: black screen and mouse icon titillating. This time (about 2 a.m my time) I counted until 200, went to the kitchen for a glass of water and then turned the laptop off, fighting against my impulse to smash it down and went to bed in a very, very cold (minus 3 celsius) night.
Last night I did everything the same except loading FSP. It was perfect.
The only times I have had this problem is when flying the LDS B763. I like to use FSP with it because after loading it I have a good %CG which once loaded into the FMC gives you a very reliable elevator trim setting.
What I did last night was to load the FSP, get the %CG and then abort the FSP flight. This way the loading scheme remains so the settings.
Before writing this, I went to the FLogger forum section looking for something like that but I could not find it.
This is why I think that I maybe the only one with this problem.
Will appreciate your comments on that.
Next time I will use FSP with a plane other than the B763 to see what happens.
Cheers,
Hector