Red_Dragon

Thank you! It looks like you right. At some point, this was added to the editor, because at first everything worked fine in the list of points. I should have deleted the extra line after the PP, but obviously I missed it or forgot

Your mission works perfectly. I changed USA to USSA, from spawn in flight to hot start on the field.. everything is fine. But my mission (8 WP and 1 PP) don't wark properly. When I spawned on the field I saw WP but didn't see my PP1 in the destination list. WP_JF17.miz I checked dest.list after I spawned and after DTC updating on the field WP_2_NO_PP_.trk

In my post above you can see wrong coordinates. Note that 36 was empty. No others positions for PP or RP were set except 40 that time. And as I said usually PP set as 36 but sometimes i see it as 40 or even 41 I removed all mods I was able find. Next time I'll save track. I wanted to save track today but just forgot did it after flights..

Its great if you have stable results. But sadly I don't have. In numerous test I have quite different results. In the same condition Nav.Targ.Point can set in 36 position even without comments in their window but then when I started again it didn't set at all. When I named Nav.Targ.point as PP1 it was able set as 36 and as 40 another time to my surprise. More over when I have tried it today and when I turned to A-G mod, I saw first my rout nav.point as a target point (but not in the air, just on the ground) insted of PP1 and after 5 mins of flight that point changed to right PP1 with right localisation without any addition actions from me.

MT is still not working properly. A few years ago, I got rid of the old computer and bought a new one with 3080, 32 GB to match the DCS. DCS was running great until MT appeared. You know, endless stutters. I've sent tons of DCS logs. No result. Then I bought a new computer with 4080 and 64 GB RAM and others stuff.. DCS ran great again. A week or two ago, the stutters reappeared. I deleted all the mods I could find, did a restore, and the entire list such rituals. But I can't play anyway. Often, after a reboot, the DCS works fine again. But its too randomly. If this computer was working perfectly five minutes ago, why the hell isn't it working a moment later with the same tasks? I will no longer send endless logs and listen to nonsense about what I should delete and what settings to use et cetera.. My computer has SUFFICIENT configuration for DCS. Everything is simple for me. No game, no money. PS Please do not write about magical actions with cores, links to wonderful videos with examples of getting rid of all problems, I'm just not going to waste any more time on settings instead of flights. Understand that these are not words of resentment, they are just facts, if you want a reminder of the persistence of the problem. PS 2 By the way, I do not exclude that the problems may be related to the Windows update (I have the 11th on board). But in any case, the MT path is ED's choice.

It's not just about alt. The parameters set in the editor may be completely mistakenly transmitted to the aircraft. For example, here are the set coordinates for PP1. In the cockpit, I already see OTHER coordinates for PP1. And after I updated the cartridge data while in the cockpit at the airfield, the PP1 disappeared altogether. Although the entire flight route remained exactly the same. It is not worth mentioning that the test with inserting of parameters for PP1 by the F10 map, when I was already in the cockpit at the airfield, showed perfect results on the contrary. I'm more and more inclined to consider this a bug or a broken data transmission mechanism.

Thanks for help, but I am aware of this... That's where I started learning this module, of course. After several tests, I discovered a new problem. The coordinates are transmitted incorrectly. For example, the PP1 set in the editor can appears in a different location after the mission is launched (not always). I can't imagine why this is happening. I think I'm tired of it now (endless problems in DCS) and I will set the PP and RP on the F10 map as I did before.

UPD 2 I finally figured out how it works. It just wasn't enough to just turn on the A-G mode. However, it is not necessary to name a point in editor (but of cource its not the case with F10 map). (UPD - in later my tests it didn't wark without named it PP or RP) Point #1 without a name is set to 36. If you name the point PP1, it becomes 41. In flight, you can press the DST button and select 36 or 39, or of course you can immediately dial these numbers on the UFCP and then you see the your point

