Don't get me wrong, the ticket has merit. I just wish there was less "me too" or "please fix" posts. At least the new feedback tracker doesn't notify for each and every reply and seems to summarize them.

What does obfuscation have to do with the static memory limit?

Obfuscation does increase memory usage, [...]

You answered your own question.

Honestly, your comment doesn't add anything new to the conversation.

Honestly, I do not care about your opinion. And stop bolding your replies as if that made it carry any more weight.

If people would stop using obfuscation (or BI would remove the ability to load obfuscated PBOs in the first place, like they did for Reforger), this problem would go away. Also can someone ban all the damn bot accounts, it is really annoying to read through all the noise.

Yes, and this ticket is specifically about Motorbike_01_ColorBase.

My gist is now obsolete, the functionality has been added to CF-Test (on Steam) as CF.ResolvePath and CF.FindFileEx. The latter is a wrapper around FindFile that'll do all the necessary work: Test if the issue is present, and then use CF.ResolvePath to deal with it. Switch all your FindFile calls to CF.FindFileEx to use it.

$storage: works fine, but you can only use it after the mission has started (OnMissionStart).

(this was re bzed's github link, not the ticket)

You can work-around it.
https://gist.github.com/lava76/c2abebb99ff4c9929e9e467a0e3895cc

gist is now obsolete. See https://report.bistudio.com/issues/DZEXP-134?commentId=6ac1194f41140b7f57c5c89d

FindFile is also broken for enumerating files in a mod PBO.

Same issue with trying to list anything in $mission and likely the other vars

It's in scripts/4_world/entities/manbase/dayzplayer/dayzplayercamera_base.c, around line 172

It seems the current 1.30 UpdateUDAngleUnlocked can be fixed by just replacing this block inside of it

				pAngleAdd 	= pAngle + pAngleAdd - target;
				pAngle 		= target;

with

				if (Math.AbsFloat(pAngleAdd) > 0.001)
				{
					pAngleAdd 	= pAngle + pAngleAdd - target;
					pAngle 		= target;
				}

(i.e. restoring the surrounding condition that was used in 1.29 and is also consistent with UpdateLRAngleUnlocked)

This looks (no pun intended) to be related to the changes in DayZPlayerCameraBase::UpdateUDAngleUnlocked in 1.30. Reverting these to the 1.29 code fixes the issue.