SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002149SphereServerexecutable - genericpublic20-03-13 02:2624-03-13 18:07
ReporterErebusDragon 
Assigned ToBen 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformPC (Desktop)OSWindowsOS VersionSeven
Product Version20-09-2009, 0.56b Prerelease 
Target VersionFixed in Version 
Nightly VersionAutomated (specify build number)
Experimental FlagsNone
Option FlagsNone
Internal Build Number
Summary0002149: Saving Stactics with SaveBackground option on (set to 1) makes statics save loop indefinetly
DescriptionI've started my server and made some changes that I wished to save.
I've executed ".save" from in-game as owner and the statics save started to loop!
So I've tryed to execute from the console, just to try it out, and the result was the same (It seemed obvious, but it's always nice to try xD)
Even restarting the server, to make sure it wasn't a resync issue, the problem continues!

Can't tell for sure the version I'm using, cause I've just installed the vSphereLauncher. Checking in the application info I found:
Version = 0.56.2.0
Last Update = 02/19/2013 00:07
Steps To Reproduce1 - Set "SaveBackground=0"
2 - Save (in-game command or console command "save")
3 - Check that it saves normally

4 - Set "SaveBackground=1"
5 - Save (as in step 2)
6 - Check the indefinetly loop
Additional InformationI select "None" for flags, since I just runned vSphereLauncher and it has some flags set as default! But I think it won't make any diference!

One last thing, I've oppened "sphere_serv_trigger" to check for the cause, and it seems to be the following lines:

/////////////////////////////////////////////////////////////////

// This function is called before server is going to save.
// ARGN1 --> save is forced (writable)
// ARGN2 --> save stage (for backgroud save goes 1 to 6146 [sector count + 2])
// RETURN
// 0 --> normal action (save)
// 1 --> denyes save
[FUNCTION f_onserver_save]
serv.savestatics

/////////////////////////////////////////////////////////////////

It seems to be the ARGN2 that will be saving an huge amount of static sectors or something :/
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
20-03-13 02:26ErebusDragonNew Issue
20-03-13 10:21ShaklabanNote Added: 0001500
20-03-13 10:22ShaklabanNote Edited: 0001500bug_revision_view_page.php?bugnote_id=0001500#r482
20-03-13 12:38ErebusDragonNote Added: 0001501
24-03-13 18:07BenNote Added: 0001520
24-03-13 18:07BenStatusnew => closed
24-03-13 18:07BenAssigned To => Ben
24-03-13 18:07BenResolutionopen => no change required

Notes
(0001500)
Shaklaban   
20-03-13 10:21   
(edited on: 20-03-13 10:22)
background save saving sectors one by by. so this is a intended behaviour. you need to check argn2, example:

[FUNCTION f_onserver_save]
if (<argn2> = 1)
    serv.savestatics
endif

or save statics under save finished trigger:

[FUNCTION f_onserver_save_finished]
serv.savestatics
(0001501)
ErebusDragon   
20-03-13 12:38   
Shaklaban, I got that from:

// ARGN2 --> save stage (for backgroud save goes 1 to 6146 [sector count + 2])


but it should come as you told me to do without the need to change by hand.

I imagine someone trying to run his new saves in background and get that 6146 saving messagem in all clients! What a major lag that would cause!
Just fixing it in the Nightly Releases would enough ;)
(0001520)
Ben   
24-03-13 18:07   
Having serv.savestatics in this trigger is not part of the default script pack, so there is nothing to fix here for sphere.

Your problem is with the SCP. Report your problem on the forum in the SCP section.