Skip to content

Commit 9a6c023

Browse files
authored
Remove outdated troubleshooting infos (#16)
* Next version of NTRE will use gameinfo.txt to handle mounting OG:NT assets mounting instead, the "neopath" mounting is removed * Linux glic issue no longer applies since the TF2 64-bit SDK update
1 parent 1324c27 commit 9a6c023

File tree

1 file changed

+0
-37
lines changed

1 file changed

+0
-37
lines changed

src/guide/install/index.md

Lines changed: 0 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -66,16 +66,6 @@ standard setups. However if you have issues...
6666

6767
## Troubleshooting
6868

69-
### Cannot mount original NEOTOKYO assets
70-
71-
This could happen if you have NEOTOKYO/Steam installed at a non-default
72-
location. Open up "Properties..." then launch options and set to your
73-
custom install path:
74-
75-
```
76-
-neopath "C:\PATH\TO\YOUR\NEOTOKYO\NeotokyoSource\"
77-
```
78-
7969
### Cannot join VAC servers
8070

8171
The client loads up in insecure mode by default, which will get blocked by
@@ -110,30 +100,3 @@ then click "Run". This will popup everytime NT;RE is started through Steam.
110100

111101
![Picture of the installation folder](folderstructure.png)
112102

113-
### Linux - engine.so: cannot enable executable stack as shared object requires: Invalid argument
114-
115-
Since [glibc 2.41, Source SDK 2013's `engine.so` will fail to load](https://github.com/ValveSoftware/portal2/issues/451)
116-
causing the game to not start. To workaround this, go to the Source SDK 2013 Multiplayer's bin directory:
117-
118-
```
119-
~/.steam/steam/steamapps/common/Source SDK Base 2013 Multiplayer/bin
120-
```
121-
122-
Then make a backup of `engine.so` and use either:
123-
124-
[patchelf](https://github.com/NixOS/patchelf):
125-
126-
```
127-
$ cp engine.so engine.so.bak
128-
$ patchelf --clear-execstack engine.so
129-
```
130-
131-
Or [execstack](https://linux.die.net/man/8/execstack):
132-
133-
```
134-
$ cp engine.so engine.so.bak
135-
$ execstack -c engine.so
136-
```
137-
138-
NT;RE should be able to load up normally afterward.
139-

0 commit comments

Comments
 (0)