Jump to content
Dwarden

A2/A2:OA Patch 18.12.2015

Recommended Posts

there appear to be working camo1 and camo2 selections for the outer skin in lods 1-5, but in 6 it has camo3 only.

e.g.

 

camo1 = mi35_001_co.tga

camo2 = mi35_002_co.tga

 

and

camo3 = mi35_mlod_ca.tga  --> this is a blank beige texture

 

so how would we fix it? delete lod6?

 

We could fix it deleting the lod6 or creating a working texture for that lod (but I haven't experience on texturing!)

Share this post


Link to post
Share on other sites

Hi goliath86,

 

Is this a config issue that you can fix? Or is it a JSRS problem?

 

 

Hi dreadpirate!

I've tested it and I can't reproduce the issue you encounter. I've used the latest version of JSRS (v1.5 final) and CBA (v1.0.1.196)

  • Like 1

Share this post


Link to post
Share on other sites

We could fix it deleting the lod6 or creating a working texture for that lod (but I haven't experience on texturing!)

yeah lod6 is a simple single mesh with a crappy basic blank texture, and camo3 overlaps both camo1 and camo2 selection areas so i guess deleting it is the way to go

  • Like 1

Share this post


Link to post
Share on other sites

Hi dreadpirate!

I've tested it and I can't reproduce the issue you encounter. I've used the latest version of JSRS (v1.5 final) and CBA (v1.0.1.196)

 

Hmmm. It must be a problem with my install, I guess.

 

I got all the files from Armaholic. I thought I had it all patched up correctly.

 

Let me reinstall everything and see what happens.

 

Sorry for wasting your time.

 

Edit: Still not working for me, I guess I won't use G36s in my missions...

Share this post


Link to post
Share on other sites

Hmmm. It must be a problem with my install, I guess.

 

I got all the files from Armaholic. I thought I had it all patched up correctly.

 

Let me reinstall everything and see what happens.

 

Sorry for wasting your time.

 

Edit: Still not working for me, I guess I won't use G36s in my missions...

 

It is very strange cause I can't reproduce that issue. Try to change the CorePatch.pbo name (like CorePatch.pbo.bak) excluding the corepatch update and retry your tests.

Share this post


Link to post
Share on other sites

And please, need to fix.

If you destroy any of the Mi-24 (Russian, CDF, ChDKZ, Takistan), it (does not matter) creates a destroyed model of the Taskitan Army Mi-24.

The same problem with Su-25 and Mi-8, creates destroyed CDF Su-25, and creates destroyed Russian Mi-8.

Share this post


Link to post
Share on other sites

dyou mind confirming how? i need to repeat fix in my nmod pack too! thx mate

Share this post


Link to post
Share on other sites

dyou mind confirming how? i need to repeat fix in my nmod pack too! thx mate

 

I've deleted the LOD n. 6.000 :ph34r:

  • Like 1

Share this post


Link to post
Share on other sites

It is very strange cause I can't reproduce that issue. Try to change the CorePatch.pbo name (like CorePatch.pbo.bak) excluding the corepatch update and retry your tests.

 

That fixed it! All the G36 variants sound the same now.

Share this post


Link to post
Share on other sites

Hi, 

 

is it possible to change the Pchela back to the single-seated one. Since this update came out this version does not longer exist in epoch and instead there is a two-seater version of the Pchela now. But this two-seater version is hard to fly and makes not that fun like the old one with one seat. It would be great if this changed back. 

 

Thanks Megamoep

Share this post


Link to post
Share on other sites

Hi goliath86, don't know if this is something you can fix or if it's a JSRS issue, but the following weapons:

 

G36a 

G36K 

G36A_camo 

G36K_camo

 

use the default OA sounds, while these weapons:

 

G36C

G36C_camo

MG36 

MG36_camo

 

use the JSRS sounds.

 

Also, the:

 

m8_SAW

 

uses the OA sound, while all the other M8s use the JSRS sound.

This was due to...

Share this post


Link to post
Share on other sites

... these changes

hi Goliath, Dwarden etc

 

thanks for all the work you put in - am looking forward to seeing the improvements - many hidden performance boosts from not having undefined variables spamming the logs! etc

 

I have one minor, but annoying issue to report

 

I can verify that the modeloptics is borked in the G36's

We use modded versions which reproduce many of the BIS configs, so I imagine it is way up the inheritance

I would suggest you look here

	class G36a: Rifle
	{
		muzzles[] = {"MuzzleFar"};
		class MuzzleFar: G36C
		{
			optics = 1;
			opticsDisablePeripherialVision = 1;
			modelOptics = "\ca\weapons\G36\G36_optics"; //IS THIS MISSING?

as all of the G36's inherit this from muzzlefar.

Already fixed for next patch!

  • Like 1

Share this post


Link to post
Share on other sites
if (BIS_ARTY_DEBUG==1) then>

  Error position: <_shell);

};

 

if (BIS_ARTY_DEBUG==1) then>

  Error Undefined variable in expression: _shell

File ca\modules\ARTY\data\scripts\ARTY_shellMonitor.sqf, line 165

Error in expression <dCount = 0;};

 

 

waitUntil

{

if (!isNull(_shell)) then

{

private "_pos";

 

_shellP>

  Error position: <_shell)) then

{

private "_pos";

 

_shellP>

  Error Undefined variable in expression: _shell

File ca\modules\ARTY\data\scripts\ARTY_shellMonitor.sqf, line 90

Error in expression <;

};

};

};

};

