| 12 Oct 2020 |
 RedNovember | Am I able to extract pbo files now? | 15:07:27 |
 muttley | Somewhere there isarmake2 binary, you can add it to your PATH or copy it to /usr/bin | 15:40:06 |
| RedNovember | I found the armake2 file in my home folder, so how exactly does this work? | 15:41:59 |
| RedNovember | Looking at the Readme Usage content, its not showing any obvious instructions on how to extract .pbo mission files | 15:44:03 |
 The Great Australian Baguette | Probably the unpack command? idk | 15:45:50 |
| The Great Australian Baguette | armake2 --help might give more info | 15:46:15 |
| RedNovember | when I do that in console it gives me an error that the command is not found. Probably means installation went wrong? | 15:47:21 |
| The Great Australian Baguette | Suppose you're new to terminals | 15:47:38 |
| The Great Australian Baguette | If you're executing something in the current directory, you have to specify it explicitly otherwise it assumes you're trying to execute something in your path
So if armake2 is in the current directory, you'd do ./armake2 --help | 15:48:25 |
| RedNovember | yeah, I'm not fluent in terminals. | 15:48:36 |
| RedNovember | when I open the console and do cd armake2 and do armake2 --help it shows that the command is not found. What am I doing wrong here? | 15:50:33 |
| The Great Australian Baguette | the ./ is important | 15:50:43 |
| RedNovember | hm, I'll try that | 15:50:51 |
| RedNovember | so my file is stored in /home/my_username_here/armake2/ so I guess its not cd ./armake2 as I tried doing that lol. | 15:52:24 |
| The Great Australian Baguette | hang on I'll build it | 15:52:56 |
| The Great Australian Baguette | So it put the executable in the target/release directory
So from where you are you'd cd into target/release
Your full path would probably look like home/my_username_here/armake2/target/release | 15:54:48 |
| The Great Australian Baguette | From there, ./armake2 --help should work | 15:55:05 |
| The Great Australian Baguette | edit: So it put the executable in the target/release directory
So from where you are you'd cd into target/release
Your full path would probably look like home/my_username_here/armake2/target/release
So it put the executable in the target/release directory
So from where you are you'd cd into target/release
Your full path would probably look like /home/my_username_here/armake2/target/release | 15:56:26 |
| RedNovember | 
Download 978.png | 16:04:58 |
| RedNovember | uhhh chief its not working when I do cd /home/gp/armake2/target/release. | 16:04:58 |
| The Great Australian Baguette | Times like this I open a normal file manager and look around | 16:09:35 |
| RedNovember | yeah even if I'm in the release directory I still can't do armake2 --help | 16:15:31 |
| The Great Australian Baguette | Screenshot? | 16:15:58 |
| RedNovember | 
Download Screenshot_20201012_121613.png | 16:17:43 |
| RedNovember | This might look a bit funny to you so bear with me | 16:17:44 |
| The Great Australian Baguette | No need to run it as sudo
And once again, the ./ is important when trying to run a file in that directory
./armake2 --help | 16:18:27 |
| RedNovember | oh yeah that totally worked. | 16:18:47 |
| RedNovember | now that that was figured out, I have a sample mission file I need to convert from pbo so I can make it useable for 3den. How does this process work?
I guess armake2 unpack? | 16:20:18 |
| The Great Australian Baguette | I think so | 16:20:48 |
| The Great Australian Baguette | ./armake2 unpack /path/to/file.pbo /path/to/folder/you/want/to/unpack/it/to/ | 16:21:38 |
