Engine X 5.50 Beta

[vegetous]

If you're playing a single player map, you NEED to keep your maxfps at 72, otherwise you WILL get these kind of weird physics bugs.

Physics bugs where hapen @ 72 fps too!

[smokey]

Hey Bakes nice job man....yellow no 5 texture pack i like the dm3 look also...added some ss's for those who have not yet taken a look

as for bugs i was having trouble running on my laptop at full resolution (1366x780) but it runs no problem at 1270x...i could adjust it in game to max resolution with no problem but when i tried to restart the engine i would get the loading error saying to post all bugs to the forum etc.....

we need some nostalgia IHOC or ra matches some time drop in if you see me on the servers!

[woods]

Mac

Eager to try this out right now.. Thanks for the OSX support!

[MH]

Gun kicks and bobs are disabled by default and they won't re-enable. This feels and looks weird if you're used to them; must be an MP thing but it's also a change from default Quake behaviour.

The gun model looks all wrong - is it being drawn at a higher FOV than the rest of the scene? Whatever, it looks too skinny and seems to curve inwards towards the tip. Do a side-by-side with WinQuake and check.

Brush models rotate in the wrong direction.



I'm not too sure that I like the hostile takeover caused by it's own gamedir and content pack, nor the fact that it won't run without the pack. The above screenshot went to the "enginex" gamedir - presume that's a bug and not intentional?

[Baker]

Can this run the Expansion packs?

Can I use this for SP?

Can I play Quake 1 again till my eyeballs fall out of their sockets?

I wouldn't make a niche engine. I like single player, multiplayer and everything in-between.

Some people argue that Quake is [someone says some niche], but Quake was revolutionary because of its depth.

[Baker]

Shouldn't you normalize this, so jumping is not dependent on the frames-per-second one can achieve with their setup?

I have more to do here. MH has done FPS independence work recently and I have studied some of this. LordHavoc has FPS independence in DarkPlaces. QW clients must have FPS independence in single player.

In order to implement FPS independence, I have to do some tests.

Spike alluded to problems with super high FPS and Quake and I need to address this for a few different reasons.

My *ONLY* goal for super-high FPS was smoothness on any hardware. I don't inherently think super-high FPS has any sort of advantage. No one has any use for 1000 (or 5000 fps).

But this also means the engine won't stress out on lower end hardware and can guarantee smoothness.

[Baker]

How do I "install" it on Mac OS X? I put it in my quake folder and ran it and nothing happens, just the icon hops up and down on the dock. When I click it, it disappears. I'm running OS X 10.7.3

I made the OS X zip archive on a Windows machine. I'll check this out, I've been out-of-town for 3 days.

[Baker]

The gun model looks all wrong - is it being drawn at a higher FOV than the rest of the scene? Whatever, it looks too skinny and seems to curve inwards towards the tip. Do a side-by-side with WinQuake and check.

viewmodel_fovscale controls the weapon rendering. I have it default to an FOV of 110.

I'm not too sure that I like the hostile takeover caused by it's own gamedir and content pack, nor the fact that it won't run without the pack. The above screenshot went to the "enginex" gamedir - presume that's a bug and not intentional?

Yes. Considering Engine X labels screenshots very throughly, I though having a single place to put them would be appropriate.

Type: "folder shots" in the console. It opens the screen shots folder.

Note for MH: Engine X will eventually not require those packs at all.

[Baker]

Using Wine:

Starting up I chose OpenGL, saw some checkerboard pulsating, then I got the console. Entering "timedemo demo1" told me it was running it but it stood at the console. I started a "new game", then I could timedemo just fine.

I don't know too much about WINE emulation on Linux.

I do use it on OS X for Windows-only stuff I don't want to live without (WinMerge, TextPad are things I am used to) but I don't use it for games on OS X.

I know you don't like replacement textures, but you might find these Engine X features interesting:

1. It will not use replacement textures in a gamedir mod. This is due to absorbing Quakespasm's replacement content prioritization structure where the search path is explicitly limited to the realm of where the content exists. So, for example, it shouldn't use a .lit file for Travail start.bsp.