Share this post


Link to post
Share on other sites
Error in expression <ep 5;

_batteryLead = _batteryScope call BIS_ARTY_F_BatteryLead;

};

 

if (isNull(_>

  Error position: <BIS_ARTY_F_BatteryLead;

};

 

if (isNull(_>

  Error Undefined variable in expression: bis_arty_f_batterylead

File ca\modules\ARTY\data\scripts\ARTY_Firebase.sqf, line 31

Error in expression <

 

for [{_i=0;},{_i < count (units group _batteryLead);},{_i=_i+1;}] do

{

_curUni>

  Error position: <_batteryLead);},{_i=_i+1;}] do

{

_curUni>

  Error Undefined variable in expression: _batterylead

File ca\modules\ARTY\data\scripts\ARTY_Firebase.sqf, line 79

Error in expression <ScopeVars", _batteryScope], false] call BIS_ARTY_F_NetRun;

};

};

 

 

_batteryScope>

  Error position: <BIS_ARTY_F_NetRun;

};

};

 

 

_batteryScope>

  Error Undefined variable in expression: bis_arty_f_netrun

File ca\modules\ARTY\data\scripts\ARTY_Firebase.sqf, line 166

Error in expression < BIS_ARTY_F_BatteryLead;

};

 

if (isNull(_batteryLead)) exitWith {

if (BIS_ARTY_D>

  Error position: <_batteryLead)) exitWith {

if (BIS_ARTY_D>

  Error Undefined variable in expression: _batterylead

File ca\modules\ARTY\data\scripts\ARTY_Firebase.sqf, line 34

No owner

Share this post


Link to post
Share on other sites

New patch, new errors. My weekend games were spoiled by two bugs. Ðll seen in the screenshots:

http://images.akamai.steamusercontent.com/ugc/352771022152201292/622DA8975A655ED0AB13893465E2C9B2B90FC0F9/

http://images.akamai.steamusercontent.com/ugc/352771022152202261/03F09222B17CC4693262EF0A65608ACC3286AC3A/

Please, next time Ñheck that what you are doing before release.

 

Share this post


Link to post
Share on other sites

New patch, new errors. My weekend games were spoiled by two bugs. Ðll seen in the screenshots:

http://images.akamai.steamusercontent.com/ugc/352771022152201292/622DA8975A655ED0AB13893465E2C9B2B90FC0F9/

http://images.akamai.steamusercontent.com/ugc/352771022152202261/03F09222B17CC4693262EF0A65608ACC3286AC3A/

Please, next time Ñheck that what you are doing before release.

Ðе иÑпользуй корпатч, в Ñтиме выбери бета-патч - Legacy, и вÑÑ‘.

Share this post


Link to post
Share on other sites

alexvladn, thanks for report!

New patch, new errors. My weekend games were spoiled by two bugs. Ðll seen in the screenshots:

http://images.akamai.steamusercontent.com/ugc/352771022152201292/622DA8975A655ED0AB13893465E2C9B2B90FC0F9/

http://images.akamai.steamusercontent.com/ugc/352771022152202261/03F09222B17CC4693262EF0A65608ACC3286AC3A/

Please, next time Ñheck that what you are doing before release.

These bugs are fixed. BTW, thanks for report!

 

Ðе иÑпользуй корпатч, в Ñтиме выбери бета-патч - Legacy, и вÑÑ‘.

I think he can decide without you.

Share this post


Link to post
Share on other sites

New patch, new errors. My weekend games were spoiled by two bugs. Ðll seen in the screenshots:

http://images.akamai.steamusercontent.com/ugc/352771022152201292/622DA8975A655ED0AB13893465E2C9B2B90FC0F9/

http://images.akamai.steamusercontent.com/ugc/352771022152202261/03F09222B17CC4693262EF0A65608ACC3286AC3A/

Please, next time Ñheck that what you are doing before release.

I have no those errors.

Share this post


Link to post
Share on other sites

I have no those errors.

Seems, hotfix was published yesterday.

Share this post


Link to post
Share on other sites

Seems, hotfix was published yesterday.

I did not have these errors before Hotfix.  

yet one from arty module:

 

-----------------------------

 

Error in expression <};
} forEach vehicles;
};
 
 
_this spawn BIS_ARTY_F_Firebase;
>
  Error position: <BIS_ARTY_F_Firebase;
>
  Error Undefined variable in expression: bis_arty_f_firebase
