10 hours ago, mack said:

or they do have a jammer in the loadout (eg IOPG)

That's a great start for me to try and refine the bandaid.

6 hours ago, donaldseadog said:

Maybe if the blue side has some jammers run them to see if there's an obvious result.

The prowlers jamming works perfectly.

this is real cat and mouse. I thought I'd try the IOPG BadgerJ, looked for a scenario with it in, gave up and wrote one, then found it has no radar which has to be activated to get the jammer going

I'll write a test in NACV with the blue side having a badgerJ and see if it does any good

ed

LOL it looks like you can't man blue bases with Russian AC 

 

 

I don't know why there might be some problem with red jammers, the modified BadgerJ have the same jammer as the blue, i even tried a version with 3 jammers per aircraft.

It's not as easy a problem as it first appeared.

I'll shift to a later export.dll version that will let us have operable radar for the IOPG badgerJ. This will mean needing to play with ideally the 2025 comprehensive update game. Then we can see if it's jammer works.

It might be easier to rewrite the scenario in a 'modern' battleset with hcdb DB 😄🥴

Oh BOy, this is a learning curve for me

The attached seems to work in BS2 for the BadgerJ jammer, I kind of know why my previous didn't. The only issue at the moment until I learn a new way of determining the battleset that is loaded is that if you use it for any other battleset but NACV original it will screw up something (depending on the DB) and maybe crash the game - a minor issue  

NOTE: It will only work in late beta versions of the game engine including the 2025 comprehensive update. These allow use of a feature that loads the DB changes before the scenario is loaded and allows the new radar/ECM gear to operate - at least that is my theory seemingly proven here.

But I've nothing better to do and have a lead so who knows, we might catch a fish yet.

PS although I haven't tested it if you run this in the folder ExportDLL it should also make the changes in the SE as well as the GE, but there's not much point so run it in the ExportDLL\GE folder (you might have to create it if you haven't already.

ErrataBS2.zip

8 hours ago, donaldseadog said:

It might be easier to rewrite the scenario in a 'modern' battleset with hcdb DB

I just had a look all the way down the list and found the USNI battleset that was apparently written in 1991 which does include two versions of this mission (for each side) and the Badger-J in that has two ECM sets. And it works perfectly.

I'll have a look at the file as well.

1 hour ago, mack said:

I just had a look all the way down the list and found the USNI battleset that was apparently written in 1991 which does include two versions of this mission (for each side) and the Badger-J in that has two ECM sets. And it works perfectly.

I'll have a look at the file as well.

That looks like the optimal fix to me  Does it launch SA-N9s from SA-N9 launchers ? 
Well not the Badger  but Baku

 

Yeah the weaponry on the baku is fixed, and I tried the badgers in NACV and their jammers worked.

4 minutes ago, mack said:

Yeah the weaponry on the baku is fixed, and I tried the badgers in NACV and their jammers worked.

Good that BAKU is fine.

The fix for NACV needs more fiddling and testing to provide a test so that it will only be applied to appropriate battlesets and the best idea I have isn't very rigorous and could fail (although it's not likely).

Anyway I might fiddle more with it in case it is needed in the future but for the moment you need to remember to disable that DLL (move it or rename the file type) when playing other Battlesets.

this is the final offering but while it seems OK it's definitely a use at own risk job.

It's OK to leave in place if playing from the original battleset series and probably any battleset, but maybe not.

Anyway it was a good exercise and brought up a bit of a behind curtains issue to be looked at so thanks.

ErrataBS2.zip