View Single Post
  #3  
Old 02-01-2009, 03:24 AM
Edward Edgemenace's Avatar
Edward Edgemenace Edward Edgemenace is offline
Has Walked The Plank!
Edward Edgemenace's Primary Pirate Info

Join Date: Jun 2008
Posts: 1,539
Edward Edgemenace is a pirate wannabeEdward Edgemenace is a pirate wannabe
Quote:
Originally Posted by Walker Boh View Post
this sounds exactly like the problem im having. login screen changes then crashes to bug report and pirates login page.. i tried entering a new port but am not sure if i did it right. heres steps i took. if wrong can some one please correct me..
opened up windows firewall. turned it off. at top there are 3 tabs general, exceptions and advanced. i chose exceptions . window changes to one with some programs listed in as exceptions currently running such as IE trillian etc. there are 4 tabs under the list being add program , add port , edit delete. i got to add port. click on it . another window comes up. it has place to type Name and under it port number. below that are 2 check boxes marked tcp and udp . tcp is checked . i hit ok . i named it pirates. it then shows up on exceptions list. so now to add the programs . i click add program button. a whole list of things comes up all programs. i find pirates program and add it. then add the launcher and then again add pirates .exe. my question is this did i do it right. cause it still not letting me past login page . i made sure game-options say working version 14 and api is pandadx9. did i check the wrong tcp box or should it be udp.when i try to log in and the crash happens i check the cashe and it has 800 files in it each time. i clear it each time as well. help please
It sounds like you entered the windows firewall exceptions correctly. (With it turned off entirely, as you do, you don't need them, of course.) I assume you've tried the GRAPHICS OPTIONS on the login screen, trying openGL, Pandadx8 as well, right? I never clear the cache...it maintains it itself, usually about 1,000 files or so.

There might be hints for you in pirates-090131-xxxxxx.log to help narrow the problem down.