As you can see the attached file, saving duration is too long(about 2.5min).

Is it normal?

It seems reasonable time consuming to play with 70MB xml file, but it makes the autosave feature obscure

Using Intel 2160 CPU(duel core, overclocked to 2.8Ghz), 2gb ram, x86 OS(XP sp3). Not a fancy system, but I think it's not too slow computer...

During saving the game, onlink uses very big part of CPU and memory(about 1.5 gig!).

Even more, the game crashed BEFORE saving procedure terminated, for now.
("Staging world state into XML structures", "Writing to ~~~.xml.gz" are done, but no "write to disk" message appeared.)

Any troubleshooting guide?

I'm using the most recent Onlink version(0.2.0 a8 r23).

It's a known issue specifically with XP, and we're looking into it. Hang tight.

Miah, before I hunt this problem down, can you think of anything that would cause this?

Maybe my savefile would be helping(or not. Who knows?).

I played about 3 game-days, and I did no quest-line or "special" missions. I made 27 denial clients, but it will hardly matters for this problem, I think. However, the uncompressed savefile has 75mb, which I think pretty big size for little progress.


I forced to re-compress the XML file because gz-compressed savefile exceeded 5mb.

i cant quote it but took about 550 second last time i tried to go out of onlink
i think the "save as XML" idea didn't work out 2 good - its simply 2 slow >.<, should make some sort of binary-format instead, also if removing the compression would make "noticeably faster", i wouldn't care if it so used 10x the size
ps:using v 0.2.0-a8-23-g0c617cf

and i haven't even came so very far yet, only got log deleter/proxy disabler v5/ start stuff

Don't now about that, it works fine for me. Try running it as admin, it does need privliges for app data.

how long have you came? was no problem for me either untill i played few hours yesterday

could som1 check how long they use to save this? http://www.speedyshare.com/265431882.html
(sorry for double-posting, tho was intensional)

oh.. i got same problem

Are you on XP? If you're on XP, this is a known problem and a fix is being worked on.

-- Griffinhart

EDIT: I'm merging this thread with the other thread re: saving/loading times.

i cant play onlink untill this is resolved )-:

btw what i can tell on my pc at least, an excessive amount of memory is being used, and its constantly "using the pagefile" while saves... >.< (even if its more ram available)

Note that the problem is XP-specific. If you use any other OS, things seem fine. We're working on resolving this, but we need to identify what DLLs Onlink is using on Windows XP, so we can bundle the correct ones with it. Theoretically, once the correct DLLs are discovered, we can just push out an update and everyone with XP will start having decent save times.

dependency walker ftw?

Basically.

I think i have the same problem with XP, took off autosaving and the game quits/crashes when trying to logout from the Onlink user, therefore not saving my progress. Upgraded to Windows 7 and still have the same problem

Worth noting that im not that far into the game, same as Hans, Proxy disabler v.5, 1st Gateway etc.

You "upgraded" to Windows 7. As in, via the installer 'Upgrade' option, or reformatted and installed Windows 7? If the former, that's interesting news, because that means that Windows 7 isn't distributed with whatever is causing the problem, but it doesn't eliminate it on an upgrade, either.

Sorry yeah bad phrasing, i installed Windows 7 from scratch. Just spent an hour on Onlink, and has happened again ....seems like it hangs for a few minutes then it states Run Time error before telling me Onlink will now close.

Not sure if the following may be partly correlated in any way:

-'Connecting to the gateway' at the beginning can take a few minutes.
-Fast forwarding the game sometimes brings this message (also happened in XP):

'Onlink has recovered from a serious error. Please zip and send your player profile to forensics@onlink-mod.net. Your player profile is still stable and you may resume play.'

It'd also be helpful to see the specs of the machines encountering the issue (especially pertaining to the processor). I suspect it could be a scheduling issue, which would actually be pretty easy to fix.

short,
Intel Core Duo, 1,66 GHz, SSE3
1 GB physical memory (interesting enough, onlink uses over 500 MB ram while loading, using the pagefile allot even when more physical memory available, and disabling the pagefile=onlink crash on load..)

Dual core 2500 running windows 7, and i have no problems

I really need a multi-factored poll for this. I need a poll that covers this:

1. Are you experiencing the load/save duration issue?
2. What operating system are you currently running? Did you use the "upgrade" install option to upgrade from a previous version? If yes, what OS did you run previously?
3. What processor do you have? Single core? Dual core? Hyperthreaded?

It'd be great to get a graphical representation of this. Anyone want to set up a poll for this, somehow, somewhere?

I'd really like to get this load/save issue resolved before we really get Cerberus going.

http://www.polldaddy.com/ ?

I believe XP doesn't maintain any kind of buffer for file writing operations, which means that each fwrite() will be a system call, so I would advise keeping a buffer in memory and then writing save files in one shot.

1) Yes. But only save seems to take quite a long time
2) XP home. "Upgraded" from 98 SE.
3) Core 2 DUO E8400 (3GHZ)

Hope it helps.