Ciribob

I think your significant other will be very grateful the server is down! Sounds like a productive time [emoji14] We've fixed all the scripting issues, so the server does run but the performance and stability are too poor to leave the server up unfortunately. Should be fine with the next patch from ED as issues are reported internally :) Sorry there's not more we can do! Sent from my ONEPLUS A3003 using Tapatalk

Had a good play around can't get it working either - my sample mission doesnt work either for this so I'll test on an internal build and report if it doesnt work there too! :) Thanks for reporting!

Thought I said it a while ago but yes, we'll probably add the weather rotation we had before where there are a few different options that are randomly cycled, including nigh time! Yup - Problem is mirage & possibly gazelles too - not checked in a while. For Normany - capture will be by TF, thats planned for now but Normandy is I think also down for now as it's being worked on by Xcom currently - so yes WIP :)

Thank you very much uboats :) Sent from my ONEPLUS A3003 using Tapatalk

Check out the new Normandy server when it's up. Xcom has been working hard on it and it has ships :) Because of the mirage and a few other airframes. There are no red specific skins and I've had to set the skin by editing the mission file manually ( not very fun & dangerous). Afaik there is no way to limit the skins, it appears to give you the full list available to that aircraft the same as the mission editor. It'll just add to IFF confusion if everyone uses it. Yes people should use Comms but this at least helps a bit with FF. :) Sent from my ONEPLUS A3003 using Tapatalk

Were you damaged or were the radios turned off / have enough power? If there is a problem between dcs and the SRS you'll get nothing on any radio. If you have some radios and not others working in an airframe then that is DCS telling SRS that. :) Sent from my ONEPLUS A3003 using Tapatalk

You are right, the line of sight calculation is ray tracing, distance is not... And I already calculate 2d distance in that way. Either way, please check out the timings I've already provided. I don't get all players and then iterate and do distance and then line of sight calculations for ewr or jtac, that's relatively slow (jtac used too). I use a different method provided by DCS. In DCS there is also only a main event loop, no multithreading (co routine is not multithreading). Most things in BF are event driven as well to reduce processing times even further. Edit: the slowest part I think I remember is actually getting the list of players or units as you have to do various checks to make sure they are valid before you use them Sent from my ONEPLUS A3003 using Tapatalk

If skin changes can be seen by other clients then yes we'll disable it. :) CTLD & dynamic spawning is now fixed but the lag caused by radars is unavoidable until patch unfortunately. Please stop arguing about mods, open a new thread for that - IC will always be on on BF so it really doesnt affect this server. Regarding using trigger zones instead of ray tracing, Trigger zones are ray tracing (or if not they'll be slower than current implementation) :) so no need for trigger zones. As I said somewhere before, any lag is not due to scripts any more as they're as optimised as can be. Timings are somewhere in this thread but basically bugger all :)

Not anymore its not... As long as you have the latest version :) Sent from my ONEPLUS A3003 using Tapatalk

Update Due to lag & Heavy stutter for chopper pilots on 1.5.7 and stability issues BlueFlag is on hold until the next update. Will work through and report any bugs not already reported internally :) Regarding skins - Swapping skins only shows client side (its just for you) so doesnt need to be disabled as it doesnt affect anyone else.

Try waiting for a while, the BlueFlag server took a lot longer to start than normal Sent from my ONEPLUS A3003 using Tapatalk

When it's fixed... [emoji14] Sent from my ONEPLUS A3003 using Tapatalk

Sorry to say - server is offline until further notice. Can't get the server to stay up - will be running closed tests to narrow down what it is. No errors or logs so tricky to work out. Please don't argue about mods here, not really a BF topic as we will always run with IC on in actual rounds :) Sent from my ONEPLUS A3003 using Tapatalk

Server having issues staying up - not sure why. As a quick test, turned off Pure Client enforcement. Please don't make us regret it.... :)

Server is back up Takes a little longer to load up the map with the update so dont connected unless 2 minutes have passed (you wont be able too and you'll just get frustrated!) to give the map time to setup everything :) Interesting to see if performance is better or worse, nothing changed map wise so its just DCS thats changed. Edit: the Pure Client system seems a bit stricter, check you've got a green shield before connecting. Click the shield to see what made it angry - likely terrain mod as thats now a little more protected I think Seeing quite a few kicked by it: [19:57:34] NEUTRAL player =RvE=Snowman disconnected Reason:Client is tainted [19:57:45] NEUTRAL player DIAMOND 2-1 | Kozar disconnected Reason:Client is tainted

Just join, wait a minute or so and someone else will join. Someone has to go first but others usually follow quite quickly. :) The above is something we can't solve unfortunately.

