Eternity v3.35.90

Awesome. :)

:O :O :O :O
OMFG!

Happy days.
Essel, you fail at BB code linkage.

So long as we know which bit to copy'n'paste - who cares. Downloading. . . .

Oddly enough, the links seem to work fine in the actual news article itself.

http://www.doomworld.com/php/oldnews.php?time=1231737094

Nuxius said:

Oddly enough, the links seem to work fine in the actual news article itself.

http://www.doomworld.com/php/oldnews.php?time=1231737094

No, they all lead to doomworld.com.

Also :o downloading

MasterOFDeath said:

No, they all lead to doomworld.com.

And so they do.

Nevermind then.

Awesome! I'm happy to see there is a new official release.

By the way, does anyone know how to start up EE in Doom Compatibility mode for demo recording and such. Like PrBoom complevel 7.

YAY EE!

kristus said:

:O :O :O :O
OMFG!

Happy days.
Essel, you fail at BB code linkage.

It works with quotes when it's actually a forum post, but not when it's a news article :[

There should be no quotes. Looking at it on there it either adds them on it's own accord or you added double.

I only had single quotes, which appeared correctly and worked as links in the original post. Somehow double quotes got added.

The best part about the new software renderer is how balls-on accurate it is.

HackNeyed said:
By the way, does anyone know how to start up EE in Doom Compatibility mode for demo recording and such. Like PrBoom complevel 7.

No, it uses the MBF method, where each difference is a compatibility setting. As you may know these are also present in PrBoom, give and take some. They're a pain in the ass to keep track of and not worth messing with generally, but might occasionally be of use with some WAD made under odd settings. If you want to record demos with standardized behaviors (Doom or Boom) you're better off using PrBoom/+ or any of the engines they emulate.

I hear such a setting will be added, though. For demo recording purposes, my suggestion is to still record it into the usual Eternity demo version as a setting it takes, and not with an original version mark (1.9, Boom, &c) unless the engine is trying to be 100% compatible the way Chocolate Doom does Doom or PrBoom 2.02 does Boom.

myk said:

If you want to record demos with standardized behaviors (Doom or Boom) you're better off using PrBoom/+ or any of the engines they emulate.

Understood, that was merely an example. Using the TNTCOMP will put EE into, well, MBF-ish Doom Compatibility mode allowing broken Doom levels to play properly. In Pr/Boom 2.02 there is an option in the config though no command line switch. I have a PrBoom 2.02 set for Boom and another set for Doom and use command line complevels for PrBoom-Plus.

I like to stick with an engine for a while and just want some ease of use and consistency while I run EE through the fun grinder. As I stated in some other topic I feel Boom's Doom Compatibility is a little tougher, different random damage, whatever, then true Doom and Doom/Complevels.

I would like to possibly transition EE toward having a PrBoom-like compatibility-level system in the future. The problem is establishing a matrix of variable settings for every pertinent demo version, and that is no small undertaking at all.

Yes! Best news ever. BTW: Does it have fully working linked portals?

No. The clipping code remains unfinished.

Hooray! I can finish Lost Episode now! :D

*ahem* -- I mean, congrats on the new release! Good to see Eternity is not dead still kicking ass. ;P

No documentation? :|

printz said:

No documentation? :|

There's too much stuff for Quasar to write. We have an EE wiki now. it's not finished (or really started) but we hope EE users will help build it.

Yeah, the outdatedness of the docs was actually one of the major things that held up this release so long. After a while Quasar decided it would be better to just release the update without them instead of holding it off indefinitely.

Then how do I figure out the new EDF, small etc. features present in the new version? :) Unless they appear in the wiki in due time...

The doc update for 3.35.90 was begun but not finished, and as such the docs which can be found in the SVN repo are incomplete. If I can get them done, a 3.35.90-docs package will be released later. If not, then we need to think about alternative ways to accomplish this stuff.

In the meanwhile, please feel free to ask questions about any of the new features and I will explain them in-depth. It's a far less than ideal situation, but I just couldn't use the documentation problem to justify delaying the release any further.

The EE instruction manual:

Hallelujah! I think EE is becoming one of my favorite Doom sourceports these days.

Mechadon said:

Hallelujah! I think EE is becoming one of my favorite Doom sourceports these days.

It already is mine. :O

Wondering if Always Run is hidden in the settings somewhere, as I couldn't find it.

udderdude said:

Wondering if Always Run is hidden in the settings somewhere, as I couldn't find it.

Just hit CAPSLOCK to toggle on. I wish though when Always Run were on that holding Run would make you walk and releasing Run would make you run again.

HackNeyed said:

Just hit CAPSLOCK to toggle on.

tHAT WAY WHEN YOU LEAVE THE GAME TO BROWSE SOME FORUM< CAPSLOCK IS STILL ON AND YOU ARE PERCEIVED AS BEING RUDE ON THE INTERNET>

Gez said:

tHAT WAY WHEN YOU LEAVE THE GAME TO BROWSE SOME FORUM< CAPSLOCK IS STILL ON AND YOU ARE PERCEIVED AS BEING RUDE ON THE INTERNET>

It's not particularly intuitive, but I discovered a really easy workaround for this a long time ago.

Hit capslock in Eternity to set autorun, alt-tab into any other program and hit capslock again. Now alt-tab back into Eternity and autorun is still enabled, and will still be enabled if you quit it and start it again. Pressing capslock again while in Eternity will turn it off.

It'll probably work in other ports that don't have a specified always-run option, as well.

Well that would depend if the other ports have the same bug ;)

Specifically, Eternity is storing the state of the capslock locally but is not updating this state when it loses/gains focus.