Sign in to follow this  
Followers 0
.kju

Community Helicopter Initiative MOD (CHI)

45 posts in this topic

With Take On Helicopters: Rearmed finally available (in a beta), I'd like to try to get this project going.

Rearmed broadens the scope of TKOH and Hinds to a very large degree and the hope is to catch the attention

of players and modders alike for the engine.

Even though the Arma 3 community alpha is already on the horizon or precisely for that reason

the engine could serve as a good learning tool and test bed for future endeavors.

Overall the initiative is to focus on the armed conflict - Hinds, and hopefully other combat choppers,

to be sent into missions in singleplayer, two crew COOP or multiplayer scenarios with ground and air assets working together.

That said with a higher popularity and increased modding, we may also see scenarios and systems useful for civilian pilots.

Now why should you care if you dislike choppers and always crash them as soon as you enter?

The reason is your buddy and people in your group might be in love with them, and they cannot wait to get a real challenge

and still be able to join the battlefield alongside with you. Or in other words your world can remain almost the same,

while your ace pilot will be a happy dude from there on. :)

For players the MOD is meant to generate, provide and offer:

  • New scenarios both in SP and MP
  • Upgraded A2/OA missions playable with TKOH choppers
  • Hopefully more challenging and dynamic missions
  • Or even dynamic missions/campaigns focused around combat chopper assignments
  • More realistic and challenging weapon systems
  • More advanced systems for radar, armament and other systems you can think of
  • Tweaks to the FM of existing TKOH choppers
  • Update and improve existing A2/OA choppers to make use of the TKOH FMs and new features

For modders the MOD is meant to create an open and loose group and at the same time dedicated team to:

  • realize some of the ideas above for players
  • explore and share new insights of modding in the TKOH engine
  • learn about and make use of new scripting commands (like profileNamespace)

These are some of the ideas I could think of - surely there are plenty more. :cool:

My personal dream would be story-driven/very atmospheric scenarios/campaigns that make use of radio chatter,

and other assets of old chopper games that are abandonware or where permissions can be obtained for external use.

Something along the lines of Jane's AH-64D Longbow is what a good friend of mine would love to see.

While I am personally as (way) less hardcore and like the Comanche series back in the day. :)

With that being said this initiative, MOD and new team can only become successful with your participation in one form or another.

Therefore with this start I'd like to ask about your thoughts as well as your conditions to participate and obstacle that would prevent you to.

Thank you. :bounce3:

PS: This is not to become a request thread. :(

Edited by .kju [PvPscene]

Share this post


Link to post
Share on other sites

I don't mind having a go at making some MP and SP missions to play, I already have a few drawn up (on both Taki and South Asia). I could actually make some TOH versions of some of the old [EVO] missions I made if you want. I don't have Hinds yet but should be getting it at the end of this month. (I am sure I can get [EVO] Crash to come up with some awesome ideas like he usually does)(also I don't have the beta patch, probably going to wait till the stable version is out before updating)

Share this post


Link to post
Share on other sites

  • Update and improve existing A2/OA choppers to make use of the TKOH FMs and new features

I may have something to show you, guys:

Best about this is that there are no changes in the original air*.pbo files, which means, that:

one - the chopper behaves just as usual when being flown in ArmA,

two - the copywrights are obeyed.

The only issue is a horrific sound bug appearing at startup if the mod is run with A.C.E.

I've run some similar test with AH-1Z and UH-1Y (with Medium's FM) among others and they were allso succesfull, what leads me to belief, that it's possible to make literally every stock/addon ArmA chopper to fly more realisticly in ToH :D

So now all that we need are modders with means and knowledge to write dedicated FMs for those ArmA helos :)

Best regards!

Share this post


Link to post
Share on other sites
I may have something to show you, guys:

Best about this is that there are no changes in the original air*.pbo files, which means, that:

one - the chopper behaves just as usual when being flown in ArmA,

two - the copywrights are obeyed.

The only issue is a horrific sound bug appearing at startup if the mod is run with A.C.E.

I've run some similar test with AH-1Z and UH-1Y (with Medium's FM) among others and they were allso succesfull, what leads me to belief, that it's possible to make literally every stock/addon ArmA chopper to fly more realisticly in ToH :D

So now all that we need are modders with means and knowledge to write dedicated FMs for those ArmA helos :)

