It looks like the resupply module is causing a long delay in the init time:
Line 3660: ALiVE [m_26|28] Module ALiVE_sys_weather INIT COMPLETE TIME: 1.32397
Line 3662: ALiVE [m_0|0] Module ALiVE_SUP_PLAYER_RESUPPLY INIT COMPLETE TIME: 38.947
Is this normal?
Infact, I've removed that module as I'm not using it as I can't customize the contents of the drop (in the boxes, I use diff weapon mods ect)
Here is my RPT:
Im not sure if that init time is normal or not :) (near the bottom)
Yeah that looks pretty standard to me. Init time will differ greatly, but resupply probably isnt the main culprit. Placement modules, CQB and OPCOM generally have the longest startup times.
Ah ok, maybe I placebo effected myself on initial testing of your mod.. then when I'm properly using it with everything loading I'm getting the true loading times.
Always best to start small when testing of course.. but everything in full force!
Thanks for the reply ARJay - I hope this thread helps someone else in the future with the same 'worries' I had! :D
Yeah, no worries, good that you are testing it thoroughly. Also different maps will have a big difference on init times also. A large scale mission on Altis with all the bells and whistles can take 2-3 minutes to init depending on the hardware.
My mission is relatively small:
Two blufor military spawns which will be reduced to one after the initial mission, first mission encompasses flying from HQ to the FOB (immersion reasons but I want both to seem ocupied)
One civilian spawn in Pyrgos on Altis (high density)
One opfor opcom and one opfor cqb (probably where the delay is coming from)
I have a few ambush points and extra patrols setup also but I'm just about to make a thread on that with a question/suggestion! (I hate suggesting things in my conversations, running a community of my own based on public servers.. if people dont suggest in separate threads things get lost easily and the suggestees get grumpy that its missed!)