ZDoom

No idea but the LE guy wants to go back to FMod so he probably has cause to think it works with slow CPUs better than OpenAL. Again you can estimate it yourself by testing with and without sound on; there's a vast number of old ZDoom versions out there to test if you want to satisfy curiosity. As ...

OK, 2006. I still understand why it was done (also that the year Vista came out, possibly some relation). It does show dpJudas's strange rant above to be uninformed, though; it would be quite a few years after XP before any new computer could run D3D 8 or 9. (Mine is 2004 and can't.) But anyway I'm ...

I know that. But I obviously have always seen it in DirectDraw and it's never looked or otherwise seemed 'shitty' to me. Anyway - it's not about 'what I want'; my comments are not to be taken as orders! Especially when they are phrased in the form of a question, which you just answered to the best ...

Yeah, I think that's why people don't use voxels more, there aren't very easy tools to work with them. They really shouldn't be much harder than sprites, and probably easier if the sprite would use rotations. Indeed for the software renderer a voxel is equivalent, I think, to a sprite with a very ...

This has nothing to do with my system, for which the issue is moot. It's about the OP's systems, on which he actually found that DirectDraw runs significantly faster. I was trying to add to that. On PCs you can't necessarily determine someone's hardware very precisely from the OS version they are ...

I already tested win95c and ran fine, i've discarded the changes. It's really slow on that 486, probably fmod is holding it back. Test with -nosound to check that; that's what I do all the time. Seriously is there any reason to hold on to FMod when OpenAL (which runs on all machines) is now ...

Yes, that's the confusing bit. Direct3D is, as this user found, likely to be slower on systems where it matters. Why is DirectDraw not the default for XP and earlier?

I guess we'll have to wait some while longer, then, for LE to be really useful. Well, it's not urgent, anyway. Doom's renderer was never meant to be floating point, but the more precise fixed point. When I wrote a demonstration renderer (which is apparently lost) in DJGPP (the only programming tool ...

The reason for that was that 320x240 required an undocumented hack mode that couldn't be guaranteed to exist on all hardware. Not really. Doom already used a 'hacked' mode, and the way to modify it to 320x240 had already been made publicly available, and why it necessarily worked on all VGAs was ...

Thanks again to dpJudas for the explanation. I and the other posters had no idea; at which version of GZDoom was that change made, if you know? And the potential importance of LE is confirmed again.

I've been suspecting that too, given my recent tests - GZDoom's (non-truecolor) software renderer does seem slower, but maybe this is _only_ on the new releases that also have the truecolor one, as in fact it should have been the same. It is possible, though, that the difference started much earlier ...

320x200 has actually been quadrupled by the video card since the original VGA! If it is now quadrupled in software (before the video card), then it's not the card's fault it is not available. Anyway 320x240 should always work as a substitute for 320x200 - indeed, Doom should have originally been ...

You would, if you run GZDoom under that configuration, experience the same video issue I recently encountered, and tried to explain in my current thread 'ZDoom current progress'. Briefly, you will not get truecolor software rendering, even when the engine tells you that you are, because it relies on ...

This sounds interesting - is it a one-off or will it become a true maintenance branch that will continue to incorporate fixes and conservative new features? The latter is what I've been looking for with ZDoom (I'm not interested in those ports that preserve _bad_ vanilla behavior, like infinitely ...

I have also been informed of an issue with my demos: Andy at SDA says my M1 demos desync, and I have seen that they do on 1.2 but not _my_ 1.1 . Since importing the 1.1 map into 1.2 fixes it, it must have been some change to the map; the desync happens turning the corner just before the non-secret ...