FMB Triggers for 4.15.x Request

[wheelsup_cavu]

Originally Posted by Tolwyn

It likely breaks the packet recorder because certain variables aren't yet defined. So the game doesn't know what to do when that packet shows up on playback.

I'd imagine that if DT incorporated triggers, they'd work around that.

It's also likely a mission encoding issue that over the network, it's not expecting <army> syntaxes. So, yes, I agree that some work needs to be done.

I do NOT want NTRK functionality to break!

They are aware of the problem and I agree I don't want the ntrk function to be any more broken.

Originally Posted by Tolwyn

On an aside, where can I download JUST the 1.2 trigger mod for HSFX?

It may exist but I am personally unaware of a stand alone version of the v1.2 Trigger mod. It was incorporated into HSFX v7.03.
HSFX 7.0 to 7.03 patch: http://www.mission4today.com/index.p...etails&id=2313


Wheels

[Tolwyn]

My downloaded version of HSFX 7.0.3 ONLY included ver. 1.x of Triggers. I went to Mission4Today and downloaded THEIR version of 7.0.3 and it included Triggers v. 2.x. Weird.

** I simply extracted the files in their FILES folder into mine, which overwrote a few things... likely my triggers!

Originally Posted by wheelsup_cavu

They are aware of the problem and I agree I don't want the ntrk function to be any more broken.



It may exist but I am personally unaware of a stand alone version of the v1.2 Trigger mod. It was incorporated into HSFX v7.03.
HSFX 7.0 to 7.03 patch: http://www.mission4today.com/index.p...etails&id=2313


Wheels

[wheelsup_cavu]

Interesting Tolwyn. There have been confusing situations with docile enemies that have had plenty of fuel while I have been flying online with other group members and now I am wondering if there are two versions of 7.03 since you say that your 7.03 build did not have v1.2 of the Triggers.

Lucky me, I also found another way that the Triggers break the ntrk function today. I was working on a mission and I added a couple of "Message" triggers to keep some notes on the build and a 9.5 hour delay since I did not want them to show up during the mission. I ran it as a dogfight mission and when I tried to record a track I got the dreaded "track not saved" error even though the message was never displayed. I found out about this after flying for over three hours and right after I had dead sticked my P-38 in from 20,000 feet in for a really nice landing without breaking anything.

I removed those Message Triggers and flew the mission again and there were no issues with saving an ntrk.


Wheels

[Tolwyn]

DELETED.
We're all fine here. Nothing to see.

[Tolwyn]

FWIW, the Triggers 1.2 update is simply this file:


B44652ee36c23d32

In the ./files folder.