Moon_chilD

So, first time since the Release but I guess I should report it then: I got a server crash again. I'm still not sure if theses crashes are really ACE related (because some people already reported crashes without ACE). I think its more that the game/server at some point can't handle any more spawning and/or caching of AI. I have a mission (I stress tested ALiVE abit today) where I let many AI Units spawn (CSAT, AAF and Civilians). All went fine. But at some point (I was flying with the ALiVE Combat Support) the game froze and the RAM Usage on the server was raising each sec. When it hit about 3000MB it crashes with a memory related error (sorry, I missed to catch it T^T) I'll now give you the mission I used. Be aware that you'll need certain mods to launch it...but for testing sake... To maybe find out what goes wrong I'll upload it anyway. (Mods are: Euroforce, MCC, ACE, CBA and ALiVE)(That should be all needed mods in order to run the mission, if not let me know) (Poor editing skills incoming xD) https://drive.google.com/file/d/0B4x7N57WyGnSaTF4NmhiVFNzeG8/view?usp=sharing This is the RPT of the mission when it crashed. There are MANY entries and I don't know if something is going on in the mission or if thats due to the performance build #18 by dwarden! https://drive.google.com/file/d/0B4x7N57WyGnSOFNwR2U1dlFIRVU/view?usp=sharing I'll maybe have some test with only ALiVE tomorrow but I am not entirely sure if I find the time! ^^ (Don't hesitate to ask me questions here, via PM or on Steam) Many Greetings Moony

Hey send me you mission file(via pm) and I'll have a look on it!

