R3vo/Sandbox – User

From Bohemia Interactive Community
< R3vo
Categories:
mNo edit summary
mNo edit summary
 
(110 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{TOC|side}}
= Mobile To-Do =
Since Arma 3 Jets DLC (v1.68) it is possible to catapult Jets off an aircraft carrier. For this system to work properly a few new definitions need to be made inside the plane's config. This page will show an overview over the definitions and explain what they do.
''A list of things that would improve mobile compatibility''


== Aircraft Configuration ==


=== Requirments ===
''Lou thinks just because the list is empty there is nothing left to improve. Only if he knew.''
* Compatible aircraft must have an animation for arrest/tail hook selection defined in CfgVehicles and modeled in 3D model (model.cfg)
* Compatible aircraft must have a memory point for cable attach position


=== CarrierOpsCompatability Sub-Class ===
= Done =
<syntaxhighlight lang="cpp">
class CfgVehicles
{
class B_Plane_Fighter_01_F
{
tailHook = true; // Allow to land on carrier
class CarrierOpsCompatability
{
ArrestHookAnimationList[] = {"tailhook", "tailhook_door_l", "tailhook_door_r"}; // List of animation played to animate tailhook. Defined in model.cfg (type user)
ArrestHookAnimationStates[] = {0,0.53,1}; // Tailhook animation states when down, hooked, up.
ArrestHookMemoryPoint = "pos_tailhook"; // TailHook memory point in plane model.p3d
ArrestMaxAllowedSpeed = 275; // Max speed km/h allowed for successful landing
ArrestSlowDownStep = 0.8; // Simulation step for calcualting how smooth plane will be slowed down.
ArrestVelocityReduction = -12; // Speed reduced per simulation step
LaunchVelocity = 300; // Speed required for take off
LaunchVelocityIncrease = 10; // Speed increased per simulation step
LaunchAccelerationStep = 0.001; // Simulation step for calcualting how smooth plane will launched from carrier catapult.
LaunchBarMemoryPoint = "pos_gear_f_hook"; // LaunchBar memory point
};
};
};
</syntaxhighlight>


== Aircraft Carrier Configuration ==
* Creator dlc template needs a noresize.
Requirments:
** {{Link|Spearhead_1944}}
- Compatible carrier part must have a config definition for all sub-systems that will be invoked by this function
* Long command names should wrap
** {{Link|removeAllUserActionEventHandlers}}


example of cfgVehicles subclass definitions for carrier part;
* See also entries on command and function pages are broken
class Catapults
** {{Link|parsingNamespace}}
{
 
class Catapult1
* Command and function template layout wastes a lot of space due to the two column design
{
 
memoryPoint = "pos_catapult_01"; Memory point in carrier part model.p3d
* Tables with fixed widths need to be avoided. If they are too wide use noresize class wrapper
dirOffset = -5.5; Offset angle in degrees between carrier part direction and actual catapult launch direction
** {{Link|Arma_3:_Visual_Upgrade}}
animations[] = {"Deflector_1","Deflector_1_hydraulic_1", "Deflector_1_hydraulic_2","Deflector_1_hydraulic_3"}; Array with animation names for carrier part jet blast deflectors
 
launchActionName = "$STR_A3_action_launchFromCatapult_1"; Visual display name of "Attach Action"
* YouTube embeds and images should not have a fixed width
detachActionName = "$STR_A3_action_detachFromCatapult_1"; Visual display name of "Dettach Action"
** {{Link|Category:DayZ}}
};
** {{Link|Spearhead_1944_Frontline_Function}}
};
** It is because the youtube template has a hardcoded minimum width. This should get removed

Latest revision as of 18:11, 18 May 2025

Mobile To-Do

A list of things that would improve mobile compatibility


Lou thinks just because the list is empty there is nothing left to improve. Only if he knew.

Done

  • Command and function template layout wastes a lot of space due to the two column design
  • Tables with fixed widths need to be avoided. If they are too wide use noresize class wrapper