Author Topic: Singleplayer mode problem  (Read 2969 times)

Singleplayer mode problem
« on: August 14, 2016, 03:42:36 pm »
Why is possible to run in singleplayer mode Fonline SDK rev. 412 without any problems, even with working (!) load/save feature, but same thing is impossible with 2238/Reloaded SDK? After soem tests I can say that Fonline SDK running ok in every part of process, 2238 just stuck on login/registration screen with big bunch of errors everywhere. Of course in both cases I used similiar config and running procedure.
Question is where is the difference and why on 412 SDK problem not occured? I read that these errors can be caused by cache, bad config or other things, but well, probably it is not the answer in this case.
I attach here some logs, maybe it will help if someone want try to dig in this thing

2238 client log http://pastebin.com/ZKg02H3h
2238 server log http://pastebin.com/FQ5fajR2
2238 main.fos http://pastebin.com/CwDy2zsm

fonline v.412 client log http://pastebin.com/QtacuLvn
fonline v.412 server log http://pastebin.com/JywW6iME
fonline v412 main.fos http://pastebin.com/kRRNJ9Sq

JovankaB

  • Guest
Re: Singleplayer mode problem
« Reply #1 on: August 15, 2016, 08:31:42 pm »
The difference is 2238 wasn't made with single player mode in mind, so this feature never worked.
And Reloaded is based on 2238.

It's certainly possible to "fix", but requires more than a few small changes in the code.
I tried to do it in the past, but didn't go far: http://fodev.net/forum/index.php/topic,29612.msg259774.html

Wow, it was over 2 years ago. Time flies quickly.
« Last Edit: August 16, 2016, 01:54:01 pm by JovankaB »

Re: Singleplayer mode problem
« Reply #2 on: August 19, 2016, 08:13:04 pm »
I think changing some things in main.fos would make some interesting effect, but it is not solution for mentioned problem. When you compare main.fos of tla sdk and 2238 you will see that they are similiar and tla working in singleplayer mode without any special settings there. I tried to dig it in this case and I think that problem can be in cache. For singleplayer mode you need different cache file that for regular and there is no problem with TLA becasue you download this file with sdk. 2238 don't have this file so can't initialise proper menu to start game and connect to server. Of course due to lack of conncetion is not able to download fresh cache. Closed circle. Of course renaming default cache file to singleplayer not work. I maked test and I deleted singleplayer cache from TLA cache folder and I got same errors and problem with connection like when I tried run 2238. Well, dead point.
« Last Edit: August 19, 2016, 08:17:37 pm by loord »

Offline Wipe

  • Rotator
  • Random is god
Re: Singleplayer mode problem
« Reply #3 on: August 21, 2016, 07:02:04 am »
Cache have nothing to do with screwed up initialization order [from singleplayer perspective]
Games are meant to be created, not played...