Jump to content
Bohemia Interactive Forums

radeck1983

Member
 View Profile  See their activity

  • Content Count

    21

  • Joined

  • Last visited

  • Medals

Posts posted by radeck1983

  6. Posted

    I think it did, though. I inserted all these lines to my init.sqf because they had already been in the init.sqf from the UPSMON package. So I copied them.

    I've just looked up these commands on the BI Wiki and, unfortunatelly, I don't understand why they aren't working as they should. The Wiki says that finishMissionInit is finishing the world initialization before a mission is launched, so all the more it's incomprehensible to me. However, I'm not that curious to investigate all these relations. The most important for me is that the problem is solved.

  8. Posted

    Nimrod, I've checked it out and still no result. By the way, I have tried again without UPSMON - I've deleted from the init.sqf these lines: 

    //Init UPSMON scritp (must be run on all clients)
call compile preprocessFileLineNumbers "scripts\Init_UPSMON.sqf";	
//Process statements stored using setVehicleInit
processInitCommands;
//Finish world initialization before mission is launched. 
finishMissionInit;

    and the HALO jump works great then, as well as there is no "reholding" there. However, there is one thing I'm wondering about. I use this HALO jump code:

    [this, 1000] exec "ca\air2\halo\data\Scripts\HALO_init.sqs"

    I've noticed that at the mission start, before i was doing the HALO, i had been standing at the ground for 1-2 seconds. Is it normal?

  10. Posted

    Hi seba. Yes, I've already tested this and I'm 100% sure that the problem occurs when the UPSMON is in use. I've noticed that the time elapsed between a mission start and that weapon "reholding", which I wrote about in my last post, is longer if I put more UPSMON patrols. These times aren't long though - let's say, it's 0s (not noticable) if there are 1-4 patrol zones, to 2s, when I put more than 12 patrol zones. But still, it wrecks most of my ideas...

  11. Posted

    Hi all! I've recently joined your forum, both to ask for help and to learn and give some help if possible. Unluckily :) at the begining I certainly won't be a good advisor. To not be groundless, here's my first question...

    I have a problem with initializing the UPSMON script before a mission start. It manifests itself with a visible weapon "reholding" (I mean, a player lifts a weapon twice in a second - I suspect that the UPSMON is being initialized then). It happens just two seconds after joining a game as a first player.

    It is quite a bit frustrating as it makes it impossible to e.g. start a mission with a HALO jump. Why? It looks like this - I click "continue" -> a game starts -> the HALO jump is being and has been initialized -> now, I'm descending, ready to open a parachute -> the UPSMON is being initialized with that weapon "reholding", of which I wrote above -> the UPSMON has been initialized and now, I'm descending in a standard, ground position "on my feet" - cool, but i'm still falling down to the ground...

    I know that the problem is in the init.sqf file, but I can't figure out how to use the commands responsible for waiting with a mission start till all scripts are initialized. Asking you for help, I paste my init.sqf below.

    nul=[] execVM "briefing.sqf"; 
execVM "revive\ReviveAceWounds.sqf"; 

if ((!isServer) && (player != player)) then 
{ 

//Init UPSMON scritp (must be run on all clients) 
call compile preprocessFileLineNumbers "scripts\Init_UPSMON.sqf";     
//Process statements stored using setVehicleInit 
processInitCommands; 
//Finish world initialization before mission is launched.  
finishMissionInit; 

waitUntil {player == player}; 

};

  13. Posted

    Hi all! I've recently joined your forum, both to ask for help and to learn and give some help if possible. Unluckily :) at the begining I certainly won't be a good advisor. To not be groundless, here's my first question...

    I have a problem with initializing the UPSMON script before a mission start. It manifests itself with a visible weapon "reholding" (I mean, a player lifts a weapon twice in a second - I suspect that the UPSMON is being initialized then). It happens just two seconds after joining a game as a first player.

    It is quite a bit frustrating as it makes it impossible to e.g. start a mission with a HALO jump. Why? It looks like this - I click "continue" -> a game starts -> the HALO jump is being and has been initialized -> now, I'm descending, ready to open a parachute -> the UPSMON is being initialized with that weapon "reholding", of which I wrote above -> the UPSMON has been initialized and now, I'm descending in a standard, ground position "on my feet" - cool, but i'm still falling down to the ground...

    I know that the problem is in the init.sqf file, but I can't figure out how to use the commands responsible for waiting with a mission start till all scripts are initialized. Asking you for help, I paste my init.sqf below.

    nul=[] execVM "briefing.sqf";
execVM "revive\ReviveAceWounds.sqf";

if ((!isServer) && (player != player)) then
{

//Init UPSMON scritp (must be run on all clients)
call compile preprocessFileLineNumbers "scripts\Init_UPSMON.sqf";	
//Process statements stored using setVehicleInit
processInitCommands;
//Finish world initialization before mission is launched. 
finishMissionInit;

waitUntil {player == player};

};

  17. Posted

    Most of the answers have already been posted here, on this forum. My suggestion is you shouldn't start making missions with a 3d editor, but familiarize yourself with a standard 2d editor. At the begining, look for the topics with resources about editing and scripting - unfortunatelly I don't remember much of the titles. It is a good idea to look up some already done scripts, but still... I think it's better to start with waypoints, synhronization etc. As soon as you gain knowledge in this field, you'll answer yourself to the most of your questions.

  20. Posted

    What SetCurrentTask command do is setting the task as a current task of the person. The problem is that by completing objective 1 you are setting the current task to objective 2, even if objective 2 was SUCCEEDED before. The trigger with "On Activation: player setCurrentTask tskobj_2;" is responsible for that.

    First, don't produce so many triggers, it's unnecessary. You can merge trigger which set task as suceedded with the one setting another objective as current.

    Try this:

    Trigger 1:

    Condition: (!alive hvt);

    On Act: tskobj_1 setTaskState "SUCCEEDED"; nul = [objNull, ObjNull, tskobj_1, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf"; taskhint ["Task accomplished", [1, 0, 0, 1], "taskDone"]; if ((taskState tskobj_2 != "SUCCEEDED")) then {player setCurrentTask tskobj_2}; obj1 = true;

    Trigger 2:

    Condition: (!alive scud1) AND (!alive scud2);

    On Act: tskobj_2 setTaskState "SUCCEEDED"; nul = [objNull, ObjNull, tskobj_2, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf"; taskhint ["Task accomplished", [1, 0, 0, 1], "taskDone"];; if ((taskState tskobj_1 != "SUCCEEDED")) then {player setCurrentTask tskobj_1}; obj2 = true;

    Trigger 3:

    Condition: obj1 AND obj2;

    On Act: player setCurrentTask tskobj_3;

  21. Posted

    Hi!

    I have the same problem with units changing direction at the start of the mission preview. I've managed to solve the problem partially. While editing my friend's mission, who used 3D editor to put units and objects into the mission and then made minor changes in a regular editor, I've noticed that units are turning towards objects put in the 3D editor. I think they are turning towards the nearest object. When I delete the object, units change their direction to another nearest one. Though I have a clue, I don't understand why it is happening.

    You wrote that you had solved the problem. Can you share this solution?

×