Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Can't kill Pap without Dcing
#1
I can't seem to kill Pap without dcing half way. I've tried lowering my quality to the lowest and played in Window Mode as well. But before I can even damage Pap half way, the game closes automatically. =/
I've wasted soooo many crack pieces and pots by fighting so many times already. -_-

Here are my computer's specs:
Windows 7 Home Premium 64Bit
4 GB DDR3 RAM
640 GB Hard Drive
Intel GMA x4500 graphics
CPU: Intel Premium Processor
Reply
#2
Your specs aren't necessary. Right now, the d/cing is a glitch that needs fixing like many of the other summoned bosses I'm afraid.
Reply
#3
So this is normal for now? >.<
Reply
#4
Pretty much until Nexon fixes the glitch. :/
Reply
#5
ItzLouis Wrote:So this is normal for now? >.<

You can still fight mano without d.cing!
Reply
#6
Gregory Wrote:You can still fight mano without d.cing!

But Mano is not a spawn that you don't have to enter some special room or offer something to summon. From what it seems anyplace where you have to summon a boss there's this D/C problem.
Reply
#7
Is this problem affecting everyone or just certain people?
Reply
#8
Cavalier Wrote:Is this problem affecting everyone or just certain people?

Seems like its everyone. I'm pretty sure it has to do with the memory leak problem or w/e its called that people were talking about.
Reply
#9
Submitting a ticket is all you can do for now. It's mostly the Boss's HP bar that's causing the issue.

I will say if you login and then directly go to Pap and defeat him, you might not D/C as quickly.

Someone even suggested disabling the sound card. I'm researching using OpenAL wrappers currently for people with Realtek, Creative, and ASUS sound cards.
Reply
#10
hasn't happened to me yet and i've paped maybe 5 times now.
Reply
#11
I haven't either but when I do beat Pap, the exit NPC's dialog screen is glitched and I have a 10 second delay exiting Pap's area which usually crashes afterwards if I try to enter the MTS. Other than that the game plays fine minus the annoying audio loop glitch..
Reply
#12
GunisBack Wrote:Seems like its everyone. I'm pretty sure it has to do with the memory leak problem or w/e its called that people were talking about.

in summoned monster maps maple eats memory 4mags at a time. Mine eventually just stopped at around 1.3 gigs of ram. When i opened system option menu, it finally release the memory.
 Spoiler
Reply
#13
SunnySis Wrote:in summoned monster maps maple eats memory 4mags at a time. Mine eventually just stopped at around 1.3 gigs of ram. When i opened system option menu, it finally release the memory.
 Spoiler

Could you theoretically keep opening the system options menu every time Pap goes into its shell to stop d/cing? (For those of us who don't kill Pap in 20 seconds)
Reply
#14
Cavalier Wrote:Could you theoretically keep opening the system options menu every time Pap goes into its shell to stop d/cing? (For those of us who don't kill Pap in 20 seconds)

the act of opening the system options made the mem usage go back down to normal but it took a few seconds, and while it was going back down the game was frozen. Once the game came back, even with the menu open, it started to hog memory again. It would seem logical that you could just keep opening the system options menu to keep resetting it. I would suggest you make sure it is checked to windows mode, if that is how you play, before you go in. Sometimes the system option menu does not display correctly or at all so you have to remember how many keys to press to get it to open. i think it is (esc up up up enter).
Reply
#15
you do mean, that when you try and talk to the npc the dialog is like.. transparent? if so i usually just change the resolution from lowest to highest(whichever) and it seems to usually solve the problem for me) and I usually get out fine.
Reply
#16
It appears that disabling your sound driver has worked for many people in this thread http://www.southperry.net/showthread.php?t=36029
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)