Not sure how you would define better? There could be a conflict between the limits set in WTG300 and the limits Dakfly sets in his mod, removing the WT G3000 limits could defer to Dakfly’s…
But I’m just I pilot, I don’t work under the hood, I just fly the plane, so I’ll let the engineers work it out lol.
I think the cruise and climb N1 limits are new to the latest version.
I would define better as: WT N1 limits remain in place and the autothrottle problem is fixed elsewhere.
Perhaps Dakfly could comment on whether his mod might have some conflict with these N1 limits?
If you read his release notes he discusses setting N1 limits. His appear to me more complex than WT’s execution. But again, what do I know, I’m just a fake pilot. I’m not going to argue with someone (WT) who is clearly smarter than me, especially when it fixes the problem.
I’d still like to hear directly from Dakfly. I’m a software engineer and I feel there is an important distinction between a “fix” and a workaround. Just getting things working is not always the best solution if it doesn’t fix the real problem. If that is indeed the correct solution, then I would expect WT to issue another patch updating their mod to work with Dakfly’s mod, like they just did.
That’s fair. From my perspective a “fix” vs. a “workaround” is a distinction without a difference, but I am not a software engineer. Just someone who has had to fix things. Something about more than one way to skin a cat…
Anyways I wasn’t trying to get argumentative. Happy flying.
95% for climb seems to be ok, maybe only the 85% for cruise was too low. I’ll try to fidle the numbers a bit tonight
I’m testing 95 and 95 right now. Definitely seems to capture and hold speed better at cruise for me. But as you know from our conversation on the Discord I wasn’t really experiencing the issue. 
I think it wasn’t showing for me before because I was on a short flight at a lower weight than usual, so I didn’t need more than 85% of available N1.
But the thing was that all along climb it was full power at .78, then when it switched from flc to cruise it started to power back and was not able to keep speed at all
I flew a short flight at FL430 the other day and didn’t notice a problem. But I turned on AT after takeoff. I don’t see why turning it on on the ground should matter, since it’s a cruise max N1 we’re talking about.
For those that have made the “fix” What mod file are you referring to / adjusting? If there is a new setting in a config file that limits the cruise N1 max, then 85% would be too low esp. when at high aircraft weight or at or near max altitude. Just would be nice to know what file this value is being configured / changed so I can explore the issue.
It’s a file in the Working Title G3000 (v0.5.1) Mod folder:
workingtitle-g3000 > html_ui > WTg3000.cfg
Line 49
Line 50
I’ve done two flights now at 0.95 and 0.95 and it’s flying great. Thanks for your work as always.
My hypothesis is that limit (in the WT config) is limiting whatever your limit is set to in your mod config files, as it doesn’t appear to affect the stock Longitude (per feedback in the WT discord).
Okay - understood. So I’m not sure what it’s modifying in the Longitude mod - that makes it harder to adjust on my side. When I have a chance, I’ll download the latest WT mod and see if I can’t figure it out.
+1
Highest n1 i got on cruise was 91% with 95%/95%
I’ll try tonight 95%/91%
Edit: 95/95 is the way to go
What I’m curious about is that these two settings are for max N1 in climb mode and max N1 in cruise mode. AFAIK the Longitude does not have a climb “mode” or cruise “mode” like the WT CJ4. Or does it?
Ooohhhh! Shiny!!
did some test and so far it works perfectly
highest n1, with no live weather, @FL450 was 89% (with AT at 93% lever position, with no difference at 100%)
highest n1 with live weather I got was 91%, but most of the time its 90% (dont know if it can go at 92% with specific weather though)
so I would say
for climb 0.95 is perfect
for cruise, anything between 0.91 & 1
stock 0.85 for cruise is way too low, as it needs about 88% to keep speed at max weight
*dont think Working Title guys are gonna tweak their numbers, as their mod is made for the stock Longitude.
maybe @Dakfly0219 leave a note on your mod instructions to put those tweaks in the G3000 mod files for those that use it?
** I havent made a lot of tests with different scenarios, so maybe the cruise % would need more tweakings
But imho 0.91 is bare minimum
Edit: consensus is now 95/95
They don’t have to tweak their numbers. Those values are set by aircraft type. They already modified their code to distinguish between the stock Longitude and the Dakfly mod since they use a different name for type. Easy enough to add a line of code to have different N1 values specifically for the Dakfly mod. Just have to ask them to.
