18 minutes ago, pmplayer said:

Not broken, learn the plane, not one problem on a dozen flights now so very fine here..

cheers 😉

Hi Pmplayer. I am sometimes harsh of new foundings.

Thing is, I started a 1st flight. I put in a star with 90 degree turns, 3 turns in a row. 

I deviated from the lnav path and went in a roll and then deep dive.

Perhaps it was because of 1st startup. I just started it 1st time thinking that it would work right away. Hdg mode did not respond it was if in sim session automated flight was entirely broken.

Should I start ifly plugin manually?

I take the benefit of the doubt from you because I know you like quality airliners too.

 

 

I came across phantom controller input again lately and PMDG and MaddogX does not like this. Descend during takeoff or complete loss of electric and engines after takeoff.

Spoilers and flaps and who knows deploy even without visually movement(flaps in the PMDG)

This is really a killer as it kills the flight model completely.

Just a thought

Latest i made a rather clean keyboard config as well and latest trip was positive even going to visit the MSFS menu and back.

Fingers crossed

Michael Moe 

How to get weather request. Acars does not respond? Dep/arr weather info. Where via EFB perhaps?

1 hour ago, Piotr007 said:

Should I start ifly plugin manually?

If everything is working it should start automatically when you start the flight. 

Okay, everytime I buy a new airplane I have to use it once and restart sim. 1st use causes always broken stuff for me.

I guess it is a standard reboot procedure I should follow.

However. I find the simbrief options very limited.

Init ref page no auto populated isa/tat fields. Somehow my wx uplink is invalid though it is pointed to wx/appdata folder.

I cannot request weather data for departure and arrival?

 

29 minutes ago, Piotr007 said:

Okay, everytime I buy a new airplane I have to use it once and restart sim. 1st use causes always broken stuff for me.

I guess it is a standard reboot procedure I should follow.

However. I find the simbrief options very limited.

Init ref page no auto populated isa/tat fields. Somehow my wx uplink is invalid though it is pointed to wx/appdata folder.

I cannot request weather data for departure and arrival?

 

I recommend this to You if You are interesting (ofcourse there is a few other tutorial but check all those videos and no problem):

Start tutorial 1

 

Still I noticed some erratic behaviour. 240 flaps 1, 4500 ft , suddenly with v/s set -800 it started to climb and add thrust.... went totally bezerk.

3 hours ago, Piotr007 said:

How to get weather request. Acars does not respond? Dep/arr weather info. Where via EFB perhaps?

You can’t. It’s the one glaring thing I find missing in it.

Edited November 4, 20241 yr by B777ER

1 hour ago, B777ER said:

You can’t. It’s the one glaring thing I find missing in it.

Not so good, but it is flyable. But not mature as pmdg. I see a huge contrast. I have to go external for weather info. That is plain bad.

How about the wind data uplink?

I put wx. Data from simbrief in the work-folder for WX.

I am getting invalid uplink messages. Is this option just cosmetic?

 

 

 

Wind data uplink works without you putting anything anywhere, it just pulls from simbrief.  You click Request and then Load.  Have you added your simbrief id in the appropriate place in the tablet?

7 hours ago, Piotr007 said:

Still I noticed some erratic behaviour. 240 flaps 1, 4500 ft , suddenly with v/s set -800 it started to climb and add thrust.... went totally bezerk.

This is spiky controller inputs.  Probably when you touched your quadrant to set flaps 1, you got a throttle input.  It's definitely not anything wrong with autoflight logic or we'd all be seeing it.  I've put this thing through more paces than probably any other simmer out there in the course of testing navdata (almost constant maneuvering flight vs just cruising around) and I've never seen erratic behavior, I guess because I'm lucky enough not to have spiky controls. 

The solution for now is to set dead zones on your control axes.  An update is coming that will lock out controller inputs while autoflight is engaged.

20 minutes ago, Stearmandriver said:

  An update is coming that will lock out controller inputs while autoflight is engaged.

That is exactly what I was thinking so phenomenal to hear they are already on it...

2 hours ago, Stearmandriver said:

This is spiky controller inputs.  Probably when you touched your quadrant to set flaps 1, you got a throttle input.  It's definitely not anything wrong with autoflight logic or we'd all be seeing it.  I've put this thing through more paces than probably any other simmer out there in the course of testing navdata (almost constant maneuvering flight vs just cruising around) and I've never seen erratic behavior, I guess because I'm lucky enough not to have spiky controls. 

The solution for now is to set dead zones on your control axes.  An update is coming that will lock out controller inputs while autoflight is engaged.

Aha! I have spiking. That is true. Ifly has standard throttle override, forgot about that. Should be an option indeed.

So spike is seen as manual input. I understand, could even explain the issues I had earlier as well.

Tried to fly a tidy holding pattern, went quite well I have to say. But with 250kts it went beyond maneuvering arc, nevertheless will fly holdings with 220-230 kts then.

 

1 hour ago, Piotr007 said:

Aha! I have spiking. That is true. Ifly has standard throttle override, forgot about that. Should be an option indeed.

So spike is seen as manual input. I understand, could even explain the issues I had earlier as well.

Tried to fly a tidy holding pattern, went quite well I have to say. But with 250kts it went beyond maneuvering arc, nevertheless will fly holdings with 220-230 kts then.

 

That arc in a holding pattern isn't really a defined path unless legs are distance defined.  If it was time-defined, you'll see the hold redrawn as you overshoot it to account for where you end up based on winds, speed changes etc. 

Yeah, the control spikes have been getting a lot of people.  It is kind of surprising a dev - especially an experienced and really top-tier one - would let that slip through in a release version, even if it is still "early release".  But at least it's been identified and they've got a fix coming.

4 hours ago, Stearmandriver said:

That arc in a holding pattern isn't really a defined path unless legs are distance defined.  If it was time-defined, you'll see the hold redrawn as you overshoot it to account for where you end up based on winds, speed changes etc. 

Yeah, the control spikes have been getting a lot of people.  It is kind of surprising a dev - especially an experienced and really top-tier one - would let that slip through in a release version, even if it is still "early release".  But at least it's been identified and they've got a fix coming.

Thanks for all of the info Stearmandriver.

But one question left is, we have a WX. Folder. As I point wx.file of simbrief downloader into that file I still cannot uplink wind data in fmc as it says wind dat uplink invalid.

What is the main reason for this? AIRAC version perhaps?

I am using activesky msfs.