 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
r_skyalpha and r_skyfog only work right if I have "gamma 1" but any other gamma setting causes them to do weird things.
Ya know, I see that solid white "scr_sbaralpha" thing someone else mentioned, but only on my old laptop. I don't see it happen on my netbook where I'm getting the weird sky issues with gamma != 1. As I mentioned before, Fitzquake Mark V is really insistent upon playing the demos (and there's no way to stop it); so much that it seems to prevent Qview from connecting to a server. When I try to use Fitzquake through Qview, it starts up and I see the message that I'm connecting through Qview, and then the demo starts playing and I don't connect to the server :/ But then I can just type "exec qview.cfg" to get connected, but still.... Fitzquake is gonna play those demos NO MATTER WHAT! Gee, it sounds like I'm really complaining a lot with all my bug/issue reports... but here are some more!
Widescreen resolutions seem to cause the weapon model to be much more hidden "under" the bottom of the screen. Like at 800x600 the weapon model sticks up a lot (like in proquake), but at 1024x600 the weapon model doesn't stick up very much (like in standard quake). In some windowed resolutions, the top of the screen is hidden so that you can't see all the lines of text. Like, in 800x600 (windowed) you never see the first line of text (and maybe half of the second line too) at the top of the screen. So if you start typing a message, you never see what you're typing. Setting my windowed resolution to something weird like 750x550 on the command lines causes the problem to go away. The names in the scoreboard when you press Tab are "bronze." I don't like that; it's usually harder to read on top of Quake's mostly-brown world. The names should be the proper color (white) unless the person used bronze characters to make their name. OH... if I actually make my name with bronze characters, then it appears white in the scoreboard! It seems backwards.... The r_noshadow list should also include k_spike.mdl and lavaball.mdl (glowing things shouldn't really cast shadows). And I mentioned before that bolt.mdl should be in there, but I'll clarify that "bolt1.mdl" should be renamed to "bolt.mdl" since there is no bolt1.mdl in (standard) Quake. For other people who wanna fix this, you just need this altered list in your autoexec.cfg file: r_noshadow_list "progs/flame.mdl,progs/flame2.mdl,progs/bolt.mdl,progs/bolt2.mdl,progs/bolt3.mdl,progs/laser.mdl,progs/k_spike.mdl,progs/lavaball.mdl" I guess I'll mention that trying to make shadows for bolt.mdl (if it's kind of long) causes a major slowdown for an instant, but this behavior didn't happen in standard Fitzquake 0.85 Hm, I think I have to mention a niggle I have with the r_nolerp list: it contains models that are not a part of standard Quake. I don't think you should be catering to all the different mods out there by adding their modiels to the default settings in "standard" Fitzquake. That's something that each mod author (or possibly player) should have to configure themselves, with a custom r_nolerplist, and not expect the engine author to account for all their custom models.... If you start accounting for all the possible custom mods out there, the list is going to become really bloated (hey, I've got a few models from FvF you could add to that list ;). Not that it matters, since it is how it is and probably isn't going to change; that's just my thought on the matter. I'm really not just trying to complain with all these bug reports.... It just shows that I'm playing the heck out of Fitzquake! And the only little annoying issue that I can't work around is the centerprints and scoreboard appearing right in the middle of the screen and blocking the view. I really wish they behaved like in proquake and appeared near the top of the screen.... Hmm, and here's something I've seen several times: Fitzquake V doesn't always honor the -window command on the command line (from my batch file). Like I just ran standard Fitzquake without any parameters (so it ran full screen), and then after I closed that and ran Fitzquake V -window -width 750 -height 550 (batch file) it started up full-screen.... Then when I hit ALT+ENTER it switched to the proper-size window. Widescreen resolutions seem to cause the weapon model to be much more hidden "under" the bottom of the screen. Like at 800x600 the weapon model sticks up a lot (like in proquake), but at 1024x600 the weapon model doesn't stick up very much (like in standard quake).
isn't this desired behaviour? it retains the look of the weapon regardless of fov or aspect ratio. older engines would make the weapon look weird at wide screen or high fov. Having a tiny weapon is annoying. However I play my game with these variables to make the weapon look "chunky".
r_viewmodelfov 110 v_gunangle 2 Give it a try? Having a tiny weapon is annoying. However I play my game with these variables to make the weapon look "chunky".
r_viewmodelfov 110 v_gunangle 2 Give it a try? If I "view" a "model" at the right "angle", when I "play my game", my "weapon" also goes from "tiny" to "chunky"... It took me way longer than I will admit to to understand what you were getting at there Kinn...
Perv! ;) Yes, having a tiny weapon is annoying :p Everyone laughs at you. So I've heard....
The desired effect is that your weapon looks the same (sticks up the same amount) no matter what resolution or FOV you are in. @ FifthElephant r_viewmodelfov 110 does the trick to make the weapon model look the same in wide-screen modes as it does normally in non-widescreen modes. Too bad that's not automatic, but it's good to know there's a way to adjust it. Thanks. v_gunangle seems to be an unknown command though. One bug I've noticed is that when you complete a level, the music doesn't stop playing and will continue to play over the song in the next level. I am using mp3 files in the music folder by the way. Everything else works great though!
One work-around is to save your game, quit, and reload your save. Another is to simply turn off the music, but that's a bit drastic... OGG files aren't supported in Fitzquake ;)
Ok, I investigated the music glitch.... Here's where the problem occurs: Upon touching the exit there's is a noticeable pause while the mp3 track loads and you see in the console: "current music track: music/track03.mp3" -- that's the Quake intermission track. However, it never stops the current music track from playing at that point, like it should. And then both (I think) the current background track and the intermission track enter "the phantom zone" and you will hear those tracks playing in the background, EVEN if you alt-tab away from the Quake window! Meanwhile, the new music track for the new level you enter will be playing in Quake (and you will only hear that track when the Quake window has focus -- you always hear the phantom tracks). Additionally, the phantom tracks will not respond to bgmvolume commands in Quake, but the active track will. It looks like if you just keep exiting levels, eventually you have like ALL the quake music tracks playing at once in the phantom zone.... Note: you do not get the phantom track effect when using the changelevel command as opposed to touching the exit, since Changelevel never tries to run the "end of level" code that should stop the current track from playing then load the intermission music. If you use "cd off" and then "cd on" right before exiting, it will then play the intermission music and will not continue playing it when you switch to the next map. However, after doing this, any music playing in Quake will no longer respond to bgmvolume commands, and it will still be playing even if you alt-tab away from Quake.... The Correct Workaround: If you issue "cd stop" just before exiting a level, you're golden. The intermission music will play and not keep playing on the next level, and the music tracks will continue to respond to bgmvolume commands.... Crud. it looks like the "phantom track" is impossible to kill (short of closing Quake) once it starts. So the "cd stop" command MUST be issued BEFORE you touch the exit.... I'll have to fiddle with my QuakeC to see if there's any way possible to issue a "cd stop" command AS SOON as the exit it touched, before any of the glitches can kick in.... Annnnd another issue I have.... Looks like setting "mouslook" to default "on" in the menu is not such a good thing either :/ Two reasons why: It overrides any alias settings I have to temporarily disable mouselook, and more egregiously, if I turn it off in the menu, it turns itself back on the next time I start Fitzquake.... Here's an example of something I set up in a cfg file: +mlook alias +nolook "-mlook" alias -nolook "+mlook" bind z +nolook So +mlook is on , but when I hold down the Z button, mouselook will temporarily be OFF so that I can, for example, move a few "inches" forward very slowly using the mouse (to get the perfect view or position for a screenshot or something). But as mentioned above, the menu setting overrides mouselook ever being off, so I have to turn it off to use this stuff. But the menu setting keeps turning itself back on.... Yep, issuing a "cd stop" command via QuakeC stuffcmd to each of the players as soon as the level exit is triggered -- that totally fixes the glitch.
Also, "cd off" was the command I was looking for to completely prevent the MP3 tracks from loading. Though oddly, if I put "cd off" in my autoexec, I will then need to do "cd on" followed by "cd reset" to get the tracks to play again (level change alone won't do it). If I just issue "cd off" inside of quake (and not in autoexec), then all it takes to get the tracks playing again is "cd on" (and a level change, as usual). The "mouse look" menu option doesn't bother me anymore; +strafe is the command I was looking for to temporarily disable it and allow moving with the mouse.
But unfortunately "cd off" command only works if you actually have a CD drive. So as I mentioned upthread, there's no way to disable the loading of MP3s -- or to make them play -- if you have no CD drive (so I'll have to create a virtual CD drive before playing Quake even if I'm not going to use MP3s, just to prevent the considerable delay as it loads them into memory). As I mentioned before, E1M2 and E2M3 will crash if you try to toggle external_textures on or off. I noticed that when these levels load, there is an error: "mod_loadtexinfo: 1 texture(s) missing from bsp file." And Fitzquake V does not handle missing textures very well (crashing). I know there's that one weird untextured button on E2M23 in DM mode. tool_texturepointer says it's "notexture." New issues: You can't use % in normal chat messages.... For example, I tried to say, "we need to kill 100% monsters" and it comes out "we need to kill 100(invalid macro ' ')monsters" In Proquake, you get the little color boxes with scores (representing the top two players) in the HUD, to the right of your Cells ammo. Proquake will show no more than 2 of them, because if it were to show 3 or more there, they would block the clock. Fitzquake V blocks the clock with 3 ore more of them.... And more issues with centerprint: When you die, the scoreboard appeared right in the middle of the screen, the same as with the centerprints, so that if there are 3 or so names in the scoreboard, it will block the centerprint. For example, when you die in FvF there is a centerprint message "Press 2 to Observe" but you can't read it because names in the scoreboard will hide it. Proquake keeps the scoreboard at the top of the screen and avoids this issue. Was playing today on END map. Me and another player were using Fitzquake Mark V (server was proquake). He got disconnected and could not reconnect, because Fitzquake was giving him the error:
"host_error: Colors slots full." I didn't encounter this, but he couldn't reconnect until we were at the next map. I know that has to do with the colormaps for the dead bodies, right? But why would it prevent him from connecting to the server at all? Not so critical continued reports: Toggling high-quality textures on or off in a game causes the player skin to go completely white. Other players will look solid white after you do this. But rarely it doesn't happen.... It seems to require restarting Fitzquake to fix it. Oh, and you can use the PAUSE button even in Deathmatch on a server that has Pause disabled. It won't pause the server -- it will just pause YOU and your view of the action will be completely frozen until you unpause yourself.... Of course, you'll probably be dead by then.... And... I have a modified DM6 map with a few small extra areas. It seems to no longer be recognized by Fitzquake as far as applying high-quality textures to the walls. The wall texture names are still all the same, but Fitz won't apply them to my modified DM6. High-quality item textures still work fine. Gunter, hats off that you have singlehandedly brute-force revealed weaknesses in the engine.
And this is the kind of gauntlet of testing that almost any engine author could only dream to have --- in the thoroughness and the rigor. I'm replying out of this admiration. In a perfect world, I could correct these and the other bugs that others have graciously found -- and this level of bug-testing is frankly incredible compared to what I can recall seeing in maybe anything except maybe Quakespasm and ezQuake (I got really high levels of feedback for "modern" ProQuake, and the detail and testing in this thread seems to vastly exceed even that). Mark V Final was apparently not as bug-free as I hoped when given a wide-array of testing in different environments and the kinds of uses that normal FitzQuake didn't even typically encounter (like as a client to a multiplayer server, as an example. I'm sure it got drilled and grilled in SP and coop not only up/down but left/right and forward/backwards). I wish there were 2 of me. The one of me that exists isn't likely to ever have the time to revisit Mark V. :( On the plus side, it is open source. And I don't see much posted that wouldn't be somewhat easy to remedy by an experienced engine coder. Ultimately, attention is probably better served by people contributing to or whole-heartedly endorsing Quakespasm. Mark V doesn't contain too much that couldn't be ported to that engine to achieve a singular "old school" classic engine You have to admire his resilience in finding all these bugs...
It's a shame you don't have time to revisit the engine (in particular my biggest peeve being the distorted texture scaling issues). I have always envied people who can code, I tried to learn how to code for best part of a year when I was unemployed and I just don't have the mindset for it. Yeah, it's a great misfortune that you don't and probably never will have time to put a little more polish on this... :/
Maybe some other engine coder will decide to pick it up. I'm tempted to take up engine coding myself to see if I could fix some of these things, but I doubt I'd have the time for that either. I tried Quakespasm but I just don't like it. It's just not right, somehow. Perhaps if they imported some of the Fitz V features, like the ability to disable custom textures. Additionally, I find the Quakespasm website to be nothing but annoying. Yeah, great, they chose to have an "artistic" presentation with vague, arcane-sounding words and messages, but that's just stupid and irritating when I'm trying to find solid information about the thing. It's even difficult to find any real documentation of the features (as far as like console variables, etc.) in the included readme files... and I don't feel motivated to bother with the effort of digging through all the changelogs in the file to try and figure it out. Digressing a bit, I remember giving feedback and reports for modern proquake, but the farther that project went along, the farther and farther it got away from standard Quake in feel and function, and it was a major hassle to track down all the console variables I needed to reset back to the defaults in order to get the right Quake feel back, so I gave up on that and just stuck with Proquake 3.5 (the last version by the original author). Modern Proquake was just no longer the same game. Apparently that's what hard-core runequake players wanted (to disable all special effects and change the defaults in order to get any and every advantage in deathmatch)... however, I feel that was against the spirit of the original Proquake to fix things without making too many changes to the presentation. Also, after "string safety" stuff was added in to Proquake 3.39+, it broke the FvF vote menu.... So yeah, I just can't use modern Proquake. It made too many changes. I always liked Fitzquake, but it was just lacking some features to push it to the top of the pile. With the great additional features added by Baker (NAT fix possibly being the biggest factor for online play), I just can't prefer anything else over Fitzquake Mark V. Going "back to basics" with usability improvements and bug fixes (and optional graphics enhancements that can be toggled off easily), instead of just cramming in everything everyone wants (I cringe a little when people start asking for Darkplaces stuff to be added in to this) is why this little engine has received so much attention. It's refreshing to go back to how Quake was meant to feel, instead of getting a bloated engine full of too much eyecandy, changed defaults, and hyperactive tweaker features. I've found ways to work around most of the bugs (hah, I hard-coded some Fitz-specific workarounds into the FvF mod!), and I even put up a Fitzquake configuration page on the FvF website to help people get it setup, heh.... So yeah, I'm goiing to stick with Fitz V and I'll keep recommending it to people who play FvF. It just looks and feels "right" and has all the right enhancements in the right places (well, almost -- it would benefit greatly from a few specific proquake features). Anyway, you have my admiration, Baker, for taking this little engine which had so much unrealized potential, and unlocking some of that potential. Even if seeing some of the potential unlocked just leaves us wanting to see MORE of it unlocked, heh. The rest of you, come play FvF using Fitzquake Mark V :P www.fvfonline.com fvf.servequake.com:26008 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?
|
|
| This thread has been closed by a moderator. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |