cannot reproduce targeting pod issue (AT flir)

[mla306]

Hi, I am having trouble in ROTPL2 mission 4.  I am targeting a ship in the harbour at wpt 2 (designated as target) but I can't get the targeting pod to switch from WFOV to either MFOV or NFOV and also the zoom button isn't working.  I am just using the buttons on the MFCD, I don't have any of them mapped, and I can't get it to switch views.  Can someone look at the track file and see if you can figure out what I'm doing wrong.  I have tried the mission a number of times to no avail!  Badger has looked at is as well and doesn't have the same problem when he flies it and he doesn't think it is a mission editor issue.

 

Thoughts?

No Mfov or Nfov .trk

[Razor18]

Do you have your FOV/HARM SEQ/RAID button binded?

The F-18 uses the radar elevation up and down AXIS or same keypresses for TGP zoom, if you put the priority diamond to the tgp screen.

[Skeet]

I flew a mission last night and the exact same thing occurred as is being described in the OP’s comment.  ATFLIR would not switch from Wide to Medium (and certainly not down to Narrow) with the use of the computer mouse pushing the top left button on the display as typically used. The top center button changed the TV mode to IR and back just fine, and the TDC moved the targeting retinal around just fine, but no zoom aside of extreme wide angle.

I dropped all of the JDAMs as best as possible out of the Wide Angle view and returned to the carrier and called it an evening, was hopeful that it was just going to be a weird single occurrence anomaly. Like perhaps the game just didn’t open correctly and a reboot would somehow correct.

Razor, I absolutely do have the Foid/Raid button bound, but was not pressing it. And the one thing that I had done earlier prior to loading the mission was remapped my control button for the Radar Elevation, however was not attempting to utilize that in any way either. The ATFLIR screen was definitely the sensor of interest, it’s what I needed to designate targets out of TOO mode. Next time I will try using the radar elevation switch and/or the Foid/Raid button; hopeful of success.

It is sad to hear that my occurrence was not just a coincidence. I’ve experienced several of the same issues others have had over the past week and a half; my control bindings all disappeared, fusing errors on bombs where several randomly become duds/turn into a 500# paperweight, weapons X-out on the store’s page, etc. ALL since the recent update; DCS brings out a new module (the Phantom) and somehow the coding for the Hornet gets buggy?

[mla306]

I do not have them binded.  I do have the tgp as soi with the diamond.  I am able to move the camera to the harbor and lock up the target.  I can also switch from tv to ir mode.  I'm not sure I follow your suggestion.  Should I map that button?  I'm just using the mfcd, not my stick or throttle.

 

Thoughts?

[Skeet]

@mla306

If I am understanding correctly, he is saying that another way to switch the Field of Views from Wide, to Medium, to Narrow is to press your FOID/RAID button (assuming that you have that assigned to a button).  By default, I believe this is the 'I' key on the computer keyboard. In addition to possibly using your mouse, hovering over and left clicking on the top left button of the display the way you and I had previously attempted, this FOID/RAID button hopefully would work, because it is not working the way we would expect it to.

Furthermore, in lieu of using the mouse to click the zoom levels (in or out) of the left side of the display, the Radar Elevation switch (again, assuming that it is bound to one of your controls) could be used. With the ATFLIR, the wide-angle field of view does not have any zoom opportunities at all, so being stuck in that wide setting certainly makes it hard to accurately target your munitions drop. If you can get it to Medium or Narrow, then you would potentially have zoom-in opportunities via the Radar Elevation switch.

I am at work, so no way to test drive it to confirm for another 6-hrs or so.

[mla306]

Hey thanks man!  I follow.  I'll give it a try.

 

Thanks again for the help!

[Skeet]

My issue was in fact the way that I had the Radar Elevation bound to my controls.  I have a WinWing Throttle and on the front of the handle under my middle finger is a wheel used for this purpose. This wheel is spring loaded so that after rolling it, by simply letting go it will physically snap back to the center position. Long in the short of it, had I not had to rebind half of my controls for no Fnkn reason, but now I am just complaining.  It took me 3 or 4 attempts before I was able to get that wheel to act as I want; roll forward and it lowers the elevation of the radar and it stays put, roll backwards and raises and then stays put ... 

