Rachael

Like I said - it's been so long that I don't even remember all the specific details of the problems that I had. This may very well have been it - but I can't confirm that, because I really don't remember. I'd imagine he got it from the name of a Skulltag medal that became popular for the way it mocked users for not being able to score a frag after being killed a certain number of times. Nevertheless, I do have to agree with Graf - I have to take a double take every time I see the domain name and remember the meme and that it's not supposed to be as jarring as it is. As for rehosting it - why would you do that? Unless you feel really constricted on that site and really feel the need to move, or something. You could probably just get a dedicated domain name (eternity-engine.org, or maybe something cheaper if it's available) and point it to the site, and ask the host to update the configuration files, if they're willing.

He deliberately misinterpreted my post to ignore his own worst offense - in an effort to discredit me, if you really want to know.

Both do - but Eternity's is worse in some cases. But as for the issue tracker, if I find it again, I'll keep that in mind. I think the worst offender was Frozen Time, which yes I know wasn't meant for Eternity, but compared to other software renderers, Eternity's really comes in dead last on this one. I remember being completely unable to even move, there. Like - my computer was almost frozen even trying it. Bear in mind, however, this was a long time ago that I tried it. If any efforts were made recently to optimize the renderer, then I have yet to try it again with the changes.

We're done here. I have nothing more to say to you.

Fine. It's still better than having only one option for a paletted software renderer. But the reason why I think you guys need OpenGL is mostly because some maps run really slowly on Eternity. Could be my weak CPU, but having a little bit of extra speed would help things a lot. Yes - I am. As far as I remember I did try the steps, I don't remember what failed exactly, it's been a long time.

You're god damn right I am upset. And yes, I can and will make an exception: You have been attacking and haranguing Graf unfairly over this issue merely for your own personal interest and for spectacle. Just for nothing more than brownie points. Yes, I have seen how people who attack Graf are catapulted into instant popularity here. So, you just couldn't resist joining in on the fun - could you? Congratulations. Now you're popular. You've had your fun now. So Graf solved it by doing exactly what you guys do in Eternity: stuffed a general attribution in a readme file that no one is going to read anyway. They say - be the change you want to be. You could start by putting "// This line was made by soandso." on every line of code so that we know exactly who did it. "git blame" is really helpful with that. Too much? You're right - that is unreasonable. Maybe it's better to just let sleeping dogs lie, instead.

Eternity is a really cool and awesome port, and I love it to pieces. I have always felt this way, and I always will. It has WELL earned its place in the Doom stratosphere, and has done so for a very long time. But I cannot abide SoM, Quasar, and Altazimuth's actions - which pretty much amount to diminishing the work that Graf put into implementing a "clean-room" version of the feature all for the sake of their own ego-stroking, trying to take undue credit for it, when it is not even the same as Eternity's by nature. In fact, an Eternity map with portals requires tweaks before it even works in GZDoom (such as building sectors behind the portal linedefs). Are some very basic concepts the same? Sure. But when you look at the forest past the trees, in the end Graf really just piggy-backed on the work that ZZYZX originally did, anyhow. He was the one who originally got portals into ZDoom in the first place. Fact is fact: A portal-laden map from Eternity just won't run on GZDoom - even if you use no custom monsters or EDF tweaks - even if you tweak GZDoom's translator enough to be able to read it in the first place. It's a shame that it keeps getting dragged by its own authors into messes like this. Honestly - I think if the maintainers really cared about the port, they'd put in features like optional OpenGL rendering (which GLBoom+ already has - how behind the times are you??!!!) and easier console commands that don't feel so hacky - so that it stands as a viable opponent (and a good alternative) to GZDoom. Oh - and while we're at it - make it easier to contribute to by removing the SDL dependency (maybe others too?) - because I've wanted to write features for Eternity also, but I can't even compile the damn thing. Again - I love Eternity itself - but this fuckery from certain members of their team is not doing it any justice.

Unfortunately I don't participate in this idol worship that is extremely rampant in this section of the Doom community (seriously, could you guys suck up to a select few people ANY harder - including SoM? - makes me want to throw up how much some people here kiss people's asses) - so sad day for you. If he wants that kind of credit maybe he should start making pull requests. Otherwise, he gets treated the same as any other contributor.

