Jump to content

Recommended Posts

Posted

This means that a target locked in point track mode say 10 degrees OFF the nose left, the PBIL and thus the in range countdown tick mark are aligned to the right of the nose when both should be tracking one piece and providing steering cues.

 

Maybe its the A-10C shadowing how I understand the mechanism but here is what I do:

 

1- on the ground cold, STP00 = LAT/LONG from Lcrtl+Y when on NAV (INS assumed aligned after 10 minutes on either ALN knobs).

 

2- Call JTAC, get LAT/LONG. Write down dividing seconds given by 60 to get the proper format.

 

3- On NAV master mode, hit STPT, cycle to STP01, punch in Lat/Long after step #2. Along with AGL from TACs 9line.

 

4- Once done, enter AG mode with TGP on and mode CCRP. Laser switch up.

 

5- CCRP mode directs crosshair to intended target and locks it in point track mode.

 

6- on HUD, no visible TGP cue indicators so use the dot on the TGP page to get the nose pointed directly at target.

 

7- PBIL and its countdown does not want to move with the target relative to nose position. Pointing elsewhere. Only relying on distance from many bombing steps before to release in pseudo-CCRP with a misaligned PBIL, then fire laser and lase in hopes the bomb would correct and home in on target.

 

 

Is this a normal behaviour or should it behave differently?

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted

I will try and fly the mission (air start) but for now I have made a youtube video of the problem

 

 

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted

Yeah its a known bug, You can't input coordinates at the moment I don't think.

 

Workaround is to make sure that the aircraft has at least one waypoint in the Mission editor and then select that steerpoint once you get in the jet, you can slew the TGP around from there and that CCRP PBIL will updates as you would expect.

Proud owner of:

PointCTRL VR : Finger Trackers for VR -- Real Simulator : FSSB R3L Force Sensing Stick. -- Deltasim : Force Sensor WH Slew Upgrade -- Mach3Ti Ring : Real Flown Mach 3 SR-71 Titanium, made into an amazing ring.

 

My Fathers Aviation Memoirs: 50 Years of Flying Fun - From Hunter to Spitfire and back again.

Posted
Yeah its a known bug, You can't input coordinates at the moment I don't think.

 

Workaround is to make sure that the aircraft has at least one waypoint in the Mission editor and then select that steerpoint once you get in the jet, you can slew the TGP around from there and that CCRP PBIL will updates as you would expect.

 

No I can input coordinates and the TGP unlocks to them correctly in CCRP. However, the steerpoints coordinates are changed as the TGP tracks objects on the ground. It should be steady on the coordinate as if you're referencing bullseye.

 

My gripe is the PROJECTED BOMB IMPACT LINE. The STEERING LINE for CCRP is not looking with the TGP. The CCRP system is off.

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted

Sigh...

 

Ok let me rephrase my explanation. Currently you can only edit existing steer-points (as placed in mission editor) to new coordinates. If you try and create a new steer-point by inputting new coordinates the CCRP line won’t work. I have a mission setup with one steerpoint. I can edit that to whatever I want or slew my TGP to wherever I want as long as that steerpoint is selected and the CCRP line will work. Yes this will also move the steerpoint around on the HSD, it’s WIP.

Proud owner of:

PointCTRL VR : Finger Trackers for VR -- Real Simulator : FSSB R3L Force Sensing Stick. -- Deltasim : Force Sensor WH Slew Upgrade -- Mach3Ti Ring : Real Flown Mach 3 SR-71 Titanium, made into an amazing ring.

 

My Fathers Aviation Memoirs: 50 Years of Flying Fun - From Hunter to Spitfire and back again.

  • 3 weeks later...
Posted
Sigh...

 

Ok let me rephrase my explanation. Currently you can only edit existing steer-points (as placed in mission editor) to new coordinates. If you try and create a new steer-point by inputting new coordinates the CCRP line won’t work. I have a mission setup with one steerpoint. I can edit that to whatever I want or slew my TGP to wherever I want as long as that steerpoint is selected and the CCRP line will work. Yes this will also move the steerpoint around on the HSD, it’s WIP.

 

Gotcha thanks. It makes sense now.

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...