leddzepp

It has been around for a lot longer than that. I recall having similar issues back when fred41 first released his custom memory allocator. I haven't had any issues at all since removing the memory allocator parameter, with 8-10 hours gameplay. I also have an army of people on my communities' servers who can confirm it is working for them. (We have been stress testing on a variety of different mission files, also. [such as king of the hill, Altis Life, modded Life servers as well as NPC heavy missions.])

Have you removed -malloc= and/or unticked the option from the arma 3 launcher?

I'm simply a player who has always had a lot of issues with arma crashes, lag, etc and as such I have become well informed. I am not part of the dev team.

The mission selection screen only shows to admins, it will not show if you set the difficulty in the basic.cfg AND enable automatic initiation of the mission file. Additionally, the difficulty option players choose will be overrided by the servers difficulty settings. If you set it to 'Veteran' or 'Mercenary' then players will be forced to play with that difficulty regardless of their own options. In order to force a custom difficulty, you must edit the config.cfg to have the following. This will stop the 'Mission selection screen' from appearing, and force a custom difficulty. class Missions { class mission { template="NameofMission_mission.Altis";// omit the .pbo suffix difficulty="Custom";// difficulty: recruit, regular, veteran, mercenary or Custom (see CfgDifficulties in the main game config) }; }; As well as do what the above video states. If you want to autoinit the mission file so that it does not come up with mission select screen, add -autoinit to the command line for the arma3server.exe or .bat file you use to launch your server. NOTE: You MUST define a default mission where it says 'template=' above. All of these combined will make the server automatically start without the option to select the mission or difficulty. Again I will say only admins who have logged in via #login will be able to change the mission difficulty/choose a mission.

Greetings, I am a server manager at the SealTeamSloth community. One of our developers, Kevin, has given a video tutorial as to how you might do this. You must force the difficulty in both the username.Arma3Profile AND config.cfg file. The difficulty setting syntax we have used made by Killzone_Kid is in the description of the video!

Ensure you do not have large pages enabled. (Regedit: Image File Execution Options > Arma3.exe > UseLargePages 32-bit DWORD value to (0x000000) 0 NOTE: They are working on an actual fix. The 'FIX' I posted was simply intended to alleviate the LOD Degradation issue as a result of Dwarden working tirelessly to give users a chance to continue playing. THE REAL HOTFIX will come, just sit tight!

Hello guys! Please make sure you simply UNTICK the Malloc option in the launcher. More details below. Do not tick it to use tbb4malloc_bi, as some users have reported they still get the 1fps issue if they have it ticked even with the default memory allocator in the text box. Just UNTICK it. To quickly DETAIL THE FIXES: For anyone who didn't see this post - It has worked for a lot of people so I will repost in threads where it may be of some use. Dwarden, feel free to remove this if this is not what you want. REMOVE ANY custom memory allocator (Untick the box in the launcher, or remove the '-malloc=' entry from your startup exe/shortcut/etc.) REMOVE ANY custom memory allocator from 'STEAM LAUNCH PARAMETERS'. (Right click ArmA 3 in Steam Library > Properties > Set Launch Parameters) REMOVE ANY custom memory allocator from 'CUSTOM ARMA LAUNCHERS'. (Arma3Sync, etc) CONFIRM THERE ARE NO CUSTOM MEMORY ALLOCATORS (Open ArmA 3 Launcher, click 'Parameters' > Basic 'Tab' > If there is entry 'Command Line Parameters', check it doesn't have -malloc=etc). If it DOES have that entry, that means you have a memory allocator launch parameter being forced via some other method, such as a shortcut to the arma3.exe. Download the 1.58.135689 v1 'arma3client_performance_158_135689.7z' file from the link. (OPTIONAL STEP, MAY NOT ACTUALLY CONTRIBUTE TO THE FIX.) Backup your arma3.exe from your arma 3 installation directory Delete the arma3.exe and then put the arma3client_performance executable in your arma 3 installation folder. Rename the arma3client_performance executable you just placed in the directory to arma3.exe Play the game! Be sure to THANK DWARDEN AND DEV TEAM FOR THE QUICK FIX/RESPONSE AND POST YOUR FEEDBACK HERE IN THE CORRECT THREAD IF THIS WORKED FOR YOU

I will edit my post to account for the fact that people can have custom memory allocators forced via Steam launch parameters, shortcuts to the arma3.exe and also via custom arma launchers. The issue truly is the fact that people were using non-default memory allocators, so if you can remove the custom memory allocator for the time being, this will eventually be hotfixed and you may be able to use your custom memory allocator once again. While I see your point that it shouldn't be up to the user to fix a game that costs money, it is however the users responsibility to maintain WORKING launch parameters as BIS cannot do that for you. If you have set custom parameters and they no longer work, then you remove those custom parameters and it DOES work, then I would call that a fix. As I say above, they will eventually fix the custom memory allocator bug, they are currently collecting any LOGS (.bidmp, .minidump and .rpt) in order to work out an actual hotfix to push to all users so they might be able to re-enable custom memory allocators in the near future. If you have some logs (LOCATION of logs can be found in the above hyperlink) then SUBMIT THEM via PM to Razazel or Dwarden (Or both) so they can begin working on this! HOLD TIGHT. They are working on it.

Oh I see it now, I thought he was talking about the tearing of the texture, but the model actually looks like he has a broken hand (I loaded it up in-game, as the images didn't really show much of the 3d aspect)

Great new performance results (Fixes the 1fps LOD degradation bug) from this new v1 binary. I have the details of how to install the new client performance binary in this thead.

It worked. I have given the fix to the members of my community, and have a lot of perfect results. It seems to resolve the issue for 3 hours of gameplay (So far) I will edit the post above to reflect these new findings!

Replace the arma3.exe (rename the file you download) in your arma directory. NOTE: Recommend backing up the normal arma3.exe - If you do not rename the file properly then you will have issues, and if you screw it up its good to have a backup.

The texture is slightly warped but there's no way to fix that short of changing the entire model of the hand. I suppose they could change the texture so that it is able to withstand being stretched more.

This comes from the MAIN THREAD ABOUT THE SAME ISSUE, with BI Developer replies - Look through the threads before making new ones! Has been fixed. Check the following excerpt from my post on the MAIN THREAD.

Hello guys! EDIT: THE FOLLOWING FIX WORKS. PLEASE READ CAREFULLY. I contacted dwarden/razazel directly via PM about this issue, providing crash logs, they have recommended that I try the following - note: these are direct copy pastes from two of dwarden's replies (first one is the PM he sent me, second one is from the STABLE CLIENT FEEDBACK THREAD.) To quickly DETAIL THE FIXES: REMOVE ANY custom memory allocator (Untick the box in the launcher, or remove the '-malloc=' entry from your startup exe/shortcut/etc.) REMOVE ANY custom memory allocator from 'STEAM LAUNCH PARAMETERS'. (Right click ArmA 3 in Steam Library > Properties > Set Launch Parameters) REMOVE ANY custom memory allocator from 'CUSTOM ARMA LAUNCHERS'. (Arma3Sync, etc) CONFIRM THERE ARE NO CUSTOM MEMORY ALLOCATORS (Open ArmA 3 Launcher, click 'Parameters' > Basic 'Tab' > If there is entry 'Command Line Parameters', check it doesn't have -malloc=etc). If it DOES have that entry, that means you have a memory allocator launch parameter being forced via some other method, such as a shortcut to the arma3.exe. Download the 1.58.135689 v1 'arma3client_performance_158_135689.7z' file from the link. (OPTIONAL STEP, MAY NOT ACTUALLY CONTRIBUTE TO THE FIX.) Backup your arma3.exe from your arma 3 installation directory Delete the arma3.exe and then put the arma3client_performance executable in your arma 3 installation folder. Rename the arma3client_performance executable you just placed in the directory to arma3.exe Play the game! Be sure to THANK DWARDEN AND DEV TEAM FOR THE QUICK FIX/RESPONSE AND POST YOUR FEEDBACK HERE IN THE CORRECT THREAD IF THIS WORKED FOR YOU