(Posted the same in the VCOM Thread) So little input here. Got some help from TeTeT today. Looks like he solved the mystery behind that VCOM and ALiVE Combat Support. Instead of this: {_x setVariable ["NOAI",true];} ForEach crew this; you need to use this: {_x setVariable ["NOAI",true];} ForEach crew (this); (I've been told that the false is not needed because its default anyway) That is the explanation by SpyderBlack: For now that worked with the Test3 Version of VCOM and the Combat Support is finally obeying! Now I can die in peace! Many Greetings Moony

So little input here. Got some help from TeTeT today. Looks like he solved the mystery behind that VCOM and ALiVE Combat Support. Instead of this: {_x setVariable ["NOAI",true];} ForEach crew this; you need to use this: {_x setVariable ["NOAI",true];} ForEach crew (this); (I've been told that the false is not needed because its default anyway) That is the explanation by SpyderBlack: For now that worked with the Test3 Version of VCOM and the Combat Support is finally obeying! Now I can die in peace! Many Greetings Moony Edit: Now I hope that I and the rest can finally stop bothering "genesis92x". Thanks for the patience, help and VCOM overall!

So I tested a bit. When using this: {_x setVariable ["NOAI",true,false];} ForEach crew this; I get: Error in expression <} ForEach crew _this select 0> Error position: <} ForEach crew _this select 0> Error Missing { Thats probably why the script is not applied at all!

Gonna make some more Tests tomorrow but first testing doesn't look that promising! T^T

Okay, I tested it with the Test 3 Mod Version. It still does not work. I'm gonna go into more detail though. The Problem is: I want to exclude the ALiVE Combat Support from VCOM because it breaks the Combat Support. For that purpose ALiVE has a "Code" Line build in. This "Code" will be run on the Vehicle that is spawned for Combat Support. When the Vehicle spawns nothing strange happens. As it is supposed to be, it just stands on its spot. But when I call for Combat Support the following happens: As you can see I marked several things. First I marked the two CAS Support I call. A Attack Helicopter and a Plane. After the Lift of they fly where the red line is pointing to (the Green Circled Marker). The things on the Green Circled Marker are three HQ - Blufor, Opfor and Indfor. No object is spawned there...just these markings...or whatever it is. Anyway, as you can see the Chopper was flying over there and actually landed o.O keeping it destroyed. What they where supposed to do (and what they do without VCOM enabled) is flying along the Blue line. I use this Code on each unit: this setVariable ["NOAI",true,false]; this setVariable ["VCOM_NOPATHING_Unit",true,false]; but I'm very sure the same happens with just: this setVariable ["NOAI",true,false]; This is driving me insane. I really want to use VCOM because it works SO good T^T Also my second question is still unanswered (for me ^^): When using VCOM AI, should I still install VCOM Driving or is it build into VCOM as well?

So I did some testing. And I cannot get VCOM to be disabled on a unit. Here you find my Test Mission. I use the Addon Version of VCOM! Obviously marker are supposed to be turned on as well as Debug. As you can see, each unit, even those I applied the following codes to, are using VCOM AI. (Clearly visibly due to the arrows above them. And their behaviour!) this setVariable ["NOAI",1,false]; this setVariable ["VCOM_NOPATHING_Unit",1,false]; or this setVariable ["NOAI",true,false]; this setVariable ["VCOM_NOPATHING_Unit",true,false]; I really need VCOM to be disabled on some units (mostly due to ALiVE's Combat Support!). Is there any way to do it? On another Note: I have another question. When using VCOM AI, should I still install VCOM Driving or is it build into VCOM as well? Many Greetings Moony

I think you kinda misunderstood me (Happens a lot lately): I want the same. I want the ALiVE Combat Support not to be affected by VCOM at all. But I can't get it to work. However, I'll just try out the new version. Maybe it'll magically work! T^T Edit: Test and no, it does not work with that new version either!

Same here with ALiVE Combat Support...tied so many things. Of course I tried the things on the first post...they just not get excluded from VCOM. Any Idea on that?

Are you sure you mean "the Alive CAS Module Initialization"? Because that does not work for me. My Artillery is still engaging any Target on the map by themself. (Even if they are very far away) I managed to disable VCOM of any other ALiVE CS via the "Code" field of the ALiVE CS. Only the Artillery is causing HUGE problems since I can not disable the VCOM AI on it. I even tried it with a Trigger. Type: None Activation: BLUFOR Repeadedly Present Condition: ({(typeOf _x == "IP_B_MBT_01_mlrs_F_EFAltis");} count thisList) > 0; On Activation: {if (typeOf _x == "IP_B_MBT_01_mlrs_F_EFAltis") then {_x setVariable ["NOAI",1]; _x setVariable ["VCOM_NOPATHING_Unit",1,false]};} forEach thisList; I mean, you I could just go without the Artillery...but it would be sooo cool!

That sounds good. A problem I see now is, lets say the Artillery does get destroyed and needs to be respawned...in that case I think I need to apply the command again. Therefore I think a Trigger would be a better idea, but I suck at scripting. How could I do that the best way? (sorry for spamming your nice new thread xD)

I wasn't sure if it is possible to Sync Artillery to the modules. I guess I just use this then! :3 The question I have though would be, do I need to sync these units to an vehicle respawn module or does the CS Module still takes care of that?

Wait ALiVE can Handle multiple HC's too? That'd be neat! No No, as I said, I found the trouble maker (Werthles' Headless Module). The Combat support works now as intended and MCC does not interfere with it. Only problem is still the Artillery and the exclusion from VCOM!

Little Update from me here: Thanks @S.Crowe. Then it is right what I did the only problem I have atm is, that the Artillery Combat Support does not have this "Code" field. Therefore (while they listen to my Combat Support Request) they engage enemies at will! I guess the easiest way to fix that would be with a Trigger, hu? I now tested it without VCOM but had the same problem. Now I tested it without HC and it worked. Therefore I expect Werthles' Headless Module to f thinks up. My next test will be Server and one HC with VCOM! Edit: Tested and now I can most definitely tell you that Werthles' Headless Module is incompatible with ALiVE. The Combat Support is working okay with VCOM and just one normal headless client. Though I really need to get Artillery ignored by VCOM. They engage Enemies that are more than 3-5 clicks away. xD

Yeah, I already understood that. The question is where does that code go. In the "code" field or in the "Initialization" field on the CS. I ask because the Artillery CS does not have a "code" field. (Will test it without Vcom soon)

Thanks for the response. We actually use ASR AI. I'll now switch over to VCOM because 1. I can't find an appropriate code and 2. I'm not 100% satisfied with ASR anyway. One question though. Do you mean the "Code" field or the "Initialization" of the Module? Because if you mean the First, the Artillery does not have such a field!

You might have missunderstood me. When I said they told me its been caused by HCs I meant like some time ago. (Some month) With "But they stated they fixed it." I meant that they wrote in the Changelog they fixed it while it is still not working for me. (Again, that might be a mod incompatibility. I'm still testing around)

Okay, if thats intentional thats cool for me! ^^ I already have been told, that the issues where caused by the Headless Client. But they stated they fixed it.

Hey guys, Congrats on Version 1.0! I was very excited to finally test it with the problems I had before (Mainly Combat Support not working and crashes when using with MCC or ACE). Good news is, the server did not crash for me while I was using the same mission, where it crashed last week. I'll give it more tries though! Just to make sure! Sadly the Combat Support is still not working. When Calling in Artillery they still keep saying they fire, but they don't! When Calling in Chopper to "Land" (with Engine Active) they Land and immediately go in the air again. When using Insertion with a Chopper they just hover at the destination. Is that intended...do I need to do something? (Didn't it throw out ropes before?) CAS's still not working (either Plane or Chopper) with a SAD Order! Something new that happens now: On mission start the CAS Planes taxi to the runway and lifiting off by themself. When they respawn they wait with the cockpit open. I think thats all that happens. I'm pretty sure that at least number 5 might be caused by another mod (MCC?). Does the rest not work due to Werthles' Headless Module because we are using 3 headless clients in our mission? Thats all for me now. I'll test some more later. Many Greetings Moony

That is very odd. You should be able to get rid of it by simply delete the pbo's. My group uses that without any problem for about two month now. Make sure only these for files are in the addons folder of the movement mod: babe_core.pbo babe_core.pbo.badbensonEM.bisign babe_em.pbo babe_em.pbo.badbensonEM.bisign If you have that only the advance movement should appear in the ESC Menu. And the climbing works...it does for me!

I shared my log already. If its wanted I can also upload the mission....though it uses a bunch of other mods as well!

Yeah but it might just be a tiny setting that Fs everything up!

Yes, when you drive fast you can't turn at all. If you drive slow it is possible (while still a bit wanky ^^)

The cause is that the Windowskey is supposed to bring you from your main program to the start menu (by sometimes minimizing said program). The solution is to deactivate that or change ACE's keybindings!