Best regards!

This can be big news. Looking eager to see more.

Share this post


Link to post
Share on other sites

well done Rahonavis :bounce3:

I assume you have ported the config definition to the A2/OA choppers?

Looks very promising - would be nice to integrate it into Rearmed. :)

From what I understand modifying the model would allow more fine-tuned tweaks to the FM at least,

and to define the interaction points. Still an interesting FM for all A2/OA choppers would be a great start!

Share this post


Link to post
Share on other sites

So if I understand well we'll be able to fly in ARMA2 with TOH fly model?

Or with Arma2's chopper in TOH?

Share this post


Link to post
Share on other sites
well done Rahonavis :bounce3:

Thanks! :)

I assume you have ported the config definition to the A2/OA choppers?

Something like that, only I didn't modify the original configs. Instead I made a small new config, that upon activation in ToH calls for the original config (Mi-17 config in this case) and adds ToH definitions to it. This way we can keep things vanilla clean in ArmA (should one want to play it without ToH), whle enchancing A2/OA capabilities in ToH Rearmed. Other good thing is, as I understand, the copywrights are obeyed - downloading the mod won't let you to fly the Mi-8/Mi-17 unless you have the original stuff from ArmA. Last, but not least, this small mod deosn't affect just stock A2 Mi-8, but any other mod choppers, that call for it's configs, like the Mi-8 from Vilass' mod, that I fly in the video, or the H-19 that stands in front of it.

Looks very promising - would be nice to integrate it into Rearmed. :)

From what I understand modifying the model would allow more fine-tuned tweaks to the FM at least,

and to define the interaction points. Still an interesting FM for all A2/OA choppers would be a great start!

What I meant is that it would be great if someone could create dedicated FM for Hip and other A2 choppers. For now the Mi-8 has the Heavy/Merlin FM and flies like one, but ToH allows to create new FMs, so if had one featuring Mi-8 characteristics instead of Merlin's, the Hip would fly more realisticly than now. Same goes for any other A2 rotorcraft. I tried tweaking the FM myself, but the results were a disaster, so I decided to stick with just slightly modified Heavy FM for now ;)

Aside of that, I wonder if it would be possible to make those copters use some other ToH features. For instance PiP function in the rearview mirror on that Mi-8.

Anyways, here's the link to that Mi-8 mod, if you'd like to test it yourself:

http://www.mediafire.com/?395cq4937cqzwa4

Or with Arma2's chopper in TOH?

We'll be able to fly A2 choppers in ToH, just as now, only with the ToH flight modelling apllied applied to those A2 helos.

Edited by Rahonavis

Share this post


Link to post
Share on other sites

Anyone interested in getting the TKOH FM for A2/OA choppers should try this starter pack:

http://pvpscene.armaholic.com/files/temp/TKOH_FM_4_CO_Choppers.7z

It includes:

  • Rahonavis sample config (a bit improved)
  • A template config for all A2/OA choppers
  • Configs for all TKOH choppers reduced to their TKOH only values

When new to this, a start would be to copy and paste the desired FM values from the TKOH choppers to the A2/OA ones.

More experienced modders could transfer also others part of the TKOH technology over. :)

@Rahonavis

Are you sure your sound definitions work? I was told it required model modifications; so for A2/OA choppers we have to use the A2/OA sound system/definitions.

Share this post


Link to post
Share on other sites

I'm too much of a newbe in ArmA/ToH moding to be sure of anything ;) Anyways, those definitions are basically taken from Heavy's config, and they work with the Mi-8 fine to me (as you can hear on the vid). They allso worked with UH-1Y and AH-1Z (though I was sorta learning and experimenting with those, so I was modyfying the original configs inside air.pbo - that's why I didn't make a analogue mod for those yet).

Coming back to the Hip - sound problems may occur (at least occured to me) only if you run A.C.E. mod and my mod at the same time and it doesn't matter if you add new sound definitions, or stick with stock A2/OA/CO sounds. I've no idea, what couses that bug, but that's how it is. :confused:

Share this post


Link to post
Share on other sites

You did an excellent start there Rahonavis :)

It would be really nice to see the template config filled with the FM config data most fitting as a start.

From there people could experiment to port other features over or tweak the FM. :)

Share this post


Link to post
Share on other sites

