On the contrary, it would be quite desirable! There is no difference between an obstacle being outside of a straight track and outside of a turn. If you set up SD to compute the MSA based on obstacles a certain distance from your track, it doesn't matter if you're on a straight line or in a turn. If anything, it is more critical in the turn since you don't have any course guidance in the turn itself.

If you have a long leg and there is a significant obstacle near one end which affects the whole leg, you can insert intermediate waypoints. Again no difference between turns and straight tracks.

Also, from a regulatory point of view, there is a minimum altitude for night VFR which is based on obstacles a certain distance away. This distance apply equally in turns as it does in when flying in a straight line.

Tim,

I would like to discuss again the calculation of the MSA. Please see attached screenshot.
‌
The MSA for the first route section is given with 800 ft, although the obstacle (568 ft) is almost directly on the track.
I would expect the MSA to read 1.600 ft.

S‌ettings for safety margins are 500 ft / 5 NM (Terrain) and 1.000 ft / 5 NM (Obstacles).

P‌roposal: Virtually extend the track line by xx NMs to include the obstacles within the turn area for MSA calculation.
‌ ‌

‌‌
R‌egards
Jan

You are welcome to post a thread regarding this change in our Suggestions forum. I believe that we had at least one complaint in the past when we allowed an obstacle that the user deliberately planned to turn before, to greatly influence the MSA of both the before and after leg. I can see how you might want it to, but our behaviour has been consistent for quite a long time now.