Quasar

I believe that the "blue" disciples are the result of the "screenshot" being taken with a camera off a CRT and then possibly further enhanced through the CYMK printing process by being blue enough to get printed as blue instead of black. The general color of these screenshots is very "off" as such in a way that is similar to other camera-pointing-at-a-CRT shots of that time period.

Given Morey Goldstein passed away many years ago, I really doubt there's anything left of his work processes or belongings, and the process of looking for them would require disturbing his next-of-kin. Some stones are better left unturned.

The reason those are there is to support playing the games on the Slayer's computer in the Fortress of Doom, for the curious and not-already-knowing.

This. Also, they only had ONE guy doing the mapping on this game. Everybody else was already working on Doom 64 at the time.

Uses an (at the time it was implemented at least) allegedly faster way of uploading a texture to video memory.

This is intentional, on account of the fact you'd otherwise be able to make a map that just gives you pretty much every achievement for free, and you're really not supposed to let users do that on most platforms. Besides the fact it'd be lame, especially if you didn't mean to get the achievements that way as a user.

Now you know why Sandy's not treated as a reliable source for the wiki unless what he's talking about is backed up by others or pre-existing accounts. A couple years ago he kind of just started making stuff up, to put it nicely, to fill in what I presume must be memory gaps. Whatever the reasoning, it's led to a number of weird gaffes and misinformation like the stuff above.

Unfortunately a very real possibility. Though for clarity the shredding I'm referring to starts at 1:34 in Silent Scream. The other part of a Doom song I'm hearing in it is at 10 seconds but now I'm remembering that's probably un18.mid and not any of the others.

I really suspect that No Remorse was still an influence on it. However the rhythm does unambiguously occur in Master of Puppets as well. It's possible he did a blend on the songs, and maybe that's why he doesn't seem to remember which one he based it on. @Gez Your listing of the os2.wad file claims two different songs are listed for E2M1; is this correct? The only part of Silent Scream that sounds remotely like E2M1 to me are the various shreds in the last third of the song. The rest of E2M1 is unambiguously Big Gun, but Big Gun does not contain any running shreds even remotely like the ones in E2M1 so it's interesting - it may be a mix of ideas. However that being said this also confirms Silent Scream was an influence and I hear other parts of Doom songs in it and I'm terrible at matching that kind of thing from memory so it'd be good for somebody to figure that out and get it on the wiki.

I already had it from earlier research for the wiki but I never thought to look into the MIDI files because I assumed they'd be knock-off MUS2MIDI back-conversions done in a haste by the ONE guy they had working on that port. But nope, this is legit.

Heretic II. Cool game. Shame the source was never released, though, because it is rapidly accumulating problems when running on modern systems. To spare anybody else interested in it from searching the web in vain for hours trying to find a solution to one of them, I will document it here. If you start up the program in OpenGL mode on pretty much anything newer than a Voodoo or a Rage Pro, it will crash. The crash is a common idTech 2 issue and results from Carmack's incessant use of sprintf() on fixed-size buffers - it tries to read in the OpenGL extensions string at startup just to show it to the user, but on modern cards this string is way longer than they anticipated. To fix this, open ref_gl.dll in a hex editor of your choice and find the string "GL_EXTENSIONS: %s". Change the %s to "xx" or any two other characters not including a %. This will disable sprintf from accessing the too-large string passed to it. Unfortunately the music also won't loop in Windows 7, which is a ANOTHER bug in the MCI API on that platform. I don't have a solution for this one yet.

The branding change was a real punch in the gut back in the day. They changed everything to a rainbow playschool logo at practically the last minute with a cop-out excuse of something about trademarks in Japan, as if there wasn't opportunity to have that sorted long before anything was ever announced to begin with. That together with the weird controller, the constant delays in the release schedule, and third parties nervous about the system led to me buying a PlayStation first when I got wowed by it on display at Wal-Mart, whereas I had originally intended to skip out on that and just go for the Ultra 64 when it came out (or Project Reality as we also knew it). I wasn't sold til I got to play Mario 64 first-hand.

