TuffAsAir

After powering on the AGM-88C and selecting POS on the WPN page, the TTG number changes to a ridiculously high number. Once you select RUK mode on the WPN page, TTG disappears from the HUD and will not reappear afterwards, no matter what config is selected. I am unable to save a track.

The procedure is as follows: -If you are using TIR(or other head tracking), pause it or turn it off. -Center the view by pressing NumPad 5.(by default) -Use NumPad 8 to raise(tilt up) your POV. -Pressing RAlt+NumPad 0 will save the new POV as default center. When you reactivate TrackIR, it should center on your new view.

If you consider the center of the screen is "where you are looking". Note the quotes. As far as your point as to VR doing it correctly; Vr centers the view to where you are looking, whereas there is no way for the software to know where you are actually looking on a 2D display. Head tracking tracks your head, not your eyes.

The procedure is as follows: -If you are using TIR(or other head tracking), pause it or turn it off. -Center the view by pressing NumPad 5.(by default) -Use NumPad 8 to raise your POV. -Pressing RAlt+NumPad 0 will save the new POV as default center.

These are your screenshots, to which I have added a cross over the center of the screen. In the first screenshot, you can clearly see that the HMD crosshair is centered on the screen, if you consider that the center of the screen is "where you are looking", then you are looking below the VVI. In the second screenshot, both are centered, thus "correct". The center of view for the HUD and HMD cursor coincide. The fact that you can not see your HMDs on the screen at the same time is a "side effect" of being on center. The default view being "lower than center" is a way of permitting constant overview of HMDS but does not allow overlapping HMD crosshair with VVI.

It should be the same keys as if you were to take a screenshot in Windows, and there is no visual cue, in-game, that shows that a screenshot has been taken. Screenshots should be found in your Saved Games folder: (e.g.) C:\[user]\Saved Games\DCS[.openbeta]\Screenshots Hope this helps.

Slight addendum, the UHF squelch can not be mouse-clicked either, but is triggered by clicking on the UHF tone switch.

The Status button on the UHF radio is not mouse clickable. It can, however, be set to a keybind. A10C_UHF_Status_button.trk

When the 'MAL & IND LTS' are set to DIM, if you turn the console flood light knob to the maximum brightness, or close to the max, the 'MAL & IND LTS' revert to the brightest setting. If you then click and hold the switch towards the DIM position, they go dim but upon release of the switch, they revert to the bright setting. If you lower the brightness of the console flood lights enough, it is possible to set the 'MAL & IND LTS' back to DIM setting. When the 'MAL & IND LTS' are set to DIM, if you turn the primary 'INST PNL' knob all the way to the minimum, the 'MAL & IND LTS' revert to the brightest setting. Clicking the the switch towards DIM(or clicking and holding it) does not change the brightness level of 'MAL & IND LTS'. With 'INST PNL' brightness set to any level except the minimum, it is possible to set 'MAL & IND LTS' to DIM. I have searched to find whether or not this is the intended behavior, but have been unable to find detailed info on the subject. Track attached. MAL & IND LTS switch.trk

The track file is 23mb after 4 minutes in the mission. Since the max size of a track file upload is 5mb, I simply can't upload it to confirm the issue. Attached is a screenshot of the mission debrief where you may notice, at 2:04:37, the "AN/ALE-47 container failure" just prior to Colt 1's(player) death. No mods and fresh repair. If you can tell me a way to send an oversized track file, I will gladly upload one.

Yes, I have checked to see if this was the case and no luck on that front. I can start the F-16C in any other mission without issues, but not this particular mission. It's as if I am being hit by invisible weapon fire.

I tried playing this mission a few times last night but kept blowing up spontaneously before the end of INS alignment. I figured I was making an error and decided to move along. Tonight, I tried again, same results. The nose of the aircraft jumps around a few times and the plane explodes. I just tried again(auto start this time) to grab a track, but I can't upload it here because the file is too big. I don't think that is is pilot error. :smilewink:

Thanks for your reply. Thanks also for specifics as to not finishing with 100 success. The reason I try to get 100 in missions is simple; first of all, there are not many DLC Campains and I really enjoy them, so I like to get everything I can out of them. I also feel that if I missed something in a mission and try again, it is only helping me become a better sim pilot. I somehow thought that Wolf 1 opening fire, or the cars not making it to the checkpoint was the reason for success being 90. Now I can move on to mission 2. Thank you.

I have flown this mission many times, 15 at least, and am unable to complete it with 100% success. I ALWAYS stay behind WOLF 1 and ALWAYS leave my gunners on HOLD. I am quite frustrated because: each time I must wait 13 minutes on the tarmac(that is hours of total wait time(and yes, I know that I can use ctrl+z))and fly pointlessly to the carrier group and back(hours of pointless flying) before being able to see if WOLF 1 will, again, open fire without reason. I feel like I am wasting a lot of my sim time on this mission. I am not a ME expert, but why are there multiple conflicting ROE triggers on many WOLF 1 waypoints? I believe the firing at static object happenned at waypoint 35, where the "Advanced (waypoint actions)" are: "1: ROE=Return Fire" as well as "2: ROE=Weapon Hold". This is also the case at many other WPs. As I said, I am not a ME expert, but how does AI decide which ROE to use? If I told human soldiers that the ROE were: Return Fire AND Weapons hold, how am I to expect them to know what to do? Yet you say I don't need to wait for an update... I don't think I have any more patience, regarding this mission. It's a shame, there are not many campaigns for UH-1H.

Thanks for checking. I just tried the mission again, before seing your latest reply, and Wolf 1 actually opened fire on a static object on the river bank, before arriving at the first bridge(a flag, I think). I guess I'll wait for the next update before going through the cigar thing again.

I have an issue with Mission 1, Wolf 1 opens fire on the cars as they are parked on the road which makes them drive into the trees. I have (a few times) continued the mission as prompted by the voice communications, the vehicles eventually blow up in the woods near the power station and I can finish the mission with 90 percent rating. I had previously gotten to the bridge and blown up from being too close to explosion, now it seems I can't get the cars to drive to the bridge.

Glad I could help.

There have been changes to a few script files: "MDI_right_init.lua" and "MDI_left_init.lua", found in folder "[DCS]\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\MDI_IP1556A\indicator". These lines have been added: -- green shade for "render_target_X" , to change tone - make texture with that tone used_render_mask = LockOn_Options.script_path.."../IndicationResources/MDG/flir_texture.dds"

There have been changes to a few script files: "MDI_right_init.lua" and "MDI_left_init.lua", found in folder "[DCS]\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\MDI_IP1556A\indicator". These lines have been added: -- green shade for "render_target_X" , to change tone - make texture with that tone used_render_mask = LockOn_Options.script_path.."../IndicationResources/MDG/flir_texture.dds"

No worries, trouble happens. Looking forward to diving into the campaign. Thanks for the quick responses. Cheers

Ok. I tried many different ways and it seems to be related to the use of VoiceAttack/Vaicom Pro. I haven't been able to reproduce the issue in missions that use the regular comms menu/system.

I ran a repair but no luck. As soon as I press the spacebar for communication with the tanker, I get the autopilot warning, then the intended communication.

Now I'm getting: "PULL UP, PULL UP....PULL UP, PULL UP", with every incoming communication, in level flight at 7000ft. It makes the mission(campaign?) really irritating, if not un-playable.

I have just started this campaign and am on Mission 01. Every time other flight members speak, I get Betty telling me: "Warning Autopilot", no matter what state the autopilot is in. Can't find any other mention of this. Can I expect this all through the campaign?

Thank you.