ZDoom

Better do: Repeat TNT1 A 10 // 10 times { A_SpawnItemEx("BFGImpactVapor",3,0,0,frandom(-4,4),frandom(-4,4),frandom(-4,4),0,SXF_NOCHECKPOSITION,128); A_Something(...); } and Repeat TNT1 A 10 A_SpawnItemEx("BFGImpactVapor",3,0,0,frandom(-4,4),frandom(-4,4),frandom(-4,4),0,SXF_NOCHECKPOSITION,128) or ...

Graf Zahl wrote:but building such a thing for larger maps takes forever.

over 10 seconds..

Csonicgo wrote:I never noticed any "framerate dips" or loss of performance - I saw an increase in performance.

I love these linux users who are saying: "all works for me!!!" But I don't believe in magic like this. Plus, not all of PCs have 4 core 3.2ghz processors.

Graf Zahl wrote:Conclusion: Intelligent > Monsterovich
So tell us, smartass, how are we supposed to do anything about such a problem if you keep it secret?

Oh, yes. This will probably fix this issue!!!

You should've tested it before release.

Edward-san wrote:Why didn't you do that earlier?

Because ZDoom has "great" quality control.

Linux now uses SDL2 which can produce less frame jitter with high frame rates, has some vsync support, and fullscreen is now a "desktop fullscreen" mode. So.. - SDL_FULLSCREEN_DESKTOP is a crap that works 3x times slower than normal fullscreen. Feel the difference between zdoom 2.8 (SDL2.0) and ...

So I'm not sure if this was ever addressed (I'm not around much), but a little over a year ago, there was a short discussion where Graf mentioned it might be possible to use bitmasking to exclude certain parts of a level from certain dynamic lights. SHADOWS! Please. https://iamjoe.files.wordpress ...

An efficient alternative to this system that would allow to change collision types and groups of every actor during the game would be to store two bitfields in every actor: int CollisionTypes; int CollisionGroups; And use a->CollisionTypes & b->CollisionGroups to check whether these two actors may ...

This feature is a replacement for +GHOST +THRUGHOST in situations that are complex and need more than +GHOST and +THRUGHOST, but where actors don't change their collision rules over time. CollisionType <string> - actor that goes through actors with group <string>, an actor has only one collision ...

What about cylinders instead of shitboxes.

Slade 3, I'm waiting for slopes support and I still want to see 3D floors support there.

Actors teleport
Hitscan teleports
Railgun teleports

Sweeeeeet.

It's harder to implement and it's also not a free pass to better performance. But it is not an impossible way to render levels. Yes, but if you look at GZDoom benchmark output, you'll see that at least on NVidia, rendering polygons one by one is not a performance issue, even for a map like Frozen ...

Please do some investigation first, before making any further suggestions. What investigations should I make? I don't say "implement this in gzdoom right now". Even if some problems could be solved... What other problems are not solved? you'd still have to account for a lot of factors that would ...

LOL so much talk but not even a hint of his work. If you want to know how hard it is to implement: try implementing it yourself. Show your work. Where did I say I am going to implement this? I am not, but not because "IT'S IMPOSSIBLE!111", but because it's hard to implement. All I want is to stop ...