Target steerpoint moves after assigning
Does this happen to others? I am in the recon screen of the planner, I assign steerpoint 7 as a target steerpoint, and the steerpoint moves greatly after entering 3D world…
I count 13 steerpoints in your flight plan. This is fine of course (less than 24). I don’t know which one exactly is #7.
When a steerpoint is made precision matching a recon object the DTC file/cartridge is written that position. But also the flight plan will automatically write 1-24 (up to) based on the flight plan shown on the map. The case here is both flight plan and precision target both want to write the coordinates for steerpoint 7. This is normally OK if correct steps are made to overwrite the steerpoint with the precision values and to ensure this data is loaded later in the airplane.
I will make some tests to see exactly when certain steerpoint data is written where and under what condition (ramp, taxi, takeoff).
Step 1: Before Falcon, Callsign.ini
target_1=0.000000, 0.000000, 0.000000, -1, Not set
Now I commit to ramp having never saved the flight plan. CS.ini shows 0.0… for all flight plan points. But I look through DEST page and without loading anything I see steer 1-9 coordinates loaded directly from 2D map never saved to DTC (callsign, not sure about TE.ini). So we see there is a Falcon method of populating airplane software that is entirely separate from the DTC.
OK, try again same TE but this time we will save DTC, drag around steerpoint circles in 2D and compare results.
Now I press the “Save DTC” button with normal flight plan. Callsign.ini is saved as this flight plan. (I can see in Notepad). OK now I set steerpoint 2 as some recon target but I don’t hit save button. The Callsign.ini isn’t change. Now I hit save button, file is changed.
S7 is the one near the SA2 circles. This is a campaign generated mission. I recon the target, assign S7 to the actual target I want to hit, perhaps a particular building. Once done, I save the DTC then go to the 3D world to see as the attachment.
I’ve also seen it when I don’t assign targets. The target steerpoint jumps wildly out of position. Something isn’t right.
I just wanted to renew this thread as I have noticed something strange with steerpoints over the last few weeks. It seems new steerpoints are being added into the flightplan when transitioning from 2D to 3D. Sometimes these steerpoints are way out, adding 50 to 100 track miles to the plan. I have added a couple of screenshots to illustrate: (I hope they upload correctly)
The first image shows the stock standard BARCAP flight plan which is not edited in anyway. I then save the DTC (no target steerpoints assigned) then enter the 3D world to Taxi (not going through ramp start). The second image shows the DTC uploaded flight plan in the jet (HSD) with some strange steerpoints added which does not resemble the original BARCAP plan. I am not using WDP, I have tried “clearing” the DTC and reloading then resaving, however I get the same result. Could my Callsign.ini file be corrupt? Running BMS 4.33 on W7 home premium 64 Bit.
I think Malc is on to something similar here:
Further investigation into this shows I always have the same 2 targets as steerpoints (3 and 6) in my DTC (callsign.ini) no matter what mission. So these 2 steerpoints are placed into the flightplan. I have tried overwriting the .ini file with an older one, and I have even used notepad to manually zero all steepoints, save (windows explorer), then reload DTC in game. The program still seems to be reading these 2 points from somewhere and overwriting my callsign.ini. I am doing an offline Tiger Spirit campaign in KTO theatre. Does anyone have any suggestions please? Below I have pasted the first few lines of the callsign.ini file.
target_0=0.000000, 0.000000, 0.000000, -1, Not set
target_1=0.000000, 0.000000, 0.000000, -1, Not set
target_2=0.000000, 0.000000, 0.000000, -1, Not set
target_3=1882013.375000, 1465182.125000, -2131.910645, -1, 5th Tank Battalion ZSU23-4
target_4=0.000000, 0.000000, 0.000000, -1, Not set
target_5=0.000000, 0.000000, 0.000000, -1, Not set
target_6=1992467.875000, 952334.187500, -174.000000, -1, 61st Air Defense Battalion Spoon Rest
target_7=0.000000, 0.000000, 0.000000, -1, Not set
target_8=0.000000, 0.000000, 0.000000, -1, Not set
target_9=0.000000, 0.000000, 0.000000, -1, Not set
Mark sure the callsign ini file is not set to read only or ready to archive or anything weird. Presumably you set the values manually to zero, saved, and then reopened immediately in notepad to check they are truly zero.
Also there are 2 DTC files, a callsign ini and a TE ini. The TE ini is also a source of DTC data and now in 4.33 also applies to the campaign as well. Consider looking at all relevant ini files in the campaign save directory to ensure that there isn’t some data being auto-loaded by the “TE” (campaign) .ini DTC file into memory as these recon precision targets and then inadvertently saved when you save callsign ini. Check the 4th and 6th target steerpoints in the DTC dialog in the TARGETS section at each stage of a normal flight.
Thanks Frederf, I just worked it out. You have to “Clear All” STPTs and Targets in the Recon page. It seems if you don’t, the target data will persist every time you save your DTC and load into the jet. Been bugging me for days.
Cursor Zero is your friend. Use it after use of your sensors as all STP are moved accordingly and should be reset after use.
So before attacking your stp 7 target make sure it is in place by pressing cursor zero first.
If you want to get rid of olda data in your ini start up weapon delivery program and you will find and erase with ease.