|
Post by douglas on Sept 2, 2020 6:03:59 GMT
Thank you Drake also for your clear clarification.
|
|
|
Post by douglas on Sept 2, 2020 6:06:32 GMT
Thank you Drake also for your clear explanation.
|
|
Paughco
Junior Member
Nice day for somethin'.
Posts: 98
|
Post by Paughco on Sept 6, 2020 2:53:55 GMT
I learned about flying (flight sim test flights) from that (copied and pasted from my post on DC-3 Airways forum:
"Doggone! I didn't think of the possibility that my computer time over a flight might actually be longer than my external stopwatch time! Next time I'll use the FTime and pause technique.
Ok, let's try an example. Say we have a test flight of 100 nautical miles between start point and finish point. My C-47 has a cruise speed of 163 knots. That should take 36.81 minutes. That should be the exact time I read on my in-cockpit FTime device. But, because my computer has taken a lot of time to catch up to scenery loading, etc., my iPhone stopwatch says my flight took 41.83 minutes (lots of scenery loading in this example!). I turn in 41.83 minutes for my test flight. My average speed gets listed in the official roster as 143.44 knots. That's 12% slower than my actual cruise speed. They estimate that it should take me 97.79 minutes to complete the first flight leg. I actually took 88.99 minutes when I flew the leg. That was 9% less time than the allotted time, which appears to validate this theory. Oh yeah - I'm flying with Active Sky real weather, which, if I recall, gave us a slight headwind on leg 1, which could account for the missing 3%.
Very interesting! I hope writing this all down will help me remember to use the FTime clock to record test flight times in the future!"
By the way, have you ever heard the song "Teterboro Tower?" No? Well, here it is: www.youtube.com/watch?v=x37f-_XrMJ0.
Seeya ATB
|
|
|
Post by skmcconnell on Sept 10, 2020 13:07:34 GMT
Well, X-Plane 11 updated to 11.50 with the new Valkun graphics driver. I spent the better part of last night updating the sim. I will see how much things improve this evening. As far as Screen Shots, I can not get mine to show up in the forum. I am using Jet screenshot and copying the forum link and paste the link but the picture will not show up in the post.
|
|
|
Post by skmcconnell on Sept 11, 2020 14:27:04 GMT
|
|
|
Post by Allan Lowson on Sept 13, 2020 17:13:16 GMT
Sean,
Thanks for the link, it also works for we unwashed non-AOPA members.
Time measurement was the subject of a slightly off-the-wall discussion many moons ago in a GAAR forum. Some folk got quite aerated over the acceptability of various means of measuring time. In the end the sim time was settled on as being the most accurate. The sims can hit low frame rates in high scenery density areas, and this probably affects the time clock as well. Tom's ftime meter uses the sim clock which seems to make for more consistent time measurement.
Cheers, Allan
|
|
|
Post by skmcconnell on Sept 13, 2020 19:31:59 GMT
Well upgrading XPlane 11.41 to 11.50 in the middle of this rally proved foolish. Now XPlane 11.50 just crashes to desktop. also noted windows 10 updated the same evening and am suspecting something there went a foul messing up XPlane.
EDIT: I got X-Plane11.50 working again. it turns out that XPUIPC needed the correct IP address even though everything in running on the same machine. used to be able to ignore the error in that case but not any more.
|
|
|
Post by Johan van Wyk on Sept 17, 2020 19:20:18 GMT
Well upgrading XPlane 11.41 to 11.50 in the middle of this rally proved foolish. Now XPlane 11.50 just crashes to desktop. also noted windows 10 updated the same evening and am suspecting something there went a foul messing up XPlane. If you are using LittleNavMap, your crash was most probably caused by the new X-Plane 11.50 multiplayer/tcas implementation. X-Plane 11.50 users please ensure that you have at least version 1.0.19 of the " Little XpConnect" installed in the plugins. This is a fix for potential crash. The latest version of LittleNavMap ver 2.4.5 does not ship with the latest update of "Little XpConnect". Go to your directory " \X-Plane 11\Resources\plugins\Little XpConnect", look for the file " CHANGELOG.txt". The top lines should look like this: Numbers (#) refer to Github issues. For example: albar965/littlenavmap#3 is https://github.com/albar965/littlenavmap/issues/3.
Version 1.0.19
* Fix for potential crash with new X-Plane multiplayer/tcas implementation as of 11.50.
Version 1.0.18 Version 1.0.17.rc1 The important line is the third line, if it does not say " Version 1.0.19", you will get a crash at some stage later. Download this update and replace the older Little XpConnect in the \plugins folder.
|
|
|
Post by skmcconnell on Sept 20, 2020 0:40:41 GMT
Thanks, Johan As per the edit on my previous post, I found in my case an old version XPUIPC was the culprit. inputting the correct IP address fixed the issue. I have since upgraded to XPUIPC version 2.0.5.9. I did need the updated Little Xpconnect so thanks again
|
|