The Forum

[quote="ROMELIS"]hey everyone. encountered first major problem in game. i have started healing to increase my int. in TYT people hitting bugs or just random guys hitting other random guys. at first it went fine, but then ii noticed, game freezes after 2-3 heal atempts and then d/ happens with "client had to time out". it loos like a lagg spike and hen a d/c. have tried multiple windows, healing my other char, healing others, result is the same. any ideas what is wrong ? ps i play on a windowed client[/quote]

[quote="KAZOKU"]probly due to running 2 chars or a resolution issue[/quote]

[quote="ROMELIS"]what do you mean resolution issue ? the same happens running on one screen[/quote]

[quote="KAZOKU"]Soma was made to play on 800x600, so anything outside of that has potential to be buggy Dont get me wrong some work fine, and then the same res on a different computer may crash Play about with different res to find one stable for yourself, I'd advise using the resolutions that you can set your monitor to As for using 2 chars to play, make sure there running on there own copys of soma, as 2 running instances dont like to shair the graphic files, so becomes buggy If you haven't changed soma resolution and have 2 installs of soma then my next suggestion would be to upgrade your graphics driver, it does sound like some graphics issue somewhere, other than that I duno [/quote]

[quote="DEAMOND"]Client time out messages aka the connection to the server has been terminated is a network issue. If this is the error you are receiving i would suggest having a look at your internet connection bud, if you are using wireless try an ethernet cable. [/quote]

[quote="ROMELIS"]Deamond, but it crashes only if i heal. else game runs perfectly. wouldnt it be that if network has problems it would crash constantly ? guys i wan tot stress, i am playing in window mode and it still crashes without another account running. i will try installing second client and dragging a cable i hope it works [/quote]

[quote="DEAMOND"]Yes that is true Romelis, However ideally we need a screenshot of what happens if the client crashes then yes that is something on your end, if you get terminated error from server that would be more network side. We need more information, What OS are you running and what resolution are you running [/quote]

[quote="ROMELIS"]ok, i have tried this on full screen. and it works well. no crashes. tested on few different computers. EDIT: ok so i was wrong. it doesnt work on full screen, it still crashes. this is unbelievable EDIT: and i dont know how to upload printscreens in this forum format :) lol EDIT2: either way, the table that pops up is named " soma mythological bybliography" and it says "the connection to the server has been terminated" EDIT3: crashes with 800:600 res. i cant believe noone else suffers this shit. there must be other guys installing soma on windoes 10 and recieving this.[/quote]

[quote="TIEFER"]Are you playing on a laptop?[/quote]

[quote="DEAMOND"]Finito could correct me if i'm wrong but i'm pretty sure when you get the message "the connection to the server has been terminated" it means; A) Someone else logging into that account B) You Lost network connection to the server. It could be that for some reason your connection can't handle the amount of packets required to send to the server whilst using spells and receive a timely response therefore terminating the session. Do you have another laptop or computer you could test? If it is an issue on another device then we know i'ts not going to be a device problem and more like a network related issue. [/quote]

[quote="DEVITA"]perhaps go heal someone who wants to be healed that's prob best idea[/quote]

[quote="ROMELIS"]i will try connecting my laptop with modem via cable next week while at work to see how it goes. else, i dont know what to do. it is impossible, that noen else in the realm has similar problems. deamond might be right about packets, becaue i sometimes recieve same d/c msg while playing soma (not healing, hitting mobs) so it might be that i loose conection. i will try this on othe cpu to see how it works[/quote]

[quote="FOXTRCK"]So one of the problems with a client built on code as old as this is, a problem with a sound or graphics driver can cause a untolerated timeout resulting in that kind of disconnection. You may be better off reviewing Event viewer in Windows ( https://www.digitalcitizen.life/how-start-event-viewer-windows-all-versions - For how to find it and open it). Then look in the Application (but also the System logs) and check for the time of the timeout and see if there are errors around the time this occurs. You may find Nvidia/ATI/Intel kind of errors. You may find that one of either drivers is crashing which case but even if not, I would recommend reinstalling your graphics driver to start with and your sound driver. I also notice you mention you are using a laptop. One of the main bugbears of a default setup of a laptop is that Sleep/Hibernation settings are generally set in such a way that they can in fact do harm on occasion. I would recommend running in command prompt the following command :- powercfg.exe /h off to turn off hibernation and to delete the temporary hibernation file. As a preference I turn off Sleep settings completely to further prevent potential problems but that choice has to be yours, would recommend turning away from Sleep every 5 minutes to maybe if Idle for an hour or so. Let me know if you want a remote session sometime on something like Teamviewer, I'll even use my own logon to see if its reproducable - If you don't fancy doing anything like that, a easy way to start to isolate the problem is the following 1) Create another Windows profile and login to Soma with it - does it still occur Yes / No (Windows profile problem if answer is No) 2) Logon another computer - does it still occur Yes / No (If no, than not a connection issue from your router to the Soma server but either connecitvity from the laptop to your router or an environmental problem on the laptop itself) 3) Logon to another account - does it still occur Yes / No (If No, ask a friend to logon to your account for you, on their machine and see if it occurs)[/quote]

[quote="ROMELIS"]foxtrck,, thanks for the log reply. ok so what i have managed to do on my on my own. i dont have close to none crash issues while healing when using my laptop from work internet. despite it being 80mbps and my home being 400mbps. i have tried connecting my laptop at work to the cabe and via wifi, results are very similar. none or close to none crash issues. laptop is lenovo thinkpad with graphic card "intel graphic card 620". it should be suficient. i have turned my firewall down. i have tried soma on other computers, crashing occured, but that place does not have good internet (not close to my work or home speds) i have logged on to other accounts and it still crasheswith that account as well. what have i missed ? [/quote]

[quote="SOMAWIZARD"]"The connection to the server has been terminated." Will most likely be a network issue if no one else is logging into your account. Speed is not important latency and packet loss will be in cases like this, Wi-Fi can have sporadic high latency influenced by factors outside of your control (i.e interference), a bad internet connection can also cause the same packet loss and latency issues. Soma is quite tolerant but when latency or packet loss is too high the server will be expecting a response from your client and if after a set period of time it doesn't respond to the server it may kick you off as it thinks your not connected anymore. A good test will be the following :- 1. Open command prompt. 2. Type in the following and press enter to begin the test [quote=] ping 51.79.98.95 -t [/quote] 3. Log into Soma and replicate the issue 4. Press control and C to stop the test and paste the results like my example below [quote=]Ping statistics for 51.79.98.95: Packets: Sent = 6, Received = 6, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 90ms, Maximum = 110ms, Average = 98ms[/quote] Unfortunately ping is not the most reliable test method as can be deprioritized along the way (there are others but let's not get too involved right now) importantly it will at least give us some indication. If results are bad then we need to connect via an ethernet cable and try the test again and post the result. If there is packet loss or high latency still then it the problem will not be on your LAN but rather the WAN (internet) and problems could be from your router onwards (ISP etc...) If your not healing yourself via duel clients best not to heal other people anyways if they have not agreed to it as they will get annoyed because you will slow the gains. There may be something related to that but let's try the network issues first as you also say it happens when your heal your other character.[/quote]