Bug #7486

You can not save custom loadout

Added by kju over 5 years ago. Updated over 4 years ago.

Status:Closed Start date:12/28/2009
Priority:Normal Due date:
Assignee:BCA_Cat_Toaster % Done:

100%

Category:-
Target version:release 1.14

Description

Second most annoying bug is when you're done with choosing loadout and filling up a gear slots you can not save custom loadout at the moment. You should wait for timer (i think you know what i mean) is up. I think saving a little bit changed loadout is NOT the same when you change Class. So i think it's a bug that wastes priceless seconds in the game.

Report by BLR GVOZD

error.rpt (25.5 kB) BCA_Cat_Toaster, 08/02/2010 14:31

moreerrors.txt (41.7 kB) BCA_Cat_Toaster, 08/03/2010 18:15

aas100_ArrowheadTemplate.Desert_E.pbo - Demonstration (1.3 MB) BCA_Cat_Toaster, 08/03/2010 18:15


Related issues

related to Advance and Secure (AAS) - Bug #4699: selecting custom loadout before one is saved gives empty kit Closed 09/21/2009

History

Updated by BCA_Cat_Toaster over 5 years ago

Confirmed.

Well, the armory timer was originally introduced to avoid armory-overusage, not to avoid custom-loadouts.

We tried to design the Classes and Kits in a way that makes manual loadouts in a way obsolete in the future (at least I did that) and to avoid "crazy loadouts" and "supersoldiers".
Personally I´m not using manual loadouts at all since we got the new Kit-System and because it simply eats up to much time and needs to be done in every mission again and again, even without this "bug" but I guess that´s not relevant.

Temporary workaround might be using the "Classic-Ruleset", Armory-Timer is set to just 5s in this Ruleset. Public rulesets features 30s and all others 60s.

As we have plenty of bugs with higher impact on todays gameplay and very limited resources to fix I´ve set the priority back to normal on this.

Updated by BCA_Cat_Toaster over 5 years ago

  • Priority changed from Urgent to Normal
  • Target version changed from Beta 09 V0.5 to release 1.0

Updated by BCA_Cat_Toaster about 5 years ago

  • Target version changed from release 1.0 to thefuture

Updated by BCA_Cat_Toaster almost 5 years ago

bypassed this issue for now by removing "Save-/Load Custom-Loadouts" in Default-Rules for a couple of weeks already as it was causing plenty of rpt-Errors as well. Might be re-enabled if fixed some day.

Updated by kju almost 5 years ago

What rpt errors/warnings for example?
It was warning in my editor tests after my changes. Not for you?

Updated by BCA_Cat_Toaster almost 5 years ago

Xeno told me that this was causing Script-Errors, don´t have any RPT-Data that´s older then three days. Maybe I understood/did something wrong? Don´t know, but the issue that you end up being naked loading a custom loadout without having saved one before was never fixed, right?

Updated by kju almost 5 years ago

I have fixed this in the OA version.

Updated by BCA_Cat_Toaster almost 5 years ago

lol, ok, checking again.

Updated by BCA_Cat_Toaster almost 5 years ago

  • File error.rpt added
  • Status changed from Assigned to Feedback
  • % Done changed from 0 to 100

indeed you end up still being naked but you can switch back to another Kit now without being Stuck and the need to kill yourself and respawn. Sorry for the confusion! However with testing this I now got the rpt-errors again appearing multiple times. With disabling the feature I got rid of those entries. Please take a look at the file attached.

Updated by Xeno almost 5 years ago

That was in version 1.11 or 1.12 (can't remember exactly). Haven't had any script errors popping up in the last version.

Something about clientdebug

Updated by kju almost 5 years ago

All works fine here and as advertised.

So please provide step by step repro.

Updated by BCA_Cat_Toaster almost 5 years ago

Well, just enabled Custom-Loadouts again, hostet the AAS-Template in LAN and clicked Custom-Loadout, back to a Class-/Kit, again Custom-Loadout, one more time and quit. Works as described before and found the rpt as provided.

Updated by BCA_Cat_Toaster almost 5 years ago

just did it again. Spawn default Red-X, go to an armory and click "Custom Loadout", then switch back any other Kit, then again "Custom Loadout"

No error at all in RPT if that feature is disabled while cycling thru all Classes and Kits.

Updated by kju almost 5 years ago

  • Assignee changed from CoolBox-SBS- to BCA_Cat_Toaster

ClientMainThread.sqf

Old: (line 310)

bool updateTagsThreadRun = false;

//------------------ main loop ----------------------------

New:

bool updateTagsThreadRun = false;

sleep 0.1;

//default values
customWeapons = weapons player;
customMagazines = magazines player;

//------------------ main loop ----------------------------

Updated by BCA_Cat_Toaster almost 5 years ago

  • Status changed from Feedback to Resolved
  • Target version changed from thefuture to release 1.15

checked in and tested on dedicated server. Great job and thanks kju! Custom Loadouts are enabled again.

Updated by kju almost 5 years ago

good to hear

Updated by BCA_Cat_Toaster almost 5 years ago

  • Status changed from Resolved to Closed

fixed in r624

Updated by BCA_Cat_Toaster over 4 years ago

  • Target version changed from release 1.15 to release 1.14

Also available in: Atom PDF