surrodox2001

I can't find anything about it online so I asked here.

Basically, I want to set a max thrust for a engine to be lower than its static thrust as I'm toying a concept of a modded 727 with newer engines in the sides and a normal JT8 on the center.

Sounds like more or less the way they did content.pak's for Microsoft Flight

Well, there goes the plans for a drop in compatibility to older sims. sigh

I wonder if MS is going to release a converter for FSX/P3D planes or they'll leave it as is?

I'm seeing a lack of releases of these new planes (A330neo for correction) and some others for use in a FS2004 environment.

(sidenote: It's same with FSX, too)

Why is it happening? Too similar? Lack of interest?

The similarity point could be challenged though as at least 1 type in the 32xneo family (A321XLR has different performance than a A321ceo.)

Do you have all of your gauges installed properly?

If you have FS Panel Studio, there's an easy way to detect with opening the panel.cfg. That will tell you what gauges are you missing.

Tip: Check out this post to see how are the gauges properly placed in the gauges folder.

Perhaps your Windows font is set too large? Do you have it set larger than Small (Default)?

I don't, and I tried to set the size for tooltip font, well it does change the size of the tooltip in windowed mode, it doesn't have an effect in fullscreen mode where the text is still large in higher resolutions.

Specifically, the problem happens when you run FS2004 fullscreen in a higher resolution (>720p?), the tooltips font will change its size and making some tooltips for gauges near the edge of the screen cuts off and make the portion of it unreadable.

In smaller resolutions, this doesn't happen.

Is this a Microsoft feature or can FS be modified to have a fixed/smaller tooltips font in fullscreen and in higher resolutions?

Well, I updated my database and my problem partially disappear.

And a new problem surfaces as I export my flightplans from FSBuild (via autogenerate feature), FSNavigator seems to remove the first waypoint after the departure airport.

Why is this happening?

Sometimes during my use of FSNavigator, I get this message:

"n Waypoints in this flightplan are not found in the scenery.

These waypoints are removed from the flightplan."

Why is this happening when my navdata is updated and database rebuilt?

How to fix it?