Jump to content
Sign in to follow this  
mark2000

How to fix Permanent Muzzle Flash bug?

Recommended Posts

I'm having a problem with all the weapon mods I'm using. It seems that they always have that permanent muzzle flash bug regardless of what Display Device I am using. Are there other methods for fixing this bug?

I am playing the GOTY edition btw.

Share this post


Link to post
Share on other sites

I think that's a problem with the addOn itself, with incomplete CfgModels definitions in the addOn's config. Try testing some other weapon addOns and see if the problem occurs with them too.

Share this post


Link to post
Share on other sites

You were right. I downloaded an M4A1 mod pack specifically for Resistance and it didn't have the Muzzle flash glitch.

I really like the other guns I got though so I'd still like to fix them if possible. I think I found a solution for them so I'll be testing it later.

EDIT:

Great! It worked! AWESOME!

So...... I guess now I have to figure out how to use all these stuff I have without having to make my own missions. =/

Edited by mark2000

Share this post


Link to post
Share on other sites

As you have found out the problem is with pre-resistance addons. There was a cfgmodels statement added in the config.cpp. I have fixed many old addons for my own use, it's pretty simple.

1. Un-pbo the addon.

2. edit the config.cpp file

3. add theses lines near the top with other cfg statements.

class CfgModels

{

class Default{};

class Weapon: Default{};

class SJB_M16A2E3: Weapon{};

The last line is the name of the *.p3d model, make it match what you see in the line model=

example: model="\SJB_M16A2_E3\SJB_M16A2E3.p3d";

save the config.cpp file and repbo the folder.

Share this post


Link to post
Share on other sites

it most likely can as the Pakistan infantry addon i believe was made before Resistance.

Share this post


Link to post
Share on other sites
As you have found out the problem is with pre-resistance addons. There was a cfgmodels statement added in the config.cpp. I have fixed many old addons for my own use, it's pretty simple.

1. Un-pbo the addon.

2. edit the config.cpp file

3. add theses lines near the top with other cfg statements.

class CfgModels

{

class Default{};

class Weapon: Default{};

class SJB_M16A2E3: Weapon{};

The last line is the name of the *.p3d model, make it match what you see in the line model=

example: model="\SJB_M16A2_E3\SJB_M16A2E3.p3d";

save the config.cpp file and repbo the folder.

Yep. that's basically what I found out. There WAS one weapon mod I had that even this solution never cured of the bug. It was some M24 SWS addon that also had a standard Remington 700 included in it. I can't give any specifics because I deleted the file already. I never liked the m24 that much anyway.

Sorry if I placed this in the wrong section by the way. Since all the addons I use had the same problem even after following the work-arounds detailed by the authors, I thought that the problem was already in my part.

Share this post


Link to post
Share on other sites
// some basic defines

#define TEast 0

#define TWest 1

#define TGuerrila 2

#define TCivilian 3

#define TSideUnknown 4

#define TEnemy 5

#define TFriendly 6

#define TLogic 7

#define true 1

#define false 0

// type scope

#define private 0

#define protected 1

#define public 2

class CfgModels

{

class Default

{

sections[]={};

sectionsInherit="";

};

class Weapon: Default

{

sections[]={"zasleh"};

};

class SNSSAW: Weapon{};

};

class CfgPatches

{

class PORMG3Mag

{

units[] = {};

weapons[] = {PORMG3Mag};

requiredVersion = 1.10;

};

class PORMG3

{

units[] = {};

weapons[] = {PORMG3};

requiredVersion = 1.10;

};

class PORMG3Soldier

{

units[] = {PORMG3Soldier};

weapons[] = {};

requiredVersion = 1.10;

};

};

class CfgWeapons

{

class default {};

class MGun: Default {};

class MachineGun7_6: MGun {};

class MachineGun7_6Manual: MachineGun7_6 {};

class PORMG3Mag : MachineGun7_6Manual

{

scopeWeapon = private;

scopeMagazine = public;

weaponType=1;

displayName = "POR MG3";

displayNameMagazine = "POR MG3 mag";

shortNameMagazine = "POR MG3mag";

picture="\PORMG3\magp.paa";

ammo="Bullet7_6W";

count=250;

drySound[]={"weapons\M16dry",0.010000,1};

sound[]={\PORMG3\Fire.wav,db0,1};

soundContinuous=0;

reloadTime=0.070500;

dispersion=0.005000;

initSpeed=1000;

maxLeadSpeed=300;

ffCount=6;

aiDispersionCoefX=5;

ffMagnitude=0.500000;

ffFrequency=11;

recoil="riffleSingle";

autoFire=true;

aiRateOfFire=0.070500;

aiRateOfFireDistance=500;

useAction=0;

useActionTitle="";

};

class PORMG3 : MachineGun7_6Manual

{

scopeWeapon = public;

scopeMagazine = private;

weaponType=1;

displayName = "POR MG3";

picture="\PORMG3\weaponp.paa";

model="\PORMG3\PORMG3P3D.p3d";

muzzles[]={"PORMG3muzzle"};

class PORMG3muzzle : PORMG3Mag

{

reloadMagazineSound[]={"\PORMG3\reload.wav",db-40,1};

drySound[]={"weapons\M16dry",db-40,1};

modelOptics="\PORMG3\PORMG3OPTICSP3D.p3d";

optics = true;

opticsZoomMin=0.350000;

opticsZoomMax=0.350000;

distanceZoomMin=400;

distanceZoomMax=400;

magazines[]={"PORMG3Mag"};

};

};

};

class CfgNonAIVehicles

{

class ProxyWeapon {};

class ProxyPORMG3mag : ProxyWeapon {};

class ProxyPORMG3 : ProxyWeapon {};

};

class CfgVehicles

{

class All{};

class AllVehicles:All{};

class Land:AllVehicles{};

class Man:Land{};

class Soldier:Man{};

class SoldierWB:Soldier{};

class SoldierWMG: SoldierWB{};

class PORMG3Soldier: SoldierWMG

{

displayName="POR MG3 Soldier";

scope=2;

model="MC vojakW2";

weapons[]={"PORMG3","NVGoggles","Throw","Put"};

magazines[]={"PORMG3Mag","PORMG3Mag","PORMG3Mag","PORMG3Mag","PORMG3Mag"};

};

};

this is the config of addon from which i want to remove muzzle flash bug?

Share this post


Link to post
Share on other sites

Unless it's the model itself,the problem is staring you in the face.Read what Zulu said earlier and then look at your CfgModels section again.

Share this post


Link to post
Share on other sites
Unless it's the model itself,the problem is staring you in the face.Read what Zulu said earlier and then look at your CfgModels section again.

if you know what change i have to do for removing that bug than why you did't give solution.

Share this post


Link to post
Share on other sites

Because Zulu1 already described how to correct the problem,if it exists in the config.

I'm not being nasty.But a possible answer is no more than a few posts back.

I think you're perfectly capable of trying out that solution yourself.

Rather than having someone else do it for you,I simply thought you may learn

something from finding the solution on your own.No offence intended.

Look at your CfgModels section.Do you see any reference to the model PORMG3P3D.p3d?

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  

×