News | Forum | People | FAQ | Links | Search | Register | Log in
Mark V - Release 1.00
http://quakeone.com/markv/

* Nehahra support -- better and deeper link
* Mirror support, "mirror_" textures. video
* Quaddicted install via console (i.e. "install travail")
* Full external texture support DP naming convention
* Enhanced dev tools texturepointer video inspector video
* IPv6 support, enhanced server capabilities
* Enhance co-operative play (excels at this!)
* Software renderer version (WinQuake)
* "Find" information command (ex. type "find sky")

Thanks to the beta testers! NightFright, fifth, spy, gunter, pulsar, johnny law, dwere, qmaster, mfx, icaro, kinn, adib, onetruepurple, railmccoy

And thanks to the other developers who actively provided advice or assistance: Spike (!), mh, ericw, metlslime and the sw guys: mankrip and qbism.

/Mac version is not current yet ...; Linux will happen sometime in 2017
First | Previous | Next | Last
Sky Visible Through Water 
Very nice engine. Just one thing. When you set the water to be opaque like the original, the sky is partly visible through it in the hardware renderer. But not in the software renderer. This seems to be the only noticeable discrepancy between the two, apart from affine mapping not being possible in hardware either. How hard would it be to fix this? 
@sakamoto 
Here is me on E1M2 looking at the sky with opaque water using the hardware renderer. The sky isn't partly visible.

Hardware renderer, opaque water, looking at sky -- none seen

Maybe a screenshot of what you are referring to would help? 
 
I believe he's referring to the same issue some of us have reported before: shadows and the sky are visible through models (and water surfaces it seems) in the DX9 version. (see #1098 #1206 -- mh knows about it: #1109 ).

I jumped in the pool on e2m1 and saw the effect he's describing. 
 
Hello i have problem with Dissolution of Eternity HUD.
https://www.quaddicted.com/forum/viewtopic.php?id=421
"The armour / ammo icons displayed do not match the actual armour or weapon you have equipped."
This person has the same problem,he is using a PSP port,im using a Mark V.Is the problem on my side or Mark V? How do i fix this? 
 
What command line are you using to launch it? 
 
Using -hipnotic the command line? Yes/No?

Probably your problem. Let me know.

@gunter - ok, r_shadows 3 option. Maybe a week later after his post I realized that was likely the issue he was experiencing. 
 
I meant -rogue, not -hipnotic.

