[vSRO] sro_client start up issue

[blapanda]

Hey there, since no one replied to my issues at epvp ... no one will help there actually, so requesting help on this forum here, since the most helping response comes from this forum here.


No matter which database I am using, it is always showing up correctly, that the boot process of the server succeed. However, somehow is sro_client bitching around with this issue at the dump files:
prim\mesh\nature\north africa\alexandria\alex_tilegrass02.bms


Well, I tried my own data.pk2, kSRO's data.pk2 and iSRO's data.pk2.


It is always showing the same annoying issue. My client won't pass the 238MB RAM usage and will stay there quite for an hour, if I won't take it down, no one will.


Google won't help on this one, seems that this doesn't happened to anyone.
Btw. the tilegrass02 files are there where they should be. So, nothing is wrong on the data files, nor at the servers data files (same as the iSRO's kSRO's and my own ones).




As well, does anyone know about the D15 cap130 files? I cannot get used to it, since a lot of errors will appear and the server won't start properly (WorldID 1 is even failing right at the beginning).


My usage of the server files were based on v1.188 vSRO. Client has been modified simultaneously to the gameserver. I raised my server from a cap 110+skills110 to a cap 120+skills120. Added new uniques, new features, added avatars, etc. everything works fine.


Just custom teleports and amalrun spirits aren't working somehow.



Could anyone be so kindly and hand me over a clean working d15 cap130 database?

[MentaL]

[magicsux]

Maybe additional settings for this BMS are not done correctly (in particles or map) try to replace these ones

Gesendet von meinem Nexus 4 mit Tapatalk

[blapanda]

Could be possible. Didn't thought about replacing the map.pk2, since I thought, it should be fine like using particle and data at its high end state (kSRO standard).
I will test it sometimes.

Edit:
Well, I tried it, and seems to fail again. I will recover my DB and client step by step and figure out what the fuck causes this error.