Good job

i crashed twice and i know a friend crashed at least 6 times

Try turning down your effects/distances/other peoples names when entering a high lag area.

I had 2 clients on, one on HL and one on HT, I did NW on HL didn't crash than1 hour after I did NW on HT, both clients open all that time, I didn't crash.

... Well that news made me happy. Nice to see the devs are working on updating the game some so that it can do what it should have been able to all along. b:chuckle

Channman - Lost City wrote: »

inb4fuzzycomesinandsaysstopcrying

Stop?

My computer has been acting strange ever since the Sirens update. I have
a good system, and used to be able to play at highest settings with no
problem.

Since that update tho, even with settings set to low, I crash frequently.

I have never crashed O_O

v4liance wrote: »

Something worth mentioning:

Bubbles posted a fix for a memory issue our game has had, but I was forced to take it down, due to our rules about 3rd party patches.

But our developers are working on a similar fix, to increase the amount of memory our game can handle.

I'm not sure if this is related to your crashing problem, but I do hope this will alleviate many of the crashes some players are having.

And unfortunately, I don't know exactly when this fix will be implemented. But I'll keep you all posted as I learn more.

- Val

Thank you.
Little tidbits of information like this are great, knowing what they are working on, or at the very least that the developers are actually aware of what problems there are.
So, thanks for sharing things like this b:thanks

I suggest to buy a new computer >_> Its only a logical for wooden computer to lag in this kind of game b:chuckle

My client also crashed 3 times yesterday right after NW in north Archo. I have a Dell xps notebook bought this year, more than enough for a game like pwi, I was also running in a lower resolution (1600x900) in windowed mode.

I usually don't crash much. Only thing I can really say is the rare crash in morai or teleporting to tides did it nicely. But since I can pick my keys anywhere now, that's not much of a problem anymore.

I suppose I got a pretty decent pc though, should be able to handly such an old game when it's build for graphic work. b:chuckle Can't say I ever had to turn my effects down tbh.


The only time I really crash is when I do lots of treasure maps in a row. After a while, my map will just just bug out and be blank, and upon relogging the client just crashes literally every time. Dunno if that would be related to the memory issue too?

Yuna_Sama - Heavens Tear wrote: »

I had to take the decision to turn the virus scanner off (it can't do anything about it anyway) for the time being just to be able to use my pc without annoying messages all the time... Don't know which program causes it but I regret starting PWI this week...

Either make sure the files a false positive and add it to expections or just clean the whole thing. The way you're going, you're only getting a ton more **** onto your system.

I didn't crash until after but entering we had 5/10 people crash. So much for pre buffing/chi building.

My squad recovered but throughout the entire nw we had crashes until our lead crashed. He relogged but a ghost-lead still had out squad. We all had a squad glitch where we couldn't buff each other or drop squad. Eventually a new party was formed and everything returned to semi-normal amidst the chaos that is nw.

Couple issues. Kind of a pain that you can't see whats happening to your squad while traveling. You have to exit back to the area you are in.

Bigger issue: 1200 players being dumped into North Archosaur simultaneously and it taking three complete crashes for me to walk my *** off into a corner to get away from the chaos, lag, and crashes. Can we divide the drop points after nw or return us to where we entered NW? If nothing else, I'm gonna start camping inside for 15 minutes to allow others to clear out before I leave nw.

Yuna_Sama - Heavens Tear wrote: »

You're the lucky one... I started PWI somewhere this week and my virus scanner told me there was a Trojan in one of the game files... Ever since my scanner keeps bugging me about the same Trojan being in one of my system files... It's probably another false positive (if not I'm gonna be very pissed) but it's still quite annoying... I had to take the decision to turn the virus scanner off (it can't do anything about it anyway) for the time being just to be able to use my pc without annoying messages all the time... Don't know which program causes it but I regret starting PWI this week...

Yuna, please add it to the exception list. Just not using one is just about the worst solution to that problem. Even getting a different antivirus would be better....

The crashes have to do with the client reaching 1.7 gb of ram and crashing as it, by default, cannot load more.

The people who experience crashes like this the most are those who are running the client for a very long time and those who are running on higher graphics.

Most of the time the client gives out when you going into new areas or loading all of the characters in arch because you're suddenly loading so much more that you reach cap and the client crashes.

NW causes a lot of issues with this because you have a lot of players standing in one area, thus it becomes really easy to hit that cap. With the cap fixed, I notice the usage can go up to 2.7 gb right before nw starts.

If you're running a toaster of a computer, there's a good chance you're not going to crash because you aren't loading up as many effects and higher res textures (pwi has small textures to begin with but they do stack up).

For example, it's easy for my desktop to get up to 1.2 to 1.5 just running the client on idle at the highest settings, while my toaster of a laptop gets maybe half of that at the lowest settings.

Why things are this way on x64 is easy to explain. On x86 applications have 2GB of virtual memory out of 4GB (the other 2GB are reserved for the system). On x64 these two other GB can now be accessed by 32bit applications. In order to achieve this, a flag has to be set in the file's internal format.

pwi's cap is around 1.7 gb but this is essentially the explanation.
I want to say that the cap is there because of pwi's age, but I've seen newer games like Skyrim with this same exact issue. Beth actually patched for that sometime after release though iirc.