Is your JF-17 Onspeed Caret Functioning ?

[glen.a.williamson]

In my JF-17 installation, the caret which is meant to indicate your desired air speed at a given waypoint does not seem to be functioning.

On my rig, this caret seems to be stuck at the top of its range, and never seems to move.  Does your desired airspeed caret seem to be functioning correctly for you ?

[ReyCandy]

My brackets move, although the truth is that I had never noticed them. Yours stay fixed?

 

I suppose that 2 brackets refers to the values that we have marked in the next waypoint. The altitude we have to be and the speed that we have marked in the mission editor. If you have the waypoint marked on the ground and at low speed, they will always be both below the scale.

Edited September 13, 2021 by ReyCandy

[glen.a.williamson]

ReyCandy ... Thank You for taking the time to reply. 

 

Yes, one of the two brackets seem to be stuck at the top of the scale.  My altitude caret seems to be functioning correctly... when I set the altitude of a given waypoint to say 6,000 ft, and then fly toward said waypoint, my altitude caret responds correctly to guide me to the specified altitude.  But, if I set the desired speed for the same waypoint to say 300, and then fly toward said waypoint, my speed caret remains stuck at the top of the scale and does not seem to be responding at all.  I have even tried running my speed up to 350, or 400 ... and still the darn caret remains stuck, calling for even more speed. 

 

Very strange ... a small problem, but one that bothers me none the less.

[uboats]

checked, no problem here

[glen.a.williamson]

Thanks uboats ... I appreciate your feedback ... will investigate a bit more than to see what's going on in my rig.

[uboats]

55 minutes ago, glen.a.williamson said:

Thanks uboats ... I appreciate your feedback ... will investigate a bit more than to see what's going on in my rig.

better to record a video

check whether current spi is wpt not other point

Edited September 15, 2021 by uboats

[glen.a.williamson]

I was not able to attach a track file, as it got to be quite huge... but, here are a few image files which demonstrate the problem. 

 

As you can see, the first waypoint in my mission has a target altitude of 6,500 feet at a target speed of 350 knots.

 

 

As I approach waypoint 1, my altitude caret tells me I am roughly at the right altitude; but, even though I am already at 495 knts, the speed caret tells me I need to increase my speed (even though the target speed in only 300 knots).

I'm sorry I was not able to attach the track file for this mission; but, here is a copy of my mission file if you want to give it a try.

 

JF-17 Evening Flight to Maykop in the Rain.miz

 

 

[Ramsay]

3 hours ago, glen.a.williamson said:

... even though I am already at 495 knts, the speed caret tells me I need to increase my speed (even though the target speed in only 300 knots).

 

ΔT shows you to be +8:51 behind time, the speed caret is telling you to fly as fast as you can to get back on time.

 

The ME shows a planned ETA of 21:04:07 at WP 1, while the HUD shows a time of 21:12:40

 

I think the only way you'll be able to fly to your current route timings is change to a runway spawn.

[glen.a.williamson]

Ramsay, Thank You for looking into this .... your comments make perfect sense. 

 

When I first built this mission, I actually DID have my plane starting on the runway.  After I flew the mission a few times, I decided to change the mission to a ramp startup instead, so that I could practice the startup procedure as part of this mission.  I did not realize that this change would impact the ETAs for the subsequent waypoints ... I guess I mistakenly thought the waypoint ETAs somehow would have been automatically updated by the system when I changed the type of startup.   Now that I understand what is going on, I'll go back into my mission and add about 9 minutes to each of my waypoint ETAs, and I believe this should resolve this matter. 

 

Thanks again for your time and insight. 

[Dustin]

amazing