Page MenuHomeFeedback Tracker

1.96 release engine issues megaticket
Reviewed, NormalPublic

Description

Just using this to collect all issues encountered on 1.96 release such that nothing is forgotten.
This ticket is only really about engine issues. Asset issues are seperate.

  • non ascii characters in pbo names crashing server/client
  • some weird signature verification errors
  • createVehicleLocal restrictions enabled even though they should not be
  • parseSimpleArray not properly un-escaping double quotes anymore
  • some weird command line parsing issues on linux (not a bug but a feature now)
  • -bepath parameter parsing broken
  • Memory leak on every compiled script (Cache disabled again)
  • Box trucks LOD broken https://feedback.bistudio.com/T146148

Details

Severity
Major
Resolution
Open
Reproducibility
N/A
Operating System
Windows 8 x64
Category
General
Additional Information
  • non ascii characters in pbo names crashing server/client

Test case has been sent to Dwarden "Wolf_Krankenhuustest_dedmen.zip".
pbo named "wolf_kränkenhuus.pbo" in addons folder causes
Windows: Cannot open file 'D:\Steam\steamapps\common\Arma 3\@Wolf_vehicles\addons\wolf_kr�nkenhuus'
Linux: Cannot open file '/home/steam/arma3/mods/@wolf_vehicles\addons\wolf_kr�nkenhuus'

  • createVehicleLocal restrictions enabled even though they should not be

unsafeCVL changes were removed from perf/prof previously as the implementation was bugged/unfinished.
For some reason it has been enabled now and createVehicleLocal is being blocked by default, which should not be the case.
https://feedback.bistudio.com/T146139

  • parseSimpleArray not properly un-escaping double quotes anymore

1st problem (minor)
KK wrote on biki Since Arma 3 v.1.95.145925 the command will tolerate extra spaces and supports single quotes.
But changelog says Added: Support for 'any' and '' to parseSimpleArray changelog is missing "tolerate extra spaces", I checked, it does indeed tolerate extra spaces now just missing on changelog.
2nd problem (major, breaks existing SQF scripts, even first broken CBA function reported)
1.94 profiling v2:

sqf
parseSimpleArray "[""hint """"hello world"""";""]";
//Result: ["hint ""hello world"";"]

1.96 release:

sqf
parseSimpleArray "[""hint """"hello world"""";""]";
//Expected ["hint ""hello world"";"]
//Result: ["hint """"hello world"""";"] (inner escaped double quotes not being un-escaped properly, whereas they were previously)

but single quotes now work correctly.

sqf
parseSimpleArray '[''hint ''''hello world'''';'']'
//Expected ["hint ''hello world'';"]
//Result: ["hint ''hello world'';"]
  • some weird command line parsing issues on linux

(Arma Discord) https://discordapp.com/channels/105462288051380224/105464899567669248/638819818870669342
https://discordapp.com/channels/105462288051380224/105464899567669248/638826370138505216

  • -bepath parameter parsing broken

(Arma Discord) https://discordapp.com/channels/105462288051380224/105464980635176960/638820541985325076

  • Memory leak on every compiled script

https://feedback.bistudio.com/T135718

Event Timeline

dedmen created this task.Wed, Oct 30, 3:56 PM
dedmen renamed this task from 1.96 release issues megaticket to 1.96 release engine issues megaticket.Wed, Oct 30, 4:03 PM
dedmen updated the task description. (Show Details)
dedmen edited Additional Information. (Show Details)
dedmen updated the task description. (Show Details)Wed, Oct 30, 4:39 PM
dedmen edited Additional Information. (Show Details)

The script compile memory leak is back! woo
https://feedback.bistudio.com/T135718

dedmen updated the task description. (Show Details)Wed, Oct 30, 4:52 PM
dedmen edited Additional Information. (Show Details)

Thanks for the summary of 1.96 issues. We are working on fixes. I am sorry for troubles.

Astaroth changed the task status from New to Reviewed.Thu, Oct 31, 3:24 PM
Astaroth claimed this task.

I am sorry for troubles.

I'm a programmer, you don't need to tell me that :D Hope youre not having too much of a hard time over there o7

Could we get some more information about these v3 signatures you guys have been trying to push since the last few patches? It's caused issues with every release attempt so far. Is this intended to work with old signatures, or will some v2 signatures that have worked until now won't work anymore? Because that's what is happening again now and if that's intended, then it's going to be a real problem with trying to maintain a secure server that uses mods that haven't been updated since some time.

dedmen added a comment.Fri, Nov 1, 3:55 PM

@K.Hunter old signatures will keep working.

topden added a subscriber: topden.EditedFri, Nov 1, 4:45 PM

@K.Hunter old signatures will keep working.

do you guarantee?

dedmen updated the task description. (Show Details)Mon, Nov 4, 8:23 PM

Hello, thank you for the ticket.

Now most of these issues should be fixed in the current RC, with one exception being the parsing of linux parameters, but that one is actually behaving as it should and has an easy workaround.

Other than that, we've just released an RC branch update with a fix for the signatures, so I would like to ask anyone who have encountered this issue, if you can, please try to give it a shot in RC.

Thank you and Miller bless you

dedmen updated the task description. (Show Details)Tue, Nov 12, 5:46 PM
dedmen updated the task description. (Show Details)Tue, Nov 12, 5:50 PM

parseSimpleArray fix is confirmed.
boxtruck fix I confirmed last RC.
memory leak fix confirmed (I'll fix that properly once I get my new job :D)
non ascii characters in pbo names confirmed fixed, but only tested on windows client, not on Linux server.

CVL fix not confirmed, can't test it right now so I'm leaving it in until someone confirms it fixed.
Same for signatures, I cannot confirm that on my own. But two people on Arma Discord confirm it as good. Though one issue with JSRS but might very well be mod specific issue now.
-bepath I also cannot test as I don't use BE.

dedmen updated the task description. (Show Details)Tue, Nov 12, 5:53 PM

Signatures issue is now fixed

dedmen updated the task description. (Show Details)Wed, Nov 13, 4:11 PM

I can't check -bepath, but I'm gonna assume thats solved and we can just close this ticket now @Astaroth