Search results

You either are missing a prefix in your packer, or your packer is corrupting your file most likely.

They will, they just don't react very well to them from what I can tell. I've seen them kill animals, and shoot at planes with civilians in them.

You're quoting the wrong person who is having code issues lol. rsx is just asking about making them more difficult, his missions are working.

You can't run EM1 as its the first prototype Epoch mission. The area in the DZMSBox.sqf that is supply and money are Epoch only. You can keep your DZMSBox.sqf. I'd assume how well they handle the weapon shake.

Can you post your RPT log? There are no timeouts as each mission offers considerable loot, so users shouldn't pick and choose which missions to do, at least in my opinion. There will only be one Major Mission and one Minor Mission on the map at one time. That code is indeed the only way to...

Static guns and Launchers are intended future features. At the moment, DZMS does not support this.

You need to add entries for them into the CfgLoot files if you want loot. I don't think they spawn loot in Napf.

No. They aren't roaming AI, just missions.

To add the one new prototype Epoch mission you need to open DZMSConfig and find this array: DZMSMajorArray = ["SM1","SM2","SM3","SM4","SM5","SM6"]; and add EM1 DZMSMajorArray = ["SM1","SM2","SM3","SM4","SM5","SM6","EM1"];

If you are running the newest version, the missions should be spawning everywhere. If not, find this line in DZMSFunctions.sqf: _pos = [_centerPos,0,5500,60,0,20,0] call BIS_fnc_findSafePos; and make the 5500 larger.

Major Missions Revamps are now released. This Includes an AN2 Drop mission, and a Prototype C130 Epoch Specific Mission.

I found out the problem. If you use the newest files on the github it will work. It was a scope error. The variable was defined within the if, so it was undefined outside the if.

Under _tavHeight = (getPosASL _tavTest) select 2; put diag_log format ["[DZMS]: DEBUG: TavTestPos:%1", str(getPosASL _tavTest)];

Unless you are messing up the line install, I don't see how that could be caused by DZMS as DZMS hasn't even ran yet at that point.

Only one more thing I can think of, and that is that for whatever reason, height might be returning an array. Change the diag_log line to this. diag_log format ["[DZMS]: DEBUG: Pos:[%1,%2] / noWater?:%3 / okDistance?:%4 / TaviHeight:%5", _posX, _posY, _noWater, _okDis, str(_tavHeight)];

I apologize for how many times I'm having you run code, but I have one more fix to try before I'll just revert the tavi height check. _tavHeight = (getPosASL _tavTest) select 2; becomes _tavHeight = ((getPosASL _tavTest) select 2); This is really boggling my mind as this exact code works as-is...

Remove this line: deleteVehicle _tavTest; and above this line //Lets check for minimum mission separation distance Add this: if (isNull _tavTest) then { diag_log format ["[DZMS]: DEBUG: TavTest is Null"]; };

Above _tavHeight = (getPosASL _tavTest) select 2; add sleep 3; Then retry it with the debug line still there.

I might make it an array of coordinates and distance it will check against, but it might be a while before I add that. I'll look into it.

Install the newest version from the github, and in DZMS Functions.sqf find this line: //diag_log format ["[DZMS]: DEBUG: Pos:[%1,%2] / noWater?:%3 / okDistance?:%4 / TaviHeight:%5", _posX, _posY, _noWater, _okDis, _tavHeight]; and remove the // I want to see if the height is still coming back...