[HulkNukem]

Snapmap stream will go live on the 25th
Singleplayer Campaign stream will go live on the 27th
https://bethesda.net.../2016/04/20/107

I'm really glad the Snapmap stream is first, I plan to ignore everything Doom related starting the 27th; It's only just over two weeks of waiting and I want to go in as fresh as possible.

[PikaCommando]

Daikatana 2 confirmed?

[leilei]

[xMobilemux]

Looks interesting.

[PsychoGoatee]

SnapMap looks fun to play with. I love that Romero video too, look forward to seeing what he's cooking up.

[Mr. Tibbs]

Courtesy of RPGCODEX

[Kristian Joensen]

So COD: Black Ops 3 has mod tools in a closed alpha right now, might we really end up in a situation where the latest COD is more mod friendly than the latest Doom?

[PikaCommando]

Behind the scenes on the Fight Like Hell trailer:

[PsychoGoatee]

Mr. Tibbs, on 20 April 2016 - 10:05 PM, said:

Courtesy of RPGCODEX

I want the record to show I accidentally upvoted that when I went to quote it. I liked the beta and am excited for the campaign. I get that you don't like it, but to me finding glee in other people also not liking it or making fun of people with a different view is very pointless.

[leilei]

Yes i've enjoyed the Doom MP open beta very much. Fluid smooth fps, fast action, and controller friendly consolidation of Q4 in a familiar CoDistilled format. bite me doomdorks