Oh for fuck's sake. Seriously? At least your cards are finally on the table. This is what it's been all about from the very beginning. "BOO HOO ZDoom took a feature from us that was so special!" I've been very supportive of Eternity and had a very strong desire for it to grow, but that does not give Eternity devs the right to dictate what other source ports can and can't do. That is at the very least, really fucked up. Also, while we're at it: Dark Pulse does not represent the GZDoom team, and while I cannot deny bias in that I think most of what he is posting is right, he is not directly associated with us in the way that you so flagrantly (and without proof) accused him of. Are we going to have a witch hunt for GZDoom developers now that GZDoom didn't do EXACTLY what your spoiled precious ass wanted? Tie me up at the fucking stake then. Guilty as charged. I am one of said witches. There was no need for any of this Altazimuth - YOU started this shit, because your precious little ego was hurt. Instead of investing time into features that make Eternity a real solid and attractive alternative for GZDoom (I'll have to note here that the software renderer is slow as shit on it, for complex maps), you're sitting here crying over 44-month old spilled milk. If it helps you any I'll give you a sympathy download for your latest release. Congrats numbers?

I'm sorry - violating the GPL? Sorry to burst your bubble, Altazimuth - but GPL only covers copyright law. You can't copyright an idea. Period. Additionally, in order for copyright to be in force, it requires substantial similarity - which is not present here. The only things that are similar are the basic ideas behind the implementations. In order for copyright to apply, snippets would have to be copied verbatim - to the point where even a lay man who has absolutely no understanding of code can look and see and say "yeah that's definitely copied" - and that never happened, here. If what you're are saying is true then just by this same principle ReactOS would be illegal since it reimplements the Win32 API. And Compaq making IBM clones would have been illegal way back in the day, too. DR-DOS would have been illegal because it reimplements the DOS structures and whatever bare API that MS-DOS had. As has been stated twice, now - this is a case for patents, not copyrights. And again - the GPL does not cover patents. In fact, it discourages them.

I don't know exactly what causes the issue but GZDoom is not the only program it happens with. If I run Overwatch on my Intel processor it happens - except a whole lot faster. It's happened with numerous other applications, too. This is not a GZDoom issue - it's an Intel issue - and all this time they haven't fixed it. In short: Unless you find ways to keep your GPU running super cool, there's no way to avoid this issue - and that goes for any game. For GZDoom, the best advice I can give you is run at a lower resolution (use the scaling factor feature if you need a larger window), turn off multisampling, and don't run tonemaps, bloom, or SSAO, as those tend to cook the GPU a lot faster than simple triangle rendering does. Also, make sure that your frame rate is limited in some way, either with vid_vsync or vid_maxfps, or else any effort you make towards lowering the processing your GPU does will be for nothing.

@Aquila Chrysaetos did you read this post?

I'm almost positive that if that were the issue, running at 320x240 would drastically improve things in OP's case. The others are right that having a very low-end CPU will bottleneck things. I experience problems by just running the CPU on low power settings and I know for sure it's using my NVidia graphics because I see the OpenGL init readouts on startup. In many common cases though, you would be 100% right and that would be a thing a person would have to check.

The world is changing. Traditional jobs that so many people worship and would like to worship as being "the only way to do things" are gradually but increasingly becoming a relic of the past. People are increasingly finding ways to employ themselves, and for many people it actually is the only means by which they can survive. Many people can't do the 9-5's like you think everyone "should" be doing. Say what you will about Sgt Mark, but 9-5's are a cancer in our society that we would be better off without. For all the shit Sgt Mark does wrong, for all the people he's hurt over the years, he's got the "getting myself food" part right - sorry but 9-5's are awful and should be avoided in any way possible if a person can do so.

Call out any random mod and stick to your guns enough and it'll stick. It's a standard the community holds itself to, and while many things do get through the cracks, it's only the most popular ones that receive the most scrutiny because more people are playing it and more people care. (And original artists have more to lose with someone else taking credit for their work) Even as someone who is calling out the community on its hyperbole, you yourself should understand how hyperbolic they can be when you raise enough stink.

In my experience, Windows kills tasks automatically before such a thing ever happens. Especially when it's only a single process responsible for this, in this case, GZDoom. You underestimate the safeguards that are already in place precisely for this kind of thing. (Admittedly, virtual memory thrashing will likely be more of a problem before this occurs, but the safeguards will still kick in before a blue screen of death does) However I will partially agree here. There should be some sort of spawn limit to keep things sane. Some maps are utterly disastrous with how they abuse spawn effects and those are actually legitimate. However in a very complex hobby project such as this, it is extremely difficult to account for every single case of this, especially considering the fact that most safety regulations inside the engine can easily hurt performance, which such complex mods depend on very heavily to work properly.

Hell you know what? I realized after I typed this - GZDoom is going to have more issues with NUTS.wad than Mark's petty shenanigan here - because that mod all by itself caps the CPU when all the monsters become activated. GG CPU. And yet, you don't hear of anyone having to put a fire extinguisher to their precious rig just because they dared to try that.

There are many external factors influencing this discussion that have absolutely nothing at all to do with it by themselves. We aren't exactly living in an ideal world right now and it is certainly less ideal than it was even 4 years ago. People, whether they realize it or not, bring their life stresses here, and it all comes out in shitstorms like this. That's just the way things are right now, and probably will be for another few years at least if not more.

I will agree that what Mark did was fairly petty and I already called him out for it. It's not cool, but that's as far as my condemnation goes with him, at least as far as this incident is concerned. However, I think your argument is really hyperbolic. Back in the 80's and 90's machines were literally designed to run at 100% CPU speed constantly. In fact, "Energy Star" really did not become a thing until well after the original IBM PC-XT came out. Before that, we didn't even rely on the HALT CPU instructions, we just put things in idle loops. (*shivers!*) Even so, removing the frame rate cap and vsync on GZDoom will send either your GPU or CPU to 100% anyway - whichever bottlenecks first (depending on the system). And people run this way constantly all the time with no issue. While you can make a serious case that for example, even someone like me, refuses to run GZDoom this way (I like quiet systems without the fans kicking up to max), that's not to say the system can't handle it - and even so, GZDoom is in an unresposive state well before any serious overheating issues kick in, and Windows is already asking you by that time if you want to kill the process before any even theoretical damage can be done. Even if heating becomes a serious issue, both processor sets are designed to lower their voltage and power consumption when heat creep kicks in in order to stem damage - in fact, shutting themselves down is really a worst-case scenario that almost never occurs except in the most poorly designed or poorly maintained systems. To be quite honest, I think you're going to have far more serious issues with heat problems on your system running Fallout 4 than you ever will running Mark's shenanigan here, especially since it can only consume one core anyway. (For the record though, Mark, I still haven't changed my stance that it was extremely petty of you to do that)