Awesome! I didn't think progress would be made on this (I thought I saw people say it was almost impossible), but that's awesome work Rahonavis!

Will the Mi-8 have the new FM even in missions/scenarios where it has already been placed? Or is it a new Mi-8 which need to be put into missions/scenarios?

Share this post


Link to post
Share on other sites
Awesome! I didn't think progress would be made on this (I thought I saw people say it was almost impossible), but that's awesome work Rahonavis!

Will the Mi-8 have the new FM even in missions/scenarios where it has already been placed? Or is it a new Mi-8 which need to be put into missions/scenarios?

It doesn't add any new chopper, only interacts with those, that are already in ArmA, so no need to do any changes in the missions to fly them with ToH flight modelling ;)

It would be really nice to see the template config filled with the FM config data most fitting as a start.

From there people could experiment to port other features over or tweak the FM. :)

OK, so it goes like that:

#define _ARMA_


//Class config.bin{
class CfgPatches
{
[b][color="#FFFF00"]class your_text (1)[/color][/b]
{
 units[] = {};
 weapons[] = {};
 requiredVersion = 0.108;
 requiredAddons[] = {"CAAir"};
};
};
class CfgVehicles
{
class AllVehicles;
class Air: AllVehicles{};
class Helicopter: Air{};
[b][color="#FF0000"]class Helicopter_Base_H: Helicopter (2)[/b][/color]
{
 class RotorLibHelicopterProperties;
};[/b][/color]
[b][color="#0000FF"]class YourHelicopter_Base: Helicopter_Base_H (3)[/color][/b]
{
[b][color="#EE82EE"]  class RotorLibHelicopterProperties: RotorLibHelicopterProperties
 {
  [color="#00FFFF"]RTDconfig = "folder_name\flight_model_file_name.xml"; (5)[/color]
[size=5](4)[/size]
 };[/color][/b]
[color="#FFA500"][b]  class SoundsExt
 {
[size=5](6)[/size]
    };[/b][/color]
};
};
//};

(1) Enter a text of your choice here (i.eg. Helicopter_ToH).

(2) It's important to have this class in ToH helicopter config.

