DaveDewhurst

Dave

Has anybody else played this mission? Did you think the volume of the prerecorded sections was a bit too loud? I have to either turn down helmet volume but then I cant hear Jester, or have Jester audible but quickly turn the sound down any time any speech is played. It would be better if it played back at the same volume as Jester by default so they could be turned up/down together Dave

"F-16C_50" Dave

Have you switched the radar display on? (Behind and to the left of the stick, labelled TV/Off/Radar I think) Have you also turned on the stability switches Pitch/Roll/Yaw By your left elbow. Without these on the AP wont stay on? Dave

Thanks both, All the Shrikes were the same model. I tried using the 22 and the 50 and did get tone so it seems to be an incompatibility issue. The (at the time) currently available tables said the head I was using were suitable but obviously not. Oddly though they still tracked. Dave

I've been using this User created set of missions to get used to the F4 but am having an issue with the Shrikes. I cannot get the tone to sound or the FD bars to point towards the radar even when looking right at the sam site The mission was released after the last patch and I have tried editing and resaving it in the Mission Editor to make sure that there is no mismatch there. I have selected AGM45 and ARM on the delivery/weapon dials, Master Arm is on and the Pylons with Shrikes are selected. The volume is up and the sight is in A/G (in the image below the "ARM" isn't displayed and I'm pointing away from the sam because I took the SS after I had launched all my Shrikes) The mission is to destroy an SA2 site and I am equipped with Mk24-34 (I have also tried with Mk24-5 with the same issue). Should I be getting a tone/FD indication or am I missing a step? Dave Shrike_NoTone.trk

On the top of page 890 of the manual installed with the f4 (not the online one) It states that the browser has been disabled Dave.

Oddly I started a thread on this earlier in the week. I posted that switching the knob sometimes didn't update the radar if you did it too fast. I left it to go and get a track of the issue and couldn't reproduce it so I deleted the post. Glad I'm not going mad.

MInor bug If you look in a direction that places the gaiter at the far edges of the screen you can see it disappear In this shot you can see a black square where it should be. Dave

I've just recently started using Triple monitors (mainly for driving, but DCS runs OK too) Can you move the displays at the top right and left of my screen, Id like them a bit further in Dave

I didn't play this mission in earlier versions but twice today (after 2.9) at least 1 wingman has had an issue. The picture shows one burning wingman, one wingman made it and the third suffered damage on takeoff and relanded. Also there were no F16s. after waiting around near the hold point. A

When you fly over the current waypoint. Instead of the next waypoint in sequence being selected and its heading indicated, Sometimes it increments by 2 eg set route from take off dir to wp1, on approaching within 0.1km instead of setting wp2 as the next destination it will set 3, then 5 Included a track of a mission on caucasus I made to demonstrate. Dave missed wp.trk

No problem. Smoke doesn't move until I press space, so the difference in TO time is merely seconds, but I was wondering whether the delay in getting him moving might be messing something. But I've just done mission 2 & 3 with no issues now, so I'll just keep doing a stored heading align and look forward to the overhaul and some of your other campaigns after this one. Dave

Update, After I took that screenshot, I quit so I could post it and then replayed it. Smoke decided to do his own thing again. The only thing I could think that was different (other than removing the UH60) was for the test I just did an auto start, but when I wanted to play it for real I did a full manual start. I have now run the mission a few more times and I think I can reproduce the issue and reproduce the fix Every time it works I have either done an Auto start or a stored heading INS align (which is what the auto start does) Every time the mission has gone weird, I have done a full 9min INS align. Does that sound possible as a cause? is there a timed element in there somewhere? Dave Just completed the mission, Smoke behaved perfectly (this was with a manual start but stored heading align)

Aaaand Smoke now follows me to WP2 thanks for the memory jog about the UH60. Dave