test content
  • Games
  • Social
  • Arc News
  • Support
  • Zen
What is the Arc Client?
Install Arc
Forums > Home› Support› PC Gameplay Bug Reports

Game crash only in ESD and ISA stf

auron8222auron8222 Member Posts: 97 Arc User
in PC Gameplay Bug Reports
When I go on space ESD and ISA stf the game crash.After I restart the game it work.Does anyone else have this problem?How can I fix it?
Tagged:

Comments

  • snowwolf#0563 snowwolf
    snowwolf#0563
         Member Posts: 1,018 Arc User
    Never had this problem at all. Try to verify game files through "options" in the game launcher/client.
  • dracounguisdracounguis Member Posts: 5,358 Arc User
    edited July 2017
    Verify should fix any file issues. Try updating your graphics driver and DirectX.
    Turn off STO lighting 2.0. Some people get issues w/ it.
    Other than that, I'd say turn your graphics down to minimum and see what happens on ESD. If good, then start turning on other effect one at a time till it goes kaput again.
  • auron8222auron8222 Member Posts: 97 Arc User
    I tried everything without results,this problem appeared after the last patch..I will wait for the new patch for a fix
  • arionisaarionisa Member Posts: 1,421 Arc User
    Navigate to the STO folder on your computer, sort the files by date and at the top you should see a bunch of .log files.

    Open the one with the newest date/time stamp and see what it says, open the ones with the file name that starts with "packet" not the one starting with "pcl".

    You shouldn't need anything special to open it with but if need be just right click, select "open with" and open it in notepad. That file should give you an indication as to what is going on. Once you have that info you can post it and maybe someone can help you out. Of course. try a forum search first as the "cure" might already be posted somewhere.



    For example, my system just a few patches ago started crashing quite regularly and the log files all read the same....
    """170717 01:38:22 2 [1]: Link 1191956840 (1) (pcl_client.c(1836)) added to remove list: patchclientlib redirecting:linkQueueRemove(997:Unknown socket error""""". Now that I know what caused the crash, I looked at the "pcl" file and it tells me """170717 01:38:25 15 [1]: Using HTTP patching: server level3.stohttppatch.crypticstudios.com port 80 prefix Startrek"""""

    Of course both files had more info than that but those are the key lines that I needed to know what's happening. Doing forum/google searches armed with that info I now know that going into my router set up and "port forwarding" port 80 (plus a list of others that STO uses) will likely fix my problem, I just haven't gotten around to it yet as I forgot my router password and I've been reluctant to reset the router to default so I can get in.

    LTS and loving it.
    Ariotex.png
  • auron8222auron8222 Member Posts: 97 Arc User
    arionisa wrote: »
    Navigate to the STO folder on your computer, sort the files by date and at the top you should see a bunch of .log files.

    Open the one with the newest date/time stamp and see what it says, open the ones with the file name that starts with "packet" not the one starting with "pcl".

    You shouldn't need anything special to open it with but if need be just right click, select "open with" and open it in notepad. That file should give you an indication as to what is going on. Once you have that info you can post it and maybe someone can help you out. Of course. try a forum search first as the "cure" might already be posted somewhere.



    For example, my system just a few patches ago started crashing quite regularly and the log files all read the same....
    """170717 01:38:22 2 [1]: Link 1191956840 (1) (pcl_client.c(1836)) added to remove list: patchclientlib redirecting:linkQueueRemove(997:Unknown socket error""""". Now that I know what caused the crash, I looked at the "pcl" file and it tells me """170717 01:38:25 15 [1]: Using HTTP patching: server level3.stohttppatch.crypticstudios.com port 80 prefix Startrek"""""

    Of course both files had more info than that but those are the key lines that I needed to know what's happening. Doing forum/google searches armed with that info I now know that going into my router set up and "port forwarding" port 80 (plus a list of others that STO uses) will likely fix my problem, I just haven't gotten around to it yet as I forgot my router password and I've been reluctant to reset the router to default so I can get in.

    thankyou very much for the tip,I found this on my latest Packet file:

    170717 20:14:23 1 [1]: Link 1187006416 (1) (pcl_client.c(1836)) disconnected: patchclientlib redirecting
    170717 20:14:23 2 [1]: Link 1187006416 (1) (pcl_client.c(1836)) added to remove list: patchclientlib redirecting:linkQueueRemove(997:Unknown socket error)
    170717 20:14:23 3 [1]: Link 1187006416 (1) (pcl_client.c(1836)) added to remove list: patchclientlib redirecting:linkQueueRemove:sock==INVALID_SOCKET:read failed(997:Unknown socket error)
    170717 20:14:23 4 [1]: Link 1187006416 (1) (pcl_client.c(1836)) in linkFree: patchclientlib redirecting:linkQueueRemove:sock==INVALID_SOCKET:read failed(997:Unknown socket error)
    170717 20:14:23 5 [1]: Link 1187006416 memory freed
    170717 20:14:27 6 [1]: Link 83276416 (2) (pcl_client.c(1836)) added to remove list: pclDisconnectAndDestroy:processFlushedDisconnects:linkQueueRemove(997:Unknown socket error)
    170717 20:14:27 7 [1]: Link 83276416 (2) (pcl_client.c(1836)) added to remove list: pclDisconnectAndDestroy:processFlushedDisconnects:linkQueueRemove:socket is invalid(0:No error)
    170717 20:14:27 8 [1]: Link 83276416 (2) (pcl_client.c(1836)) in linkFree: pclDisconnectAndDestroy:processFlushedDisconnects:linkQueueRemove:socket is invalid(0:No error)
    170717 20:14:27 9 [1]: Link 83276416 memory freed
    170717 20:14:37 10 [1]: Link 1420174896 (3) (pcl_client.c(1836)) disconnected: patchclientlib redirecting
    170717 20:14:37 11 [1]: Link 1420174896 (3) (pcl_client.c(1836)) added to remove list: patchclientlib redirecting:linkQueueRemove(997:Unknown socket error)
    170717 20:14:37 12 [1]: Link 1420174896 (3) (pcl_client.c(1836)) added to remove list: patchclientlib redirecting:linkQueueRemove:sock==INVALID_SOCKET:read failed(997:Unknown socket error)
    170717 20:14:37 13 [1]: Link 1420174896 (3) (pcl_client.c(1836)) in linkFree: patchclientlib redirecting:linkQueueRemove:sock==INVALID_SOCKET:read failed(997:Unknown socket error)
    170717 20:14:37 14 [1]: Link 1420174896 memory freed
  • arionisaarionisa Member Posts: 1,421 Arc User
    Well, after realizing that port forwarding is only good for a single computer on a network, which means no other computer on the network can use that port I gave up on port forwarding as there are multiple computers in my house that people play games on. So, I got brave (or stupid) and set my computer to DMZ (not behind the router firewall). Although I haven't had a lot of time to play since I did that, I haven't yet had a repeat of the regular crashes.

    If yours is the only game computer at your location you can try port forwarding and see if it helps. A simple google search for "how to forward a port" or anything close to that will get you detailed instructions on how to do it and this link
    https://support.arcgames.com/app/answers/detail/a_id/4189/tpc/4189
    tells you exactly which ports need forwarded.

    If yours isn't the only game computer, you can make darn sure you have a good AV program and go DMZ, although if you do that I would suggest only doing it while playing.
    LTS and loving it.
    Ariotex.png
  • arionisaarionisa Member Posts: 1,421 Arc User
    Well, I posted that last one too soon. Everything went great yesterday, tonight, within 3 minutes of logging in....crash.....same socket error. So, DMZ didn't work.
    LTS and loving it.
    Ariotex.png
  • simplyvangersimplyvanger Member Posts: 2 Arc User
    I had an issue with the game crashing on the loading screen trying to get to ESD
    tried many things but finnaly I got it to stop

    Log in go to setting in you character selection screen go to advanced options its the first one. make sure it is switched to ON
    I have not had it crash since.
Sign In or Register to comment.