Red_Dragon Posted February 11 Posted February 11 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.
razo+r Posted February 11 Posted February 11 (edited) You need to give it a name in the comment field, like PP# (# being the number) RP# or I think WP#. Simply placing down a navigation target point is not enough. It will then populate your DST waypoints accordingly. So if you place down RP's, they will appear as waypoint 36-39 (I think, I am not 100% sure anymore. Consult the manual/quick guide to see which ones populate what DST waypoints), WP as their number and PP as 31-35 or something. Edited February 11 by razo+r
Red_Dragon Posted February 11 Author Posted February 11 (edited) 49 минут назад, razo+r сказал: You need to give it a name in the comment field, like PP# (# being the number) RP# or I think WP#. Simply placing down a navigation target point is not enough. It will then populate your DST waypoints accordingly. So if you place down RP's, they will appear as waypoint 36-39 (I think, I am not 100% sure anymore. Consult the manual/quick guide to see which ones populate what DST waypoints), WP as their number and PP as 31-35 or something. 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 Edited February 11 by Red_Dragon
razo+r Posted February 11 Posted February 11 (edited) 14 minutes ago, Red_Dragon said: 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. Its basically the same, just one method is for more singleplayer and the other is better for multiplayer. But you can set PP# any time, either in the editor if you are there, or via the F10 map if you didn't or couldn't place any in the editor. 14 minutes ago, Red_Dragon said: 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 and set, but navig.targ.point is just one non-linked directly with any rout point ist't it? It depends on what you name it. If you name it WPT#, it should appear like any normal waypoint (at least in multiplayer). If you name them RP# or PP#, they will appear as "markpoints" that are not connected to your route. 14 minutes ago, Red_Dragon said: Doesn't this point work properly as I set it via editor when I build my mission? It does work, if you give it a name. 14 minutes ago, Red_Dragon said: 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 have never tried it that way so I cannot comment on that. Edited February 11 by razo+r
Red_Dragon Posted February 11 Author Posted February 11 (edited) 22 минуты назад, razo+r сказал: It does work, if you give it a name. 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.. Edited February 11 by Red_Dragon
razo+r Posted February 11 Posted February 11 5 minutes ago, Red_Dragon said: 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.. That is not the name, that is just the number of navigation target points you have placed down. The name for that point goes into the comment field below.
Red_Dragon Posted February 11 Author Posted February 11 (edited) And I don't know if this tool can work or broken.. 3 минуты назад, razo+r сказал: That is not the name, that is just the number of navigation target points you have placed down. The name for that point goes into the comment field below. Yes this tool can work, but we have tool in editor for operation points and I'm pretty sure I can see it before Edited February 11 by Red_Dragon
razo+r Posted February 11 Posted February 11 6 minutes ago, Red_Dragon said: but we have tool in editor for operation points and I'm pretty sure I can see it before Sorry, what exactly do you mean by that?
Red_Dragon Posted February 11 Author Posted February 11 (edited) 27 минут назад, razo+r сказал: Sorry, what exactly do you mean by that? 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 Edited February 11 by Red_Dragon
razo+r Posted February 11 Posted February 11 (edited) Are you 100% sure that is the Navigation Target Point? To me it just looks like you are designating your waypoint 1 as a SPI. I mean, the waypoint is labeled as "1" on the HSD, you have waypoint 1 selected on your UFC and that Navigation Target Point that is supposed to be bottom right of waypoint 1 isn't shown on the HSD. In both pictures the point is exactly 18.7 miles away while there should be a difference in distance between wpt 1 and NTPoint. They are also at the same bearing from you but as you show in the picture, the NTPoint is more to the east than WTP 1. So I don't think you are actually targeting NTPoint 1, but your ordinary WPT 1. It is weird though that it jumps to ground level. You did not press any other button, right? Otherwise I guess "auto" mode automatically puts the point at ground level. I will try it out once I have the opportunity to see myself what is going on. But so far, you just seem to target your normal waypoint 1, while the NTPoint 1 you added does not exist in your flight plan because you did not give it a name, so the point is not recognised and not added. Edited February 11 by razo+r
Red_Dragon Posted February 12 Author Posted February 12 (edited) 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 19 часов назад, razo+r сказал: Probably you're right, what if this way just doesn't work anymore.. Edited February 12 by Red_Dragon
Red_Dragon Posted February 12 Author Posted February 12 (edited) And turning on A-G seems just turning WP into something like markpoint as you thought Edited February 12 by Red_Dragon
Red_Dragon Posted February 12 Author Posted February 12 UPD But even with comments (like PP1) I still don't see this point. Will try to find out what is wrong
Red_Dragon Posted February 12 Author Posted February 12 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.
tekwoj Posted February 12 Posted February 12 (edited) You have at least 2 types of points that can be detached from navigation PP and RP. Just from your navigation target point the module is not able to deduce which one you want so you have to give it a correct name in the comment. If you name it wrong that's your problem. Edited February 12 by tekwoj
Red_Dragon Posted February 12 Author Posted February 12 (edited) 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. Edited February 12 by Red_Dragon
Red_Dragon Posted February 12 Author Posted February 12 (edited) 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 Edited February 16 by Red_Dragon
tekwoj Posted February 13 Posted February 13 FYI nullhttps://chucksguides.com/aircraft/dcs/jf-17/#[433,"XYZ",-8e-06,540,1] You have a table here with waypoints explained and what they are used for.
Red_Dragon Posted February 13 Author Posted February 13 (edited) 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. Edited February 17 by Red_Dragon
Napillo Posted February 14 Posted February 14 4 hours ago, Red_Dragon said: appears in a different location after the mission is launched By default, the F10 menu puts the point on the ground - in the editor, it might put it on the ground, but it'll probably be in the air - you need to check the altitude.
Red_Dragon Posted February 15 Author Posted February 15 В 14.02.2025 в 04:48, Napillo сказал: By default, the F10 menu puts the point on the ground - in the editor, it might put it on the ground, but it'll probably be in the air - you need to check the altitude. 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.
razo+r Posted February 15 Posted February 15 (edited) 3 hours ago, Red_Dragon said: 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. Waypoint 40 is not the PP waypoint, it's your SPI. You can easily check this. For example, go to AG mode and open the DST page. You'll see a SPI will be generated and Waypoint 40 is populated. Now move your cursor around and designate that point. Notice how the coordinates for waypoint 40 change. PP waypoints will be number 36 to 39. Edited February 15 by razo+r
razo+r Posted February 15 Posted February 15 On 2/12/2025 at 10:54 PM, Red_Dragon said: 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). 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 On 2/13/2025 at 10:08 PM, Red_Dragon said: 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. I don't see the same as you do. If I place down a Navigation Target Point with the comment field blank, there is no PP, no RP, no SPI and no waypoint generated. If I enter "PP1" in the comment field, it correctly enters that NTPoint as a PP at position 36 in the DST page. I think at this point it's a good idea if you provide a short track or at least the mission so we can see your setup.
razo+r Posted February 15 Posted February 15 (edited) On 2/12/2025 at 10:54 PM, Red_Dragon said: 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). 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 (Sorry for the 3rd quotation in such a short time. I've just gotten around now to try it) If you place down a "INU FIX POINT", it will populate position 41 and onwards in your DST page. Summary: In the editor, you have two points to add: "Navigation Target Point" and "INU FIX POINT". "Navigation Target Point" requires you to input a name into the comment field. If you don't add a name, like PP1, RP1 or WPT1, it will NOT populate any position on your DST page. WPT (though may conflict with already set waypoints) should populate DST position 1 to 30. PP should populate DST position 36 to 39. RP should populate DST position 31-35. "INU FIX POINT" has no comment field to enter any name. Placing one down will populate DST page 41 and onwards. DST position 40 is reserved for your SPI, created by your onboard sensors and can constantly change depending on what you are currently targeting. Edited February 15 by razo+r
Red_Dragon Posted February 15 Author Posted February 15 26 минут назад, razo+r сказал: (Sorry for the 3rd quotation in such a short time. I've just gotten around now to try it) If you place down a "INU FIX POINT", it will populate position 41 and onwards in your DST page. Summary: In the editor, you have two points to add: "Navigation Target Point" and "INU FIX POINT". "Navigation Target Point" requires you to input a name into the comment field. If you don't add a name, like PP1, RP1 or WPT1, it will NOT populate any position on your DST page. WPT (though may conflict with already set waypoints) should populate DST position 1 to 30. PP should populate DST position 36 to 39. RP should populate DST position 31-35. "INU FIX POINT" has no comment field to enter any name. Placing one down will populate DST page 41 and onwards. DST position 40 is reserved for your SPI, created by your onboard sensors and can constantly change depending on what you are currently targeting. 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.
Recommended Posts