SNAFU

Here the testmission I use... EVENT_SHOT_test.zip

Ok thanks. My first post here was related to 1.5.3. I don´t know what could be the cause, but the same/different IP since there are no mods on the dedicated server and the mission is the same. singleplayer/host client same IP as server client different IP then server 1.5.3 yes no not tested 1.5.4 yes yes no

I have tested this in the latest 1.5.4 stable release. When I host a mission on my laptop and join with my PC, I can trigger the event "SHOT" as client, without being the host. Here I use the same router, so I have the same IP (Sever IP == Client IP When I host the same mission on a dedicated server machine and join with my PC, I cannot trigger the event "SHOT". Here I do not have the same IP (Server IP ~= Client IP) So in first test, when I used my laptop and notebook, all seemed fine, now when we try to run our campaing, the mission doesn´t work as intended. Here is the script-part I use, if anybody gets the chance to test this on his dedicated server Eventmanager = {} function Eventmanager:onEvent(event) if event.id == world.event.S_EVENT_SHOT then trigger.action.outText("EVENT_SHOT triggered", 10) --... end end world.addEventHandler(Eventmanager) Mayby someone from the 132nd, of which I know use extensive scripting for their dedicated server campaigns, or other how use Training Range feedback scripts on their server have similar experience?

They didn´t respond to radio requests. Since then I always have EWR as second in the group, so I do not know if there is still an issue.

Ed Rasimus wrote in Palace Cobra that in the early versions of the F-4, the pilots were strictly told not to use the ailerons to roll, but only rudders. So they only used the stick for pitch control. Adverse yaw effects were so strong when moving ailerons a bit too fast, that some pilots new to the F-4 lost control and crashed. So it all depends on the airframe and the situation.

Same as 609_Relentov, I always use this kind of structure to repeat functions and that works well: function repeatedfunction() --[[ content --]] return timer.getTime() + 10 end timer.scheduleFunction(repeatedfunction, nil, timer.getTime() + 3) Did I miss something?

It is implemented in the A-10C, so should not be too much to add this function to the Tiger, if this was part of the F-5E modell. Helps also in BFM training.

Interesting to read these experience... I notice that you can have almost unlimited static units and that many the active AI does cause performance issues, so I limited myself to 300-600 active units (I wrote a little script which removes all non-essential groups and counts the units after mission start to better control performance) but have no limit for statics. Are these 2000 units active units or active units with switched off AI or statics?

I noticed that EWRs do not function as EWR, when they are the first unit in a group. Might be related to this, or is this bug fixed meanwhile?

I used to play the ground commander/ game master in our squad campaign and noticed in pre 1.5 missions, that giving more than 3 groups orders to move to a certain place or along a road causes terrible lags after about an hour. So I limited myself to have at most 3 groups moving at the same time and this prevented the lag. I hope this improved in 1.5. since we just wanted to continue the campaign after a longer break, but your report doesn´t give me much hope. In this regard is CA and mulitplayer a real joke. We use a dedicated server machine, with a graphic card (don´t know which one. but we just moved onto a new machine last fall) have the server also a minimum grphic settings and set to F-10 map. Usually we have 10 clients and around 300-500 ground units and lag sets in after one hour, when about 5 ground groups are moving at the same time.

I didn´t do some in-deep testing, just checked the debugging messages and they seemed to be ok. At least it indicated that most of the radars were dark and only one searching. The debugging also correctly counted the SAM launches. If the other radars were really off, I don´t know. There were are are issues with the Group AI ON/OFF so it is likely that the script is not 100% working as intended, but I only tested it briefly. At the moment I would not expect any script to really work as intended, there are simply too many bugs in the scripting environment, so at some point I just gave up and wait for the next patch.

I have no issues with the script... at least I did not notice anything while haveing the debugging messages running. :huh:

Danke für den Link. ... und wieder der obligatorische Gesichtsventilator, wenn es mal wieder Stau auf dem Taxi gibt. Fehlt nur noch der Bleistift- und Cola-Dosenhalter...

Impressive human. Impressive life he lived.

Great news. Looking forward for the update! Thank you.

Disregard transmission. Found the option.

Is the group generated by script? Then it is a bug. Otherwise it might be related to one of the units being a MANPADS or other static kind of infantry like mortar.

Willkommen im Forum, Joysticks gibt es in fast allen Preisregionen. Der Thrustmaster T.16000 soll als günstiger Joystick ganz brauchbar sein. Zeitweise gab es den für 10€ im Angbot. Wenn du ein Einsteiger HOTAS (Joystick und Schubregler mit vielen Einstellmöglichkeiten) System dir leisten willst, ist der X-52 von Saitek ganz ok. Wenn du mehr Geld zur Verfügung hast, ist der Thrustmaster Warthog mit solider Qualität ganz beliebt und empfehlenswert, hat aber auch seinen Preis. Gebraucht gibt es doch noch ganz gute Angebote. Sollte mit etwas Pflege eigentlich recht lange halten, zumindest länger als der Saitek, der nach ein 5 Jahren doch recht ausgeleiert ist. Wenn du ForceFeedback haben willst gibt es da nur noch wenig Auswahl. Die MiG-29A/S gibt es in DCS auch zu fliegen, allerdings nicht umsonst. Dafür mußt du dir FC3 als Modul kaufen.

Being fit and healthy is the best thing in the world. At the end of the day, in many cases living longer means only to suffer longer. I guess the "middle route" is still the best.

It seems that the script is looking for a group with the name "redborderline". By default the name of the group the script is looking for is "redborder". I guess you edited the script somewhere and now he cannot find the group "redborderline" anymore? I also recomment to use the latest MIST version. 3.3.2 is not combining well with DCS 1.5+, as far as I know.

Wir haben gerade die L-39ZA als AFAC genutzt. Ich bin 2h im Rücksitz geflogen und habe A-10C als AFAC als Ziele eingewiesen. Dabei waren Pilot und ich als Backseater Clients. Wir hatten keinerlei Probleme die ganzen 2h, wobei wir aber auch nicht die Kontrolle wechselten. Das klappt immerhin ganz gut. Beim BFM Training kam es allerdings auch zu ungewollten Verpuffungen, beim Zusteigen oder Konrolle wechseln. Ich hoffe das ist korrigierbar und nicht tief im Netcode verwurzelt, sonst können 3rd Party Developer die auf 2sitzer investieren ihren Laden dich machen, oder zumindest Projekte wie die F-14 werden zu Trauerveranstaltungen.

I ran into a micro-stutters with my current mission, too. Curernt release version, Caucasus, Singleplayer tested out of ME. A: Full mission has 780 units (half of them are on late activation), SW texture mod, alot of scripts -> Stutters every 1,5-2 second B: As A, but now with original textures -> stuttes the same C: As A, but deleted all scripts .> stutters the same D: As C, but deleted half of the units down to 300 active units -> stutters the same E: As D, but deleted all units, so no scripts, no units, SW texture mod -> stutters are gone In a very a similar mission, I played 2 days before, I had no stutters. My next step would be, do write a script, which removes the ground groups one by one and displays the name of the removed group. Maybe it is possible to sort the group and therefore unit out, which causes the stutter, or is this already solved? PS: There is a SA-10 Side new in this mission and I just found this one here: http://forums.eagle.ru/showthread.php?t=165711&highlight=stutter Might be related to the SA-10 TR or SR?

Thanks for the info.

Hey shamandgg, Since I cannot attach files to PMs, I just pick up your question here, where it originated from I guess. As Ciribob suggested, it should work to change a flag value as outlined. If you want to considere the coaltion the playerunit is, you just include an if-then loop into this for each coalition. You try to add the following lines in the function function Csar.rescuePilots(_heliUnit) local _redflag = 1--enter the number of the flag here local _blueflag = 2--enter the number of the flag here local _heliUnitcoaltion = Unit.getCoalition(_heliUnit) if _heliUnitcoaltion == 1 then local _blueflagvalue = trigger.misc.getUserFlag(blueflag) trigger.action.setUserFlag(redflag,_redflagvalue+1) trigger.action.outText("Red Pilot rescued. Flag #"..string.format(_redflag).." was increased by one.\n\nFlagvalue is now: "..string.format(_blueflagvalue),20) end if _heliUnitcoaltion == 2 then local _redflagvalue = trigger.misc.getUserFlag(redflag) trigger.action.setUserFlag(blueflag,_blueflagvalue+1) trigger.action.outText("Blue Pilot rescued. Flag #"..string.format(_blueflag).." was increased by one.\n\nFlagvalue is now: "..string.format(_redflagvalue),20) end I had no time to test and debugg this. This fun would be up to you. :music_whistling: Attached you also find the CSAR.lua which I modified to show you were to add the lines. Let me know, if this works for you. CSAR_Mod51th_v0.lua

I would like to add this bug to the list: Clients do not trigger the event SHOT in mulitplayer environment anymore. See individual bug report here: http://forums.eagle.ru/showthread.php?t=168435 Our squadron is running a script which manages ressources during a longer campaing and this event is important to count the spent ammunition operational costs. Many other scripts, like geting the accuracy of weapon deliveries on the weapon range, simulating duds and scripting smoke rockets for the L-39 is broken again.