Greyl

Just a quick update to my problem(s): Took your advice Stone and rearranged my triggers (just as a side not, MiST was being run from the initialization field at the bottom of the triggers setup page, not in a mission start trigger, which I changed to look like your demo mission) and changed the fields u had suggested in your previous post. It didn't get rid of the frame stutter completely, but lessened it drastically. Although I could still see the frame stuttering on my computer, in a play test on TAW's servers it ran great, and I wasn't even able to notice any frame stuttering. After the play test I upgraded to MiST 3.6.44 and that resolved the problem even on my machine. So thank you very much. :thumbup: The only problem we ran into on the play test was with CAP aircraft wandering over to the Blue starting area (Tblisi-Lochini) and basically camping there. In subsequent testing, it seems that CAP aircraft that engage in air-to-air combat, but are not killed tend to wander around the map (in my case, wandering east), regardless of borders or detection zones, rather than returning to their CAP zones or airfields. My quick solution for this was to just put down a few blue SAM sites (Patriot at the airbase(s), HAWK's at the FARP's, etc.) to shoot down any aircraft that display this behavior before they become a problem, which works fine. I was just wondering if maybe u had some suggestions or insight into why this would be happening, or maybe its just something that can't be fixed, and work arounds like mine are the best way to go. Thanks again for any help, Greyl

Thanks for the help guys. Tried turning the debugging off, but still getting the frame stutter, and it gets worse as the mission continues. Here is the mission file: https://drive.google.com/file/d/0B2nYItlUBtCxV0hqN2dXdjF6T1U/view?usp=sharing The blue fighters (2x f-14A's and 4x F/A-18C's) are there for testing GCI and it is easier to notice the frame stuttering when they are dogfighting with the CAP aircraft. The final version they will be removed. Hope that link works, never shared a .miz before. Let me know if it doesn't work. Greyl

Hello, Had a question along the same lines as Pikey on page 37. I have been getting the same debugging error he posted about (debuggingmessage interceptmain completed: counter: X/ side: red) with X counting up continuously. I understand how to turn the debugging off and on and that works fine, my question is what is that message for, and is the script supposed to be doing that? If it is not normal for the script, how would I go about fixing it? Everything else is working fine, and the only real departure from the norm is that there is no blue side CAP/GCI flights (they are all player controlled) in my mission. The message though has occurred for both sides at some point. It is also creating a very small amount of frame stutter that corresponds to the count up. Not enough to notice on the ground, but when aircraft are dogfighting, it is very noticeable. I am using MiST 3.5.37 btw. Any help is very appreciated. Thanks alot, and its a great script! Greyl

In the article Rangi posted (Open the full article), it says the USS Wasp (where these tests are taking place) has already been modified to accomodate the F-35B, including a new composite deck coating with additional heat protection.

You need to send the SU-25's in to strike their targets using the communications menu (\ key). The flights should show up under F10 in the comms menu. This goes for both the Mig-29 and SU-27 campaign's that involve SU-25 strike packages. No idea about the Mig-29S 3D cockpit. Think they are moving all FC3 related topics to this section btw, since it currently does not have its own section.