What is the 'ILS bug'?

It causes an error on the FMC "RWY/ILS Error" or similar where you have to go to RAD/NAV and delete the automatic tune of the ILS so it becomes correct. It's one of those things that's easy and quick to fix (i don't know how this got through betatesting, on my first flight i found the problem) and it isn't fixed because it's "part of the pack". Meh.

I think i said somewhere that if we have it in June, we'll be lucky.

 

[...]

 

I'm not trying to be dramatic here or similar, the 777 works good enough to be flown, it just doesn't appeal to me (yet) as much as other addons do.

 

June would be very optimistic.  :ph34r:

It causes an error on the FMC "RWY/ILS Error" or similar where you have to go to RAD/NAV and delete the automatic tune of the ILS so it becomes correct. It's one of those things that's easy and quick to fix (i don't know how this got through betatesting, on my first flight i found the problem) and it isn't fixed because it's "part of the pack". Meh.

 

 

AFAIK, this is related to the (corrupt) cold&dark panel state only. This panel state isn't the most realistic one anyway, and the other states (long/short turn) work just fine.

 

The workaround for the c&d state is to delete ALL three frequencies during your preflight, as the NAV1 and NAV2 radios are "stuck" as well.

 

Not sure that PMDG should dump their "one servicepack to fix them all" strategy (like in "Lord Of The Rings" ...) for that panel state alone ...

Yeah i know about the panel state. Nevermind me much, i guess i was just venting.

 

I hope they added alternate ways to set your BARO/RADIO altitude. Click and drag doesn't work for me. </venting 2.0>

Hmm..i thought it already was in beta...

 

Helps when you actually read things...particularly when the information is in the very first post (no, the 300ER is not part of the beta we're currently testing):

 

 

We are prepping the 300ER to go out to the beta team with the next SP1 update now as well.  Some folks have expressed some concerns that the 300ER was being held up by the SP1 and this really hasn't been true in one sense since we never intended to release the 300ER without the SP1.  To us they are essentially one large update because the functionality changes that we add to allow the 300ER to operate are part of the development cycle that brings in all the changes for SP1... 

Helps when you actually read things...particularly when the information is in the very first post (no, the 300ER is not part of the beta we're currently testing):

 

Well, it was said 'with the next SP1 update', which he probably assumed had happened sometime in the 8 days since that message. It would have been very possible that it had happened already.

 

Personally, my opinion is that we won't see SP1 or the 300ER before July/August, so I'm not waiting desperately for it.

Helps when you actually read things...particularly when the information is in the very first post (no, the 300ER is not part of the beta we're currently testing):

 

Hi,

 

Thanks for clarifying this.As per the op i understood that it was already in beta.Anyways sorry my bad.

Well, it was said 'with the next SP1 update', which he probably assumed had happened sometime in the 8 days since that message. It would have been very possible that it had happened already.

Personally, my opinion is that we won't see SP1 or the 300ER before July/August, so I'm not waiting desperately for it.

Exactly what i thought.But Kyle clarified it.Lets hope we see it soon.

 

 

Personally, my opinion is that we won't see SP1 or the 300ER before July/August, so I'm not waiting desperately for it.

Yeah. Welp, I'm outta this forum for a while.

 

[Hibernation]

This is boring and still no release in sight. See you after release!

Yeah. Welp, I'm outta this forum for a while.

 

[Hibernation]

Same here, now that the I wannit now brigade have arrived.

If I'm right about the current state of the 777's FBW logic, that issue alone will require a very MAJOR re-coding to fix, and yes, that will indeed take time as Robert R. was very upfront about when he started this thread.     I applaud his honesty about this issue and PMDG's continuing effort is certainly appreciated.

 

I think the bottom line though is that there is no quick fix, unfortunately, but they will eventually make it right however long it takes.    :mellow:

I'm still very much interested in this list.

 

Hopefully we'll see this posted sooner than later.

 

 

when it crosses that "too much perfection" line, it's bad, $89.99 of badness.

I'm not trying to be dramatic here or similar, the 777 works good enough to be flown

 

You just contradicted yourself. It's bad, it cost $89.99 for something bad, and yet it's fine to fly.

Your disclaimer doesn't really work, because you are being overly dramatic.

 

 

 

no matter what PMDG says we're seeing the 77L patch delayed because of a new product they want perfect on launch day

 

RSR has been crystal clear as to the reasons why the patch is being held up, and yet you still find the need to write this?

I know you read his updates and understand them. You just want to complain because you can't have the patch right this instant.

 

Would you rather they release a patch that isn't ready that requires another patch to fix everything that wasn't fixed, or wait for a patch that fixes everything it aims to fix?

They already covered the lack of micro updates for the time being and their plans on pushing those in the future. This isn't about perfectionism, it's about making sure the product works as it was intended to work.

Let them do their job and stop with the hyperbole.