Steam-fællesskab :: 3D2D Textscreens

Butiksside

Garry's Mod

Alt Diskussioner Skærmbilleder Illustrationer Broadcasts Videoer Værksted Nyheder Guider Anmeldelser

Garry's Mod > Værksted > Jamess værksted > 3D2D Textscreens > Diskussioner

3D2D Textscreens

Beskrivelse Diskussioner75 Kommentarer1435 Ændringsbemærkninger

Vil du gerne deltage i diskussionen? Du skal logge ind eller oprette en konto.

Dato opslået: 30. juni 2016 kl. 11:34

Indlæg: 6

Start en ny diskussion

Diskussionsregler og retningslinjer

Flere diskussioner

Textscreens going invisible at certain angles

Perma Text Screen Bug

Textscreen spawn position

d_k13

30. juni 2016 kl. 11:34

All textscreens disappeared and permament system is dead

Hello, I am the owner of the server which uses your addon. Firstly, great thanks for making this addon. It's much better that the wiremod texscreens I used to use.

But your addon doesn't seem perfect, as 1 day all the texscreeens were gone. There were about 160. I have to admit, that I own a russian server and of cource we use cyrillic symbols. But still everything was fine.

Also, when I boot the server it says something like "Spawning ### textscreens...".

< >

Viser 1-6 af 6 kommentarer

James [udvikler] 1. juli 2016 kl. 11:03

Thanks for the report! It sounds like your textscreens data file may have been corrupted. Have you tried removing it (/data/sammyservers_textscreens.txt) and recreating the textscreens? You could also have a conflicting addon - what happens if you disable those?

d_k13

1. juli 2016 kl. 16:27

Well, I have pretty much addons in the collection and quite a lot in addons folder. And yes, I deleted .txt file in data folder, and textscreens keep dissapearing.

And I have a little suggestion. Maybe you should try to make textscreens info saved into local data base sv.db? I think that would fix many issues with permament system.

I think that's of course problem of my server, not in your addon. Thank you for the answer!

James [udvikler] 5. juli 2016 kl. 18:49

Using the SQLite sv.db is actually a great idea. It'd actually likely yield a lot more performance on very large data-sets too, as I wouldn't need to unnecessarily load the entire json file, and could simply query for a sub-set of data. I'll definitely consider this in the future.