FSCAI conflict with FSX@WAR SAMs

[cbe0004]

Hello Gents, 

I was doing some testing last night with P3D v4.1, FSX@WAR 1.2.3 update and the latest FSCAI release here. I noticed whenever I had FSCAI running, the FSX@WAR SAMs would not shoot. I replicated this on the base pack and a custom pack.

I could launch the sim without FSCAI, fly to the SAM zone, VRS superbug picks up the tone and the SAM fires.
Then I restarted P3D with FSCAI running and the same SAM sites would stop working.
I also started the sim without FSCAI and had one SAM fire then opened FSCAI in the same flight and the SAMs stopped working. 

Aside from that issue FSCAI seems to be working well with P3D v4.1. 

I am curious if anyone else is having this issue. 

Thanks! 

[StuB]

What theater were you using?
Also, did you try inserting SAM's (you can have up to 10) via CCP while running FSCAI...and also while running both FSCAI and FSX@War?

[cbe0004]

I started using a custom pack created by Ed at USNVA then tried with the base pack alone (Libya v NATO campaign). They both yielded the same results. I have not tried with CCP spawned SAMs but I had the same results with Tacpack spawned SAMs. Basically the FSX@WAR and Tacpack SAMs will detect my aircraft and interact until I open and connect FSCAI (they will spawn but not interact). 

[Travis]

I'm not versed enough to comment on this, but I've brought it to Dutch's attention.

Dutch is getting over from a bad cold which was followed closely by a not-great bout with the flu.

He may be offline for a few more days still, but we're in cross-continental contact.

Regards,

[StuB]

I suggest you try running the test with only FSCAI and CCP running and see if the SAMs work.

If they do work properly , then it's likelu an issue between FSCAI and FSX@War.

If they don't, then its possibly an issue between FSCAI and Tacpack.

Jan 31, 2018 8:21:32 GMT -5 cbe0004 said:

I started using a custom pack created by Ed at USNVA then tried with the base pack alone (Libya v NATO campaign). They both yielded the same results. I have not tried with CCP spawned SAMs but I had the same results with Tacpack spawned SAMs. Basically the FSX@WAR and Tacpack SAMs will detect my aircraft and interact until I open and connect FSCAI (they will spawn but not interact). 

[cbe0004]

Jan 31, 2018 12:56:58 GMT -5 Travis said:

I'm not versed enough to comment on this, but I've brought it to Dutch's attention.

Dutch is getting over from a bad cold which was followed closely by a not-great bout with the flu.

He may be offline for a few more days still, but we're in cross-continental contact.

Regards,

Thanks Travis I appreciate it! Hope Dutch gets to feeling better. 



StuB:

I will try that tonight. I did not have time last night to try it. I suspect the same results because the issue is replicated with FSX@WAR SAMs and TacPack spawned SAMs. I will try just CCP and FSCAI tonight. 

[cbe0004]

StuB:

I tried a little bit of testing last night running CCP and FSCAI only. I departed NAS Pensacola and placed SAMs at Eglin with AAA halfway between. The SAMs locked and fired. However, FSCAI never brought up the list of spawned AAA even though CCP said they started and also when placed them 20 feet in front of me. 

Are you running FSCAI as admin? Have you been able to run the SAMs and AAA together? I am trying to rule out if it is a configuration issue. 

[Dutch Owen]

Yes, I'm going to update my FSX@War, purchase Tacpack for V4, and have a look at this today.

With both V4 and Tacpack for V4 being new, I'm sure there are some issues that need to be worked out. We certainly don't want to have any conflicts with their weapons.

Dutch

[motus]

Hi Dutch,

Happy to see you again. I hope your are fine now.

Tell me if I can help you for FSX@War part.

Motus

[cbe0004]

Thanks Dutch I'm glad you're back! And thanks Motus for your support without FSX@WAR we would all be flying rubber dog crap out of Hong Kong!