Hi,

in our last squadron evening we all had the problem that at the end of our long mission we got a warm seeker on the AIM-9.
In several tests we noticed that the seeker seems to be in the COOL state from the very start of the mission. Even if it has never been manually selected or MSL OVRD has never been put in DGFT/MRM (entering master mode via A-A On the ICP).
The manuals state, that the initial state should be WARM and it either has to be set to COOL manually or MSL OVRD has to be switched to DGFT/MRM while MASTER ARM ist hot.

I also noted, that when the coolant runs out the Seeker tone degrades but the OSB still shows COOL.

Regards

Tomahawk

@OPPOTATO
Thanks, good to know.
That seems to be an error in the DASH-34 then. On page 264 it is listed under SURVTRACK restrictions.

Anyway, big thumbs up to the BMS team. LINK 16 is really a great asset.

Tomahawk

I just found the solution. I realised that I can connect via Quest Link and still use Steam VR. And now it works just fine.

Tomahawk

@Maru That’s just it. I had the Threat Circles for them with 18 and 97nm.
However the SA-22 never fires above 6nm and the SA-20 fires at about 50nm (40nm with Jammer).
That’s only about 5nm mor than the SA-10. In some of the test runs it would fire at about 77nm but without turning the radar on and just shooting one missile after the other without guidance. It seems that the missile range has been upgraded, but the Flap Lid still has the same range limits before it turns on the radar.

Tomahawk

@scubapics
Disabling OpenXR Toolkit did the job.

Thanks

Tomahawk

@airtex2019 It doesn’t make a difference. It happens no matter at which stage I enter the cockpit.

Tomahawk

Hi,

in our last squadron evening we all had the problem that at the end of our long mission we got a warm seeker on the AIM-9.
In several tests we noticed that the seeker seems to be in the COOL state from the very start of the mission. Even if it has never been manually selected or MSL OVRD has never been put in DGFT/MRM (entering master mode via A-A On the ICP).
The manuals state, that the initial state should be WARM and it either has to be set to COOL manually or MSL OVRD has to be switched to DGFT/MRM while MASTER ARM ist hot.

I also noted, that when the coolant runs out the Seeker tone degrades but the OSB still shows COOL.

Regards

Tomahawk

@Maru said in Gibraltar Theatre for 4.37.6:

Thanks! @Hunter.-0 As far as I am concerned, nothing has changed on that regard. Sent you a PM to tackle the issue you are facing.

Hi Maru,

I have the same issue, that I cannot change the skin in game. When I click the button in the Loadout screen, nothing happens.
I compared the folders from both the old and the new version in
…\Add-On Gibraltar\Terrdata\Objects\Models
The Model_0-4.mti files in several folders have changed, so that only one texture set is left.
in the 1052 and 2002 folder the Parent.dat has been changed too, reducing Texture sets to 1.

The folders that I have identified so far are:

1052
1909 (new folder)
2002
4042
4082
4083
4088
4098

Cheers Tomahawk

@oakdesign

https://drive.google.com/file/d/1kKECnNZLUeGExM0kLawDfvAx50mxh1AA/view?usp=drive_link
https://drive.google.com/file/d/1TjF6AcjilTYT_PBaS7nk4dNlmoTTYe0C/view?usp=drive_link

Tomahawk

@oakdesign Yesterday you said there was a way to modify the old ACMI files by changing the LAT/LONG reference in the acmi.txt.

I tried this with my old Gibraltar files, but I still get the wrong position.
This are 2 recordings of the same mission. The first with the original theater.map and modified acmi.txt, the second one was recorded with the modified theate.map and works correctly.

Tomahawk

@Maru That’s just it. I had the Threat Circles for them with 18 and 97nm.
However the SA-22 never fires above 6nm and the SA-20 fires at about 50nm (40nm with Jammer).
That’s only about 5nm mor than the SA-10. In some of the test runs it would fire at about 77nm but without turning the radar on and just shooting one missile after the other without guidance. It seems that the missile range has been upgraded, but the Flap Lid still has the same range limits before it turns on the radar.

Tomahawk

Hi,
great theatre. Thanks for the work.
One question. I can set SA-20 and Sa-22 in the Editor.
From what I can tell, they behave like Sa-10 and SA-19.
Is that correct or has anything been modified for these systems that I would have to consider for my TacRef?

Tomahawk

@Mav-jp Sorry for re-opening this topic after over a year, but I’ve had some rather technical discussions over the past days regarding the AMRAAM seeker behaviour.
Could you please clarify a few things for me.
The Dash-34 lists HPRF as optional. From what I understand the missile will only activate at HPRF when the DLPP exceeds certain closure rates. The article on the acquisition model does only mention R_HPRF, bot not the closure for the activation so I’m not a hundred percent sure if that is still applicable.
One point of our discussion was, whether the missile could skip HPRF phase completely and go to MPRF only, if the closure of the target is below the threshold.
If yes, could you also tell me something about the closure criteria for the HPRF activation.

In the article it says for the HPRF selection criteria that targets are dismissed for targets with a positive closure rate and a positive aspect.
For me a positive closure is a target coming towards me and aspect defined between 0 and 180 degrees (not having negative values).
Could you please clarify the sign of those values?

The other thing was the RCS setting on the SMS page. From what I understand, this only affects R_MPRF, but not R_HPRF. Is that correct?
What are the actual values for R_MPRF and R_HRPF.

Cheers

Tomahawk

Hi,

over the last couple of weeks I have seen some rather strange behaviour from some various SAM sites.
The fire endless salvos in a ballistic trajectory without tracking anything.

Has anybody else seen this?

Cheers

Tomahawk

@Nick-san What exactly is this new zoom function. I cannot find anything on that topic?

Cheers

Tomahawk