(except for its final night when the aimbotters have gotten foothold on most matches. snapping laser sights everywhere. vac's needed for the final for sure.)

[Mr. Tibbs]

PsychoGoatee, on 21 April 2016 - 12:05 PM, said:

I want the record to show I accidentally upvoted that when I went to quote it. I liked the beta and am excited for the campaign. I get that you don't like it, but to me finding glee in other people also not liking it or making fun of people with a different view is very pointless.

Where have I made fun of people liking it? I don't need to moderate my opinions towards any video game anymore than you do, PsychoGoatee. The stakes aren't that high. My thoughts on Doom shouldn't effect your opinion/play experience one iota. There are plenty of other boards that only allow positive discussion. Being able to have a laugh and joke about why Doom looks lame is something that makes boards like Duke4 special.

[PsychoGoatee]

Mr. Tibbs, on 21 April 2016 - 01:37 PM, said:

Where have I made fun of people liking it? I don't need to moderate my opinions towards any video game anymore than you do, PsychoGoatee. The stakes aren't that high. My thoughts on Doom shouldn't effect your opinion/play experience one iota. There are plenty of other boards that only allow positive discussion. Being able to have a laugh and joke about why Doom looks lame is something that makes boards like Duke4 special.

This doesn't have much to do with what I posted? I never said you shouldn't post, not sure where moderating comes in, unless you just don't like me being critical of your posts?

You post a comic where people who think the game looks good are considered foolish, using shit as the illustration , nobody said the "stakes are high", I just posted my opinion on that. Where did I say your post would effect my experience playing the game? Your reply genuinely does not communicate with what I'm saying.

[Mr. Tibbs]

The comic pokes fun at Bethesda (hint: the t-shirt), while making light of how people aren't meant to be critical even when something is clearly shit (hint: the stuff coming out of his butt).

[PsychoGoatee]

Mr. Tibbs, on 21 April 2016 - 02:46 PM, said:

The comic pokes fun at Bethesda (hint: the t-shirt), while making light of how people aren't meant to be critical even when something is clearly shit (hint: the stuff coming out of his butt).

It's not clearly shit though, from my perspective.

[Mr. Tibbs]

PsychoGoatee, on 21 April 2016 - 02:53 PM, said:

It's not clearly shit though, from my perspective.

Yeah, but you're still missing the point. For the little cartoon guy, Doom is shit. The Bethesda dude is shitting on a plate (cute). It's a joke for people who think it's not going to be a good game. Sorry that it's not all-inclusive, but I never posited the cartoon as the single-definitive perspective on Doom (2016).

[Micky C]

The wording is actually pretty clever.

[PsychoGoatee]

I've heard that shit cliche about games coming out before. We're all basing our opinions off of the same info, some are positive some are negative. Some like the beta, some don't. Some people will like the comic you posted, some don't. You keep making these odd replies with strange qualifiers. "Sorry it's not all-inclusive" etc. You just genuinely seem like you're miffed that somebody is disagreeing with you or something. Because I'm disagreeing with you on something I apparently want everything to be all-inclusive? I wonder what thing you'll put in my mouth next, hopefully it's some Burger King or something.

[Micky C]

PsychoGoatee, on 21 April 2016 - 03:39 PM, said:

I've heard that shit cliche about games coming out before. We're all basing our opinions off of the same info, some are positive some are negative. Some like the beta, some don't. Some people will like the comic you posted, some don't. You keep making these odd replies with strange qualifiers. "Sorry it's not all-inclusive" etc. You just genuinely seem like you're miffed that somebody is disagreeing with you or something. Because I'm disagreeing with you on something I apparently want everything to be all-inclusive? I wonder what thing you'll put in my mouth next, hopefully it's some Burger King or something.

On one hand those are valid points. On the other hand... it's a joke comic.

Personally I haven't played the beta, but reading the facts I can see some odd choices and tell it wouldn't be my cup of tea. It's safe to assume that a fair proportion of people don't like the beta either. It's probably nowhere near as bad as the steam reviews suggest, but still a sizable proportion.

The singleplayer appears to be the main focus of the game for a change considering that it's done by ID with other components like the multiplayer being outsourced. And we have too little information on the singleplayer campaign to make any speculation. Although it's interesting that considering that the singleplayer is meant to be a main focus of the game, why they're focusing so much energy on advertising the multiplayer almost exclusively.

[Mr. Tibbs]

The it's "not all-inclusive" comment was meaning that the joke only presented a negative perspective, which seemed to rile you up. Are you upset that I don't redundantly qualify every one of my posts with "IMO"?

[PsychoGoatee]

We did have some gameplay from e3 last year etc so we have some stuff to go on for speculation, though granted the bulk of the campaign is a mystery. We'll see some more on April 27th.

And Tibbs, I'm not upset. I think we're just not seeing eye to eye on this interaction, hopefully we do better next time.

[Lunick]

E2M7: The Madhouse fromThe Beginning Of The End (part 1)

[Malgon]

Advanced Doom settings as taken from the Bethesda site:

Quote

Our current expected PC advanced settings include:

Manually Lock Framerate (un-locked by default)
Lights Quality
Chromatic Aberration Toggle
Shading Quality
Post Process Quality
Particles Quality
Game F/X Quality
Decal Quality
Directional Occlusion
Reflections Quality
Depth of Field Toggle
Decal / Texture Filtering
Motion Blur Quality / Toggle
Sharpening Amount
Lens Flare Toggle
Lens Dirt Toggle
Texture Atlas Size
Show Performance Metrics
Resolution Scaling
UI Opacity
Film Grain
Rendering Mode
FOV Slider
Simple Reticle
Show First-person Hands Toggle
Use Compute Shaders
Vsync (support or triple buffering)

[leilei]

Most of the "uncap framerate please" requests i've seen are more for hoping for Q3A physic exploits (i.e. like jumping higher/farther at 333fps) than smooth input or hitting 120hz monitors


There's no texture detail setting to flatten the maps or turning off the shadows. Cue the entitled "competitive pro gamer" whining and repeat Quake4's cycle once more

[deuxsonic]

Remember how they got DOOM 3 to work on a Voodoo 2? I think I may need something like that with this as my computer is rather modest.

[Striker]

leilei, on 22 April 2016 - 05:29 PM, said:

Most of the "uncap framerate please" requests i've seen are more for hoping for Q3A physic exploits (i.e. like jumping higher/farther at 333fps) than smooth input or hitting 120hz monitors


There's no texture detail setting to flatten the maps or turning off the shadows. Cue the entitled "competitive pro gamer" whining and repeat Quake4's cycle once more

As much as I like the Quake games, the Quake competitive scene is an absolute cringe-worthy joke. I've gone on rant after rant about it.

I used to rant about how if I made a game that was bare, textureless, full of bugs and exploits, had generic icons for weapons, had players that were merely neon-green cuboids, the FOV defaulted to "fisheye-mcfuckface", and all sounds were just obnoxiously loud but distinct beeps, and the game called you a fag every time you die, and every time you killed someone else, you'll get auto chat flood of "LAAAAGGGGGGGG SHIT SERVER"/other overall bitching and whining, they'd suck that shit right up.

I miss playing Quake 2 on MSN Gaming Zone, where there'd be servers that locked the CVars to reasonable values. People got better not by exploiting the engine, but by learning better strategies and sharpening their senses. The players were a lot more friendly, especially friendlier than the later Quake 3 and Quake Live crowds.

[deuxsonic]

Just set requirements at all the competitons that a certain graphics profile has to be used. If you need bugs from disabling things in the game that were never intended to be turned off, you're a cheater. It was really really bad with Quake 3, rendering surfaces as solid color, disabling nearly all of the brushwork, using 2D sprites for pickups, and so on. A lot of those graphics cvars should have been locked by default when creating servers to stop this insanity. The framerate jumping bug was probably the biggest. I remember an attempt was made to mitigate the bug allowing near infinite gains in movement speed which people quickly found a way around. If they had been persistant about cracking down on this stuff they could have nipped it in the bud. The game is capped at 80 FPS by default but people make up BS about how they need 1000 FPS or their controls aren't responsive enough.

[Micky C]

Why are all these bugs associated with high framerates?

[PokeThePower]

Micky C, on 23 April 2016 - 02:33 AM, said:

Why are all these bugs associated with high framerates?

Some engines lock their game world updates to a specific framerate regardless of how fast the rendering updates are happening. This gets rid of those sort of exploits, but has a negative effect for people with lower rendering framerates than the locked game world updates... creating a kind of slow down result on screen that feels very very laggy. Worse than what the actual rendering framerate is. Most games that do that are built to run at a minimum framerate (usually 60, but 30 is fine too... just more likely to trigger the sluggish behavior).

Some games with fixed game world steps/ticks/updates handle the rendering framerate being slower than the game world framerate by just doing one game world update per frame (sluggish on screen results because you only get 0.5 seconds of gameplay updates for every 1-2 seconds of visual update). Or they try to cram an extra game world update in during the slow rendering update (2 game world updates per 1 rendering update) which can start to cause a feedback loop driving framerate down even more, or it causes the player to never see certain actions that happen on the non-rendered update (such as a rocket muzzle flash... causing the rocket to seem to appear out of nowhere). Some engines do a combination depending on the system in question, but then you can start to get things like your particle effects being out of sync with your audio cues as an example.

Other engines don't lock the game world updates to specific "step sizes" and it creates a non-intuitive effect at first but is the source of some high framerate exploits. When talking about things like cannonball behavior (jumping)... those sort of games build the feel of the jump around a limitation in how the math is being processed for what is considered a "normal" jump.

Say you want the player to jump up with a velocity of 100 units per second and want them to land about 1 second after starting. Depending on your framerate, the jump can get very different results. As an extreme example... say you are only running at 3 frames per second... the first frame you start at 100 units per second. By the second frame you detect that they should be 2/3rds of the way through their move... thus they should already be back in the "downward" part of the jump. To the player this results in a very stunted feeling jump where they moved up really fast and then are snapping back to the ground really fast. The opposite can happen too if you process the math a certain way... in high framerate jumps you get snapped back to the ground and low framerate results in floaty jumps.

Games that don't have a fixed game step wind up building their game around the results of the "target" framerate.... but that's still depending on a limited number of steps. Add more steps and your detection of when the energy of the jump has expired and gravity starts to take over changes... as well as how much acceleration gravity is applying per update. So the gravity/jump values will have been tuned to pull the player back to the ground at a certain "feel" when you only have 10-30 updates... but that can cause floaty higher jumps in excessively high framerates if they are doing psuedo physics aimed at a gameplay feel and nothing to do with "real" physics. Things like maintaining an upward impulse for X time after the player has hit the jump key to make you feel more super human.

There are ways around that, but they typically resort to a variation of the fixed step behavior described above... just isolated to a specific behavior.

[Jblade]

Quote

Some engines lock their game world updates to a specific framerate regardless of how fast the rendering updates are happening. This gets rid of those sort of exploits, but has a negative effect for people with lower rendering framerates than the locked game world updates... creating a kind of slow down result on screen that feels very very laggy. Worse than what the actual rendering framerate is. Most games that do that are built to run at a minimum framerate (usually 60, but 30 is fine too... just more likely to trigger the sluggish behavior).

Ah cool, I suspected as much - I've noticed this tends to happen with console ports (for obvious reasons) most notably for me was in Dark corners of the Earth where certain things seemed to be tied to framerate (like movement speed) and other things weren't (like the timer on the last level before it blew up and killed you) I remember having to bump my resolution right to rock bottom so the game would run at a normal speed instead of the slow syrup one so I could actually move fast enough to beat the game.

[deuxsonic]

What I do for games that aren't already capped is to cap the framerate for them at 60, which is smooth gameplay and prevents the bugs that some games present at abnormally high framerates from appearing. Particularly with older games that act strangely on current hardware (with Unreal, the movement speed is all over the place uncapped) this is basically a necessity. The first Halo, for example, is designed to run at 30 FPS and if the framerate goes higher than that, the animations are messed up.