:( 
No More Vsync In Mark V WinQuake? 
WinQuake runs with constant stutter but I couldn't find any way to turn on vsync. Can anyone help? 
 
I don't know of any WinQuake that ever vsync since that is a Open GL feature.

That being said, if you really want a WinQuake with vsync ... here is a slightly older beta with vid_vsync 0|1 capability:

http://quakeone.com/markv/builds/1025_mark_v_beta.zip

It is the WinQuake-GL.exe in that .zip that has vid_vsync because it renders the buffer to an texture and then draws it on the screen through Open GL. 
 
Thanks Baker, I found that build last night and it's fantastic for playing Quake as authentically as possible.

Is there a reason why this .exe is no longer included or being worked on? It's really the best of both the GL and software modes, since it has no graphic glitches and z-fighting like the GL version, while retaining it's best features such as UI scaling and vsync.

It just makes no sense to me at all. 
 
The regular WinQuake can hit higher frames per second, doesn't matter much for small resolutions but if someone decides to max out in a very large resolution there is a gap.

It is actually maintained because the Linux and Mac versions of Mark V WinQuake are WinQuake-GL builds, I just don't put a Windows one in the Windows .zip because it would confuse most people. 
 
Are you planning to put WinQuake_GL.exe's in future builds? 
 
I could make it available somewhere on the page in the future when new releases happen. 
 
Also, there have been two longstanding bugs to do with monster spawns that have been around since the original WinQuake - one in e3m3 where the fiend spawns midway in the air in the circular lava room when the final bridge activates and another in e4m7 where the zombies spawn after killing all the underwater zombies in the first circular room. In both cases the monsters are stuck in the air after spawning when they should fall to the ground/water and start attacking. Could you look into fixing these issues? 
@jayoo 
Are you sure that these are engine and not QC bugs? My recollection is that they happen in all engines, not just WinQuake. If QC bugs it would be inappropriate to modify this behaviour in the engine. 
 
There's definitely source ports out there that fix these issues, but I admit that most I've seen don't.

Why would it be inappropriate to modify this behaviour in the engine? They are gameplay bugs after all so shouldn't they be fixed? 
Compaibility 
If the bug is due to bad QC code or mapping errors, then changing the behaviour of the engine to work around the bug does carry a risk: some mods may be using this behaviour of the engine intentionally to create a desirable effect. The fix for the bug in vanilla will break those mods in your engine. Which isn't to say that it's never the right choice to make those kinds of change, but you have to be thinking about the potential cost as well. 
@jayoo 
QuakeC is game logic in a progs.dat, found in Quake pak0.pak. It exists outside the engine and is the game logic program. It can be compiled with a QuakeC compiler like fteqcc.

Some people (like preach) are really into QuakeC, he is the main author of Quoth and was involved in Arcane Dimensions.

Concise version: QuakeC behavior isn't related to the engine. 
#1676 
Quake Info Pool - Currently not researched Quake bugs

"Right in the beginning on E4M7 some Zombies start spawning after you kill the ones in the water. If you stay under water as you kill them, the new ones will spawn above you, and fall down into the water. However, if you kill the ones already there under water, and get back up on the ground level, the Zombies will spawn in the ceiling, and just hang there."
Reported by Alexander "Prodigy" Møller
Demo is available for download (e4m7zombie.zip)


QIP lives! 
 
I bet it's a bug in the map itself. Some trigger misfiring or something. 
@mankrip 
Quake has a lot of silly mysteries/annoying things. It probably is a map design flaw.

Video examples:

https://www.youtube.com/watch?v=DFQVP5cKcSo
https://www.youtube.com/watch?v=3Pnf9HDNFz4
https://www.youtube.com/watch?v=JasyI2SFUuk
https://www.youtube.com/watch?v=ZS0vigujrXo

Can't imagine how this one is possible.:
https://www.youtube.com/watch?v=R9ri7Abpl_0 
 
The zombies' teleport entry points in e4m7 are just too close to the ceiling.

But if you have an online server with a sys_ticrate of 0.1 then they fall just fine, because the server doesn't check their position fast enough to know they are stuck before they fall far enough to not be stuck. sys_ticrate .05 or faster and they get hung up.

It can be fixed directly in the map or with QuakeC by altering the locations of the teleport points. 
 
Sounds like a mapper or advanced user could make an external .ent file if that is what is going on. 
 
Hey, *I* am an advanced user!!

Uh, is tool_inspector broken? it seems broken (in both GL and DX 8, 9). I had to go back to version 1.27 to make it work again. It did not work for me in 1.28


Ok, here is what the zombie problem is, I believe:

In triggers.qc, info_teleport_destination function raises ALL teleport destinations by 27 units upward. I think this is to get them off the ground a bit, to make sure monsters don't get stuck in the floor, hah. Well, the problem is that it causes the zombie teleport destinations in e4m7 to move too close to the ceiling. Though oddly, it's not completely consistent that the zombies get stuck. Sometimes they seem to fall just fine in single player, other times they may get stuck.... Maybe it has something to do with whether they are moving or seeking a target or something when they teleport in. Or it could even have to do with the FPS you are getting in Quake....

Yeah, that might make sense -- if you are getting really high FPS, then Quake checks sooner to see where the zombies are, and determines they are partially in the ceiling. If you are getting a lower FPS, then the physics check doesn't happen quite as fast, so the zombies fall down a bit and free themselves. That may explain why the original Quake people didn't catch the problem; they weren't getting a really high FPS back in the 90s!

But that's just a guess on my part, knowing that Quake physics are dependent on your frame rate.


In any case, lowering the teleport destinations should fix the problem.

So load e4m7, then type in console: copy ents

Go paste those ents into a text file: \id1\maps\e4m7.ent


Go to line 883, 889, 895 and change the "origin" Z values from 136 to 100, just to be safe. Save the file. Problem solved.

...

The problem is solved!
We solved the problem...
So ev'rything is awesome!
Problem solved! 
 
Yes, you are certainly an advanced user, haha.

You might consider uploading that file to somewhere for jayoo.

If you do, I'll mirror a permanent copy of the file.

ericw may interested in it as well.

/Yeah, Pritchard pointed out I messed up the inspector. 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.