I named it as I did it on F10 map (PP1), I did it with and without quotation marks, but I don't see point when I fly. And actually you can see possibility for adding point of both types.. although in any case, my point is called PP1. It looks like nobody set points by using editor Maybe I should additionally turn on something on the left MFD (weapon) when I turn on the A-G mode, I have to try it.

And in any case, a lot remains unclear. On the F10 map, I can name a point any way I want. But it would be stupid to name this point in the editor, for example, as in FPA or FPB, it cannot be related to the route. But the points that can be named through the F10 map should obviously be universal, unlike what I see in the editor, because the waypoints are set in another tab of the editor and they do not require additional names.

UPD But even with comments (like PP1) I still don't see this point. Will try to find out what is wrong

And turning on A-G seems just turning WP into something like markpoint as you thought

Now I tried to do the same thing without waypoints at all. I switched to A-G At first, it seemed to me that the navigation marker of the target appeared in the right place. But then it turned out that there was nothing at all in this place. null Probably you're right, what if this way just doesn't work anymore..

I just managed to make it work again. I have set up a Navigate Target Point (not PP or RP points) in the editor as you can see. It's just point #1. null Now I'm flying in navigation mode. You can see routine waypoint on 2000 m alt. null Then I turn on A-G mod and you can see 'diamant' or rhomb on the deck. There is the mark below the waypoint. This is my NTPoint. But I dont know why it doesn't work always

And I don't know if this tool can work or broken.. Yes this tool can work, but we have tool in editor for operation points and I'm pretty sure I can see it before

Yet all of it a bit unclear for me, because when I set this point from editor it at the same time set a name for the point, so the point already named automatically. In my case it is #1 as you can see And this tool added by Jeff's devs themselves..

I will try it, but i'm still in doubt. I use PP# usually when I open F10 map while I spawned on the field and get ready for flight (usually in multiplayer mod). But now I set NPPoint via editor before I started my offline mission, before spawn. And I thought that this navig.target point more like markpoint (afaik we don't need gives names for markpoints) , I mean this point isn't part of sequences.. you know PP1, then PP2 et set., but navig.targ.point is just one non-linked directly with any rout point ist't it? Doesn't this point work properly as I set it via editor when I build my mission? And second thing, before (some DCS updates ago) I was able to see this point when turn on A-G, but for some reason when I did few passes over target this navigate target point changed to current waypoint. Now I can't see it anyway

I set nav.targ.point in editor. And when I turn on A-G mod I only see my waypoint on my current altitude, not NTPoint (as it called in editor) on the ground or at least below my current alt. First of all is this bug or its just a problem on my side? And if it is a problem I can't understand what I did wrongly.

Это Ка 50 реликт то? Ну вы даете , блин

And i think you already have tried to delete fxo file in save game

You can try set 1.5 or 2.0. This can help you. Also the problem can be in you monitor. Different monitors with the same setting gives different results. And also ability to see short distance contacts depends on your anti aliasing options. I heard that for contacts visibility old antialaising better then dlss, and dlss with medium performance option can be better then dlaa , but image with dlaa far better imho. Also you can try 1080 with dlaa

Thanks, although I still haven't figured out how to see the model from the outside, I still see what I did wrongly

I can't open models in the model viewer. When I try to open for example Mi 8 and then all I see is null Nothing like loading, just empty window of load model.. I can't even imagine what is wrong

Yes I agree with you, and also I can use V joy for reduction of axis response for non VKB \ VIRPIL joys, but I just would like to have more simple way . Honestly I wander why we can't have such option as part of core DCS Imagine, we have duplication of all buttons as an easy gaming option, but we do not have an axis restriction for those who fly with a short joystick without extension

In fact, limiting the axis response won't make refueling too easy, it's certainly not a cheat. I have several joysticks, and on one of them I use a similar function to limit the axis response. But there are too few buttons on this joy for an airplane like Jeff)). Take my word for it, if you don't know how to refuel, the axis limiting won't help you. It's just that this function removes spurious movements, brings you closer to the real movements of the stick in a real airplane, if you don't have an extension for the joystick.