Dr Zaius

+ multible tracks, none of which were deemed to be 'concrete evidence' Apprecaite your efforts laertesson but user fixes make me nervous, if we start doing the work of developers then where does it stop?!

Tell me something Elmo do you guys report ED issues like this back to ED or is that a job for us forums users?

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.

My understanding of the GAU-12 Equalizer is that it's actually a very accurate gun so yes, I expect it to perform as it should.

Please don’t this as an attack @RAZBAM_ELMO but I note it’s getting harder to report problems such as this. More and more I see that critical weapon employment and poor tactical observations are being used to circumnavigate the core issue the users post is trying to help fix. The time it took to write the correct gun employment it would have been quicker to actually load the module up and see for yourself that rounds are falling a little short – the problem is that posts like these end up getting marked up as [User Error] and moved to the resolved bugs section where further dialog with the team then stops, which is incredibly frustrating. I know it’s frustrating for you guys as well, you’ve only got to be on these forums for a couple of weeks to realise how many duplicate posts there are with the same issue revisited time & time again – I suppose the manual once finished will help resolve this problem but until then can we show a little more willing to help people out please?

lol - resolved, working as intended!

Huh?

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.

Exactly this, thanks IIIcky Elmo any chance you can look at this again please, I think you think we're having a different problem, IIIcky has simplified my attempt to previously highlight the issue - thanks in advance.

Not while the issue is listed as ‘user error’ it won’t, perhaps Elmo will explain a little better once back from the holidays. Have you encountered the same thing IIIcky?

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?

I don’t use the CAS page much however if you’re receiving a 9 line talk on then I can see its usefulness, although I don’t think the FAC we have can handle more than one target engagement at a time.

You can skip the f10 map by selecting different mark points for each target via the tgp, you may find the following link to be of use:

Doesn’t the INS do this when entering lat/long info? I always thought it something to do with rounding.

Absolutley right on Buzzer, if you want to take off from the deck of a destroyer and the ME allows you to do so then why not, just because somone doesn't think its operationally a sound thing to do that shouldn't deter you from flying the sim how you want to fly it.

Thanks for the review suggestion however I think one us has misunderstood, the problem has nothing to do with the TPOD - for arguments sake lets say one isn't attached, when designating something in INS mode you can slew the designated cursor around the HUD without any problems via axis commands but if you have this slew command mapped to either a keyboard or joystick button press then the commands are inverted.

Soz vctpil, totally my misunderstanding - I've since encountered the same bug when in CCIP mode and pressing the pickle button to designate, the area designated is indeed at the top of the crosshair and ever so slightly to the right (as per your original screenshot), it's therefore bugged.

Theres a difference between pressing the TDC down (action button) to designate a target over the velocity marker and pressing the pickle button (long or short) for a tarket point, if you're trying to attempt the later then perhaps I've got my wires crossed.

This is weird, so I loaded up your track file and took over just before your first designation, as you can see it works as it should, however studying your track a little more you'll notice that for whatever reason your desigate command also looks to be changing the bomb mode from CCIP to Auto, hence the solid bomb fall line - I think then that maybe you may have a duplicated command on whatever you're using as the TDC down (action button) and that somehow has screwed with the input? CCIP.trk

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.

Yeah its already been reported, try moving the TDC in INS mode, for me it moves much more freely than it does in TV, oh and try not to use diagonals, just up, down, left & right, see if that helps.

Do we have a special F10 radio command for up periscope?

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