I'm experiencing an issue where PB causes extreme stuttering / fps loss, but only on certain megawads. Performance is normal when first starting a map, but over time a stuttering / fps drop appears. This stuttering / fps drop gets continually worse over time, and within about 2 minutes of entering the map it becomes an unplayable slideshow.

This issue doesn't occur with the vanilla Doom map sets, and I don't know enough about megawads to isolate what characteristic of the megawad triggers the issue. I've been able to reliably reproduce it using Eviternity RC1 (https://www.doomworld.com/forum/topic/103425-release-eviternity-rc1/) with the following setup:

Loader: ZDL
Source Port: GZDoom 3.7.1 Modern x64
OS: Windows 7 x64

WAD Load Order:

• Eviternity-RC1.wad
• ProjectBrutality.pk3 (latest master version, commit b659c13)

IWAD:

• doom2.wad

Project Brutality game mode, Brutal difficulty.

The issue will occur on MAP01. This issue does not occur with the PB 3.0 public test version from January 2018.

not our fault. The problem is the constant spawning of raindrop actors.Map needs to delete the actors, GarbageCollector. Compatibility wise, one would need to recreate the droplet actor,replace the default with it , give it a max timer of like 2 seconds, and have it disappear or something.

Confirm this by typing 'actorlist', wait a few seconds and repeat.You'll see what I mean

Valiant (https://www.doomworld.com/idgames/levels/doom2/Ports/megawads/valiant) is another megawad where this issue can be reproduced. I did an experiment where I left my player motionless at the spawn point of Valiant MAP01, and recorded my FPS and number of actors every 10 seconds of game time:

There's no rain effect on this map, and I'm not seeing a relationship between the number of actors and the fps loss. If I run the same experiment with the January 2018 PB public test version my FPS holds steady at 200 fps.

What are your specs with your current setup (OS, Graphics card, Processor, and GZDoom version)?

I ran the same experiment across a range of revisions, and I was successfully able to isolate 57b1f8d as the commit which introduced the issue. I'm not able to reproduce it in commit 84beea8 or earlier.

I tried changing that function override back to PostBeginPlay() in my local copy of b659c13, and it resolved the issue. I don't really understand the ramifications of that change, so I'll leave it to someone else to implement a proper fix.

OS: Windows 7 Professional x64
Processor: i7-4770
RAM: 16 GB DDR3
GPU: GTX 1080
Source Port: GZDoom 3.7.1 Modern x64

Yes, that commit seems to be the culprit of severe performance degradation. It needs to be redone.

Ok, it's a matter of waiting for a PR merge.
BTW, my computer specs:
OS: Windows 10 Enterprise x64
Processor: i5-6500
GPU: AMD RX 460

I am playing Eviternity RC1, and having no issues.

However, I was having issues with the game in-general because it was loading from such a large archive.

What I did was split out the SPRITES and SOUNDS folder into seperate archives, change all archives to use a compression level of 0, and the game ran a lot better.

New vegas headshot mod 1. This is likely NOT the source of your issues, but it might help you get some decent performance boosts, at least enough to keep playing those levels for a bit longer