News | Forum | People | FAQ | Links | Search | Register | Log in
Fitzquake Mark V
I wasn't planning on doing this mini-project, it started as an effort to address some Fitzquake issues, fix them the right way up to Fitzquake standards (i.e. do it right, once and properly versus continual releases) and donate it back.

FitzQuake Mark V Download:

http://quake-1.com/docs/utils/fitzquake_mark_v.zip

Short version: Eliminated most issues in FitzQuake thread, most issues I can even remember hearing of ever and marked every single one clearly with a very minimal implementation.

It may be the case that only metlslime and Quakespasm and engine coders may find this engine upgrade of interest.

Features: 5 button mouse support, single pass video mode, external mdl textures, alpha textures (like RMQ), record demo at any time, rotation support, video capture (bind "capturevideo toggle"), console to clipboard, screenshot to clipboard, entities to clipboard, tool_texturepointer, tool_inspector (change weapons to see different info), clock fix, contrast support, fov does not affect gun, gun displays onscreen, Quakespasm wrong content protection, external ent support, session-to-session history and .. (see readme).
First | Previous | Next | Last
Feature Request 
More stuff ...

* Adding external texture support for model skins (24bit TGA) with use of the alpha channel so that the skin can faded gradually. The external skin could be specified with an extra key on the entity. Like for example "ext_skin" "textures/hiknight1.tga" 
Small Note Regarding Alpha: 
Drawing alpha-blended models correctly requires sorting every alpha object (if convex) or triangle (of a concave object) in the scene and drawing them back to front. I don't know of any engine that does this (perhaps darkplaces.) But fitzquake certainly doesn't.

People probably haven't complained about the cheap method used in fitzquake and other engines, probably because most mappers use the feature sparingly, and only on simple convex brush-models, and not on many models in the same scene so that you see them overlapping incorrectly.

I only mention this because as a perfectionist like me, you will probably notice this problem once you start relying heavily on the feature, on many objects in the same scene, and on objects with convex, organic shapes.

The safest way to use alpha given this, is to only put it on convex shapes and make it hard for the player to have a line of sight that passes through multiple layers of alpha objects. 
Ah Yes 
I remember now...last time I checked darkplaces doesn't handle this within a model - if you have multiple layers of fur in the model you do get graphical glitches occur where they overlap. 
 
even if you do depth-sort, large objects can still cut through and overlap in screenspace even if the actual brushes don't (or for instance a transparent player standing waist-high in water).
mostly a .alpha set to 0.99 will result in the entity using the alpha channel of 32bit replacement textures (blended).

ext_skin with nice long strings would be far too painful. just use .skin if you really need that sort of thing (in combination with shaders as needed). 
Engine Question 
Would a QC controllable sound mixer be a good feature? Adding reverd echo and other dsp stuff. I remember good ol duke3d had a few option with sector effectors. Setting an effect to match a rooms size would be cool. 
 
don't care too much about that, although it would be interesting to use every once in a while.

what I want is moving sound sources and doppler effect! 
Agree! 
 
 
also, while i'm dreaming, sound that travels through leafs/portals would be totally bad ass with volume attenuated by distance traveled instead of just radius. 
@mechtech 
halflife had various triggers that can apply various eax environment settings.
the forwards-thinking audio api to use is presumably openal, which would give environmental effects as well as doppler effects.
but hey, if you want to write your own reverb library and plug it in to a quake engine, be my guest. :P
incidentilly, a couple of engines already have rate modifiers, just not editably so... doppler would theoretically be easy enough to add, but as quake traditionally never moved sounds (and with invisible entities generating sounds and thus there not always being velocity information) I'm not sure how much it would break. 
Sizedown In DirectQ Engine 
Greetings everybody,

a few hours ago I decided to install DirectQ engine for Quake 1 and find it to be brilliant.

The only (MAJOR) problem with it so far is the fact that "sizedown" command won't work.
It's properly binded to "-" but it has no effect.
Writing the command in console does nothing too.

"Sizeup" works just fine.

I run a 1920*1200 resolution on a 24 inches monitor and the fact that I can't "sizedown" the window makes the engine a bit...useless in the end.

Can anyone please aid me on this ?

Thank you in advance for your help. 
 
What does sizedown do? 
 
viewsize cvar. set it to 30 for a tiny view (not always supported nowadays), 100 for default sbar+ibar, 110 for sbar-only, and 120 for not even an sbar.
note that not all engines support a value less than 100. I've no idea what directq is meant to support, but if in doubt specify the viewsize cvar value directly and see what you get. 
Outside Chance ... 
That in the next 3 weeks I'll release a fix-up Mark V final release. I only have effectively one day off a week and not much free time in that one day off, really --- but I worked on Mark V in a 115 different mini-revisions and I know the first one of these with "the issue".

