 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
Does anyone have a working set for the standard Quake bad guys? Proving harder than I thought....
Download a DarkPlaces texture pack and look at the texture names if needed like quakeone.com/reforged.
Naming convention is simple: Model name: player.mdl Replacement name: [model name.mdl] _ [skin #].tga Result:[model = player.mdl]_[skin = 0].tga Result: [player.mdl]_[0].tga Result: player.mdl_0.tga Save your sanity, read text instead: http://icculus.org/twilight/darkplaces/readme.html#ReplacingContent
[But don't want to risk making Spirit upset.]
Revision 10 Incremental refinements but the source changes are large and includes a Visual Studio 2012 project file now. Main real changes: give ks - give yourself silver key give kg - give yourself gold key give q1 - give yourself rune #1 [r and s aren't avail] give q4 - give yourself rune #4 "give" command with no parameters gives you minimal info on give command. Reworked video mode shutdown in a way that might fix the crash one user was experiencing that I don't get [or may not]. Within the next week, there will be another upgrade to Mark V. It won't include the mp3 request due to running out of time.
On the plus side, I think it completes the idea of getting the codebase entirely straight. Keep in mind that the emphasis of this was to give back code clean-ups to the FitzQuake codebase to tune-up the 100 oddball bugs discovered at Inside3D without burdening, say, metlslime without having to read all that. Exciting? Well I do want to fix any bugs discovered, but other than that, it will be the final Mark V. It's the future!!!
By the way my faveourite thing about this engine is the demo handling. Supports multiple (most) protocols :) It will be a very boring release. At least from the angle of exciting and interesting features goes.
From the other possible angles like the "boring and uninteresting" releases angle, it might barely fit itself in to mildly underwhelm. And these are the kind of expectations I hope I can almost meet. But from the more serious side It will be a very worthy final chapter to this engine and I have to among other things type up a credits.txt to accidentally not include in the final Kidding aside, it has quite a number of things that I owe significant credits to others. For 5 days I've been tempted to release this intermittently in pieces, but no This will be the final chapter of Mark V. I'm doing some final testing and want to give a day or 2.
I'm not fond of "pre-release talk" (it's hated here, which I like because I hate it too) but I wanted to see if anyone had something to say I wasn't aware of that I needed to take into consideration. If ever the words "radical" and "conservative" fit a description, it my hope this last one achieves this. It is my desire to draw this to a close with a very wide range of conservative fixes, some of which don't seem reasonable. Thursday release. Final answer. Unless Thursday final turning requires an expansion of the definition of "Thursday" to include Hawaii or one of Jupiter's moons to meet a slight procrastination. [But yeah, I really love FitzQuake I don't know if it is too late to submit a feature request, but if not, could you add external ent support and multiple gamedir support to Mark V? I have been using these two features extensively with darkplaces, and found them to be extremely convenient and useful. Thanks.
Don't worry, maybe you don't get what you think you want, but maybe you get more than you bargained for
Is it possible to set fog parameters before the map is loaded? Then the fog parameters could be specified in the quake.rc file.
Can you add a fog distance command? Like at say 1024 units the fog does not affect surfaces? Then really tall ceilings could be black instead of the colour of the fog. Also make this a new fog command like 'fogdist' or something, don't add this feature to the existing fog command, it will cause problems with mods that use the fog command already. Can we get masked textures (like grates, chainlink fences) to have a value key in a similar way to how the "alpha" key works? This would be much better than having the texture start with a curly brace "{"
(which pissed off SleepwalkR to no end) @sock
FitzQuake expects the fog to be in the worldspawn and resets it on level load and I think new cvars are almost always bad. Better would be backwards compatible way to allow one more fog parameter in the worldspawn keys. I also think it would require more tuning and testing to make sure it looks rights than I can do in the next few hours, but I'll think about while I'm trying to get the engine out. The Kurok mod (also an engine modification of FitzQuake)used an alternate fog formula, but I haven't been thinking about fog much lately so I'll see if I can integrate the Kurok fogging for you to look with the engine release. @elephant I think me just putting something in that hasn't been discussed and argued about is how "really ugly hacks" happen. @Baker, I downloaded the new beta and I like noclip, notriggers :) good for testing. I LOVE the command auto-complete, my god about time! It even does map names within gamedir folders :)
What is r_stains? I saw it mentioned in the readme file but could not see any difference and the readme does not say what to do with it. I had a play with the new fog and it feels back to front to me. I want original fog up close and then fade to specific colour at distance. Maybe I am not getting the parameters right but I tried for a while and could only get black at distance and no fog up close or white fog up close and glowing at distance. Say for example I have fog 0.05 0.1 0.1 0.1 defined which is a nice wispy fog. On surfaces at distance (1024+) this gets brighter instead of darker regardless of light, I want to have a fog up close and then fade to nothing. I assume the distance fog would have a different colour to the foreground fog. Ultimately I want fog in a room but when looking up at a high ceiling 1024+ units it is black because there is no light, does that make sense? One possible idea for alpha textures is to link the process to the texture. If the mapper specifies external textures and they have an alpha mask defined (tga/png format) then load and use it. This does not require fancy name changes or lots of effort by mappers just an external texture directory with alpha textures. External
what? so it just loads Ok, let me clarify a little more.
- It would be a brush entity key. - It would use palette number 255 (the pink one) - It would be a normal texture. (no tga/png needed!) Why a brush entity key? Well we have this support with alpha, why not just set the key to something like "alphamask"? You could even have it as "alphamask 1" or "alphamask (insert palette number here)" and specify which colour of the palette can be the alpha texture, this way you could still make a texture look nice in both ordinary quake engines that do not support alpha masks and ones that do! I like shipping What do you think?
|
|
| This thread has been closed by a moderator. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |