10 hours ago, mac44 said:

found the option but what do you mean elevator authority down to 50%? (my options default to -2 or +2(default is 0)?

Sorry, I meant set it 50% of the way between it's current (dead centre) position, and the far left of the scale. 👍

11 hours ago, Alvega said:

Lol, of course I pressed VNAV in the AP. I believe the problem is with the default Asobo G3000 the plane uses (as Matt from WT told me), and not with the plane itself. Let's see what comes up tomorrow,

That seems contradictory.  There is a default Asobo G3000 in MSFS and then a separate WT G3000 mod.  The Hjet is using the WT G3000 (mod) integrated into the Hjet model itself. That is significantly improved over the default Asobo G3000.  And there is no need to load the separate WT G3000 mod when flying the Hjet, and there is no conflict in the Hjet if that separate WT G3000 mod is active in the Community folder.  That straight from Matt, possibly earlier in this topic.  There is a significant difference between the "default" Asobo G3000 and the WT G3000 that is in the Hjet, and Marwan has with cooperation from WT done some enhancements to the WT G3000 in the Hjet.

Matt? If you are browsing this topic would you please comment on this? 

Edited June 2, 20224 yr by fppilot

18 minutes ago, fppilot said:

That seems contradictory.  There is a default Asobo G3000 in MSFS and then a separate WT G3000 mod.  The Hjet is using the WT G3000 (mod) integrated into the Hjet model itself. That is significantly improved over the default Asobo G3000.  And there is no need to load the separate WT G3000 mod when flying the Hjet, and there is no conflict in the Hjet if that separate WT G3000 mod is active in the Community folder.  That straight from Matt, possibly earlier in this topic.  There is a significant difference between the "default" Asobo G3000 and the WT G3000 that is in the Hjet, and Marwan has with cooperation from WT done some enhancements to the WT G3000 in the Hjet.

Matt? If you are browsing this topic would you please comment on this? 

I know, but from what Matt said I got the impression even the plane's modified G3000 still uses default AP and flighplanning. I think that part was not modified. But I may be wrong.

This is what he said when I asked if there were visual approaches in the G3000 (because I couldn't find it in the plane's G3000):

Quote

The G3000 mods uses totally stock nav, flight planning, and AP
The refresh, coming later this year, will use the next-gen nav stuff

 

Edited June 2, 20224 yr by Alvega

18 hours ago, JYW said:

For those not enjoying the over-sensitive pitch controls™ , when selecting the plane in MSFS, in the screen where you enter your custom registration etc, there are sliders at the bottom (wear and tear, etc).   I found that pulling the elevator authority slider down to 50% helps this plane feel a little more stable in the pitch axis.   This method also prevents you having to make changes to your actual controller sensitivies (which would affect all planes), and the elevator authority slider on that page resets after every plane / flight.

Agree, most of this is just getting your controller to feel right.  I have to adjust the sensitivity on every aircraft.  For the H-Jet, I copied my Honeycomb profile from the WT CJ4.  I have elevator at -65%, aileron at 0% and had zero issues on my quick test flight with pitch/roll.  The Reactivity slider is good too, I have started to use that as well so will probably reduce that and bring up the sensitivity a bit on the elevator.  I have a profile for every controller for every aircraft, I would guess most are using a default profile for everything which isn't going to work very well...

Edited June 2, 20224 yr by Flic1

30 minutes ago, Alvega said:

I believe the problem is with the default Asobo G3000 the plane uses

I got the impression even the plane's modified G3000 still uses default AP and flighplanning.

OK. Now I understand what you originally intended.  If you had been more specific with the first comment, as you have with the second, then as such I would not have commented.  I understand that WT is working on the G3000 AP functions, much as they did with the G1000nxi, but it sounds like it will be some months out.  Disappointed in that....

In fact, if I'm not completely mistaken, Marwan took the G3000 modified by WT as a base, forked that, and programmed his own VNAV mode. That is, the HJet should have a VNAV mode that ist better than the one implemented in the WT G3000(mod), which is the same as the one in the Asobo G3000.

Isn't there supposed to be an update today?

5 hours ago, Flic1 said:

Agree, most of this is just getting your controller to feel right.  I have to adjust the sensitivity on every aircraft.  For the H-Jet, I copied my Honeycomb profile from the WT CJ4.  I have elevator at -65%, aileron at 0% and had zero issues on my quick test flight with pitch/roll.  The Reactivity slider is good too, I have started to use that as well so will probably reduce that and bring up the sensitivity a bit on the elevator.  I have a profile for every controller for every aircraft, I would guess most are using a default profile for everything which isn't going to work very well...

Thanks for the tip. I have not had to touch my Honeycomb profile since day one. I will make an exception for the HJet. Love this thing!

Update: -65 works well. Thanks.

Edited June 2, 20224 yr by DJJose

Does anyone have those spikes on Main thread/CoherentGTUIThread and Manipulators with H-Jet?

I have this issue only with H-jet and not with any other aircraft

thanks