 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
Mark V release 14. All reported bugs fixed (*) and thank you for the bug reports!
1) BSP2 support via Spike 2) MP3 playing on top of each other = fixed 3) White HUD bug for some video cards = fixed 4) jdhack/Requiem "automatic impulse 12" for non-supporting progs 5) jdhack/Requiem "automatic fish fix" (jdhack is brilliant!!) 6) scr_crosshairscale 0 draws a dot There are about 20 other improvements, the details are in the readme. Download: http://quake-1.com/docs/utils/fitzquake_mark_v.zip Read Me (*) Except Gunter's bug reports relating to mods missing skins and skin with toggling external textures. If you notice any bugs, please let me know ASAP! This should be a very polished release because I had no time pressures! yay, that's a nice surprise! the release notes look really delicious! bugfixes, bsp2 and even requiem features implemented, just wow.
looks like warpspasm works fine now, the skies/liquids and polyblend effects were messed up for me in previous release. old version http://imgur.com/jvqZZAY new version http://imgur.com/xLNOiT0 it's always nice to have more engine choices just in case something goes wrong with certain hw setup or map release... dynamic light performance fix and various improvements make mark v a strong contender for the best performance/mod compatibility ratio out there imo. Can't check right now, but does this also address the issues with over-limit maps and/or demo playback in such maps that were first discovered in Backsteingotik as well as the Custom Gamer video thereof?
@negke
I wasn't aware of that, but I will fix. Am I correct to assume if I check the Backensteinogtik thread I'll find the description of the bug? @Fifth Quakespasm did a power of two texture patch. http://sourceforge.net/p/quakespasm/patches/25/ I have no eye for this sort of thing, does it look like their patch solved this issue to you? There's some mention of it in the release thread, something about monsters becoming invincible under certain circumstances. sock would know in more detail.
This is the video in question. MarkV was used to playback a video for capturing, not sure which engine the demo was recorded on. IIRC, what happens is that some models are rendered black/unlit. That bug in the Daz video was fixed in the October 2013 update. The some models rendered black/unlit thing wouldn't have been the October 2013 update either.
However, should anyone spot anything like that, please record a demo and save a savegame. At the moment, I have time to fix bugs. Next week I have new 2 new mapping features I want to introduce into Mark V, but unless every known bug is smashed I won't be happy. should i expect ne_ruins pack not working with this engine? looks like it was mentioned previously mark v was going to run out of edicts on this map, and i got a crash at a certain point playing it.
I never heard of r_skyalpha before. I thought it might be great for taking "outside the map" screenshots, but no such luck. I did finally figure out what it was for though.
Curious about how exactly this works.
The engine sets a flag if the total monsters increases when a monster_fish spawnfunction is run. It then watches think functions on the first two frames after spawns, watching for any entities of class monster_fish running swimmonster_start_go. If it finds one, and the flag is set, then the engine reverses a second increase of the monster totals (should one occur). Just looks to see if when a single fish spawns if the count goes up by more than +1.
Both that and the auto-impulse 12 modification were really well crafted by jdhack in the implementation in Spirit's Requiem engine. They can be turned off, type sv_ in the console and press TAB and the names are obvious. Depending on how you fixed it either:
a) it won't set the flag when the entities are loaded because you deleted the line from swimmonster_start or b) there will be no changes during swimmonster_start_go for the engine to reverse, because you deleted the line from that function. Either way you are safe. You'd need some very strange progs, one which had a legitimate reason to increase the monster count by 1 after some monster_fish spawns while still increasing the count in the spawn function as well. Well, actually here's a potential scenario... Suppose that you add a spawnflag which allows monsters to teleport in when triggered. Also suppose that depending on the spawnflag the code in your swimmonster_spawn function branches: * with the spawnflag you increase the monster count immediately but skip swimmonster_start_go (since the teleport code will handle that setup later) * without the spawnflag you wait for swimmonster_start_go to set the monster count. I believe that a map with some fish that do and others that don't teleport would then score a false positive under this scheme, and miss the non-teleport fish off the monster count erroneously. Spirit's Requiem engine
jdhack's Requiem engine! I was just a beta tester who decided to release it after he vanished. All I do is trying to promote it and get people.interested in fixing outstanding bugs. Suppose that you add a spawnflag which allows monsters to teleport in when triggered.
yeahhh, that's why I asked. :) So I take it if all my monstercount incrementing is done in monster_fish() I'm safe? I moved all the increments out of walk/swim/flymonster/go to facilitate monsters doubling as spawners. That's safe. The engine only intervenes if you increase the monster count both during and after spawns, and only intervenes incorrectly if you only do so once per fish but are inconsistent about when you do so. The spawnflag idea was the closest to a sensible reason I could invent why it might vary from fish.
Non power of 2 is broken in quakespasm also.
Hammer of Thyrion for Hexen 2 has a cvar for this - https://www.dropbox.com/s/9hwef9vd513qteq/npot0.jpg (without NPOT) https://www.dropbox.com/s/7iy61i3rlsynpc9/npot1.jpg (with NPOT)
|
|
| This thread has been closed by a moderator. |
|
| Website copyright © 2002-2025 John Fitzgibbons. All posts are copyright their respective authors. |