Pilot Journey v1.02

  • PJ already switches planes.

    The problem with positioning is that main.mcf does not use lat/long values but 3 parameters which are presumably x/y/z coordinates.

    This would be a hint towards the earths surface possibly being modelled as a flat projection and not as an actual sphere or ellipsoid.

  • Plane switching - I hadn't noticed that one yet. Great !


    "The problem with positioning is that main.mcf does not use lat/long values but 3 parameters which are presumably x/y/z coordinates."


    Jet-Pack - any hints for us on positioning?

  • PJ already switches planes.

    The problem with positioning is that main.mcf does not use lat/long values but 3 parameters which are presumably x/y/z coordinates.

    This would be a hint towards the earths surface possibly being modelled as a flat projection and not as an actual sphere or ellipsoid.

    x, y, z is the karthesian position in space relative to earth's center, rotated with earth reference frame. X is towards 90° East meridian, Y towards 0° and Z up I think. And it's an ellipsoid model of the earth...

  • x, y, z is the karthesian position in space relative to earth's center, rotated with earth reference frame. X is towards 90° East meridian, Y towards 0° and Z up I think. And it's an ellipsoid model of the earth...

    Wow, thats that's pretty cool. Thanks a lot for the insight. For some reason I expected spherical coordinates for that shape but the values just didn't make sense for that.

  • I think this should be made a sticky or whatever in the forum.


    I bought ORBX Netherlands in the sale and decided instead of jumping to all the best bits and whizzing through the times of day, I will simply have Pilot Journey start me somewhere in Netherlands, and have it let the scenery unfold for me as I go through a career.


    Love how it sets many things now in game, and random time of day. Had to change one a bit as it had me flying a banner over Touge quite late in the day and nobody would of seen it lol.

  • Hey perestain I have another idea for an improvement. I've used Pilot Journey for every flight i've made since you launched it. I love the variety of time and weather it generates so i've been thinking of other aspects of my flights which i don't tend to vary but i could.


    How about if PJ did some ATC style things like specify what runway you should land on and whether you had to join the traffic pattern or should fly straight in?

  • Hey perestain I have another idea for an improvement. I've used Pilot Journey for every flight i've made since you launched it. I love the variety of time and weather it generates so i've been thinking of other aspects of my flights which i don't tend to vary but i could.


    How about if PJ did some ATC style things like specify what runway you should land on and whether you had to join the traffic pattern or should fly straight in?

    That sounds like a cool idea.


    I have tried pilot2ATC for Xplane once and all this flightplanning and ATC stuff is very fascinating, but I'm afraid it's also well beyond the scope of my aviation knowledge or programming abilities. For example it would probably be wrong to set the active runway randomly, since it is has to depend on the conditions and whether it has a published IFR approach etc etc. Also I would probably have to manually research all that info which I barely understand for all the runways on all airports which would take a lot of time.


    To add more realism, right now its probably best to do the flight planning manually, i.e. use the navigation link to http://www.airportnavfinder.com to get published depature and approach procedures, decide the runway based on wind and conditions yourself and then head to https://skyvector.com/ and create an actual flightplan along the published VFR or IFR routes (whatever applies) and edit that flightplan into FS2 as closely as possible. http://www.navfltsm.addr.com/ is an excellent ressource for learning how the navigation works. But I am really just a beginner at following all that stuff myself and far from being able to create automated results that are convincing here.


    I could of course add some random occurences, things happening during flight, like a sudden change of destination. flying an extra round around the airport, some dramatic stuff, engine failure which you had to manually simulate or things like that. Its on the idea list, but I can't promise very much right now, I'm currently too busy with my actual work to heavily delve into a big PJ update.

  • Yes I take your point. ILS (and local terrain) is probably what makes it complex otherwise you could just pick whichever runway is closest to upwind or randomly pick from parallel runways. That is kind of what I'm doing now. That data could be got without external references - just by looking at the FS2 runway definition files. In terms of what random scenarios could be offered by PJ I'm not entirely sure what's realistic but plenty of real world pilots on this forum would be able to suggest things. Maybe something to consider when you have more time.

  • I'll add it in the next update, no eta though since I'm still pretty busy. I think I have to rework the way planes are organized and chosen by rng. Right now it's not really expansion-friendly. I didn't really think a lot about upcoming aircraft back then.


    As a quick and dirty workaround until then you could just allow yourself to fly a R22 whenever you rent a pitts (same amount of seats) and then edit the journal entry manually. Fuel cost and range will be a little off, but they're not that accurate to begin with.

  • Same here. I'd love it if PJ would read the airport list from the IPACS directory so it automatically knows about airports in new DLCs. Oh and new planes.

  • Would be cool if the program could read all the airports in the addon scenery folder as well.

    and the My Documents area for fsCloudPort airports and other home made ones.