File ca\modules\arty\data\scripts\init.sqf, line 101
Error in expression <};
} forEach vehicles;
};
 
 
_this spawn BIS_ARTY_F_Firebase;
>
  Error position: <BIS_ARTY_F_Firebase;
>
  Error Undefined variable in expression: bis_arty_f_firebase
File ca\modules\arty\data\scripts\init.sqf, line 101

Share this post


Link to post
Share on other sites

I found this error in my .rpt file

Error in expression <e ["BIS_IS_inAgony",false]};







if (_healerIsAlreadyDragger) then
{



deta>
  Error position: <_healerIsAlreadyDragger) then
{



deta>
  Error Undefined variable in expression: _healerisalreadydragger
Error in expression <e ["BIS_IS_inAgony",false]};







if (_healerIsAlreadyDragger) then
{



deta>
  Error position: <_healerIsAlreadyDragger) then
{



deta>
  Error Undefined variable in expression: _healerisalreadydragger
Error in expression <e ["BIS_IS_inAgony",false]};







if (_healerIsAlreadyDragger) then
{



deta>
  Error position: <_healerIsAlreadyDragger) then
{



deta>
  Error Undefined variable in expression: _healerisalreadydragger

 

Share this post


Link to post
Share on other sites

I found this error in my .rpt file

 

Error in expression <e ["BIS_IS_inAgony",false]}; if (_healerIsAlreadyDragger) then { deta>

   Error position: <_healerIsAlreadyDragger) then { deta>

   Error Undefined variable in expression: _healerisalreadydragger

 

Error in expression <e ["BIS_IS_inAgony",false]}; if (_healerIsAlreadyDragger) then { deta>

   Error position: <_healerIsAlreadyDragger) then { deta>

   Error Undefined variable in expression: _healerisalreadydragger

 

Error in expression <e ["BIS_IS_inAgony",false]}; if (_healerIsAlreadyDragger) then { deta>

   Error position: <_healerIsAlreadyDragger) then { deta>

   Error Undefined variable in expression: _healerisalreadydragger

 

 

I can attest that this particular error is not a patch regression, it is a rare error of the First Aid (FA) module "healer.sqf" that has been logging since v1.63 came out.  It occurs when FA and Battlefield Clearance (BC) modules are both used.  It seems to occur when a dragger is releasing a wounded unit, and the variable "BIS_BC_dragger" is nil.  The error is so rare in my own missions I never figured out why "BIS_BC_dragger" would be nil.

 

This is what I think is happening:

in "healer.sqf":

_healerIsAlreadyDragger = _healer getVariable "BIS_BC_dragger";if (isNil "_healerIsAlreadyDragger") then {_healer setVariable ["BIS_BC_dragger",false]};
_healerInAgony = _healer getVariable "BIS_IS_inAgony";if (isNil "_healerInAgony") then {_healer setVariable ["BIS_IS_inAgony",false]};

//if (_healerIsAlreadyDragger) exitWith {textLogFormat["FA_HEALER_ EXIT _healerIsAlreadyDragger %1",[_injured, _healer]];}; //cannot be dragger-healer 

if (_healerIsAlreadyDragger) then 
{
  //stop drag
  //see (BIS_BC_Path + BIS_PATH_SQF + "draggerStop.sqf") ... this block should correspond
  
  detach _injured;

In the script, if unit's variable "BIS_BC_dragger" is defined, it gets used to define _healerIsAlreadyDragger.

When unit's variable "BIS_BC_dragger" is not defined, it gets defined as false.

But _healerIsAlreadyDragger is not defined again after the unit's variable returned nil.

The script continues on with the _healerIsAlreadyDragger undefined, which causes the error.

 

The same would seem to happen with _healerInAgony if "BIS_IS_inAgony" was undefined, but I never encountered that error.  The _healerIsAlreadyDragger error was rare.

Share this post


Link to post
Share on other sites

Hi

 

Lot of my clanmembers and members of our alied clan, started to have one really annoing issue lately and iam not sure if it couldnt be caused by the patch.

 

The issue is that they cannot join any servers including my, because theyr battle eye failed to instal (or something like that) the temporary solution is, to uninstall battleeye remove all traces of battleeye from the computer and then verify gamechache from steam and instal battleeye again. Worst thing is, they have to go trough this procedure almost every time they try to connect to a server. Reinstalling battleye four times a day becomes tiresome after some time. Iam not having the issue, so i cant get more detail.

Share this post


Link to post
Share on other sites

we just had a 22 man co-op last night, and had no problems.

 

We prepped the players over the course of the weekend - most had some issues with latest PWS version which seems to think you only play arma 3 and was forcing the launcher to use arma3.exe from the OA folder (nutso eh), or with some people it made some files read-only thus causing a different error - permissions unavailable for this repository.

 

we had to roll everyone back to previous PWS versions we had cached, aside from this, which is a PWS issue, i can say the patch is working fine for us.

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

×