Page 6 of 6 FirstFirst ... 23456
Results 51 to 58 of 58

Thread: [OA] New config values, who has info about?

  1. #51
    Hi,

    new paramters for units after 1.54 patch (hope it's the right topic ):

    to give unit engineer ability :

    engineer = 1;
    note that this is for "repairs ability", you still need to use
    canDeactivateMines = "true";
    also!

    and that's the picture you can add to the portrait :

    picture = "\ca\characters_d_baf\Data\i_eng_ca.paa";
    It's in "common" folder so I'm pretty sure you won't need BAF to add it (I've got BAF so not 100% sure)

    and they also made available again the "old" option to hide bodies :

    canHideBodies = "true";
    cheers
    massi
    Last edited by massi; Aug 28 2010 at 12:14.

  2. #52
    Gunnery Sergeant Xeno426's Avatar
    Join Date
    May 15 2010
    Location
    11th Province of Canada
    Posts
    484
    Quote Originally Posted by NZDF CRASH View Post
    for the integration of the artillery computer
    Code:
    		artilleryScanner = 1;
    		ARTY_IsArtyVehicle = 0;
    Are both of those placed in the vehicle entry?

  3. #53
    yea both are placed in the vehicle entry, it is the same for the m119 and the mlrs

    Free your mind and your ass will follow
    Acies Project Full Conversion
    Anzac Mod MkII
    BWI Addons

  4. #54
    Getting the artillery computer to work isn't as simple as that. I have been trying to add it to the vilas m109 howitzer. Those lines do enable the computer but you can't shoot. The ranges are all wacky. I changed the cannon to fire the m119 magazines but that didn't help. Anybody know anything about this?

  5. #55
    Warrant Officer Slatts's Avatar
    Join Date
    Feb 6 2008
    Location
    Dublin, Ireland
    Posts
    2,926
    Quote Originally Posted by Perineum View Post
    Getting the artillery computer to work isn't as simple as that. I have been trying to add it to the vilas m109 howitzer. Those lines do enable the computer but you can't shoot. The ranges are all wacky. I changed the cannon to fire the m119 magazines but that didn't help. Anybody know anything about this?
    heres my config for my own self propelled howitzer
    Code:
    	
    class Turrets;
    class MainTurret;
    class AnimationSources;
    class CfgVehicles
    {
            class astfor_mowag_sph: astfor_mowagBase
    	{
    		displayName = "Mowag Piranha SPH";
    		artilleryscanner = 1;
    		arty_isartyvehicle = 0;
    		model = "\astfor_mowags\astfor_mowag_sph";
    		canfloat = 0;
    		class Turrets: Turrets {
    			class MainTurret: MainTurret {
    				weapons[]={"M119"};
    				magazines[]={"30Rnd_105mmHE_M119"};
    			};
    		};
    	};
    works fine for me without any problems
    Twitter: https://twitter.com/Slatts_modding
    PhotoBucket album: http://s296.beta.photobucket.com/use...o-man/library/

    Slatts & HydroPump - Brothers in ArmA since 2002
    Due to PC related issues. Please do not contact me regarding updates/news or permissions regarding my work. I cannot help you.

  6. #56
    hiho
    I have question about the zeroing for infantry weapons. You talked about the situation if you want to add the system to a new weapon. I want to remove the BIS Zeroing system. So I removed the both entrys:

    discreteDistance
    discreteDistanceInitIndex

    So now its not anymore possible to switch the up and down in the hud. But I also want to remove the number and text belowe the number of bullets in magazine.

    And I also switched the entry:

    weaponinfotype = "RscWeaponZeroing";

    to

    weaponinfotype = "RscWeaponEmpty";

    But there isnt a difference...

    The weapon is based on the m16_base.

  7. #57
    Gunnery Sergeant Xeno426's Avatar
    Join Date
    May 15 2010
    Location
    11th Province of Canada
    Posts
    484
    I would advise against simply removing those entries. Instead, set the discretteDistance to be only one value (300 normally, 100 for red-dot, 200 for G36 scope) and set discreteDistanceInitIndex to 0, e.g.
    Code:
    		discreteDistance[] = {300};
    		discreteDistanceInitIndex = 0;
    What text are you talking about? The "Zeroing" and following number in the upper right corner (like in this picture)? That should be removed by the weaponInfoType = "RscWeaponEmpty"; entry. If it's not, then you either have weapon inheritancies wrong, you inserted the line incorrectly, or you have another mod putting them back on.
    Last edited by Xeno426; Jul 24 2011 at 23:59. Reason: added picture example

  8. #58

    lockDetectionSystem, incommingMisslieDetectionSystem, radarType, weaponLockSystem, cm

    I have been looking for a description of several of the "new" OA config entries, namely lockDetectionSystem, incommingMisslieDetectionSystem, radarType, weaponLockSystem. Seems they have been added to the BIS Wiki, but no explanation is given.

    Have you guys ever found out, what the parameters do in detail?

    Does OA now differentiate between different guidance modes, i.e. optical, wire/radio, IR, radar (mmW, etc), UV? (weaponLockSystem?)
    Is there a proper differentiation between the types of countermeasures now (flares, chaff, ecm)?
    And a proper sensor differentiation in vehicles?

    Or were these values just added for compatibility with the forthcoming title? If so, I might try to add those to the GLT weapon packs, and to retrofit it into MMA to safe some scripting overhead by using engine functionality instead.

    In A3, I hope they will put some focus on planes, helicopters, and armor/apc simulation, which compared to the infantry part still seems quite crude. Aside from CQB in buildings, the latter is very good already, but I find the disbalance is becoming limiting factor overall. I hope they add the interactive cockpits from ToH to all vehicles in A3.

Page 6 of 6 FirstFirst ... 23456

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •