ENO Posted October 28, 2013 Posted October 28, 2013 We experienced a de-sync between the server and the clients last night. When I went back to the server to check up on it, it turned out I had one of those "error in error handling" errors. I went back and looked in the log and there were no signs of where it went wrong (I've seen it trace back to particular lines in the mission.lua before- but it didn't this time.) So I went into the mission.lua anyway and looked at the mist section- and came across the entry in the attached .jpeg. It's the only line in the entire section that is "off" and probably not coincidentally that is within a line of the last successful trigger that we saw (the one above it saying that half the escaping busses have been destroyed was that last one we saw). When I was looking at the last issue I had in another mission, it related to the "off" script- but I'd been guided there by a trace back call in the dcs.log. Is scanning this section of the mission.lua a good way to go and hunt down errors before the missions go out the world? Thanks guy... "ENO" Type in anger and you will make the greatest post you will ever regret. "Sweetest's" Military Aviation Art
Recommended Posts