Archive > Ask EuroHarmony
Flogger not logging
EHM-0654 Murray:
Didimo,
I'm sure it's been mentioned before but the V3 Flight Logger is very old (in software terms) and hasn't been actively developed for almost as long.
Furthermore, it was practically a one-man product even when it was being actively developed. Do write to Microsoft and complain about bugs in Windows 3.1?
(The above is personal position, not MT. I too am a software developer, I'm part of the team working on the new Flight Logger - heck, I'm the project manager on it - and we're dealing with things in a very different way with it.)
EHM-2155 Mariano:
--- Quote ---Originally posted by EHM-2198 Didimo
My point has been that a program that is well designed would properly handle its exceptions rather than doing the crash and burn thing. FL often crashes with "Error <place a number here)" for simple things that could have been easily avoided with:
--- End quote ---
I dont know if its your case, but one day trying to save a pirep (not submitting it), it gave me such an error and it closed. I was pissed hehe.
But after some checking I understood the reason, the paths in the program were pointing to a non-existing drive (One of my hard drives had died). So all I did was correct said paths and all was OK.
Maybe a suggestion for next FL would be that if the thing cant find the path, give us a more verbose comment about it, and when we click OK it shouldnt close the proggy all together making us lose our flight ^^
EHM-0654 Murray:
Already in the list Mariano. Trust me, we spent a fair amount of time digging up the niggles in FLv3 before we drew up the list of features for FLv4.
I fully expect most everyone to be very happy with FLv4 (but please, don't ask about release dates, beta testing or anything of that nature. We're not in a position to talk about such things.)
EHM-2266 Ronny:
Hello. I have read through the posts but desided to post one myselfe. I´m a turbo prop captain as of a few hours ago and quite inexperiensed. So far I have had to submit my pireps manually.
I use the flogger to get timetables, but cannot make it log my flights.
I belive this is due to my lack of experience with it and not nesseserely any program errors. My question is:
Can someone please take the time to guide me through it in extreme detail?
I use FSX on Vista.
Sincerely
Ronny Syvertsen
EHM-2029 Sotiris:
Hi Rony,
here's how I go through, using the FLLogger.
i assume you can open it and enter your passwords OK as you already use it for timetable information.
So here goes step by step:
1 - Start your FSX, and make sure that you engines are OFF (very important this one).
[You can also choose that you start with engines off by default. This is done by loading any flight in FSX, turning the engines off, save the flight and mark it as the DEFAULT flight.]
2 - Fire off the FLLogger
You get a screen looking like this.
3 - Use the buttones to select your flight. There are many ways to make a selection.
i)First by using the division buttons you exclude any division you don't want to use
ii) You can also click on the Class numbers to exclude any classes you don't want. (Dont worry if not all classes are available this is due to your current rank. As you progress more classes will become available)
iii)Using the drop-down lists you can see what is available by airport, country or city
Anyway, let's say we want to choose a class 1 flight from Torino to Zurich. ( 1469 )
4 - Once you highlight this flight you get this screen:
notice that already there are limited numbers of aircraft to choose from according to the flight's class
5 - Choose an aircraft. In this case let's choose the B-1900D. Once you highlight the B-1900D you get a screen like this:
Once those two green lights are lit you're ready to go.
Fly your flight and have fun :-)
Once you are done flying, parked and turn the engines off you're ready to report the PiRep.
Just click on the Submit PiRep button and you're good to go.
All done!!
If you have any further questions, just let me know :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version