Hello,

The more way-points I add in my flight-plan, the less stable the video is :

No problem at all if I only use a departure and an arrival airport.

Flight-plan with departure, arrival + (1 to 20 way-points) : no stuttering. Stable video.

Flight-plan with departure, arrival + (25 to 50 way-points) : some stutterings, not really stable video from time to time ...

Flight-plan with departure, arrival + (90 way-points) : many stutterings, sometimes, 1" to 3 " picture freeze

Of course, I use the same departure time and weather conditions, I just add or remove way-points.

I fly in 1 to 3 circles around home, about 4 kms between each way-point.
I use little navmap to generate the flight-plan.

Using auto pilot or not gives same results. Removing VFR map does not help.
Using developer mode does not show more or less Ram usage.
No other app is running when using Fs 2020.

I'm probably doing something wrong, but what ?
Another strange thing : way-points names are displayed from departure to number 18, while flying. They are not displayed after N° 18-20 to the end ... only arrival airport is displayed from those points.

I9 5500k 32 gb ram, Rtx 2060 Super, Nvme disks (system + Fs 2020)
 

Edited November 12, 20205 yr by ctdlg

Using Fs 2020 flightplan, adding 45 Waypoints : no video problem. No stuttering, framerate is stable.

This means Little Navmap could contain informations that loads Fs 2020 a lot if you use many waypoints.

Difference between a ftl file and a pln file is huge.

I will fly VFR manually with little navmap displaying my 90 waypoints using  only home airport as departure and arrival points !

Edited November 12, 20205 yr by ctdlg

Above solution does work, but Auto Pilot+ flight plan is needed for my video controls + recording.
And I need displaying waypoint names -> flight plan is really needed for the video I want to get !

So,

I did change screen resolution from 5120x 1440 to 1920x1080 : same problem with many user waypoints. Back to 5120x 1440 !
I saved the flight using flt extension, instead of pln extension, reloaded the flt flight -> same problem.

I cannot use many waypoints without stutters, the limit is around 20 waypoints !
May be my waypoints are too close to each other ..

I will try a 50 user waypoints  flight using 10-15 kms between each of them ...

Problem found : I can add as many waypoints as I want using Little Navmap IF and only IF these waypoints are not too close together.
I do not know the minimum distance between each user waypoint.

This might happen to your flight plan if you want to visit your surroundings !
This information is not found anywhere !

Why in the world so many waypoints?  What is the length of the entire flight in those cases?

Edited November 12, 20205 yr by fppilot

You will find more than 100 villages around my home.
Adding them to an optimized flight plan ( the shortest possible ) displays their names while auto pilot flies and while video is recorded on computer.
As the resulting video is too long, video editing allows me to speed up (shorten video length) (speed x 4 is a good choice for me) and also remove some sequences.
Last step is adding markers : user can jump where he wants around home.
Final video will show my entire country in less than 15 minutes !
Some people are living in those 107 villages, this video might be interesting for some of them.

I do use Google Earth Studio and NOT Fs 2020 in large cities, videos are better and look more realistic, we can set camera locations, speed, pan, and much more ... very accurately.

Edited November 13, 20205 yr by ctdlg

10 hours ago, ctdlg said:

Problem found : I can add as many waypoints as I want using Little Navmap IF and only IF these waypoints are not too close together.
I do not know the minimum distance between each user waypoint.

 

1 hour ago, ctdlg said:

You will find more than 100 villages around my home.
Adding them to an optimized flight plan ( the shortest possible ) displays their names while auto pilot flies and while video is recorded on computer.
As the resulting video is too long, video editing allows me to speed up (shorten video length) (speed x 4 is a good choice for me) and also remove some sequences.
Last step is adding markers : user can jump where he wants around home.
Final video will show my entire country in less than 15 minutes !

I very much doubt that such a scenario was envisaged by the MFS designers, programmers or testers. Although it's a pain it might be worth raising this on Zendesk together with your solution and the minimum waypoint distance you achieved between your existing waypoints to give them a start value. They may well do nothing with this information but hopefully at some point they will look at the relevant code to determine what is causing the issue and resolve it. Realistically though, this is unlikely a priority as there are so many other issues higher up the list.