I don't quite understand why the memory LOD is so far off the visual LOD, but maybe as a workaround you could offer another parameter to set what LOD to use.
It would make more sense to use a visual LOD by default in my opinion, attachTo is a visual thing, but I can understand that you probably don't want to break existing code.
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Feed Advanced Search
Advanced Search
Advanced Search
Nov 4 2024
Nov 4 2024
CrankMasterPaul added a comment to T170774: attachTo to weapon proxy with followBoneRotation and offset leads to shifting.
Nov 3 2024
Nov 3 2024
Oct 22 2024
Oct 22 2024
Dec 14 2023
Dec 14 2023
Mar 14 2023
Mar 14 2023
CrankMasterPaul edited Steps To Reproduce on T170990: Flashlight quadratic attenuation does not work.
Mar 3 2023
Mar 3 2023
Jun 7 2021
Jun 7 2021
CrankMasterPaul renamed T158916: selectionPosition does not work with resolution LODs from selectionNames does not work with resolution LODs to selectionPosition does not work with resolution LODs.
Jun 3 2021
Jun 3 2021
Jun 2 2021
Jun 2 2021
Jun 1 2020
Jun 1 2020
May 10 2016
May 10 2016
CrankMasterPaul added a comment to T81281: Headless client getting kicked for invalid .bisign files.
No, re-signing does not fix it from my experience. If the keys were the issue that would mean clients would have issues with connecting too, and they don't have any.
I assume the headless client can't find his bisign files or something similar.
It's a bug with the Linux Arma server, thus this bug report.
CrankMasterPaul added a comment to T81281: Headless client getting kicked for invalid .bisign files.
Normal players can connect just fine, only the headless client gets kicked.
Of you turn verifySignatures off the headless client works just fine.
I assume the headless client can't find his bisign files because of the slash.
© Bohemia Interactive a.s. Bohemia Interactive® is a registered trademark of Bohemia Interactive a.s. All rights reserved. · Privacy Policy · Terms and Conditions