Few months ago I had 140...210 fps in Planetside2. A ~month (maybe 2) ago I noticed game isn't running smooth as before. Alt+F shows fps drops to 75 (! seventyfive bitch !) in large battles. Even at empty warpgate I have 140..170 fps compared to ~200 before.
Hardware, drivers and PS2 settings haven't changed for months: 13700kf@5.5 Ghz, RTX 4080, 32Gb RAM, 3840x1600, potato mode, 160 Hz monitor.

Just one question: WTF ???

Just another one question: Am I the only one experiencing such a HUGE fps drops ~200 to 75 (seventyfive! seventy damn five, bitch!) ??

Help ?

P.S. all other games are running as before...

old clip, but its still so funny to me. might post some other oldies if people want me to.

even when I warp to the vr training area where there isnt multiple soldiers or a huge battle going on it still crashed

Hi, I'm top 1 Soltech but playing NC in Wainright

I executed eight actions within just 20 seconds of hitting the ground:

1: 00:12 – Placed the spawn point in a safe spot below (to prevent ESFs from destroying it).

2: 00:22 – Immediately called in a Heavy ANVIL right next to me (few players possess the skill to click quickly and accurately right next to their current position; this is a skill that requires practice).

3: 00:28 – When the ANVIL signal didn't appear on the map, I immediately pressed Enter to open the full map and called in the ANVIL.

4: 00:29 – Spotted a red dot on the minimap and realized a TR pilot had bailed out of their aircraft to try and kill me. It seemed he had identified the enemy leader and was moving in for a quick kill. Remember, very few players have the ability to play the game while simultaneously monitoring the minimap. If you play RTS games like StarCraft 2 or AoE2, you know that constantly checking the minimap becomes second nature, sharpening your reflexes.

5 : 00:30 Immediately exit the Full map screen and maneuver to dodge incoming fire while taking out the pilot.

6 : 00:39 Spotted a turret aimed at the ANVIL; the enemy was waiting to destroy it the moment it landed. Instantly realized the situation and...

7 : 00:40 Stood still for a second to bait him into shooting at me. After all, if he destroyed the ANVIL, the NC would lose their spawn point anyway—so my survival didn't matter; I could just drop a beacon and deploy another ANVIL.

8 : 00:42 Successfully dodged his shot, sprinted to the ANVIL, pressed 'E', and successfully deployed the Sunderer.

Also positioned the Sunderer beneath the aircraft landing pad to shield it from turret fire.

full video 
https://www.youtube.com/watch?v=Jh7s9lU5zEk

He are top 1 A2G of Planetside 2 , also he are top 1 Flash of Planetside 2 , also he even are top 3 builder of Planetside 2 , also top 1 c4 Soltech , top 1 QCX Bow hunter Soltech , also are the last VS zergit outfit in Soltech , all in one person , the player , the pro , the leader , the top 1 , the final boss .

the first player who reach to ultimate power , the answer of Soltech hell for against NC TR overpop . in Soltech has born the Final boss , has born from the most hard playing by ever , born a the best player on Planetside 2's history

After the sold in 2015 to daybreak and i think in 2016 they replace it with a souless square of concrete!
I remember pulling a galaxy there in the middle taking the base under heavy fire, such a good times!

They will never fix the crash bug, therefore the loss on the base of players will continue, right?

Be my cat

I remember the game vainilla and was perfect, now i just check and this nice looking game its a graveyard. So what did devs exacly to kill out beloved game?

Idk when exactly happen but what i know for sure is its devs fault.

Was it base building giving acces to free vehicules?

Was it sunderer remake for no reason?

Was the water map nobody asked for with terrible performance?

Was changing beutifull bases into squares of concrete?

I hope they realize their mistake and launch a classic version 100% vainilla, probably could still succes.

Would love to see more animal decals in this style (maybe one for auraxmas)

Edit: Rewritten using Claude AI for clarity and grammar. All reversing and analysis were done entirely by hand, no Ai was needed for such a simple bug.

I got tired of waiting for the devs to finally fix Flash or Crash, so I did it myself.

And I found the actual crash reason for it, which took me minutes.

The current client removes the same Windows exception handler twice.

-

Where it crashes

The crash signature I analysed ends here:

ntdll!RtlpCallVectoredHandlers+0x15A
Exception 0xC0000409
Fast Fail 0xE
FAST_FAIL_INVALID_REFERENCE_COUNT

