Page MenuHomeFeedback Tracker

access set ReadAndCreate for cfgRecoils in core config causes various problems
Closed, ResolvedPublic


1 - ReadAndCreate: only adding new class members is allowed

Discussed this already for TKOH Rearmed with Hozki and he forwarded the problem to programmers, yet unfortunately hasn't been addressed since.

Problems are:

  • recoil definitions aren't added to cfgRecoils
  • recoil definitions aren't modified
  • in certain, unclear, cases weapons have no recoil at all on those config conflicts {F21264} {F21265} {F21266}


Legacy ID
Steps To Reproduce

Run AiA with CO in A3:

  1. Make a config dump of cfgRecoils (run attached mission) to rpt and compare vs plain A3. Notice the missing definitions and faulty modifications.
  1. Play different scenarios in SP/MP, switch weapons, use save-load. In some cases weapons will no recoil at all.
Additional Information

You find both complete cfgRecoils for A3 and CO attached. Best use a diff tool to compare.
The // commented lines at the bottom are the ones actually used by A3 weapons.
The # hash tagged lines in both files are the ones used by CO weapons.


Two solutions I can see:

  1. Set access=0 in core configs
  2. Remove all non A3 recoil definitions from a3\weapons_f\config.cpp/cfgRecoils and make sure A3 weapons have new/unique names (_F tagged).

Event Timeline

kju-PvPscene edited Additional Information. (Show Details)
kju-PvPscene set Category to Config.
kju-PvPscene set Reproducibility to Always.
kju-PvPscene set Severity to None.
kju-PvPscene set Resolution to Fixed.
kju-PvPscene set Legacy ID to 1310363334.May 7 2016, 3:52 PM
pettka added a subscriber: pettka.May 7 2016, 3:52 PM

I have adjusted the access, it should be available in dev version probably tomorrow. Could You, please, take a look then and let me know if there is any further issue? Thanks a lot.

MadDogX added a subscriber: MadDogX.May 7 2016, 3:52 PM

Mass closing tickets marked as resolved more than 1 month ago.

If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.