The bad news is I so radically changed the code base that even one "mini-revision" is a heap of changes.

But the good news is that if I spend 30 minutes a day for a week or 2, I should be able to repair it.

If I'm not way too tired to do so each day ... 
Best Way To Get Something Done 
...is to give it to someone who's busy...

<mumble> bsp2 </mumble> 
 
I don't have answers, I only have questions. Sometimes I think that Metslime, MH, Spike, the Quakespasm guys (szo, stevenaus, SleepWalker ... in no particular order) and myself should team up to make "The Answer To Everything Classic Quake Engine 42 = 6 x 7" engine.

Which is a pipe dream --- except I don't actually believe that. Such a thing almost seems like it was always meant to happen ... like it was part of the Universe's master plan and maybe the only the reason the Universe was made from this incredibly narrow and very Quake-centric point of view ...

?

[End Stereotypical Baker post ;-) Hey I gotta be me ... ] 
Diversity Is Good, A Little Competition Is Good 
 
We'll See ... 
Lately I've been spending most spare moments of thought on how to get an update out with virtually no "true" free time.

I'm rather determined to get an update out --- I'm just trying to figure out "the how".

Some of the great stuff in "Final Mark V" is irresistibly fun --- and I'm still quite irritated about the collision bug.

I hope you are doing well, SleepWalkR. Admittedly, my finite time I haven't had much time to read up on your massive contribution to Quake mapping in TrenchBroom. :( 
Fixed Version 
Read me: http://quake-1.com/docs/utils/fitzquake_mark_5.txt

Download: http://quake-1.com/docs/utils/fitzquake_mark_v_final.zip

Weight: 448k (the engine)
Speed: Yes
Features: Some
Code: Better
Map Editor Used: Notepad.exe
Is Bug Free: Should be (cross fingers)
QuakeC Version: Depends on gamedir

Recap of features: Faster, auto-completes about everything including key names, brightness only affects window, skill level recorded in demo, optional multisample capability. Borrowed some of Quakespasm's finesse and tried to largely sync with entirety of Quakespasm's codebase. See read me. External .vis support.

Short version: Light, fast, quick, better.

You won't likely notice any of the changes because they were implemented very softly and subtly, in FitzQuake style.

Last version of Mark V. 
Doesn't Work 
on my surface pro...

Seriously I have no idea what's up with this thing. It only runs DirectQ. 
 
fifth? what's the problem? spazzes out spining wildly?
that happens when the operating system ignores calls to set the mouse cursor position.
you can avoid such calls with a the -dinput argument to most engines (often alternatively settable with in_dinput 1;in_restart).
If your engine supports rawinput, that can also be used instead, fixing the issue in the same way.
In FTE, _windowed_mouse 0 will enable the touchscreen mode that I hacked together for android - other engines that retain that cvar will simply disable the mouse entirely instead.

DirectQ presumably uses dinput by default, hence why its the one that works out of the box - pretty much every other engine can use dinput too, they just don't by default. 
Some Good Advice There Spike 
but it fails to load, just crashes when you click on it. And windows 8 doesn't give any explanation to why it wont load.

I reckon it's probably driver related to be honest. As per usual. 
 
I don't claim to have any working knowledge of a Surface Pro, but you could type "nomouse 1" in the console or add that to your config.

On an iPad, I know how it would interpret mouse events and if I had any free time would consider an enhanced merge of FitzQuake Mark V + Quakespasm + iPhone Quake and peek at FTEQW's Android stuff.

I really was trying to complete merge Quakespasm and Mark V back in the spring -- but ran out of time before I could get it ready for a Mac OS X build. :(

/End Dreams ... 
On The Plus Side ... 
I was glad I was able to use a sizable chunk of the ideas that Spike and MH suggested to streamline the code. And something invaluable that Reckless provided.

Spike supplied a treasure trove of great info --- and many of these things are implemented like skill level and gamedir is recorded to demo (as one example) --- but he gave me tips on how to do some really awesome stuff.

Alas. I ran out of time. 
fitzquake 085
heapsize 512000
game quoth
map dis_sp6
die alot

fitzquake mark5 final
heapsize 512000
game quoth
map dis_sp6
hunc alloc failure 
Gosh Darn It 
I had the idea of disappearing forever with the earlier post being the last trace of "Baker" ever on any noticeable forum.

And distrans, you ruined it all!

Thanks for the bug report, I suppose I have only myself to blame.

/Will investigate, solve and all that. Rats!@!@!@ 
First | Previous | Next | Last
This thread has been closed by a moderator.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.