Disregard

Edited March 18, 20251 yr by Cpt_Piett

1 hour ago, GregP said:

Has no one noticed that the update log itself is hilariously bugged and seems to include feedback notes from testers, pointing out a ton of bugs that either existed before this update or still exist? I don't have the Ifly and have no real opinion on it, I just can't believe that no one appears to have actually read the notes that iFly seems to have really screwed up.

“We. Did. Stuff”.

-B

35 minutes ago, Stearmandriver said:

What do you mean?  It's a list of open items / tickets that have been addressed in the update. I made several of those reports myself.   What would you expect from a changelog, other than a list of areas that have been changed? 

But take a very close look at the list. It's not a list of bugs fixed, rather it seems to be an export from a bug tracking database. For example items 9 and 10, these are comments from a tester (maybe you?) about things not working properly: 

9. LE flaps transit light illuminates on rotation and comes on and off intermittently
during the initial climb. If this is based on some report from irl, let me know but it's
something I've never seen in several thousand hours of flying the NG/MAX.
Ticket/19
 
10. After takeoff without VNAV armed, speed bug set to V2, the bug was well into
the low speed bricks with the alpha floor symbol flashing on the speed window. V2
is pretty close to the bricks but definitely shouldn't be in them. ZFW was set and
checked both in the FMC and in the payload page in the EFB and I did click on "set
payload" during preflight. 
Ticket/20

Edited March 18, 20251 yr by GregP

11 minutes ago, GregP said:

But take a very close look at the list. It's not a list of bugs fixed, rather it seems to be an export from a bug tracking database. For example items 9 and 10, these are comments from a tester (maybe you?) about things not working properly: 

9. LE flaps transit light illuminates on rotation and comes on and off intermittently
during the initial climb. If this is based on some report from irl, let me know but it's
something I've never seen in several thousand hours of flying the NG/MAX.
Ticket/19
 
10. After takeoff without VNAV armed, speed bug set to V2, the bug was well into
the low speed bricks with the alpha floor symbol flashing on the speed window. V2
is pretty close to the bricks but definitely shouldn't be in them. ZFW was set and
checked both in the FMC and in the payload page in the EFB and I did click on "set
payload" during preflight. 
Ticket/20

Does it really make a difference as long as items got addressed or fixed?

13 minutes ago, GregP said:

But take a very close look at the list. It's not a list of bugs fixed, rather it seems to be an export from a bug tracking database. For example items 9 and 10, these are comments from a tester (maybe you?) about things not working properly: 

9. LE flaps transit light illuminates on rotation and comes on and off intermittently
during the initial climb. If this is based on some report from irl, let me know but it's
something I've never seen in several thousand hours of flying the NG/MAX.
Ticket/19
 
10. After takeoff without VNAV armed, speed bug set to V2, the bug was well into
the low speed bricks with the alpha floor symbol flashing on the speed window. V2
is pretty close to the bricks but definitely shouldn't be in them. ZFW was set and
checked both in the FMC and in the payload page in the EFB and I did click on "set
payload" during preflight. 
Ticket/20

Correct.  I'm not seeing your point, I guess.  The changelog is a list of bug reports or suggestions that have been acted on.  They're even labeled as support tickets.  What better way to describe the changes made, than list the tickets detailing what changes needed to be made? 

Makes pretty good sense to me.

2 hours ago, GregP said:

Has no one noticed that the update log itself is hilariously bugged and seems to include feedback notes from testers, pointing out a ton of bugs that either existed before this update or still exist? I don't have the Ifly and have no real opinion on it, I just can't believe that no one appears to have actually read the notes that iFly seems to have really screwed up.

I read the notes and OWN the airplane.  As you indicated you don't.  I suspect you'd like it if you did.  

58 minutes ago, GregP said:

But take a very close look at the list. It's not a list of bugs fixed, rather it seems to be an export from a bug tracking database. For example items 9 and 10, these are comments from a tester (maybe you?) about things not working properly: 

9. LE flaps transit light illuminates on rotation and comes on and off intermittently
during the initial climb. If this is based on some report from irl, let me know but it's
something I've never seen in several thousand hours of flying the NG/MAX.
Ticket/19
 