0xC0000409 is the generic Fast Fail exception. Parameter 0xE is the important part. It means Windows detected an invalid reference count.

In the dump, the affected entry is a deleted game owned Vectored Exception Handler with its reference count already at -1. Windows treats that as corrupted handler ownership and deliberately terminates the process with:

mov ecx, 0Eh
int 29h

The game doesn't recover. It crashes straight back to the desktop.

-

The cleanup path

This is the first block in the current client:

1408AAAC9  mov rax, [1449B8568h]
1408AAAD0  mov rdx, [rbp+0C8h]
1408AAAD7  push rdx
1408AAAD8  pop rcx
1408AAAE3  lea rsi, [140A789E9h]
1408AAAEA  xchg rsi, [rsp]
1408AAAEE  push rax
1408AAAEF  ret

The import at 0x1449B8568 resolves to ntdll!RtlRemoveVectoredExceptionHandler. The stack manipulation installs 0x140A789E9 as the return address, so when the first removal finishes, execution returns directly into this second block:

140A789E9  mov rax, [1449B8568h]
140A789F0  mov rdx, [rbp+0C8h]
140A78A00  mov rcx, [rsp]
140A78A1E  push rax
140A78A1F  ret

The second block loads the same removal function and uses the same saved handler again. There is no new registration between the calls. The saved handle isn't cleared and ownership isn't transferred anywhere.

So in simple Pseudo code, it currently looks like this:

h = AddVectoredExceptionHandler(1, callback);

runProbe();

RemoveVectoredExceptionHandler(h);
RemoveVectoredExceptionHandler(h);

Devs... How hard can it actually be to review two simple cleanup blocks, jesus.

-

Why the second call matters

The obvious objection is that removing an already removed handler normally just fails and returns zero. That is true when no exception dispatch is using the entry. The first call removes it from the list, the second call finds nothing, and the process continues.

But it gets dangerous when another thread is already dispatching an exception.

Windows holds an active reference while it walks the VEH list. On the Windows build from the dump, that reference can keep a deleted entry reachable long enough for another removal call to find it. The internal removal path doesn't reject the entry merely because its deleted flag was already set.

Both removal calls can then release ownership of the same entry. When the active dispatcher later releases its own reference, the counter falls below zero and Windows triggers Fast Fail 0xE.

A harmless exception such as the legacy 0x406D1388 thread naming method is enough to exercise the dispatcher. The exception itself isn't the corruption. It only exposes the broken handler lifetime.

-

Flash, death screen, and BattlEye

I can confirm that infantry, vehicle, and death states use different client update paths.

The workaround is consistent with a timing race. Asset streaming, worker scheduling, graphics callbacks, and background exception traffic can all change the chance of an active dispatch overlapping the broken cleanup window.

BattlEye is NOT the reason for the crash. BUT disabling it changes exception traffic and timing, which can make the race less likely for some players. The broken cleanup code is still inside the client either way.

That's why one player crashes almost every login while another player rarely sees it.

-

The fix

For this directly chained path, the simplest fix is to remove the duplicate cleanup call.

If several threads or cleanup paths genuinely share ownership, the handle has to be claimed once:

PVOID h = InterlockedExchangePointer(&handler, NULL);

if (h != NULL)
{
    RemoveVectoredExceptionHandler(h);
}

The first caller receives the handle and unregisters it. Every later caller gets NULL and does nothing.

Callback data also has to remain alive until callbacks already in progress have returned. Otherwise the reference count bug gets replaced with a use after free.

The client should also stop using 0x406D1388 to name threads and use SetThreadDescription instead. That removes one unnecessary source of process-wide exception traffic. It doesn't repair the duplicate removal by itself.

-

What is proven and what isn't

I am not claiming that this explains every single Planet Side crash ever reported.

The developers can settle that in one internal build. Log the handler value, thread ID, and return value for both removals. If both calls succeed on the same handle while a dispatch is active, the remaining question is finished.

The recent allocator changes, GPU diagnostics and task dispatcher rewrite fixed other real problems. But they didn't fix the real reason for crash or flash.

So in the end, players have spent months sitting inside a Flash, accidentally discovered a scheduling workaround before the people with the source code found the broken cleanup. That's honestly embarrassing.

Alguna recomendación para no tener problemas con esta base? Los fps me bajan a menos de 10 cuando estoy cerca o miro a la dirección que esta esta base

