John2222

Members
  • Posts

    38
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

John2222's Achievements

Rookie

Rookie (2/14)

2

Reputation

  1. Surprisingly a new arma 3 profiling branch executable was released today. First users reported that it worked.
  2. Good news. The devs have found the issue. It was (as i understand) a using of RUNPATH instead of RPATH. They posted a hotfix but there will be next week shipped a fixed version anyhow. So It would say let's wait till next week.
  3. On the discord there are some one that can reproduce this problem. This seems not an issue from your docker. We will see.
  4. Another way of testing: Can you create a "non-container" arma server for testing? Only delete that the container (and its components) are the problem?
  5. Maybe some 32bit libraries are missing? Yeah it is interresting. But if we can fix it in advance, then maybe on the next normal update it would be running out of the box.
  6. Hi, some suggestions from the discord: * Use the steamclient.so that is shipped with the arma directory (no copying over from the steamcmd folder). Someone use this (version from 2020) and said it work with 32bit version. * rights problem or steamclient.so is not flagged as executable In general he said, that the steamclient.so has to be right next to be the arma executable. no special folder is needed. Greetings
  7. Yeah i understand. No worries. RL is most important.
  8. I've read something in the discord about a problem with the manifest. Maybe this would help to update this manifest-thing?!?
  9. Nichts anderes hätte ich angenommen. One idea do i have: Can you start the profiling container and look into the logs? Because there were update in the last days. Maybe it is fixed. The hope dies at last.
  10. I wrote the problem to the devs. There are newer versions of the profiling build but i cannot test this before weekend. So let's see what happen.
  11. I tried x64. It doesn't run on my CPU. I don't think it is 64bit only because there other 32bit users who runs without problems. I search in the dev discord for "steamclient". There wasn't matches in the near time that sounds related. It is not a problem with the game/engine itself. It seems (as you say), that the steamclient.so cannot be found. That was already my guess. So i searched in the web and found a similiar problem with an other game. The solution was to set a symlink. Maybe this is here also the solution. I saw that in the general "steamcmd" folder (not that one in the "gamefiles" folder) there is a 32bit folder with a steamclient.so. Maybe it is needed to set in 32bit mode a symlink to this file? Or maybe steamclient.so has to "force" to 32bit also in some kind? Can you give this a try? If this wouldn't work i will ask the devs (but i have not much hope because it sounds more like a problem of the container than the game itself). Maybe there is a 32bit user with container in dev build around there.
  12. I've done some search for the problem in the 32bit log: "steamclient.so: cannot open shared object file: No such file or directory": It seems there is some symlink missing or the rights are not set correctly. https://community.7daystodie.com/topic/19590-dlopen-failed-trying-to-load-steamclientso-fixed/
  13. Server runs locally, but: I am kicked because of steam ticket. But reload of steam doesn't help. Maybe this is the Propblem (see last lines of your x86 log): 13:42:09 BattlEye Server: Initialized (v1.217) dlopen failed trying to load: steamclient.so with error: steamclient.so: cannot open shared object file: No such file or directory [S_API FAIL] SteamAPI_Init(): Sys_LoadModule failed to load: steamclient.so [S_API FAIL] SteamAPI_Init() failed The steamclient.so is updated in the gamefile folder. I've started one of the old docker and there is no such errors in the log.
  14. This happens in the beta branch, not the stable. I posted the start line in my first post for this issue: " If you want to try it by yourself, here is the starting line for the GAME_ID parameter: 233780 -beta profiling -betapassword CautionSpecialProfilingAndTestingBranchArma3 " And I start in 32bit "mode". This issue will be a problem for the stable, when the next update is delivered by BI. And this will be happen soon(couple of weeks) as i know. I load the beta testing branch and also the profiling/performance branch to give feedback to the devs for the supported 32bit linux versions.