Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to start cTab on Linux Server #160

Open
danielklessa opened this issue Dec 17, 2015 · 15 comments
Open

Not able to start cTab on Linux Server #160

danielklessa opened this issue Dec 17, 2015 · 15 comments

Comments

@danielklessa
Copy link

There is an issue starting cTab on Linux Servers, this is the line I get:

Cannot open file 'arma3/@ctab\addons\ctab'

The probem seems to be the call to ctab without .pbo extension. If I delete the .pbo extension at the file the mod seems to start, but without a hash:

** 9:18:44 cTab - Blue Force Tracking | @ctab | false | GAME DIR | | | **

Please have a look at this.

@nsgundy
Copy link
Collaborator

nsgundy commented Dec 17, 2015

Have you tried replacing all the backslashes in the path with forwardslashes? Never tried myself on Linux and the instructions have not been written with it in mind, apologies.

@danielklessa
Copy link
Author

Hi Gundy,
the problem isn't the start params, they are fine. The problem is somewhere in the plugin code of ctab, when it starts it calls the pbo file without the .pbo extension. this is a problem because ctab != ctab.pbo, that may work with windows, but not with linux.

I don't know anything about mod development for ArmA, so I don't know if i can figure out the Problem in your sources, Can you tell me where to find the startup processs, maybe i'll find something.

@nsgundy
Copy link
Collaborator

nsgundy commented Dec 17, 2015

Thanks for pointing that out. Let me look at the sources and get back to you. I am a bit rusty.

@danielklessa
Copy link
Author

I think I found it, the problem is not the pbo thing, its just a typo. It tries to call ctab but the pbo file is called cTab. Thats the whole problem and thats why it works with windows.

@danielklessa
Copy link
Author

Ok, I tried to start the server with just renaming the .pbo and bsign file to lowercase ctab and it solves the problem. The server is running and the hash is generated:

13:19:59 cTab - Blue Force Tracking | @ct ab | false | GAME DIR | c8ebd8832b1346905da18cc92b645ed0c64d94d 6 | 13ad2ca6 | arma3/@ctab

@nsgundy
Copy link
Collaborator

nsgundy commented Dec 17, 2015

Have gone through the sources and found the following path issues (i.e. ctab vs cTab):

  • all three model paths for the 3D models including
  • texture paths for 3D models inside .rvmat files
    I have also documented that people are to use userconfig\cTab\, but the code is looking for userconfig\ctab\. However the folder included with the distributed .zip file is all lowercase, matching the call.

I can make the changes and generate a new PBO, but to see if this gets rid of the issue, I'd need your help to verify this.

@danielklessa
Copy link
Author

In 30 Minutes I'll be available for testing.

@danielklessa
Copy link
Author

Ok, I'm back.

@nsgundy
Copy link
Collaborator

nsgundy commented Dec 17, 2015

Sorry, having to wait another 30 minutes for the A3 updates to finish.

@danielklessa
Copy link
Author

I checked my solution with just renaming the pbo file and it seems to work perfectly. Started server and logged in. everything is working fine.

@nsgundy
Copy link
Collaborator

nsgundy commented Dec 17, 2015

That's good to know. Would you mind checking if the following build here runs fine without renaming?
https://preview.cubbyusercontent.com/pli/%40cTab_2.2.2.5.zip/_701e017e29914844b268b96f07b11ee3

@danielklessa
Copy link
Author

Still the same problem Cannot open file 'arma3/@ctab\addons\ctab'

@danielklessa
Copy link
Author

I think it'll be enough to just name the files completely lowercase with your next release and you'll get a lot of linux servers. 👍

@danielklessa
Copy link
Author

I think ArmA itself is calling the files completely lowercase, so it is possible that you are not able to get it in your code.

@Jason-Terry
Copy link

So is this still an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants