Dave62ndFF

The attached images were taken in the Persian Gulf theatre using current open beta (2.8.0.33006) & Litening pod on F/A-18C. In the FLIR view you can can see the street lighting casting bright patches on the ground which is obscuring potential targets. Although I have not used a Litening pod I have seen a lot of FLIR footage and believe this lighting effect to be unrealistic. The lamp housings on the street lights should be hot spots but there should not be big bright patches where the ground is being lit by the lights. To support this I submit a link to some footage from my local police helicopter which shows both visible light & IR: PolAir Footage of Police Chase | Gold Coast Chase: PolAir has released footage of the high speed chase of a stolen car through Oxenford. QPS: A man has been charged after a stolen car... | By 7NEWS Brisbane | Facebook As you can see, there are not bright patches on the ground from street lights in the IR portions of the footage. You can also see the hotspots on the lamp housings.

Thank you for the assistance. I just flew another couple of sorties to try things out, loading up new CAS entries both while in the air and on the ground. Using RCALL from the CAS page, then the ERASE ODU button, did the trick I was looking for which was to remove the used entries from the system.

I just tried using target points set from the F10 map (and loaded on the ground) for the first time. On the first sortie I set up mark points for T00 then valid targets T01 - T06. These were successfully loaded into the Harrier's nav system as T1-T6. I using GBU-38s I engaged T1-T4 in one target area, followed by T5-T6 in a different target area. This all went well and I went back to base a re-arm & re-fuel. I then deleted the existing markpoints on the F10 map & created markpoints T00, then T01 & T02 for the actual targets. After loading these on the ground I expected to have a new T1 &T2, however what I got was T7 & T8. I flew a second sortie & successfully engaged T7 & T8 without issue, This however left me wondering if there was a way to clear the list of target points between sorties? The system seemed to support T1 - T9 & maybe an X.

I have recently found this is still a problem. When buttons are used for the Radarstick vertical axis the radar cursor or EP13 sight respond in the same direction. However if the Radarstick is bound to an axis, the vertical response is reversed between the radar & EP13 sight. The horizontal axis works fine.

I am reliably able to reproduce this issue using the Harrier_training_1.miz file attached earlier in this thread. To do this I rearm at the beginning of the mission adding a TPOD and some GBU-12s or similar to use with the TPOD. If I then try to activate the TPOD, using SSS double depress when approaching a target, I experience the issues of no HUD reticle when slewing in snowplow, zeroed coordinates after TDC depress etc. Using the workaround Ramsay found, switching the TPOD to standby then bringing it back up again, gets the TPOD working normally.

Please see the following thread for discussion of this bug, screen shots, & .trk file:

Nice work Ramsay! It all makes sense now. I was leaning toward the mission somehow getting corrupted when I saved some changes under a different version of the open beta. The older mission I tried, where things worked okay, had the TPOD already fitted and used an airstart. The new mission I created had the TPOD already loaded via the mission editor. In the troublesome mission I was rearming with the TPOD at the beginning of the mission. It also makes sense why I sometimes managed to get weapons away after "button mashing". One of the things I would have tried was putting the TPOD into STBY and bringing it back up again. I just hadn't made the connection that it was the sequence that got things working again. Are you on the beta team/connected with the devs? If not I guess one of us should bring this to their attention using the correct forum.

Fortunately this does seem to be a limited problem. Since posting the track I have tried another older mission and the TPOD worked okay. I also created another mission in Nevada, under the latest open beta build, and it seems to work okay too. But whatever went wrong with the mission file I have posted here seems to be reproduceable time after time for me.

Thanks for giving it a go. I've made a track file, first flying toward the targets and trying to lock them up with snowplow, then switching to velocity vector slave. Unfortunately when I play it back the TPOD is out of sync with the targets. It does however show the TPOD being slewed without a HUD reticle and the coordinates being only zeroes after TDC is depressed. Harrier_TPOD_problems.trk

I have determined that the TPOD problem is somehow linked to the mission file I was using. I have a version of the mission, with an airstart, saved under an earlier version of the open beta. I loaded this up and the TPOD seemed to be working okay, the HUD reticle was back for snowplow & the TPOD was showing coordinates etc. I then went back to the version of the mission I was having trouble with, a ground start version that had a few changes and was saved under the latest open beta, and the problems returned. No HUD reticle for snowplow etc. I had loaded a TPOD, GBU-12s, and APKWS prior to takeoff. I have attached a copy of the problematic mission file. Harrier _training_1.miz

As a precaution I have run DCS repair and I'm still having problems. I have the TDC slew mapped to an axis on my controllers. I have attached some screenshots to illustrate some of the problems I am seeing. Harrier_Snowplow shows the absence of the HUD reticle after I have slewed the TPOD to a position near some targets. There was no HUD reticle visible while I did this. In the screenshot Harrier_OSB I have used the TDC depress/down button since the prior screenshot, zoomed in, & slewed the TDC onto a target. I tried to use SSS to cycle between AR-PT-MT without success. As such I was trying to mouse click on the associated OSB, which can be seen pressed in the screenshot, and it was not cycling. I also note in the Harrier_OSB screenshot that the coordinates in the upper right of the display are showing as zeroes. Could this be a clue to the problem? I have also attached a screenshot of the special settings I have applied for the Harrier. Could it be something to do with the INS or GYRO settings that is causing all the zeroes in the TPOD coordinates?

Sorry I wasn't clear on that one, I did mean aft short as distinct from from down/depressing the SSS.

Is it just me or are there some issues with the TPOD in the latest release? Problems I'm seeing at the moment include: Snowplow mode: The HUD reticle indicating where the TPOD is pointing is gone. VVSLV: Start point for the slew appears to be somewhere above the VV, again no HUD reticle. SSS not responding properly, e.g. SSS down short not cycling between AR, PT, & MT. Left short does seems to change FOV okay. Problems getting the laser selection & arming OSB buttons to work. With enough button mashing & switching in & out of the TPOD I have been able to get some weapons on target but I'm finding interfacing with the TPOD quite problematic at the moment.

Thank you for the extra feedback. I have just tried out the air start mission I was using (as per uploaded .trk), and another mission with a ground start, using the 21st May open beta update. The APKWS seems to be working a lot better. I was able to knock out all seven available targets in the air start mission. I was also able to get hits after using a hot ground start & loading the APKWS via the re-arming interface. In the prior build I didn't get any hits after the ground start. I still seem to be getting some rockets that don't track but haven't so far identified a specific sequence of events that causes this to happen.

After seeing iLOVEwindmills mention using an airstart I set up an airstart myself. Sometimes the APKWS seems to work, often it doesn't. I've attached a .trk file (Nevada theatre) showing it not working if anyone can see something I'm missing. Harrier_APKWS.trk