Not around here it wouldn't be. There were protests outside theaters here when The Golden Compass was released. Deep in wacko fundie land.

As far as technicals go, probably. I'd imagine there shouldn't be a problem getting the app transferred back to Nightdive with everything being under the same ownership anyways.

The usual disclaimers: Stuff below is either based on public knowledge (ie. even just read the Atari wikipedia article) or is based on my opinions/personal understandings of the situation. The most important thing to note is that the Atari company has dramatically shifted direction since around this time last year. The crypto stuff is either already discontinued or is on the way out and was separated into a different division than any of the games stuff a while back. The guy who was previously CEO and was in charge of that stuff is no longer part of the organization at all. Controversial projects like the VCS and the speaker hats pre-dated the current leadership or originated before it was in full effect. The hotels were already shut down a while back. The guy at Atari leading this acquisition was previously the main investor in Nightdive. So from his POV he's expecting the company to continue doing what it has been doing, just with more resources at hand. Part of the buyout deal is even predicated on this continuing. The main reason for this was that growing the company any further with only Stephen's resources was becoming too difficult and it turns out that you can't throw enough people at the number of games waiting to get remastered right now. There will not be any restrictions on what gets worked on, other than who in terms of game companies is willing to work with Nightdive, as always. The obvious hope is that having a publicly traded company behind the brand opens some doors that weren't previously budging. In the short term, literally nothing should change. Long-term is as always "who knows" when it comes to business. Anything could have happened to NDS without a buyout; tomorrow is never guaranteed. If anything, this should make at least the next 5-ish years more of a lock-in.

r+ is read/write.

TBH with a game like that I'd probably just start from scratch with the game logic. Trying to reverse engineer it leads to you finding out that its main loop is a sort of interpreter that jumps through indexed tables of function pointers - several layers deep in some cases. I worked on a game very similar to this called Noctropolis. Even though it was written in x86 assembly, all of the game loop was driven by a custom compiled scripting language they called "Room Assembler". Fortunately I was given fully commented source code for that game, because if it had to have been reverse engineered, I'd have been lost the same way in a huge table of function pointers with no obvious control flow to help figure out what any of them were for.

There are more Doom3 ports than that. I recommend CstDoom3 personally, it has a ton of gameplay customization options. Doesn't support mods with their own DLLs though sadly.

Yeah I did miss the "2" part. Makes more sense now.

Hopefully not distracting too much from the topic but, the GBA version is based entirely on Jaguar Doom. I've done a partial reverse engineering of it in the past and there's no evidence it used code from anywhere else, certainly not from any public source ports. They may have gotten ideas from such but there's no way to know that for sure, especially with features that are simple and almost obvious to anybody working on the game.

Not actually, pictures of this level occurred in several magazine articles, including Nintendo Power and some others. However it was not easy to recognize as different areas are shown off in the video than the screenshots were taken from; however, just enough common landmarks do appear to confirm it was the same map.

It would need to be fully reverse engineered to figure out what addresses it's trying to load everything from, and what format(s) it should be in (I suspect it uses either the Jaguar formats, or PSX ones - it definitely has some of the PSX Doom code ported over in it, as it makes reference to some features from that version, but not all of them - it's not seemingly "PSX Doom but on N64" in other words).

Incorrect from a technical POV. Various versions of the game have had problems with this case but it was because they were doing it wrong, not because there isn't a way it can be handled properly.

Not totally sure, it's just what I've heard. Correct me if I'm wrong of course. What happened with Aureal was indeed sad.

Creative spent more time patent trolling and extinguishing their competition through buy-outs than innovating, in the end. Definitely an early entrant into vulture capitalism in the software market. Their ultimate coup was getting Microsoft to remove all the support for 3D audio out of DirectX starting with Windows Vista, leaving only their own drivers supporting it and making a shitton of games' audio engines no longer capable of using the features.