Dr Zaius

Yeah I think the gun does need a little spread, shame this clip doesn't clearly show the engagment range.

Its a shame the APU can’t be spun up to actuate the gun, not sure I’ll ever get used to diving towards the ground with power.

Having a working manual would prevent this sort of thing, you need perseverance to fly this module you really do.

Interesting, it looks like the squeeze of the gun trigger sets a mark point for the targeting pod!

That's odd, though not related to the same issue the below link does have a screen shot of another users export and all looks fine - have you any mods installed and/or maybe try to adjust the mfd resolution in the sim settings?

Are the FLIR images fixed as well? Along with the map brightness issue I found the DMT and TPOD to be a little too dark when extrating exports.

I adore the Harrier but she's a fickle mistress, imo Razbam are very close to having the best module out there but are let down by the little things, annoying bugs that make you question your own sanity, strange control logic that’s difficult to replicate / report, that sort of thing - having no (official) manual doesn't help although it's being worked on by the excellent Baltic Dragon who consistently delivers quality with both missions and campaigns - its therefore a bit of a mixed bag, despite her faults though she's bloody hard to walk away from! I’d therefore say go for it but would urge caution with future Razbam products, all this doesn’t bode well for the Mudhen which is much, much more complex and therefore could sit ‘unfinished’ for years.

Its hardly the same though is it, one is a simple hud icon indicator for vehicles only, the other is a friend or foe colour coded label that details what the unit is along with its distance. If you want it to pick up every single heat source then the system pretty much becomes a moot point.

Hopefully I’m wrong but I very much doubt the new FLIR will ever be that complex, my previous suggestion was more an attempt to highlight a possible workaround, a quick easy fix that could potentially indicate ‘active’ vehicles, I'm really not that bothered if the system doesn't pick up anything else, thinking about it I’d prefer that it didn't.

Reinstalling isn’t the answer, get yourself a copy of Chuck’s guide and start reading, you’ll soon work it out. Note: I bet even seasoned sim pilots still forget to turn off the ground power resulting with an annoyed crew chief shouting at you, I still forgot myself - this though will in no way effect weapon release.

Have you checked your input mappings?

Why don’t you include a track showing us your procedures right up to the point of trying to get a lock, that’ll give us a better understanding of whats gone wrong.

What fuzing have you selected? Try either PR (1.2 second from release to burst) or OP (4 seconds)

I think theres a bit of a misunderstanding as to how this feature works, as I understand it its a very subtle lighting effect that changes depending on the outside environment, an example would be taxing next to some green grass should result in a faint green tinge to the cockpit, as I say it it subtle though.

As with most of these bugs there often are workarounds, still it should be reported. How exactly are you able to get fine control using the point of view hat, are you able to dial in some accuracy via the control setup? I've reported it btw

I can't replicate the issue however I use the axis slew upgrade on my warthog, not the point of view hat which is what I think you’re using? I do have a backup mapped though via the use of a modifier and the castle switch on the joystick - the strange thing is that I can replicate the problem using this backup method which makes me think that the issue occurs only when using a non-axis inputs, thats why I recommended that you give it a try.

I stand corrected, follow this procedure and you can drop on 10 different targets, one after the other - the key is mark points created using the targeting pod!

The dreaded input reversal is back?! Last time this was reported it was to do with the Maverick input but they fixed that issue last update or so, I was new to the module back then and was certain it wasn’t just the Mavs that caused problems but couldn’t replicate and assumed I was wrong - out of interest do you map you tdc to an axis or button press? I mapped both and iirc it worked OK with one input but not the other, give it a try.

Mapping to the OSB commands worked really well, thanks for the tip! Add it to the list - suggest reporting it as a new post though, you'll also be asked to supply a trk. file

It's actually SSS left to change FOV not NWS, my mistake. I didn't realise you could map zoom in & out like that, I did try and map those commands to the china hat on my TMWH but it doesn't work very well, a press and hold does nothing and pressing it again and again is a bit hit & miss, or as you say wonky.

Hey good find, landing gear must be fairly beefy to handle all these 'drops'

Wow, simple and very effective!

What exactly have you got mapped to your axis? As i understood it the only zoom feature you have using HOTAS is changing wide to narrow FOV, are you able to make a small video of the problem? Iirc theres only 2 sensors on the aircraft that zoom, one is the targeting pod the other is Maverick optics, unless you’re referring to other aircraft in which case each the targeting pods do differ in their functionality.

Does anyone else think the pilot hit the deck a little on the hard side?

I watched a harrier documentry on YT the other night, one of our best Royal Navy / RAF pilots said the aircraft itself wasn't difficult to fly (including STOVL) but if you got it a little bit wrong then it can get very wrong very quickly - one of the things mentioned was control reversal when flying backwards over a given speed, he almost had a crash because of that little issue. Great vid btw