So...what if Bulls is Stpt 31.

[Carbon715]

Got a question. Lately I been hopping into the TTI servers as its the holidays etc. and ran into a conundrum with bulls that hasn't been a problem until now. So, in brief, the bullseye is Stpt 31 and that's where the ME bulls is too. There's like 31+ stpts already input so when bullseye is enabled, it defaults to 25...and cannot be changed to 31 regardless anyway. What's the work around other than, it seems, writing down stpt 31's coordinates and inputting them in stpt 25 or less?

[Frederf]

Currently if you have a nav point 25 then BE will appear at that nav point 25 and not in the mission BE position. Apparently you can only set the BE to be represented by points 1-25 (some F-16 1-25, some 1-99). Of course certain number ranges are a bad idea because they could be overwritten at any time which would move BE unexpectedly.

Really the F-16 shouldn't be assigned flight plan steerpoints outside of 1-25 as that's the maximum size of the connected dots. Those are the only ones that can be DTC initialized. 26+ is for marks, lines, PPTs, DL, weapons, etc. Of course you can type stuff in UFC outside that range but what a lot of work and you can get odd behaviors.

The mission maker should probably limit the flight plan to 24-25 waypoints and/or DCS should only put the first 24-25 points from the flight plan in slots 1 through 24-25.

[Carbon715]

Yeah that's what I was figuring. Looks like I'm going to have to manually overwrite a steerpoint in a server that has more than 25 with the corridinates of miz bullseye to get accurate readouts etc with other players. Was curious if I missed something as in Wags bullseye video he stated 1-99 however that's not currently the case. Thank you.