Hopefully the next update will fix that. :smile:

 

Regards,

Mo

 

 

Hopefully the next update will fix that.

 

Has it been reported at support.precisionmanuals.com?

Has it appeared in the issue tracking thread as being addressed?

 

If not, report it using the above link.

...otherwise, there's no reason to hope.

Has it been reported at support.precisionmanuals.com?

Has it appeared in the issue tracking thread as being addressed?

 

If not, report it using the above link.

...otherwise, there's no reason to hope.

 

Lots of topics been acknowledged in here so no need to report all the time.

 

Regards,

Mo

 

 

Lots of topics been acknowledged in here so no need to report all the time.

 

If you want it to be fixed, and it's not reported, then they don't know to fix it.

 

If you're experiencing the issue, then you should report it.

 

Vertical speed is not mentioned even once in the thread they're using to track what's been reported (here: http://forum.avsim.net/topic/418750-pmdg-777-issue-tracking-thread-read-before-posting/).

 

 

 

...so again, if you don't report it, then they may not know about it, and it won't get fixed.  So, do you still not want to submit a ticket?

So has anyone submitted a ticket yet? If not I'll surely do it but want to find out before doing so as not to bug them with a report they already received.

So has anyone submitted a ticket yet? If not I'll surely do it but want to find out before doing so as not to bug them with a report they already received.

 

It's not in the tracking thread.  Having multiple tickets from people actually experiencing the issue will help them take note of it.  One ticket looks like an isolated incident.

 

If you experience a problem, submit a ticket.

 

You don't need to check to make sure someone else has or has not reported it.

Yeah, Per Kyle's suggestion, I submitted a ticket.  No response yet.  I would hope everybody who is experiencing this submits one.  In my opinion, this is a serious problem that needs to be rectified.  The real 777 flight control system does not behave in this way and as of yet, I have not found a specific root cause on my end of things.

Yes, unrealistic trimming.

 

Mo

PMDG, could you possibly find a qualified Beta tester for testing your plane in the future, so we don't have this kind of problem.

 

@Kyle I appreciate your input but please in the future come up with a more constructive answer. If I wanted to issue a ticket I would have in the first place before starting this topic. There was a topic in the PMDG forum related to the trim problem and it was acknowledged by the PMDG team. If they can rectify that problem with the trimming then this problem will go away, I presume. That is why I am waiting for an update to see the problem is fixed. If it is not fixed then I will issue a ticket.

 

Regards

Mo

 

 

PMDG, could you possibly find a qualified Beta tester for testing your plane in the future, so we don't have this kind of problem.

 

With all due respect, but what qualifies you to tell them their beta testers arent qualified enough? Kyle was a beta tester and he didnt seem to notice this issue, perhaps the others didnt either. I'll go ahead and issue a ticket anyway. The more they receive, the more urgently it may get dealt with.

PMDG, could you possibly find a qualified Beta tester for testing your plane in the future, so we don't have this kind of problem.

 

(...)

 

 

Like in "There's not even a single qualified PMDG T7 beta-tester"?

 

That's tough, Mo, really tough ...

With all due respect, but what qualifies you to tell them their beta testers arent qualified enough? Kyle was a beta tester and he didnt seem to notice this issue, perhaps the others didnt either. I'll go ahead and issue a ticket anyway. The more they receive, the more urgently it may get dealt with.

First of all I am not a beta tester I am a customer and I have paid $90 for this product. I am not a real pilot either but I want to enjoy the product, not come on to the forum being told I have to put a ticket to resolve the issue. I wasn't implying in a bad way to getting a real beta tester but at the same time, in my opinion, that some of the beta tester want to get there hands on this plane for nothing, so that they don't have to pay $90. Also, from myself who has no real experience and only basic knowledge of this aircraft, I was the one that noticed this behaviour, which should have been noticed in the first place by a beta tester and not me!

 

Regards

Mo

 

 

PMDG, could you possibly find a qualified Beta tester for testing your plane in the future, so we don't have this kind of problem.

 

That's kinda uncalled for, honestly.  There are two teams: a tech team and a beta team.  The tech team is comprised mainly of pilots of the real thing, or other people with relevant real experience with it.  The beta team is just a group of enthusiastic testers with whom PMDG has some sort of relationship.

 

Since the tech team also makes a pass at the plane (and missed this), you're telling me that real pilots of the bird aren't qualified?

 

There's no reason to call people unqualified because a bug slipped through.  There are a ton of things to check, recheck, and so on.  Some things are bound to slip through.  It's unfortunate, but that doesn't mean that people weren't qualified.

 

 

 

@Kyle I appreciate your input but please in the future come up with a more constructive answer.

 

I don't think you do, honestly.  I think you're looking for the answer that you want to hear and not the answer that you need to hear.  The reason I gave you the answer I gave you is included below.

 

 

 

If I wanted to issue a ticket I would have in the first place before starting this topic. There was a topic in the PMDG forum related to the trim problem and it was acknowledged by the PMDG team. If they can rectify that problem with the trimming then this problem will go away, I presume. That is why I am waiting for an update to see the problem is fixed. If it is not fixed then I will issue a ticket.

 

The reason I told you to submit a ticket was so that they could track the problem.  That's part of the reason for the support portal (collecting/tracking known issues).  You are not guaranteed a response from the team here.  You are with the support portal.

 

Heck, you only need to look as far as the Ops Center to see how they view the world:

-Community Support Forum (note the community, meaning you're getting support from the community, not  necessarily them)

-Support Portal

 

 

 

I am not a real pilot either but I want to enjoy the product, not come on to the forum being told I have to put a ticket to resolve the issue.

 

So, how did you want them to find out about the issue?  Telepathy?  Reading crystals?  Calling Miss Cleo?

 

If nobody tells them there's a problem, then how are they going to know?  The forum is not how you get into contact with the team for support.  You go to the portal for that, as I've pointed out several times, in an effort to get you the help that you deserve.

 

Sitting on information for whatever reason just doesn't make any sense.  If I have to go look at problems in my code, it's best that I know all of the problems going in so that I can better fix the issue.  When you're in the weeds all day, looking at code, knowing all possible issues going into the fix is hugely important.  That way, you know where to look and what might be affected by your changes.

 

 

 

I wasn't implying in a bad way to getting a real beta tester but at the same time, in my opinion, that some of the beta tester want to get there hands on this plane for nothing, so that they don't have to pay $90.

 

People don't apply to be PMDG beta testers; they're invited.  It's this way for a couple reasons, but one of them is just so that you don't get people wanting to be on the team just to get a free plane.

 

 

 

Also, from myself who has no real experience and only basic knowledge of this aircraft, I was the one that noticed this behaviour, which should have been noticed in the first place by a beta tester and not me!

 

That's not a fair assessment.  Things slip through the cracks, and part of the beta process is fixing things that pop up.

 

Look at it this way:

As a beta tester, I flagged several issues.

Problem A

Problem B

Problem C

(System D appears to be working fine, so I don't make any comments about it)

 

PMDG then went in to fix:

Problem A

Problem B

Problem C

 

The updated version notes that A, B and C are fixed.  I go fly to verify the fixes for:

Problem A

Problem B

Problem C

 

...but the change to Problem A caused a problem with System D.  We'll call this Problem D.  Since System D was working fine earlier, I may only check it briefly, if at all.

 

Problem D goes unnoticed in the release version and customers are the ones who notice it.  It sucks, but if those customers never bring it up, it might not get noticed.

 

 

 

I'm trying to help you help yourself here, but for whatever reason you won't have it.  I can't, for the life of me, figure out why.

 

I was the one that noticed this behaviour, which should have been noticed in the first place by a beta tester and not me!

 

I hadnt noticed it really because i am mostly either hand flying the thing or in other modes like level change or VNAV. This V/S issue isnt a show stopper so i dont see why it would prevent you from enjoying the product anyway, as you said, it probably just an after effect caused by the supposedly "funny" FBW behaviour which has been noted in the issue tracking thread.

 

PMDG have said themselves that they cannot test their product on every single combination of computer parts and software configuration to release a 100% bug free product (not quoting exact words here), so if something happens on your setup that doesnt seem right, it may not happen on their setup, and in some rare instances they probably cant even replicate it, and if it did happen before release they would have fixed it if they thought it serious enough to not let it wait for a patch, its just the reality of software programming, you name 1 single piece of complicated software for flightsim with thousands of lines of codes that works flawlessly, you wont have to look further than FSX itself as a start. Just hang in there, submit a ticket if you wish, the more submitted the merrier.

 

It's very complex piece of software. There's gonna be bugs when released. This happens across all software genres. Microsoft still sputters out service packs and hotfixes for Win7 occasionally. If you're gonna venture outside of DOS, get used to bugs being in initial releases. Flightsim releases have had it MUCH worse; as in "can't get the plane into the air" worse.

 

As far as putting beta testers against the wall and pulling the trigger, do some research first. Yes, part of the beta group aren't RW T7 pilots. But they did have RW T7 pilots not only on the beta team, but on the development team. They provided insight and advice to PMDG throughout the development process, which included internal testing before the beta tests. I'm sure some are still providing advice. PMDG is currently working (like crazy, I'm sure) to resolve all issues as fast as possible. Not only issues with the programming itself, but also issues stemming from the infinite number of hardware setups and individual software configurations within the community. 

 

 

As far the comment about not having RW T7 experience...I doubt you're a RW software programmer either. If you were, I doubt you'd make such ridiculous comments.

 

 

 

That's kinda uncalled for, honestly.

 

Entirely uncalled for.