From the logs i checked last night, it looked like you hadn't destroyed everything so you couldnt capture. The fact its now captured seems to confirm :) DCS controls repair & rearm at an airfield so it possible that you can do that, even if its not in your coalition depending on DCS. Should be rare though. The final say on if there are defenders or not is PAK info. If it says defenders present there are troops of some kind in the capture area. Thanks for the reports though - can you do a Pak Info screenshot if you want to report possible future bugs? helps me debug as well :) Another good test is bombers, they will find targets no matter what. Jtac is also very helpful but it must have line of sight to report an enemy. I'll check, should be a pair of TFs at every airfield (but not roadbases by design :) ( Anapa was literally the first base added to the new scripts so there is probably a wrongly named group. I'll check. The capture code is the same for all bases - I can also see Uckulan just got capped so its working in general which is good. Server will be updated shortly to the new 1.5.7 so dont forget to update if you cant see the server

Unfortunately literally everything can cause DCS to lag (slow / long connections etc) but ED have done a great job with server stability since the multiplayer test. It's very rare for a server crash now. The aircraft are all loaded at the start of the mission to avoid SERVER lag, as if the server is lagging, everyone lags / warps around while it pauses to load a model. From the testing I've done it seems you don't need to leave the model up, once loaded, the server is happy and clients will either load it anyway on entering the server or they're loading a low poly quick one anyway as there doesn't appear to be lag client side when spawning aircraft as people slot in. Made the change late late night for Defenders spawn so thy'll spawn within a 20m circle of the center of the base. If you see any odd spawn locations for them, please let me know :)

What soundcard do you have? SRS uses the same audio APIs as TeamSpeak, do you have the same issue with that? Either way it sounds like DCS is somehow set to take "exclusive access" of your sound. https://help.uaudio.com/hc/en-us/articles/211166003-How-to-Disable-Exclusive-Mode-in-Windows-Sound-Preferences ^ will show you how to stop that so they all work together :)

Not tested.... but try this one attached. Look at the section in the script that matches the sample below - It has been configured so Gazelles of any type can only transport troops but not crates. Swap the true and false round to do the opposite :) -- ************** Allowable actions for UNIT TYPES ****************** -- Put the name of the Unit you want to limit actions for -- NOTE - the unit must've been listed in the transportPilotNames list above -- This can be used in conjunction with the options above for group sizes -- By default you can load both crates and troops unless overridden below -- i.e -- ["UH-1H"] = {crates=true, troops=false}, -- -- Will limit UH1 to only transport CRATES but NOT TROOPS -- -- ["SA342Mistral"] = {crates=false, troops=true}, -- Will allow Mistral Gazelle to only transport crates, not troops ctld.unitActions = { -- Remove the -- below to turn on options ["SA342Mistral"] = {crates=false, troops=true}, ["SA342L"] = {crates=false, troops=true}, ["SA342M"] = {crates=false, troops=true}, } Let me know how you get on or if there are any issues CTLD.lua

Ah sorry, totally forgot. Was sorting BF. Will look at it tonight :) Sent from my ONEPLUS A3003 using Tapatalk

Correct on both. Repair will reset timer :) Sent from my ONEPLUS A3003 using Tapatalk

Thanks! Thats very helpful. Will change the logic so they always spawn at the center of the zone, and i'll make sure that the center of all the zones is in an open area. Does make them slightly easier to find but it's better than losing them in the trees / buildings/ They shouldn't be.... I'll double check. They will be removed over time now, as will JTAC and Stingers / Iglas. Times are below in minutes: JTAC - 380 Ammo Truck - 220 IGLA / Stinger - 220 Kub - 180 EWR - 380 Units are only removed at the start of a 3 hour round so if a unit is set to live for 4 hours, it'll be present in two 3 hour rounds and removed in the 3rd round (so after 9 hours max)

Can you let me know which places you've seen it happen at? I'll double check but they should always spawn at the "center" of the base (where the marker puts it on the online map) but I think I added a radius around that spawn. Either way if you let me know, i'll move the center to ensure they dont spawn in trees. Thanks for the report! :)