Fulcrum Mission System v2.1a

[horbin]

v1.5b

Some small bug fixes.

Automatic map recognition - no need to configure for your  map.

Tracker Logic available for patrols - icon will follow AI showing an icon on the map.

Smart Mission spawning to prevent encounter overlap and 'drop in' on players and their bases.

 

Note: Map recognition obtains center and size. I still need 'reserved nospawn' regions for other maps. Inputs appreciated!

 

 

 

• Fixed bug that resulted in repeated mission spawning when FuMS Admin Controls where disabled.
• Fixed bug with that was not properly disabling FuMS Admin Tools when set to false. -- ensure your HC folder in mission.pbo is updated!
• Fixed bug that was causing paratroopers to sometimes despawn upon landing.

• Fixed bug with smoking loot boxes not following configured settings.

• Added code to prevent server side HC initialization from hanging if the HC can not be assigned a gender. This will correct issues where the server would not perform object cleanuup for an HC that connects to the server with no identity.

• New AI Logic: ["TRACKROUTE", [spawnloc], [actionloc], [behaviour, speed, [locations], FlagRTB, FlagRoads, FlagDespawn, flyHeight] Identical syntax and behavior is the same as "PatrolRoute", but when this logic is associated with a group in the mission file a symbol appropriate to the group's vehicle will mark the group's movement on the map. (updates every 3 seconds based off the leader's position).

  • See the Test/LandPatrol and HeloPatrols/ missions for example usage.
  • See Docs folder on GitHub for details.

• Smart Mission spawning: Missions using random locations as spawn points will now check for similar type territory within their encounter radius. As an example a "LAND" mission with an encounter radius of 150m will ensure land is present within its radius in all directions. To take advantage of this new check, place the parameter "WATER" or "LAND" after the encounter radius in the mission file. Additionally, the mission MUST be trying to use a 'random' location. (See TestMission01.sqf for details) Example from BikeGang test mission:

  [

  "BikeGang", // Mission Title NOSPACES!

  300, // encounter radius

  "LAND" // location requirement: LAND, WATER, NONE

  // this parameter is optional, but if a value is present it MUST be one of the three above values.
  

  ],

• When spawning, FuMS will check 100m, 200m and 300m N/E/S/W for land. If water found on any check a new random position will be selected. A maximum of 15 attempts are made before settling on a position. Note: PlotPole/Player proximity is still honored for both water and land missions.

• Mission Overlap checking: Missions using random locations as spawn points will now check for other missions within their radius before spawning.

• Automatic world identification. BaseServer.sqf no longer requires information about the world map. Admin's ensure you update your BaseServer.sqf. See \FuMS\HC\Util\GetWorldInfo.sqf for list of currently supported maps. Feedback needed to populate other maps' Exclusion Areas (ie spawn locations)

• FuMS Server side 'theme spawning enable flag' moved to BaseServer.sqf, default is false (OFF)

[Metalfoundry]

I´m completely stuck...  2 questions for you..

 

 

1. I was testing lot of time this missions, decreased the time of mission despawn for testing, if it isnt be done.... now I cant find the variable to increase the time, in which the mission despawns, if nobody goes to it... lol....

 

can somebody help me here.. my brain is overloaded today i think ^^

 

2. I can´t start missions as admin. I defined the admins with the player ID, I added all the SEM mission to the FuMS\Themes\Admin... but I cant spawn any missions..

 

Metal

[horbin]

Mission Respawn - time after a mission finishes before another is created - located in the ThemeData.sqf

 

Mission Duration - controlled by placing a Timer trigger (Ex: ["Timer", 1800] )  in the 'Lose' area of the Triggers section of each mission. 

  (see the TestMission01.sqf and the Docs folder for more details).

 

Most of the stock FuMS missions are not configured with failure conditions, so all remain up until the 'Win' conditions are met.  The one exception is the TownRaid Theme. The missions in this theme only last a certain time, before the AI are picked up by vehicles and leave town, ending the mission.

 

 

For #2.  You do NOT add anything to FuMS\Themes\Admin.  This theme is there for special admin missions.  You can launch any mission from any theme with the admin tools.

 

3 Things you need to do 1st:

Set the Anchor - what player the mission will spawn on.

Set the Source - what device will run the mission (HC or Server)

Set the Mission - select the mission to be launched.

 

Once all three of these are set, you can select the 'launch mission' and the mission will begin.

 

Note: The missions in the admin theme are designed to be manually launched, thus they do not have a 'respawn' time.  If you launch a mission from a different theme that mission will respawn when the 'respawn' timer for that theme expires.

[Metalfoundry]

wow mate, thats fast service.. :D thnx a lot, i´ll look for it.

 

If you need help, testing or sth else, write me a pm.

 

Metal

[MillerTime]

im getting alot of server and client network errors any body got a idea of what to do

 

15:02:02 Server: Network message 86c2 is pending

15:02:02 Server: Network message 86c2 is pending

15:02:02 Server: Network message 86c2 is pending

15:02:02 Server: Network message 86c3 is pending

15:02:02 Server: Network message 86c3 is pending

15:02:02 Server: Network message 86c3 is pending

15:02:02 Server: Network message 86c3 is pending

15:02:02 Server: Network message 86c4 is pending

 

14:15:37 Client: Object 2:5499 (type Type_90) not found.

14:15:38 Client: Object 2:5497 (type Type_90) not found.

14:15:38 Client: Object 2:5503 (type Type_90) not found.

14:15:38 Client: Object 2:5496 (type Type_90) not found.

14:15:38 Client: Object 2:5495 (type Type_90) not found.

14:15:38 Client: Object 2:5494 (type Type_90) not found.

14:15:38 Client: Object 2:5510 (type Type_90) not found.

14:15:38 Client: Object 2:5492 (type Type_90) not found.

14:15:38 Client: Object 2:5518 (type Type_90) not found.

14:15:38 Client: Object 2:5517 (type Type_90) not found.

14:15:38 Client: Object 2:5516 (type Type_90) not found.

14:15:38 Client: Object 2:5515 (type Type_90) not found.

[ReMuS]

HI new FumS work but i have one problem Hc connected: missions spawn! Hc have Disconnect: Mission stay and can not Finished! HC Reconnect: new Mission spawn old mission stay everytime what can i do that when the HC have DC that the NEW HC controll the old Mission again!

[ReMuS]

_players = _box nearEntities ["Man",FuMS_SmokeProximity]>
 6:01:25   Error position: <nearEntities ["Man",FuMS_SmokeProximity]>
 6:01:25   Error 0 elements provided, 3 expected
 6:01:25 File FuMS\HC\Loot\FillLoot.sqf, line 88
 6:01:26 Bad conversion: array
 6:01:26 Error in expression <
while {!_smokeOn} do
{
_players = _box nearEntities ["Man",FuMS_SmokeProximity]>
 6:01:26   Error position: <nearEntities ["Man",FuMS_SmokeProximity]>
 6:01:26   Error 0 elements provided, 3 expected
 6:01:26 File FuMS\HC\Loot\FillLoot.sqf, line 88
 6:01:27 Bad conversion: array
 6:01:27 Error in expression <
while {!_smokeOn} do

[ReMuS]

13:40:10 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:13 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:16 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:19 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:23 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:26 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:29 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:32 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:35 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:38 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:41 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:44 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:46 [ZCP]: Initiate Zupa's Capture Points
13:40:46 [ZCP]: Capture Points is fully running.
13:40:46 Attempt to override final function - bis_fnc_init
13:40:47 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:50 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:50 "<infiSTAR.de> 139.319 - Thread #3: Server #3 waited 120s"
13:40:53 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:56 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:40:56 [ZCP]: No 0 started.
13:40:56 [ZCP]: No 2 started.
13:40:59 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:02 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:05 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:08 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:11 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:14 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:17 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:20 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:23 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:26 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:29 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:32 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:35 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:38 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:41 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:44 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:47 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:49 [ZCP]: Waiting for 0 players to be online.
13:41:49 [ZCP]: 0 players reached, starting cap point.
13:41:50 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:51 [ZCP]: Cap Point Alpha :Spawning dynamic on [23293.3,19294.6,0]
13:41:51 [ZCP]: Cap Point Alpha started.
13:41:53 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:56 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:41:59 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:42:02 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:42:05 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:42:08 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:42:11 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:42:14 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:42:17 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:42:20 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:42:23 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:42:26 "##HeartMonitor: Waiting on Gender for <NULL-object>"
13:42:29 "##HeartMonitor: Gender assignment timeout! No GenderAssigned for HC_HAL"
13:42:29 "##HeartMonitor:HC_HAL: Disconnect detected. Cleaning up the Mess!!!!FuMS_HC_isAlive3"
13:42:29 "##HC_DataCleanup: FuMS_HCIDs:[0,3]"
13:42:29 "##HC_DataCleanup: FuMS_HCNames:["SERVER",""]"
13:42:29 "##HC_DataCleanup: _varName :FuMS_HC_HAL_AIGroups3"
13:42:29 "HC:CLEANUP Groups: 14 deleted from "
13:42:29 "HC:CLEANUP Markers: 8 deleted from FuMS_HC_HAL_Markers3"
13:42:29 "HC:CLEANUP Buildings: 4 deleted from FuMS_HC_HAL_Buildings3"
13:42:29 "HCCLEANUP Triggers: 4 deleted from FuMS_HC_HAL_Triggers3"
13:42:29 "HC:HC_HAL: Complete in 0 secs!FuMS_HC_isAlive3"
13:42:29 "##HeartMonitor: Has ended for HC_HAL:FuMS_HC_isAlive3"

 

 

can anybody help me pls to fix this all

[HerrOrhan]

horbins support is amazing, as soon as you have a problem, he will have the solution a few hours later.

 

no spawn zones: will u need again "upper loft to lower right corner" or will u just place a marker in future?

[rhammer2003]

Hello All,

I am trying this mission and headless client out for the first time, so far I get the missions to spawn however I do not see the headless client on my server, should I see a player connected besides myself when the headless client is running?

I have followed the instructions on the github and  not sure where my problem is located.

I am running a dedi box and have the headless client running from a batch file I created.

[Darth_Rogue]

Having a multitude of errors with 1.5b.  Tried it without making any file changes and also with making edits and limiting the themes to SEM and Small.  Results are the same.  It detects the map Bornholm fine, but according to the logs it's still looking for towns in Altis.  Also, I get three missions spawned in at server start, but gender assignment on the HC fails and then the missions are cleaned up and will not spawn again.  Logs are attached.  

 

 

 

FuMS Logs.zip

[Darth_Rogue]

Finding a suitable position needs a little work too.  This is from v1.4

 

[ReMuS]

Having a multitude of errors with 1.5b.  Tried it without making any file changes and also with making edits and limiting the themes to SEM and Small.  Results are the same.  It detects the map Bornholm fine, but according to the logs it's still looking for towns in Altis.  Also, I get three missions spawned in at server start, but gender assignment on the HC fails and then the missions are cleaned up and will not spawn again.  Logs are attached.  

 

 

 

FuMS Logs.zip

same here -.-

[horbin]

10:59:49 "##HeartMonitor: Waiting on Gender for HC_HAL"

10:59:51 No speaker given for Abdullah Haidari

10:59:51 Speaker Male01_F not found in CfgVoiceTypes

10:59:52 "##HeartMonitor: Waiting on Gender for <NULL-object>"

 

See the above clip.  Between time 10:59:49 and 10:59:52 something is cleaning up global variables on the server.

 

For those experiencing the problem with NULL-object Gender, please try and run FuMS without Infistar or any other HC addon and let me know if the problem persists.

 

 

Darth,

  I also saw in your logs via a report from A3EAI that the HC connected as L Charlie 1-2:1 Remote.  I think this is a 'player' slot. The HC should not be connecting there if you have the HC config in the 1st slot in the mission.sqm.

[horbin]

If you are going to use FuMS on a map different from ALTIS, you WILL need to check some of the themes.

 

Outside of the 'Test' theme, the only one that is MAP dependent is HeloPatrols.  An admin will need to set the city names up for where he wants the helo's to patrol.

 

All other themes are not map specific.

[horbin]

If you log in as 'admin' on your server, you should see the HC in the lobby with the 'Logic' icon next to it.

[horbin]

Suitable positions have been dramatically tweaked in v1.5b. Hopefully ya wont see that sort of thing all too often.....though with 'random' picked locations and custom maps, nothing is a promise :)

[Darth_Rogue]

 

10:59:49 "##HeartMonitor: Waiting on Gender for HC_HAL"

10:59:51 No speaker given for Abdullah Haidari

10:59:51 Speaker Male01_F not found in CfgVoiceTypes

10:59:52 "##HeartMonitor: Waiting on Gender for <NULL-object>"

 

See the above clip.  Between time 10:59:49 and 10:59:52 something is cleaning up global variables on the server.

 

For those experiencing the problem with NULL-object Gender, please try and run FuMS without Infistar or any other HC addon and let me know if the problem persists.

 

 

Darth,

  I also saw in your logs via a report from A3EAI that the HC connected as L Charlie 1-2:1 Remote.  I think this is a 'player' slot. The HC should not be connecting there if you have the HC config in the 1st slot in the mission.sqm.

 

 

 

Happens with stock AH and also with NO AH at all.

16:24:48 "##HeartMonitor: Waiting on Gender for HC_HAL_SoA"

16:24:51 "##HeartMonitor: Waiting on Gender for HC_HAL_SoA"

16:24:54 "##HeartMonitor: Waiting on Gender for HC_HAL_SoA"

16:24:57 "##HeartMonitor: Waiting on Gender for HC_HAL_SoA"

16:25:00 "##HeartMonitor: Waiting on Gender for HC_HAL_SoA"

16:25:02 No speaker given for Hussein Siddiqi

16:25:03 Speaker Male01_F not found in CfgVoiceTypes

16:25:03 "DEBUG: player auth token set ["qiycscznrmegwaujuqoednrqdlafzucvtix",B Alpha 1-1:1 (HC_HAL_SoA) REMOTE,"oawyfaqd"]"

16:25:03 "##HeartMonitor: Waiting on Gender for <NULL-object>"

16:25:06 "##HeartMonitor: Waiting on Gender for <NULL-object>"

16:25:09 "##HeartMonitor: Waiting on Gender for <NULL-object>"

16:27:25 "##HeartMonitor: Waiting on Gender for <NULL-object>"

16:27:28 "##HeartMonitor: Waiting on Gender for <NULL-object>"

16:27:31 "##HeartMonitor: Waiting on Gender for <NULL-object>"

16:27:34 "##HeartMonitor: Gender assignment timeout! No GenderAssigned for HC_HAL_SoA"

16:27:34 "##HeartMonitor:HC_HAL_SoA: Disconnect detected. Cleaning up the Mess!!!!FuMS_HC_isAlive3"

16:27:34 "##HC_DataCleanup: FuMS_HCIDs:[0,3]"

16:27:34 "##HC_DataCleanup: FuMS_HCNames:["SERVER",""]"

16:27:34 "##HC_DataCleanup: _varName :FuMS_HC_HAL_AIGroups3"

16:27:34 "HC:HC_HAL_SoA: Complete in 0 secs!FuMS_HC_isAlive3"

16:27:34 "##HeartMonitor: Has ended for HC_HAL_SoA:FuMS_HC_isAlive3"

 

 

 

A3EAI HC connectivity is disabled.  No change.

 

It says the HC disconnects but if you look at the HC client program window it does not show a disconnect.

[horbin]

yea, its EPOCH flushing out global variables or something.

 

Still not sure why this happens on some systems and not others. I'll keep looking into it...

 

I'm going to put a 'hack' work-around for it together and will post it this evening.

 

It won't be pretty, but it will keep things together until I can find out the root cause.

[Darth_Rogue]

Seems to me the issue is right here

16:44:24 "##HeartMonitor: Waiting on Gender for HC_HAL_SoA"
16:44:26 No speaker given for Hussein Siddiqi
16:44:27 Speaker Male01_F not found in CfgVoiceTypes
16:44:27 "##HeartMonitor: Waiting on Gender for <NULL-object>"

Is there a specific profile that needs to be loading for the HC so it doesn't assign a "speaker"?

[ReMuS]

here logs with no infistar:

 

https://drive.google.com/file/d/0B6kYk7pwr8ckT3BldXE0U0tBbWc/view?usp=sharing

 

 

sry other way i can not upload

[horbin]

Ok, think I can duplicate the error now.

 

I normally never reboot my HC. Because of this, it is typically the 1st to connect after a server restart.  When this occurs, all seems to work well.

 

I am seeing the same thing you are when the HC is NOT 1st to connect.

 

Odd that this sort of connection is not seen the same as when you kick the HC.

 

Anyway, able to duplicate what you are seeing, Trouble shooting now.

 

But a 'work around' is to just make sure your HC is running before your server.

[Darth_Rogue]

If I leave the HC running then it will crash after every 4th server restart.  Besides that, the HC is always the first player to connect as part of my server's startup batch.  The HC exe starts immediately after the server exe.  No other players connected.

[ReMuS]

If I leave the HC running then it will crash after every 4th server restart.  Besides that, the HC is always the first player to connect as part of my server's startup batch.  The HC exe starts immediately after the server exe.  No other players connected.

That is true same by me xD

[Darth_Rogue]

I just switched around my batch file so the HC starts first followed by a 10 second delay starting the server and it made no difference.  Still getting the "##HeartMonitor: Waiting on Gender for <NULL-object>" after the server fails to assign a speaker.