(3) This should a base class of your helicopter (i.eg. AH1_Base (for AH-1Z), UH1_Base (UH-1Y), or Mi17_base (Mi-8 and MI-17). You'll find those classes in configs of the original ArmA helicopters. Keep in mind, that in the original config it goes like:

"class YourHelicopter_Base: Helicopter"

but you need to change that in your config to:

"class YourHelicopter_Base: Helicopter_Base_H".

(4) This is where you paste the flight characteristics data, which you have to copy from a config of one of original ToH chppers.

(5) This line tells the game, where it should look for the FM file for this chopper. You can put there a path directly to the original file (i.eg. HSim\Air_US_H\Helicopters_Light\Light-GenHeli600-DesktopSim.xml), but I recommend you to copy and paste that file, together with this config to the folder of your helicopter mod and gice it a name different from the original one. This way any changes you'll make to the FM will affect only your chopper and not the stock one.

(6) This is where you paste deffinitions for ToH sound effects (like starters, APU, or touchdown sounds). Just as with flight characteristics, you have to copy these definitions from a config of one of original ToH chppers. DO NOT copy the "class Sounds" definitions, as you want purely the "class SoundsExt" ones.

If you did allright, you should end up with a config, looking like this:

#define _ARMA_


//Class config.bin{
class CfgPatches
{
[color="#FFFF00"]class AH1Z_ToH[/color]
{
 units[] = {};
 weapons[] = {};
 requiredVersion = 0.108;
 requiredAddons[] = {"CAAir"};
};
};
class CfgVehicles
{
class AllVehicles;
class Air: AllVehicles{};
class Helicopter: Air{};
[color="#FF0000"][b]class Helicopter_Base_H: Helicopter
{
 class RotorLibHelicopterProperties;
};[/b][/color]
[color="#0000FF"][b]class AH1_Base: Helicopter_Base_H[/b][/color]
{
 [color="#EE82EE"][b]class RotorLibHelicopterProperties: RotorLibHelicopterProperties
 {
  [color="#00FFFF"]RTDconfig = "AH-1Z_ToH\AH1Z-GenHeli600-DesktopSim.xml";[/color]
  defaultCollective = 0.75;
  starterTime = 10;
  throttleOffToIdle = 10;
  throttleIdleToOff = 10;
  throttleIdleToFull = 8;
  throttleFullToIdle = 15;
  autoHoverCorrection[] = {5,2.4,0};
  maxTorque = 2168;
  maxMainRotorStress = 130000;
  maxTailRotorStress = 10000;
  retreatBladeStallWarningSpeed = 71.597;
  class Procedures
  {
   class Startup
   {
    class RotorBrakeOff
    {
     delayFromCondition = 0;
     condition = "[2, _this] call (uiNamespace getVariable 'BIS_fnc_rotorBrakeOff')";
     statement = "[3, _this select 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_rotorBrakeOff')";
     bypass = "[4, _this] call (uiNamespace getVariable 'BIS_fnc_rotorBrakeOff')";
    };
    class BatteriesOn
    {
     delayFromCondition = 1;
     condition = "[0, _this] call (uiNamespace getVariable 'BIS_fnc_batteriesOn')";
     statement = "[3, _this select 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_batteriesOn')";
     bypass = "[4, _this] call (uiNamespace getVariable 'BIS_fnc_batteriesOn')";
    };
    class StarterOn0
    {
     delayFromCondition = 2;
     condition = "[2, _this, 0] call (uiNamespace getVariable 'BIS_fnc_starterOn1')";
     statement = "[3, _this select 0, 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_starterOn1')";
     bypass = "[4, _this, 0] call (uiNamespace getVariable 'BIS_fnc_starterOn1')";
    };
    class ThrottleIdle0
    {
     delayFromCondition = 1;
     condition = "[2, _this, 0] call (uiNamespace getVariable 'BIS_fnc_throttleIdle1')";
     statement = "[3, _this select 0, 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_throttleIdle1')";
     bypass = "[4, _this, 0] call (uiNamespace getVariable 'BIS_fnc_throttleIdle1')";
    };
    class StarterOff0
    {
     delayFromCondition = 0;
     condition = "[2, _this, 0] call (uiNamespace getVariable 'BIS_fnc_starterOff1')";
     statement = "[3, _this select 0, 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_starterOff1')";
     bypass = "[4, _this, 0] call (uiNamespace getVariable 'BIS_fnc_starterOff1')";
    };
    class StarterOn1
    {
     delayFromCondition = 2;
     condition = "[2, _this, 1] call (uiNamespace getVariable 'BIS_fnc_starterOn1')";
     statement = "[3, _this select 0, 1, _this select 1] call (uiNamespace getVariable 'BIS_fnc_starterOn1')";
     bypass = "[4, _this, 1] call (uiNamespace getVariable 'BIS_fnc_starterOn1')";
    };
    class ThrottleIdle1
    {
     delayFromCondition = 1;
     condition = "[2, _this, 1] call (uiNamespace getVariable 'BIS_fnc_throttleIdle1')";
     statement = "[3, _this select 0, 1, _this select 1] call (uiNamespace getVariable 'BIS_fnc_throttleIdle1')";
     bypass = "[4, _this, 1] call (uiNamespace getVariable 'BIS_fnc_throttleIdle1')";
    };
    class StarterOff1
    {
     delayFromCondition = 0;
     condition = "[2, _this, 1] call (uiNamespace getVariable 'BIS_fnc_starterOff1')";
     statement = "[3, _this select 0, 1, _this select 1] call (uiNamespace getVariable 'BIS_fnc_starterOff1')";
     bypass = "[4, _this, 1] call (uiNamespace getVariable 'BIS_fnc_starterOff1')";
    };
    class WarmupStart
    {
     delayFromCondition = 2;
     condition = "[2, _this] call (uiNamespace getVariable 'BIS_fnc_warmupStart')";
     statement = "[3, _this select 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_warmupStart')";
    };
    class ThrottleFull0
    {
     delayFromCondition = 17;
     condition = "[2, _this, 0] call (uiNamespace getVariable 'BIS_fnc_throttleFull1')";
     statement = "[3, _this select 0, 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_throttleFull1')";
     bypass = "[4, _this, 0] call (uiNamespace getVariable 'BIS_fnc_throttleFull1')";
    };
    class ThrottleFull1
    {
     delayFromCondition = 0;
     condition = "[2, _this, 1] call (uiNamespace getVariable 'BIS_fnc_throttleFull1')";
     statement = "[3, _this select 0, 1, _this select 1] call (uiNamespace getVariable 'BIS_fnc_throttleFull1')";
     bypass = "[4, _this, 1] call (uiNamespace getVariable 'BIS_fnc_throttleFull1')";
    };
    class EnginesOn
    {
     delayFromCondition = 0;
     condition = "[2, _this] call (uiNamespace getVariable 'BIS_fnc_enginesOn')";
     statement = "[3, _this select 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_enginesOn')";
    };
   };
   class Shutdown
   {
    class ThrottleIdle0
    {
     delayFromCondition = 0;
     condition = "[2, _this, 0] call (uiNamespace getVariable 'BIS_fnc_throttleIdle1')";
     statement = "[3, _this select 0, 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_throttleIdle1')";
     bypass = "[4, _this, 0] call (uiNamespace getVariable 'BIS_fnc_throttleIdle1')";
    };
    class ThrottleIdle1
    {
     delayFromCondition = 0;
     condition = "[2, _this, 1] call (uiNamespace getVariable 'BIS_fnc_throttleIdle1')";
     statement = "[3, _this select 0, 1, _this select 1] call (uiNamespace getVariable 'BIS_fnc_throttleIdle1')";
     bypass = "[4, _this, 1] call (uiNamespace getVariable 'BIS_fnc_throttleIdle1')";
    };
    class CoolDownStart
    {
     delayFromCondition = 0;
     condition = "[2, _this] call (uiNamespace getVariable 'BIS_fnc_cooldownStart')";
     statement = "[3, _this select 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_cooldownStart')";
    };
    class ThrottleClosed0
    {
     delayFromCondition = 10;
     condition = "[2, _this, 0] call (uiNamespace getVariable 'BIS_fnc_throttleOff1')";
     statement = "[3, _this select 0, 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_throttleOff1')";
     bypass = "[4, _this, 0] call (uiNamespace getVariable 'BIS_fnc_throttleOff1')";
    };
    class ThrottleClosed1
    {
     delayFromCondition = 0;
     condition = "[2, _this, 1] call (uiNamespace getVariable 'BIS_fnc_throttleOff1')";
     statement = "[3, _this select 0, 1, _this select 1] call (uiNamespace getVariable 'BIS_fnc_throttleOff1')";
     bypass = "[4, _this, 1] call (uiNamespace getVariable 'BIS_fnc_throttleOff1')";
    };
    class RotorBrakeOn
    {
     delayFromCondition = 0;
     condition = "[2, _this] call (uiNamespace getVariable 'BIS_fnc_rotorBrakeOn')";
     statement = "[3, _this select 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_rotorBrakeOn')";
     bypass = "[4, _this] call (uiNamespace getVariable 'BIS_fnc_rotorBrakeOn')";
    };
    class RotorBrakeOff
    {
     delayFromCondition = 0;
     condition = "[2, _this] call (uiNamespace getVariable 'BIS_fnc_rotorBrakeOff')";
     statement = "[3, _this select 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_rotorBrakeOff')";
     bypass = "[4, _this] call (uiNamespace getVariable 'BIS_fnc_rotorBrakeOff')";
    };
    class BatteriesOff
    {
     delayFromCondition = 0;
     condition = "[0, _this] call (uiNamespace getVariable 'BIS_fnc_batteriesOff')";
     statement = "[3, _this select 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_batteriesOff')";
     bypass = "[4, _this] call (uiNamespace getVariable 'BIS_fnc_batteriesOff')";
    };
    class EnginesOff
    {
     delayFromCondition = 2;
     condition = "[2, _this] call (uiNamespace getVariable 'BIS_fnc_enginesOff')";
     statement = "[3, _this select 0, _this select 1] call (uiNamespace getVariable 'BIS_fnc_enginesOff')";
    };
   };
  };
 };[/color]
 [color="#FFA500"]class SoundsExt
 {
  class Starter
  {
   startInt[] = {"HSim\Sounds_H\Air\Heli_Middle\medium_int_starter_start",0.0562341,1};
   startExt[] = {"HSim\Sounds_H\Air\Heli_Middle\medium_ext_starter_start",1,1,200};
   stopInt[] = {"HSim\Sounds_H\Air\Heli_Middle\medium_int_starter_stop",0.0562341,1};
   stopExt[] = {"HSim\Sounds_H\Air\Heli_Middle\medium_ext_starter_stop",1,1,200};
   damageInt[] = {"HSim\Sounds_H\Air\Noises\damage_starter_int",1,1};
   damageOut[] = {"HSim\Sounds_H\Air\Noises\damage_starter_ext",1,1,300};
  };
  class Starter1
  {
   startInt[] = {"HSim\Sounds_H\Air\Heli_Middle\medium_int_starter_start_2",0.0562341,1};
   startExt[] = {"HSim\Sounds_H\Air\Heli_Middle\medium_ext_starter_start_2",1,1,200};
   stopInt[] = {"HSim\Sounds_H\Air\Heli_Middle\medium_int_starter_stop_2",0.0562341,1};
   stopExt[] = {"HSim\Sounds_H\Air\Heli_Middle\medium_ext_starter_stop_2",1,1,200};
   damageInt[] = {"HSim\Sounds_H\Air\Noises\damage_starter_int",0.1,1};
   damageOut[] = {"HSim\Sounds_H\Air\Noises\damage_starter_ext",1,1,300};
  };
  class RotorNoiseExt
  {
   sound[] = {"HSim\Sounds_H\Air\Noises\swist1-efected-high",1,1,450};
   frequency = 1;
   volume = "(rotorSpeed factor [0.6, 0.85])";
   cone[] = {0.3,1,1,0};
  };
  starterClickInt[] = {"HSim\Sounds_H\Air\Heli_Middle\starter_click2_int",0.00562341,1};
  starterClickExt[] = {"HSim\Sounds_H\Air\Heli_Middle\starter_click2",316.228,1,600};
  starterClick[] = {"starterClickInt","starterClickExt"};
  idleStartInt[] = {"HSim\Sounds_H\Air\Heli_Middle\medium_int_idle_start",0.0112202,1};
  idleStartExt[] = {"HSim\Sounds_H\Air\Heli_Middle\medium_ext_idle_start",1,1,600};
  idleThrottle[] = {"idleStartInt","idleStartExt"};
  transmissionDamageInt[] = {"HSim\Sounds_H\Air\Noises\damage_transmission_int_2",1,1};
  transmissionDamageOut[] = {"HSim\Sounds_H\Air\Noises\damage_transmission_ext_2",1,1,300};
  transmissionDamage[] = {"transmissionDamageInt","transmissionDamageOut"};
  rotorDamageInt[] = {"HSim\Sounds_H\Air\Noises\damage_rotor_int",1,1};
  rotorDamageOut[] = {"HSim\Sounds_H\Air\Noises\damage_rotor_ext",1,1,300};
  rotorDamage[] = {"rotorDamageInt","rotorDamageOut"};
  engineDamageInt[] = {"HSim\Sounds_H\Air\Noises\damage_engine2_int",1,1};
  engineDamageOut[] = {"HSim\Sounds_H\Air\Noises\damage_engine2_ext",1,1,300};
  engineDamage[] = {"engineDamageInt","engineDamageOut"};
  starterDamageInt[] = {"HSim\Sounds_H\Air\Noises\damage_starter_int",1,1};
  starterDamageOut[] = {"HSim\Sounds_H\Air\Noises\damage_starter_ext",1,1,300};
  starterDamage[] = {"starterDamageInt","starterDamageOut"};
  landingSoundInt0[] = {"HSim\Sounds_H\Air\Noises\landing1_int",1,1};
  landingSoundInt1[] = {"HSim\Sounds_H\Air\Noises\landing2_int",1,1};
  landingSoundInt2[] = {"HSim\Sounds_H\Air\Noises\landing3_int",1,1};
  landingSoundInt[] = {"landingSoundInt0",0.33,"landingSoundInt1",0.33,"landingSoundInt2",0.333};
  landingSoundOut0[] = {"HSim\Sounds_H\Air\Noises\landing1_ext",1,1,200};
  landingSoundOut1[] = {"HSim\Sounds_H\Air\Noises\landing2_ext",1,1,200};
  landingSoundOut2[] = {"HSim\Sounds_H\Air\Noises\landing3_ext",1,1,200};
  landingSoundOut[] = {"landingSoundOut0",0.33,"landingSoundOut1",0.33,"landingSoundOut2",0.33};
 };
};
};[/b][/color]
//};

Once you have this you can put this together with the FM file, make pbo, run it just as any other mod, and voila - you can enjoy your A2 chopper with ToH FM ;)

