Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Yes this was reported before a few times, but it should be fixed with the latest addon version by now. This was probably not caused by an conflict, but it could be. It all depends on the error messages.
- Please check the version of the server and the client to be the latest.
- Check the addon to be the latest version (rev. 365 or above). The version should be written on every error message you see got from this addon.
- Are there any more errors, a console dump would be nice.
Information about the big update:
https://steamhost.cn/steamcommunity_com/workshop/filedetails/discussion/246756300/1520386297700421028/
Trouble shooting and conflict resolving information you might need:
https://steamhost.cn/steamcommunity_com/groups/SligsAddonsGroup/discussions/0/358417008723619723/
It looks like that the file was not send to the client. That only happens when the addon is not run on the server. Are there any errors on the server. Can you give me a console dump from the server?
Edit:
I just did a test with my didcated server (fresh install (live branch, version 171212), with the addon collection from above). The radio addon just works fine. There are no conflicts with HG Sandbox Addons.
The log file will be saved at "garrysmod/console.log". If necessary you should remove private stuff. I need the log from server launch to server idle.
BTW, there is no way a around gameserver restart for addon updates or for getting a console dump.
Im telling you this, because in the past I had cases of server adminstrators refusing to do gameserver restarts (server restarts + adminstrators = not best friends :P) but also still annoying me about errors that would be fixed by just restarting. :)
In the mean time you could test the radio in single player, just to exclude any problems that could be connected by your game client.
Can you tell if your and Grim's problem are some how related beside the error message?
At the moment there are four cases of this problem known, while one is confirmed to be fixed after update rev. 365. That was caused by a bad version check on the server side.
The addon was changed to refuse to load if any addon related lua errors happen during startup to avoid bad or undefined states that would result in error spam or unexpected behavior later ingame. All these errors are shown in the console after the addon files were executed in the realm (Server/Client).
These ingame errors wouldn't be very helpful for anyone and would make trobble shooting more difficult, because the wrong errors messages (from subsequent errors) would be rightfully reported.
This is a good example for that.
A condump was send to me and I saw the problem immediately:
Supposedly the server was outdated for like 8+ months. But that would be impossible as you would not be able to connect to the server with the current client.
This was the error:
3D Stream Radio (rev. 365):
Your GMod-Server (Version: 170422) is too old! Update your GMod-Server! Load aborted!
So I told that you would have to do this:
1.) Delete <server>/garrysmod/garrysmod.ver (this file seems to have the version number in it)
2.) Start steamcmd and login as anonymous
3.) Run this: app_update 4020 -beta NONE validate
4.) Check <server>/garrysmod/garrysmod.ver to be at least version 171212
5.) Restart the server, everything should be fine.
I just made an update to this addon, so it tells the client about it's server errors now. You would no longer need to get a condump for trouble shooting for this addon at least. :)