2. Replacement content follows FuhQuake EXMY rules. If a map isn't (E1M1 through E4M8 ), replacement content will not be used.

3. Engine X does not need "vised Quake maps". It uses external .vis and the these are supplied with the engine. All original Quake maps are vised via external vis.

4. I hate how fog varies from engine to engine. Engine X follows the FitzQuake fog standard.

5. Engine X already supports both a ProQuake (GLQuake) and FitzQuake rendering mode. What I need to do is make this convenient to swap between.

Right now, due to the sheer number of changes --- and I'm not sure of the exact number of features added but I wouldn't be surprised if were something like 75-120 features --- what I most need to do is polish up to more conveniently control them to keep the user interface simple.

For instance: I forget features. I forgot to mention it supports powerup shells; it kind of gives me a headache to try to recall everything I added. But everything I added was done carefully and precisely. So right now, this is polish stage before I release far more changes.

[Syluxguy28O3]

found bug i think

when i change the music volume, then exit, then re-launch, music is back at default setting.

[golden_boy]

Congrats Baker.

I must say the weird replacement stuff is scaring me a little, I like using *my own* replacements.

Since it is OpenGL, I hope it will eventually be ported to Linux... until then, I sadly have to file it under "don't bother".

A surprising number of Quake community members use Linux; we have multiple Linux users on the RMQ team for example. You wouldn't believe it.

Some people argue that Quake is [someone says some niche], but Quake was revolutionary because of its depth.

Fanboyism is all well and good, but... man. Have you played any other games recently?

Kill monsters (which have barely enough AI to walk in the player's direction), find exit... depth?

[Baker]

Congrats Baker.

I must say the weird replacement stuff is scaring me a little, I like using *my own* replacements.

Since it is OpenGL, I hope it will eventually be ported to Linux... until then, I sadly have to file it under "don't bother".

A surprising number of Quake community members use Linux; we have multiple Linux users on the RMQ team for example. You wouldn't believe it.



Fanboyism is all well and good, but... man. Have you played any other games recently?

Kill monsters (which have barely enough AI to walk in the player's direction), find exit... depth?

Actually, I quite specifically have no intention of pleasing everyone

There are all kinds of tastes, interests and preferences out there. There are plenty of other Quake engines for those who have differing views on what makes an engine great. I do have an appreciation for more conservative engines, but there are plenty of those.

Engine X will be tuned to the mainstream. The target base is new players when I get the rest of the framework in place.

Ultra-conversatives will like this engine less and less as time goes on , but the engine will be remarkably modern and easy to use.

The short version goes like this: This ain't a Func_Msgboard engine

[LordKane]

I wouldn't make a niche engine. I like single player, multiplayer and everything in-between.

Some people argue that Quake is [someone says some niche], but Quake was revolutionary because of its depth.

Quake defined my formative years so yeah I say it has a appreciable depth for its day, and thank you for remembering those of us that from time to time, like to slap shub-niggurath around from time to time.

[Mindf!3ldzX]

No one has any use for 1000 (or 5000 fps).

I do, everytime I play quake I'm using cl_maxfps 1001 and getting between 1500/3000 fps fluxuating.. It's all in the 1 !
Thats if im using vid_maxframelatency 0. When its at 3 its 3000/4000 fluxuating. framelatency 5 = 4000/5000 fps fluxuating.

Whoever said more is better was right.

[MH]

Raw performance with id1 content isn't that important. Benchmarks in dm3 are quite meaningless once you get above 1000fps. What is important is that these are a consequence of the primary goal, rather than being the primary goal itself. That goal is to get a good framerate with heavier content in more complex maps. If I can show the Marcher Fortress running at 800 fps or ne_tower running at 600 fps on mid-range target hardware, then it means that someone who likes to play with a maxfps of 250 should be able to hit that 250 fps on lower-end hardware, or with external textures, detail settings cranked up, etc.

A consequence of that is that you may be able to hit 5 billion fps in dm3, but don't think that being able to hit 5 billion fps in dm3 is the primary objective of any performance tuning, because it's not. On the other hand, some performance tuning for larger maps may result in a framerate drop with id1 maps - if so, so be it. Getting a good game in larger maps is the goal worth shooting for.