P.S.: I hope my english was understandable enough.

P.P.S.: Bored with Hip already? I have something new for you, this time with Medium's FM :D

AH-1Z

UH-1Y

Edited by Rahonavis

Share this post


Link to post
Share on other sites
It doesn't add any new chopper, only interacts with those, that are already in ArmA, so no need to do any changes in the missions to fly them with ToH flight modelling ;)

P.S.: I hope my english was understandable enough.

P.P.S.: Bored with Hip already? I have something new for you, this time with Medium's FM :D

AH-1Z

UH-1Y

YOU ARE AWESOME! Thank you so much for the AH-1Z and UH-1Y! This is possibly the best thing to ever happen to ToH - for me at least.

Also, your English seems perfect to me; certainly a lot better than most native speakers that I know.

Thanks again for all of this :)

Edit: The only problem that I've noticed is that the bottom HUD display (the one which shows you your speed, vertical speed, torque, etc) doesn't work on the helicopters with the new flight model. I didn't notice with the Hip, because the heavy flight model is relatively easy to fly without damaging, so I never bothered to turn the HUD on. But the medium flight model over-torques from just about anything you do with the helicopter, so I tried to turn the HUD on so I could see when I was over-torquing, but it didn't show up. Is there any way to make this show up?

Edited by Mattressi