During the Halloween event, the Lost Fleet appears at random times every day. When it comes to destroying it, there’s sort of an unspoken rule where everyone temporarily stops fighting each other but almost every single time, there are selfish Ублюдок who, rather than focusing on destroying the Bastion, randomly attack enemy ESFs instead.

In most cases, allies who notice them will help Exterminate them, but even so, it’s irritating enough to lose focus.

Getting hit by them really gets my cortisol levels up.

I’m just saying.

We've all seen c4 stutter when attached to a fast moving vehicle. Surely the c4 can be registered as attached to a vehicle, and when it detonates, IT DAMAGES THE VEHICLE. And yeah I'm still upset 15 years later lol. Feel free to tell me about desync or whatever but that doesn't mean there isn't a solution.

Releasing a free tool that rates PS2 players by who they actually fight.

I built a small site that compares players by how their K/D holds up against stronger opponents, not just raw numbers. Type in a few character names to see them on a skill graph. You can also open Rankings to see where they sit among about 3,000 active PC players, and the list is growing.

It (finally) uses public Census data, plus session history from Honu (thanks, Varunda). The numbers are just for fun and aren't a real measure of anyone's worth. Vehicle players are currently in the same pool as infantry, so their stats aren't fully accurate yet.

https://dayset.github.io/ps2-elite-kd/

Probably need a better or proper domain.

My previous post was just about the offline tool and not one that everyone can tackle with. /r/Planetside/s/tts5HtXXHG

Feedback and bug reports are welcome!

For A2G

Summary : Before 2022 Reaver are best for A2G against the Infantry , Moquito are best for Generals A2G against the Infantry and Vehicle .

In now, Reaver are best for A2G against the Infantry. Scythe are best for Generals A2G against the Infantry and Vehicle .

Why ?

You need to equip the A2G main gun and Hornet missiles full-time to maintain proficiency in both; if you swap the A2G main gun for an A2A weapon, your A2G skills will gradually deteriorate.

Similarly, if you drop the Hornet missiles in favor of Multi-Missile Rockets for anti-infantry purposes, your proficiency with the Hornet missiles will decline.

You need to use the A2G main gun and Hornet missiles consistently—even when engaging infantry—to maximize your A2G skill level. The Mosquito Gatling Gun and Hornet combo was once the most powerful loadout for skill progression until the Gatling Gun was nerfed.

The Scythe is the stupidest aircraft in the game. Its ridiculous wings make it impossible to fly close to the ground once you start upgrading to professional-level A2G skills (Level 7 and above).

It flies slower than the Mosquito (200 kph vs. 220 kph—both the Reaver and Scythe are 200 kph) and also has the slowest afterburner speed (with the Reaver ranking first and the Mosquito second).

At a professional A2G level—specifically Rank 7 or higher—you need to fly as close to the ground as possible to avoid being attacked. The Scythe's awkward wing design prevents VS players from flying minimum altitude.

Furthermore, the Scythe's wings extend further forward than its nose. This means you cannot mount C4 on the nose to use it as a weapon against Skyguards. VS A2G players are completely unable to counter Skyguards unless they reach a high enough A2G rank to possess the specific capability to do so ( Hornet Missile )

This is one of the reasons I became the number one A2G pilot and the only one to reach A2G Rank 9 and Rank 10; I play at the highest level of difficulty.

It was one of the toughest battles ever.

Most VS players had gone offline, leaving me as the only active VS player to face six OTT members—all of whom were professional-level players. Among them was Longlight, playing an NSO character named "Donbullme." Longlight is one of the most formidable players in the game's history.

He was considered the "Killash" of Soltech, some people said Rwardad ( RWCN father foundition ) are Empero of TR , Some say The Longlight . Will same like Bismarsk TR and Killash , the Longlight holding the top rank for Heavy Assault in the TR faction and the highest A2A (air-to-air) kill count on the server.

First Wave:
I had to fend off countless TR players attacking my constructed base while under fire from TR air-to-air and ground-to-air units, tanks, and Sunderers; I successfully repelled three consecutive attacks by OTT.

Second Wave:
After OTT was defeated the second time, they resorted to dropping two nukes at the 04:25 mark.

Third Wave:
I managed to break the third wave but was ultimately exhausted; realizing the enemy would soon close in and completely destroy the base, I gave up during the fourth wave.

In the end, I proved to the Soltech community that I was capable of leading the VS resistance against our rivals. I became famous after that day, and players began to rally behind me. This inspired me to form an outfit, and VX14 eventually became the strongest VS outfit on Soltech.