10. After takeoff without VNAV armed, speed bug set to V2, the bug was well into
the low speed bricks with the alpha floor symbol flashing on the speed window. V2
is pretty close to the bricks but definitely shouldn't be in them. ZFW was set and
checked both in the FMC and in the payload page in the EFB and I did click on "set
payload" during preflight. 
Ticket/20

It looks like an ideal way to respond to logged issues. 

 

38 minutes ago, micstatic said:

I read the notes and OWN the airplane.  As you indicated you don't.  I suspect you'd like it if you did.  

You don't need to own the plane to see that it's a terrible way to write changelogs. Never seen it done that way, and all it does is pollute everything with verbosity.

Like this for example:

Quote

• Thanks for adding the delay between selecting GND and the START VALVE OPEN light but it’s a bit too long now, by about a second (just based on my impression of it). Also, you should get N2 indications the instant that the start valve opens, there’s a lag there too in the iFly which shouldn’t be there.

Now - what does that mean in terms of the actual thing getting changed? Did they fix both delays? Is the N2 indication still an issue? Really unclear and makes for a long, pointless read.

The right way to do it would have been to put something like:

Quote

• Adjusted delay between GND and START VALVE OPEN
• Removed lag from N2 indications after start valve opens 

 

See how much better that is? Instantly clear.
Also means you can just scan the changelog quickly.

This and proper commit messages are my bugbear.

Edited March 18, 20251 yr by Georgleboui

Dunno, I would argue that more detail is gleaned from reading the actual tickets.  Obviously you had no difficulty understanding it as you were able to parse it into your preferred verbiage. 

But, whatever.  If this is the inconsequential thing users have to gripe about for this release, I guess they've done a pretty good job.  😉

9 minutes ago, Stearmandriver said:

Dunno, I would argue that more detail is gleaned from reading the actual tickets.  Obviously you had no difficulty understanding it as you were able to parse it into your preferred verbiage. 

But, whatever.  If this is the inconsequential thing users have to gripe about for this release, I guess they've done a pretty good job.  😉

The issue is that I made assumptions in translating it and that’s a bad thing to do for changelogs.

But hey, I’m with you that this is a minor point - who cares. Just struck me as strange and a bit unprofessional, as someone who has to write a lot of outward facing changelogs.

45 minutes ago, Georgleboui said:

The issue is that I made assumptions in translating it and that’s a bad thing to do for changelogs.

But hey, I’m with you that this is a minor point - who cares. Just struck me as strange and a bit unprofessional, as someone who has to write a lot of outward facing changelogs.

Again what difference does it make, they fixed alot of issues and you're nit picking their wording explaining what they done. Why don't you go fly the plane and report your bugs to them in your perfect way.

1 hour ago, Georgleboui said:

You don't need to own the plane to see that it's a terrible way to write changelogs. Never seen it done that way, and all it does is pollute everything with verbosity.

Like this for example:

Now - what does that mean in terms of the actual thing getting changed? Did they fix both delays? Is the N2 indication still an issue? Really unclear and makes for a long, pointless read.

The right way to do it would have been to put something like:

See how much better that is? Instantly clear.
Also means you can just scan the changelog quickly.

This and proper commit messages are my bugbear.

Just wait till you get a hefty amount of notams. At least half depending on where you are flying don't even get read. Then maybe what you see has been written on the changelog isn't actually pointless.

Edited March 19, 20251 yr by carlanthony24

After the RJ ...or before the RJ (depends on the week)

My favorite plane to fly. I was happy without the latest update.

Now I am happier (not sure that is a word)

 

8 hours ago, Ron Lefebvre said:

After the RJ ...or before the RJ (depends on the week)

My favorite plane to fly. I was happy without the latest update.

Now I am happier (not sure that is a word)

 

Hi Ron,

I love the RJ's too.  Great work by JF.

If you like them, you'll love their Version 2 F28.  So So good mate.

Jase

13 hours ago, Ron Lefebvre said:

After the RJ ...or before the RJ (depends on the week)

My favorite plane to fly. I was happy without the latest update.

Now I am happier (not sure that is a word)

 

My new favorite plane to fly is the updated SWS PC12.  It is the only plane I have ever flown in a sim that makes me feel like I am flying a plane in real life.