I say the Doomworld moderators can do whatever they feel is best in this situation, and what they do reflects on them, and only them, and not on the community as a whole. Just because they let Sgt Mark "get away with it" doesn't mean the community is letting him do that, and I think it's important to recognize that separation. Doomworld staff is not the whole community, and the whole community is not Doomworld staff. In fact, Doomworld staff really are only a small part of it. So let them bear the consequences of acting, if they so choose, or choosing not to act in this case. And there will be consequences either way - fun to be in a position to make tough decisions, isn't it? But that's their problem, not your's. EDIT: To be clear, I was not trying to imply that I would hold the Doomworld staff in moral contempt. What I meant by that was, they'd have to deal with people being upset on one side or the other, depending on who felt "wronged" by it.

You want to know the best thing to do in that case, Mark, when you can't find who made something? Don't use it. It's rough. As a mod author myself, I know it is. But if you want to be the better person, you have to make that call. And sometimes, maybe not always, but sometimes you might just find that when you do - you find something better to use in its place, anyway. I'm going to be culling assets from my community project here soon, and trust me I am *NOT* looking forward to it - but I know it has to be done, because I value my own integrity more than I value my own pride.

And yet, you completely ignored this point - @ Sgt Mark: It's not up to people like wildweasel to furnish a list for you. The onus is on you, and always was. You can solicit help if you need it (and hell, I'll be honest with you - I do solicit such help, myself), but it's still your responsibility and you can't make others do the work for you.

To be fair, no one would blow things out of proportion if you didn't give them things to blow them out of proportion with in the first place. And yeah, that was really petty of you. You darn well know it was a mistake and that's why you're fixing it right now. But you won't be a real adult and own up to it and say "yeah guys, I'm sorry I did it" - instead you're still trying to pretend like it's not a big deal and that no harm was done. But hey, I am not the one who has to defend my reputation after inserting an intentional crash/freeze bug into something. ;) So carry on! Just know that not everyone is as stupid as you think they are to believe bullshit like this.

I've done a little bit more work on GZDoom today to get it Haiku-compatible. I've decided to branch my work since the changes I'm starting to make could be seen as a bit disruptive and I want to minimize that as much as possible. The issue I am running into right now is thread-local storage not being supported. There was an issue with that regarding OpenBSD, too, and unfortunately I can't find what the OpenBSD guy did to get it to compile on his system (or if he even did). It's a bit daunting to encounter a system that has this issue. For now, I am keeping development in the Haiku-develop branch. However, unless the BSD's and Haiku decide to pick up thread-local storage, we may have to deprecate all of them preemptively, because this is something that's going to be counted on in future development for GZDoom.