Jump to content

Lenyoga

Member
  • Content Count

    588
  • Joined

  • Last visited

  • Medals

Posts posted by Lenyoga


  1. but when playing in the campaign the error shows..

    That's strange, my guess is that the game is trying to find that folder in the main campaign directory - so putting the .sqs file in the mission folder instead of a sub-folder might be the easiest solution. And in the init.sqs file it should just work the same as from a trigger or mission editor init field.


  2. I saw the video and also know of other examples that somehow manage to screw up the PC port to a certain degree, but I'm kind of baffled, although I'm usually quite an anti-optimist. How and why do these developers or publishers allow their big titles to have such major issues on one of the most important platforms? I mean, even if they're aimed at consoles - the console generations of the future will probably lose a big lot of their market value. So is it just short-sighted and quick-cash oriented business strategy or am I missing something here?


  3. It's easier to simply change the camera's position and target instead of killing the old one and creating a new one. The code would look like that:

    _camera = "camera" camcreate [0,0,0]
    _camera cameraEffect ["internal","back"]
    _camera camsettarget target1
    _camera camsetrelpos [0,6,3]
    _camera camcommit 0
    
    ;; camera looks at target1 for 3 seconds
    ~3
    
    @camCommitted _camera
    _camera camsettarget target2
    _camera camsetrelpos [0,9,5]
    _camera camcommit 0
    ;; camera cuts to target2 and does a slow zoom which takes 5 seconds 
    
    @camCommitted _camera
    _camera camsetrelpos [0,6,5]
    _camera camcommit 5
    
    ~6
    _camera cameraEffect ["terminate","back"]
    camDestroy _camera
    
    exit
    

    ---------- Post added at 01:16 ---------- Previous post was at 01:10 ----------

    A little explanation, too: "@camCommitted _camera" checks if a camera is done with its operations (change in position, target, field of view), "camCommit" sets the duration for the camera's operations, "camsetrelpos" sets the position to the relative of the target, so [1,0,5] would be 1 meter west of the target and 5 meters above it.


  4. There's basically two possibilities, you could execute the script from the unit's init eventHandler (they don't work in multiplayer, though, I think) or you could turn "_F16" into "yourTag_F16" and then define that global variable in the the init script or any init field "yourTag_F16 = plane1" - I'd suggest using eventhandlers, though:

    class Unit: 
    {
    	parameter = ;
    	parameter = ;
    	parameter = ;
    	class EventHandlers
    	{
    		init = "[(_this select 0)] exec {\AddonFolderName\scriptname.sqs}";
    	};
    };
    

    then, the name in the script would be

    _F16 = _this select 0
    


  5. I've seen a "armor" script a long time ago, what it did was basically to react when a unit is damaged and undo that damage until a certain value is reached, then the unit would take normal damage and die - you could try that. What might work as an easier way would be to use "this setdammage -10" in a unit's init field. I've tried that out a year or two ago and it made the unit more durable, but it made the soldier's hands shake (I guess the damage value, even if it's negative, still influences the arm shaking) - maybe it works, or maybe they'll be unable to fire a straight shot.


  6. There was a collection of scripts on OFPEC.com, also various tutorials for scripts and basic missions... maybe other sites still have some. And respawning in single player isn't possible, sadly. I've tried a few things out, and it didn't end too well.

    ---------- Post added at 21:34 ---------- Previous post was at 21:32 ----------

    Ah, I got something, here we go: http://ofp.toadlife.net/downloads/tutorials/scripting_guide/scripting.htm


  7. I would like to ask about two things:

    1. Is changing loadouts of soldiers a good idea? I'd like to add them more ammo, and remove hand grenades. Can this cause any problems while playing BIS missions/campaigns?

    2. Where I can find speed of sprinting soldiers in config file? I'd like to decrease it a little bit.

    1 - I think it won't cause many problems, as long as you keep the loadout of the specialists the same - engineers should still have enough mines, and you shouldn't give them any more ammo than they can carry in their inventory, that might lead to issues.

    2 - you can find it under CfgMovesMC - it's "class CombatSprintF: Default" - just change the speed value. It's a negative value, though, -0.4, so changing it to -0.5 would make it slower.


  8. No, I didn't but I'll just leave it as it's not that important. Now I'd need these BIS Sample models - could you please upload it somewhere (just tank model) as the link is dead?

    I couldn't find them either, so here's a Dropbox link with the p3d: https://dl.dropboxusercontent.com/u/102863946/BISM1A1.p3d

    ---------- Post added at 20:03 ---------- Previous post was at 19:55 ----------

    By the way, it would make things easier for later if you already use the Texture Path Swap Tool on the M1A1 - that way you don't have to do it on the three other tanks each.

×