TonyG

Question regarding the script in multiplayer. We run a training server for our wing, and the script runs on it. On a somewhat regular basis, the script stops responding to commands. It has been in use up to that point, but something happens (we can’t detect any one circumstance) and the only solution is to restart the server. Have you guys run across anything like this in your sessions? Our server can be pretty populated, with 15 pilots coming in and out of the training server as time permits. We’ve had the script stop working with lots of people, and with few people. Sometimes it works fine with no issues. I tried adding a trigger to reload the script after 1 hour, but all it did was duplicate the menu which won’t respond to commands. Any suggestions on this issue?

Here's a track from a MP session where I'm hitting the strafing pit. Runs at the strafing pit are about 22 minutes in. I make two passes. server-20181125-121848.trk

The images don't show where it's impacting. This measures the rounds going into the strafing pit. https://forums.eagle.ru/showthread.php?t=157991 It works.

I set up the strafing range, and with practice, am now scoring significant hits with the canon. You need to make sure the pipper indicates ´IN RANGE’ or you’re never gonna hit anything. Roll in at 4000’ AGL and pull out before 1500’ and it works. Also can do some pretty nice pop up attacks too. I don’t think anything is broken with it.

I’ve used both, I much prefer the VR.

I ported the original mission over to the Persian Gulf, you can find it here. https://forums.eagle.ru/showpost.php?p=3523147&postcount=46

You need to box either TCN or WPT in order to have a nav point for the course line to be based off.

Enter the unit name as hpriority ( you could have dozens of them, they’ll be named hpriority#001, hpriority#002 etc) and the autolase will work through all of the hpriority targets before moving onto anything else.

I used JTAC Autolase to put in multiple JTACs with individual laser codes. They don’t run as a conventional JTAC, rather the laser is always on and you don’t need to radio for runs. Very handy for a training server where you might have multiple squadrons working a range at the same time. https://forums.eagle.ru/showthread.php?t=141297

I can second this bug. I ran a server tonite with about 10-15 participants. At some point the script stopped accepting commands. I don’t know if it’s a situation that was caused by more than 1 player being in a certain aircraft, but as we were running training that was the case. The correct tail numbers were appearing in the list but there is no option to make a call. Resetting it to Case I/CaseIII didn’t make a difference. I can provide the trk file if you’d like.

I was getting the exact same error when CTLD wasn’t loading properly. Are you sure CTLD is loading?

Got it working, thanks for the tips and tricks!

That's quite helpful.... No other suggestions what would cause the script to not recognize bombs entering the trigger zone?

Ahhhhh....that’s probably what I did wrong. Thanks!!!!

I'm trying to add a JTAC with autolase with CTLD. I've got timemore set to load mist and then ctld, both downloaded directly from their sites today with no modifications to either. I keep getting a message error when it loads CTLD indicating an error with line 7 i believe. I've attached the file to see if anyone can point out what I'm doing wrong. This is the error from the log file that shows the error as soon as it tries to load CTLD. 2018-11-10 01:54:19.411 INFO SCRIPTING: Mist version 4.3.74 loaded. 2018-11-10 01:54:42.285 ERROR DCS: Mission script error: : [string "C:\Users\Office\AppData\Local\Temp\DCS.openbeta\/~mis0000462A"]:7: unexpected symbol near '<' Thanks! Tony JTAC Autolase test.miz

Is there a change log so we know what changed? I looked through the first post and didn’t see what changed.

Great video Jar, thanks for sharing. Tons of info!

I’ve got it set up in a mission, the F10 menu is present, I’ve set trigger zones according to the list of target names in the lua, but it’s not detecting drops or hits. Any suggestions on why it’s not recognizing the bombs? MK-83 from a Hornet.

This is a standalone computer used as a server, it's ran flawlessly for 6 months with pretty regular usage as a server, never crashed before. This is the crash log from 45 minutes into a pretty regular mission. Any comments on what would have caused the crash? i5-3570k 16GB ram 7970 GPU dcs.log-20181026-014222.zip

Awesome, thanks!!! Any way of scripting something if you stay in the pattern? After launch, gear stays down, <800’, then you can circle for another pass? It would be good to be able to add in carquals without having to leave the patttern and reenter.

Where are the last 15 recorded? Is this something that can be exported for tracking purposes? I’ve read through this thread but I can’t find anywhere the last 15 are noted. I know I can see them through the F10 menu, it would be nice if the data could be exported.

https://forums.eagle.ru/showthread.php?t=212966

Some how I think the first crash of the virtual F-14 will happen a lot quicker than 9 days after release.

I'd rather arrive overheard with an excess of altitude than to arrive a bit short. Harder to regain altitude than it is to lose height in the case of a fuel emergency. Look up high key/low key approach.

I changed the load out to AIM-120C and AIM-9X. My record is a little under 4 minutes :)