Share this post


Link to post
Share on other sites

It's not something I'm sure of, but I guess, that's not possible (at least not without messing with some core A2 files). Avionics of A2 choppers are much more simplified and it seems to me, that's why they don't interact with ToH well. I may be wrong and it may actually possible, but even if so, it's something compeletelly out of my league, so can't help you, sorry. :(

Share this post


Link to post
Share on other sites
It's not something I'm sure of, but I guess, that's not possible (at least not without messing with some core A2 files). Avionics of A2 choppers are much more simplified and it seems to me, that's why they don't interact with ToH well. I may be wrong and it may actually possible, but even if so, it's something compeletelly out of my league, so can't help you, sorry. :(

No need to be sorry - you've done great work! Just thought I'd ask in case there was a quick fix. It's not too big of an issue - I'll just fly less crazy lol.

Share this post


Link to post
Share on other sites

Great work on this, cant wait to try it out with a few mates.

Also, what do you guys think of a mi2 or ka25k? I have some low poly models in the works at the moment (for another project) that I was thinking of perhaps making into better models for TOH?

Share this post


Link to post
Share on other sites
Dan;2227845']Also' date=' what do you guys think of a mi2 or ka25k? I have some low poly models in the works at the moment (for another project) that I was thinking of perhaps making into better models for TOH?[/quote']

