). When you see one of these for the first time in a level (especially when I'm using the flame and smoke together), there's a momentary slowdown, then the game gets back to full speed and only really slows down again if I throw loads of these things into the map - but that's obviously for a different reason.Most of the time, it's barely noticeable (but something I'd like to improve on if possible) however, yesterday (for my sins) I downloaded the Risen3D version of the hi-res texture textures and tried them with GZDoom. Once they were up and running, tings were fine - but if I moved into a new area where a lot of previously unseen textures suddenly came into view (opening a door is a perfect way to make this happen) there was a very noticeable performance hit as the data was loaded. I reckon once, opening the door nearest to the player on the right in E1M2 the hiccup was the bast part of 1/2 a second. Not a life shattering delay, but one that could certainly interfere with gameplay, especially when similar delays were happening quite a lot.
I also get the feeling that it's more common when the mod being played has a lot of data in it, even if the thing being encountered isn't that big. Perhaps search time in big WAD files or something is an issue?
I'm sometimes aware of it in regular Doom/2 too. However, then the data being loaded is so small that I think I'm really only noticing it because I'm aware of, and sensitive to the issue.
So, are there any suggestions for a way for me to improve on this?