The FOID/RAID button works as indicated it should, and then this Radar Elevation works as it should.

Thank you all that helped!

[mla306]

I'm still having the same problem.  I bound the FOID/Raid button and tried the mission again.  I tried using the bound key in the mission and then tried just using the button on the MFCD and neither one worked.  You can see the screen momentarily switch to MFOV and NFOV but then quickly switches back to WFOV and the zoom button doesn't work at all?  Not sure what to try now?  Here's the track file again.  I also noticed that the last update changed all my bindings for the Viper....I'm wondering if there is a similar issue with the Hornet although everything else seemed to work as usual.  I'll start by checking all my bindings.

Any more thoughts?

No Mfov or Nfov .trk

[jaylw314]

17 hours ago, mla306 said:

I'm still having the same problem.  I bound the FOID/Raid button and tried the mission again.  I tried using the bound key in the mission and then tried just using the button on the MFCD and neither one worked.  You can see the screen momentarily switch to MFOV and NFOV but then quickly switches back to WFOV and the zoom button doesn't work at all?  Not sure what to try now?  Here's the track file again.  I also noticed that the last update changed all my bindings for the Viper....I'm wondering if there is a similar issue with the Hornet although everything else seemed to work as usual.  I'll start by checking all my bindings.

Any more thoughts?

No Mfov or Nfov .trk 22.99 MB · 1 download

Check EVERY column in the Antenna Elevation up/down button bindings.  If you have a centering switch somewhere accidentally bound to Elevation up or down, it'll stay stuck in that direction.

[Skeet]

As noted above in my comment, in my situation it absolutely was the Radar Elevation switch that was causing the issue.  It was not only an issue with the Tpod, but was not functioning correctly for A2A radar.

For testing purposes, as the previous post suggests, find the Radar Elevation in the controls settings, look at how you have up and down bound, make note of this, and then delete them.  Now go try a training mission to determine if that fixes the Tpod.

Now you are going to have to go back and fix the Radar Elevator switch.

[Skeet]

My Radar Elevation switch is a spring loaded wheel.  To get it to work properly, within the Control Settings, “Add” which pulls up the dialogue box, then I had to roll the wheel AND hold it (taking my finger off it, physically the spring will snap it back to center, so I had to hold it such that it would not) and while holding it I used the mouse to Click “Save” or “Accept” or whatever the heck it is. Rinse and repeat for Down Elevation and Up Elevation.

For practical purposes, when it is set up wrong that way, every second you have the jet engines running, that switch is telling the computer “lower the radar”, “lower the radar”, “lower the radar”, “lower the radar”, “lower the radar”… so you hit the button on the FLIR Screen and it complies for just a fraction of a second, and then your Radar Elevation switch changes it right back!

[jaylw314]

2 hours ago, AG-51_Skeet said:

My Radar Elevation switch is a spring loaded wheel.  To get it to work properly, within the Control Settings, “Add” which pulls up the dialogue box, then I had to roll the wheel AND hold it (taking my finger off it, physically the spring will snap it back to center, so I had to hold it such that it would not) and while holding it I used the mouse to Click “Save” or “Accept” or whatever the heck it is. Rinse and repeat for Down Elevation and Up Elevation.

For practical purposes, when it is set up wrong that way, every second you have the jet engines running, that switch is telling the computer “lower the radar”, “lower the radar”, “lower the radar”, “lower the radar”, “lower the radar”… so you hit the button on the FLIR Screen and it complies for just a fraction of a second, and then your Radar Elevation switch changes it right back!

I believe that is an issue if you are using the button bindings for up/down.  If you set your spring wheel to the radar elevation axis there is no ambiguity and it should read correctly.

You may already realize this, but in SimApp Pro, you can change how your throttle reports that axis, either axis, buttons, or both axis and buttons.   

[mla306]

Hey sorry for taking so long to get back to you Skeet!  You guys were absolutely right.  I'm not sure how the radar elevation got bound to a button, it wasn't me that bound it.  But I cleared it and the trouble went away.  Completed my mission with no hiccups!

Thanks for the help, much appreciated.  Not sure I would have ever figured it out on my own!