Not that it is of much use, but, the Patch evidently stopped it from logging flight time. duh.

Yup. Something is wrong with the logbook for me too. Some flights are logged and some not. Annoying. 

I found out the Log Book feature is not available if you are in the Developer Mode.  I opted out of Dev Mode and the Log Book is back available and working for me.  duh.  Who wouddy thunk it.

3 hours ago, raymar said:

I found out the Log Book feature is not available if you are in the Developer Mode.  I opted out of Dev Mode and the Log Book is back available and working for me.  duh.  Who wouddy thunk it.

I am not in dev mode however.. 😕

 

Hmm, no problems as far as that goes for me. Had a quick 15 min flight around the airport I was last in, to see the new things from the patch(after it was finally installed Weds night) and that was saved along with 2 flights I did on Thurs an hour & hour and a half long flights.

Did notice a fix in the log, prior to patch, flight was only shown as month/year. Post patch it was now showing Month/Day/Year.

It would be nice to have an editor for it.

I do notice that I think you have to be at an actual set parking spot for it to log... 

After the patch the logbook stopped working for me as well.  Yes, I'm always in developers mode.  So I just did a quick flight with dev mode switched off and it did actually log the flight.  It makes sense MS/Asobo made that logbook change as working on scenery in developer mode if I don't start parked or forget to turn off the aircraft it logs tons of entries with no actual flight time.  I wonder if there's a way to edit the logbook entries as the logbook seems buggy anyway.  Sometimes it doesn't log certain takeoffs or landings.  It also doesn't record night takeoffs or landings correctly if I change the time once airborne.  Thankfully not a huge issue but hope it's corrected at some point.

I've had a few hour plus flights after the patch and none were logged. I do keep developer mode on and will turn it off tonight to see if it makes a difference.

10 hours ago, raymar said:

I found out the Log Book feature is not available if you are in the Developer Mode.  I opted out of Dev Mode and the Log Book is back available and working for me.  duh.  Who wouddy thunk it.

Good fine, I hope. None of my flights yesterday were logged and I reported so. Responses I received indicated it was unique to me.  Thanks for this.

3 hours ago, Jimbo_in_Thailand said:

After the patch the logbook stopped working for me as well.  Yes, I'm always in developers mode.  So I just did a quick flight with dev mode switched off and it did actually log the flight.  It makes sense MS/Asobo made that logbook change as working on scenery in developer mode if I don't start parked or forget to turn off the aircraft it logs tons of entries with no actual flight time.  I wonder if there's a way to edit the logbook entries as the logbook seems buggy anyway.  Sometimes it doesn't log certain takeoffs or landings.  It also doesn't record night takeoffs or landings correctly if I change the time once airborne.  Thankfully not a huge issue but hope it's corrected at some point.

Yes I have noticed a lot of short coming of the Log Book. I hav one total night landing recorded but, must have made dozens.

After turning off Developer mode my log book is back working. 👍

Scratch that. It seems it sometimes does and sometimes doesn't. Tonight it logged my 1:20 hr flight, but not the takeoff or landing.

Thanks for the heads up! I also noticed that the G5000 is not working in the Cessna Longitude after the patch. I am unable to manually input or view flight plan. Any suggestions?

I am not sure about this but I have noticed that takeoffs and landings might not be counted if you re not using ATC and receive the requisite clearances. Flights I have done with no ATC did log flight hours but 0 for both takeoff and landing. Then with ATC, they were counted. Not tested enough to be sure though.

Mine seems to work all the time. Do not even have to land a flight either for it to be logged. It just gets logged as flying in the 'Vicinity' of the airport I took off from.

CJ