Fougerite Official 1.9.9.71

[DreTaX]

Threaded autosaving is not working properly. The server still lags during the autosave

It might be because I disabled It for some reason. <.<
Will put It back.

Edit https://github.com/Notulp/Fougerite/blob/master/Fougerite/Fougerite/Hooks.cs#L1406

Nah I put It back.

But holy shit 84k.

 

[tarynkelley]

The code is fine. I also don't get it why its not working. I haven't found any reliable decay tool yet.

Is the decay function of "Wiper" reliable?

 

[DreTaX]

The code is fine. I also don't get it why its not working. I haven't found any reliable decay tool yet.

Is the decay function of "Wiper" reliable?

Sorta, but just to think about It, even myself would put It under Loom just in-case.

https://github.com/dretax/Python-Plugins/blob/master/FougeritePlugins/Wiper/Wiper.py#L204

Loom:
http://fougerite.com/wiki/calling-methods-from-the-main-thread-using-loom/

Loom.ExecuteInBiggerStackThread(lambda:
self.ForceDecay()
)

^Maybe that can do It.

You can also try:
https://github.com/Notulp/Fougerite/blob/master/Fougerite/Fougerite/Hooks.cs#L1406

Putting the Thread object as a global variable in the Hooks class, and see if anything happens.
If the Saving is under thread, the Console shouldn't not even say that It's saving, you could only see It in the logs.

 

[salva]

DreTaX updated Fougerite Official with a new update entry:

1.5.2



Read the rest of this update entry...

From 1.51b to 1.52 .... Is it enough with Fougerite.dll update?

 

[DreTaX]

From 1.51b to 1.52 .... Is it enough with Fougerite.dll update?

yes

 

[gintaras]

I have suggestion to save data asinc way because now it saves 3,4k and it took 0.1sec so for this time no one gets fps better to save like every time is object placed destroyed or smth and save only this staff or something else but need to fix it if server gets bigger server will take longer to save

 

[DreTaX]

DreTaX updated Fougerite Official with a new update entry:

1.5.3

• Only a Fougerite.dll update, with minimal changes, i promise to check on mysql next round. For now i added a new tp method too, which could possibly solve the problems of far teleportation. It finds the closest spawnpoint near the given vector, teleports you on the ground, and you can teleport the player in his house next, since he will load the objects near him.
• https://github.com/Notulp/Fougerite/commit/6c4764197aa021371233bd7da906e80dc2980b57

Read the rest of this update entry...

 

[salva]

DreTaX updated Fougerite Official with a new update entry:

1.5.3



Read the rest of this update entry...

Hmm .. very interesting .. I will update now, thanks for this update. I imagine this also solves / tpto and / tphere? ,I'm going to check that

 

[DreTaX]

Hmm .. very interesting .. I will update now, thanks for this update. I imagine this also solves / tpto and / tphere? ,I'm going to check that

Nah, I didn't add It for Rust++ yet. But HomeSystem has it.

 

[salva]

Take your time and my apologies for posting without control xd ... my mind is on fire !!

 

[salva]

DreTaX updated Fougerite Official with a new update entry:

1.5.3



Read the rest of this update entry...

I've done a full update from 1.5.2 to 1.5.3 including pre-patched files.

I can not connect to my own local server, it gives me kick.

I again try to connect and kick me again (and so up to 5 attempts) .... the funny thing is that without anyone connected to the local server, 5 players are connected, 1 player for every time I tried to connect .. Really strange, maybe this broken version 1.5.3 ??

This is the error on the console on the client side

 

[DreTaX]

I've done a full update from 1.5.2 to 1.5.3 including pre-patched files.

I can not connect to my own local server, it gives me kick.

I again try to connect and kick me again (and so up to 5 attempts) .... the funny thing is that without anyone connected to the local server, 5 players are connected, 1 player for every time I tried to connect .. Really strange, maybe this broken version 1.5.3 ??

This is the error on the console on the client side
View attachment 1869

I didn't change anything on the fougerite module that could cause this. Did you try restarting?

 

[salva]

I didn't change anything on the fougerite module that could cause this. Did you try restarting?

I did many tests, closed and opened different servers in different versions ... even restart the pc ... maybe someone else can test if this happens to check this matter? @xandeturf @tarynkelley

 

[xandeturf]

Are not you getting errors on the server console? I have not updated my fougerite server yet, but I will be testing

 

[DreTaX]

Dunno, got 17 players on 1.4.7 now.

 

[DreTaX]

Wait, no, wtf?

 

[DreTaX]

DreTaX updated Fougerite Official with a new update entry:

1.5.3B

• Quick fix.

Read the rest of this update entry...

 

[salva]

Apparently after doing several tests, it seems that with version 1.5.3B has been solved, thank you very much

 

[Brālis Tezenis]

DreTaX updated Fougerite Official with a new update entry:

1.5.3B



Read the rest of this update entry...

1 - with the explosion of the walls get the error in the chat RPC
2 - make the hook and remove the add item in a separate then - and then dupaty things can be - moved from the chest to his and threw - and it is again in the chest appears

 

[salva]

1 - with the explosion of the walls get the error in the chat RPC
2 - make the hook and remove the add item in a separate then - and then dupaty things can be - moved from the chest to his and threw - and it is again in the chest appears

I confirm the error in console when using c4 in a wall - No Network View with id ViewID Unassigned to send RPC "Client_OnKilled"