Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Altazimuth

Eternity Engine 4.02.00 Forseti

Recommended Posts

Posted (edited)

As a quick answer Eternity may already have what you're looking for; if you want complevel 2, 3 and 4, use the -vanilla launch parameter (which one is used is context sensitive; -vanilla with TNT or Plutonia is the equivalent of complevel 4, for example).

 

But why just that and not a full complevel function? Complevel isn't something you simply add, the compatibility levels have specific meanings and implications for demo compatibility. Eternity can't guarantee demo compat for most of them given it cannot guarantee Boom demo compatibility, nor pre v1.9 compatibility. There's also situations where it outright wouldn't work at all. For example, you can't have a vanilla or boom demo with a map that has portals, the relevant compatibility would be immediately switched.

 

So as it stands it can't currently provide the same parameter in a way that makes sense.

 

 

Edited by Edward850

Share this post


Link to post

 

Finally it's all clear to me,thanks for the detailed answer.

Share this post


Link to post
Posted (edited)

Since compatibility levels can be enabled to play Boom and MBF demos, maybe they can also be enabled to record them (on future development). There are still a few more challenges to it, because unlike vanilla Doom, both Boom and MBF are highly configurable. For recording such demos, you shouldn't just change the complevel, but also prepare the desired gameplay options before starting the game.

Share this post


Link to post

Would it be possible to implement presets in the options, which automatically flip the various flags to reflect vanilla/boom/default Eternity etc? Similar to how GZDoom options do it. From past experience, launching with a -vanilla parameter resets to default if you pistol start the next map, and it's hard to tell which flags need to be flipped on or off for Boom wads.

Share this post


Link to post
Posted (edited)

-vanilla is a special issue in that it indeed does not persist throughout the game like other options, such as -respawn, -fast or even the cheats (thanks to Boom). It's something I'd like to see fixed at some point. Funnily enough, it is saved in savegames, but not kept when starting a new game or warping.

 

Having presets is something highly demanded, yeah. There are a few Boom and MBF settings which are highly mod dependent (all those sector motion and monster behaviour settings), so I expect there to be multiple levels even per port. Technically, on development's side, it's kinda tricky to implement this, hence why they're still not here.

Share this post


Link to post

Having -vanilla stick between launches is a bad idea IMO, but having actual proper compat presets is a good idea.

Share this post


Link to post
6 hours ago, Altazimuth said:

Having -vanilla stick between launches is a bad idea IMO, but having actual proper compat presets is a good idea.

It's more about how it doesn't persist when warping or restarting a map. Say I launch Scythe with -vanilla and finish map01. I want to pistol start map02, so I type idclev02 but now the -vanilla parameter is gone and the game is running the default preset. Having to quit out after each map and modify a .bat file is rather inconvenient when casually pistol starting vanilla wads.

Share this post


Link to post
11 hours ago, Altazimuth said:

Having -vanilla stick between launches is a bad idea IMO, but having actual proper compat presets is a good idea.

The closest analogy is the complevel setting in PrBoom, which persists until you quit.

Share this post


Link to post

I'd honestly just really like a "default compatibility" setting in one of the menus similar to ZDoom and PRBoom+'s

Share this post


Link to post
Posted (edited)

Thank you for providing the Mac build and compiling for Apple Silicon! Heartland runs great on my Mac Mini 2020 so far.

 

Edit: Just saw that just the launcher is compiled for Apple Silicon. Maybe you can do the same for the engine.

Share this post


Link to post

I just got into this great source port on account of Heartland. It's full of cool features too.

Anyway, I just have a question: I set the v_ticker 3 console command when playing, and I'd like to have that on at start-up.
However, I don't know if an autoexec would do the trick and, even if it did, I made a bat file for Heartland, which wouldn't work with that.
I also thought of binding a key to that command but, even though it's apparently sucessful, nothing happens when I press it.

I have this version of Eternity. If you could help me out with this minor issue, I'd really appreciate it.

Share this post


Link to post

If you make a "default.gfs" in base/doom2 and then have it contain "cscfile = addticker.csc" then have "addticker.csc" in the same folder and put "v_ticker 3" in that file it should work, I think. This only works if you do "-game doom2" on the command line though.

Alternatively I think that you can set cscript_1 in eternity.cfg in base/doom and put the "v_ticker 3" in there.

Edited by Altazimuth

Share this post


Link to post
8 hours ago, Altazimuth said:

Alternatively I think that you can set cscript_1 in eternity.cfg in base/doom and put the "v_ticker 3" in there.

I tried that solution first, but it didn't work.

Now I'm trying the first, and I've made the addticker.csc file with v_ticker 3 inside, but I have no idea how to create a .gfs one.
If it's not too much of a pain, would you mind sending me an empty file with that extension? Then I'll write your instructions there and test it out.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×