Muzzle Flash Bug: Difference between revisions

Latest revision as of 12:04, 6 December 2023

The Problem

This problem may occur for addonmakers in the form of the muzzle flash of a weapon model is visible at all times ingame, and does not simply flash when fired.

The Solution

This problem has two solutions. You may have to do both.

Solution 1

Open your model in Oxygen 2 and make sure that the selection zasleh does infact highlight the model part of the muzzle flash on your weapon. Do this in all the LODs.

If in some LOD the muzzle flash selection does not highlight when clicking the zasleh selection, select it on your model, rightclick zasleh in the selections window and select redefine selection.

Solution 2

In your Config.cpp (for OFP) or model.cfg (for Armed Assault), you should include (or already have) a CfgModels class, which includes the weapon name as classes. For instance, your weapon model is named "MyM16A2.p3d", then the CfgModels section should look as following:

class CfgModels
{
	class Default {};
	class Weapon : Default {};
	class MyM16A2 : Weapon {};
};

This should be inserted into your Config.cpp (only for Operation Flashpoint) before your CfgVehicles or CfgWeapons sections and you have to put it in there before binarizing the model.

@@ Line 1: / Line 1: @@
-==The Problem==
+__NOTOC__
+== The Problem ==
 This problem may occur for addonmakers in the form of the muzzle flash of a weapon model is visible at all times ingame, and does not simply flash when fired.
-==The Solution==
-This Problem has two solutions. You may have to do both.
-===A)===
+== The Solution ==
+This problem has two solutions. You may have to do both.
+=== Solution 1 ===
 Open your model in [[Oxygen 2]] and make sure that the selection [[zasleh]] does infact highlight the model part of the muzzle flash on your weapon. Do this in all the [[LOD]]s.
 If in some [[LOD]] the muzzle flash selection does '''not''' highlight when clicking the [[zasleh]] selection, select it on your model, rightclick [[zasleh]] in the selections window and select '''redefine selection'''.
+=== Solution 2 ===
-===B)===
+In your [[Config.cpp]] (for OFP) or [[model.cfg]] (for {{arma1}}), you should include (or already have) a CfgModels class, which includes the weapon name as classes. For instance, your weapon model is named "MyM16A2.p3d", then the {{hl|CfgModels}} section should look as following:
-In your [[Config.cpp]] (or in some cases, [[Config.bin]]), you should include (or allready have) a CfgModels class, wich includes the weapon name as classes. For instance, your weapon model is named "MyM16A2.p3d", then the CfgModels section should look as following:
+<syntaxhighlight lang="cpp">
-<code>class CfgModels
+class CfgModels
 {
 	class Default {};
-	class Weapon: Default {};
+	class Weapon : Default {};
-	class MyM16A2: Weapon {};
+	class MyM16A2 : Weapon {};
-};</code>
+};
+</syntaxhighlight>
+This should be inserted into your [[Config.cpp]] (only for {{ofp}}) '''before''' your {{hl|CfgVehicles}} or {{hl|CfgWeapons}} sections and you have to put it in there '''before''' [[Binarize|binarizing]] the model.
-This should be inserted into your [[Config.cpp]] '''before''' your CfgVehicles or CfgWeapons sections.
+{{GameCategory|ofp|Modelling}}