Sounds great! I'd love to see an Mi-2. Hadn't heard of the Ka-25 before, but it looks awesome too.

Share this post


Link to post
Share on other sites
Dan;2227845']Great work on this' date=' cant wait to try it out with a few mates.

Also, what do you guys think of a mi2 or ka25k? I have some low poly models in the works at the moment (for another project) that I was thinking of perhaps making into better models for TOH?[/quote']

At this point any kind of new helicopter is vital for ToH in my opinion. Personally I agree with PvPscene's opinion about the potential of Rearmed in terms of multiplayer cooperation between chopper pilots and land troops - just imagine virtual helo squadrons cooperating with other teams/clans in mp missions - supplies, insertions, extractions, MedEvac, CAPs, C-SARs and all sorts of other missions played by real players, specialize in either air or land (virtual) combat. Imagine this type of missions played in VTE or UNS mod :yay: With ToH's approach to civil exploatation of helicopters we could allso play some natural disaster-elimination, or law - enforcement missions. This type of online coop between different forces is something practicly unseen in other helicopter simulators (yeah, regardless of some opinions from other flightsimmers ToH deserves a 'title' of a flight simulator imho, though Hind FM would use a little tweaking) and, with this new level of realism, unseen even in ArmA, not to mention some other titles (I bet, you get, which ones I mean ;) ). Honestly I feel the game has such modding potential, that if someone would make some dinos and other stuff for it, we could have a very playable Jurassic Park mod (as you can guess from my nickname, I'm a huge dino and all things-reptile fan ;) ). This JPmod is not something I'd suggest modders to focus on, but it's merely an example, that we can even do something exceeding usual usement of A2/ToH to enchance the fun of playing ;)

The only problem for now is that ToH looks to be like in some kind of stagnation. By this I mean relatively low levell of interest in this game (at least that's, how I see that). Most flightsimmers gave up on ToH and I'm not really sure, why - the game had it's teething problems, but it's mostly behind us now, and if we ever get vortex ring, it will became a full-scale helosim.

By looking on ArmA I think, that we can break this stagnation bymaking mods for ToH. In my opinion ArmA isn't a popular title just because of its realism and general playability, but allso (if not mainly) thanks to mods. It looks, like constant enchancements in the game make it constantly attractive for both 'seasoned' and new players. And I think ToH should follow same pattern.

The short way to do it is by making ArmA choppers fitted with ToH-class FM, to create a something like a basis for eventual future mods. But it is upon those mods to create wider interestment in Rearmed, so go ahead with your ideas. :D

And personally I'd go mainly with the Mi-2 for couple of resons. Firstly there were more built and they were in much wider use, than Kamov. Secondly I'm afraid, that making realistic FM for a typical Kamov coaxial helicopter is pretty impossible (I think ToH doesn't really support coaxials, so you may get an arcadish style FM with all the good sides of this rotor configuration, but without it's downsides, like clashing the rotor blades due to over-G), so I'd treat this one, as a sort of background project ;)

As for the low poly, personally I prefer relatively low-poly exterior in favour of detailed interior. Flying from the cockpit I don't get much chance to admire the overall appearence of my chopper, and keeping it low-poly allows to have better performance.

P.S.: Just for a note, I've been trying to put my Mi-1M/MU/SM-1W "Hare" model for ToH, but I kinda stuck in a dead end, so it's no go for this one (for now at least)

EDIT:

If you'd need some info on Mi-2, let me know. I have some contact with Cygan, who is technician on Polish Mi-2s and Mi-24s.

EDIT2:

YOU ARE AWESOME! Thank you so much for the AH-1Z and UH-1Y! This is possibly the best thing to ever happen to ToH - for me at least.

You may like reading these then:

AH-1Z PocketGuide

UH-1Y PocketGuide

I used those to adjust span of the skids in FMs used with A2 Viper and Venom ;)

Edited by Rahonavis

Share this post


Link to post
Share on other sites

I completely agree with everything you said Rahonavis. I've noticed the lack of life here since...well, since I came here a few months ago. I've been hoping that it was because people didn't see much point modding things into ToH, when BI were going to do most of the work for them (with the Rearmed patch). Now that Rearmed is out, I think/hope some of the modders and scenario makers will bring this game back to life. If I had any talent and time, I would contribute, but I don't have either unfortunately. I'm very thankful for everyone who makes all the great mods and scenarios for ToH (and all games, really).

Also, thanks for those pocketguides - I haven't seen them before and they've got some great info :D

Share this post


Link to post
Share on other sites

I am planning on doing some missions in rearmed, but it wont be until next week that I will be starting them more then likely.

Share this post


Link to post
Share on other sites

Well an easy start would be to take A2/OA missions with the player as east helicopter/plane and swap up it out with a Hind (if you have the DLC). :)

(There is also a littlebird in Hinds, isnt it?)

Or with the choppers Rahonavis is supplying here.

Share this post


Link to post
Share on other sites

We do have Hinds, as well as littlebirds (default ones from TOH), but I was thinking of a PMC style mission using PMC stuff, based in Chernarus.

BTW do the torque gauges on the avionics actually work with the A2 helis once you use the new FM because it is pretty useful for me to look at that?

ALso thanks for the offer of info for the mi2, will probably take you up on that once I get a bit more time to start on the project. I had a look on global security and wikipedia and saw all the variants! One amazingly versitile helicopter.

Edited by [EVO] Dan

Share this post


Link to post
Share on other sites

Sounds great, Dan! Honestly, I'd love for any new ToH content. I've always wished that the Littlebird mission from OA would be ported into ToH, since there's even a littlebird in ToH. But if someone ported other missions and put Hinds in, that would be awesome too. I just love flying all kinds of missions. I loved both of your previous missions, Dan. I've played them so many times now, lol.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  
Followers 0