 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
Mark V saves settings every time you exit the settings menu or the console.
So if you wonder why no matter what happens, everything is always saved the console history is always up-to-date. That's why! /I prefer to not mention these little niceties and polish-ups because I just consider it part of polish. Like how Mark V forces a WASD default key setup and makes the mousewheel do previous weapon/next weapon by default. makes me want to rip out my autoexec cfg and do some gamedir testing... i think if i do a gamedir AD then my current gamedir should save config.cfg first switch dirs then load config.cfg from there, and vice versa. I hope this is the case already if not i'll have to change it. I have added a writealias command that dumps an alias.cfg for each gamedir but the user then has to make an autoexec.cfg to exec alias.cfg or maybe i should make it do that automatically...hmm
my levels menu doesn't work in the quakespasm folder. I have the quake HRP and the menu graphics change. What does this? In the DP folder works fine.
DX9 version is great, it kills on my R9 280. Also what graphical things are supported? Just unpacked textures? Can it ever support things like dp pretty water? "Single"
"New Game" "Load "Save" "Levels" (Only appears if nothing above graphically replaced) ----- So if an exceptionally rare mod (X-Men, for instance) replaces a graphics there Or if a user is using high definition graphics for those menu items Rather than present the user a "Levels" graphic that clashes with the appearance of the menu, it simply disables itself ;-) I'm just rather picky and I'd rather have menus that look nice than a menu with an item that clashes with the rest of the items on-screen. Mark V can save multiplayer games, including co-op games which was the main target.
/If it isn't working, let me know. Also what graphical things are supported? Just unpacked textures? Can it ever support things like dp pretty water?
QMB particle option in menu, MH waterwarp (defaults on), MH volumetric shadows (r_shadows 3). The Open GL version (not DX9) has a raw test implementation of bloom that needs more work in the future. Eventually, it'll be run through the gauntlet, maybe possibly sometime in the spring, but not necessarily because isn't high priority item. External textures use the same names as DarkPlaces. Mark V only supports That would need a VERY significant overhaul of the entire renderer.
It might not be immediately obvious, but DP pretty water needs shaders. Then you're in a position where, in order to have other effects be consistent, you have to implement *everything* in shaders. Another thing is: the reason why DP runs slower is because it does all these effects. If you start with another engine that runs faster, port DP's effects to it, then I've always been of the opinion that it's a big world and there should be room for lots of engine options in it. Each engine has different goals. If you want to "pimp my Quake" then DarkPlaces is the engine for you, but other engines don't share that goal to the same extent. DX9 version is great, it kills on my R9 280.
MH did an incredible job with the DX9. One of the rare (and fun) examples of something going from simply non-existent to polished in just over 3 weeks. The awesome beta-testers here who help out and provide fast, high quality feedback is unimaginably helpful to engine development. Most incredible beta-testers ever! Engine development is hard, but smart detailed-oriented testing can take quite the edge off! Lol, I had no idea. I thought it was like standard quakes implementation. Plus the save option sits under the single player menu
Stuff like DP dies on AD, down to 7fps. Other games, ie Q2, Q4 run much better at the same resolution with HD and extra effects cranked.
I've had the best luck with this engine and quakespasm spiked. For instance ad_fuma... markv/dp = slowdown right at the start by the lift. markvDX9 = smooth. >QMB particle option in menu, MH waterwarp (defaults on), MH volumetric shadows (r_shadows 3) I found the particles and if waterwarp is on by default I just have to try the shadows. My transparent water in QSS has issues rendering, wrong things or distant things will show up. >>Rather than present the user a "Levels" graphic that clashes with the appearance of the menu, it simply disables itself ;-) I wish I could override this. Typing map is somewhat of a substitute. I do 1080P on a 42" screen so I really like the high res. See your point on shaders though; I remember playing quake and quake2 on voodoo2 back in the day and to see it keel over with a quad, 16gb of ram and a card faster than the original PC is shocking. Remove or rename gfx\sp_menu.tga (or gfx\sp_menu.lmp) and will probably load, if that is what is going on.
Possible (non-ideal) workaround. Hm, I would say the information and function is more important than the aesthetics.
It's no big deal if the "Levels" menu looks different; it's no less useful, and it's not like people are going to be staring at the menus for long periods of time. A menu isn't there for artistic value -- it's there for functionality, just as a way to get to the setting you want. Oh... AND it makes it even worse with your force-choosing what map to stick me on when I go to start a New Single-Player Game (oh how
I hate that feature). I tested with FvF3 (a later version, not the version my server is based on) which contains custom menu graphics. If install the custom maps from FvF4 (which contains one called fvfstart.bsp) along with, say, the iikka, terra, and dopa maps, then your map-forcing feature (which I hate so, so much) decides to ALWAYS stick me on fvfstart rather than the default start.bsp when I use the default menu option to start a single-player game. Furthermore, since there are custom menu graphics, the "Levels" menu is missing, so I cannot even use the menu to work around the feature (which I truly, truly hate) to start the standard start.bsp. So, the "Levels" menu should always be there, even if it's ugly, but more importantly... (you can imagine me shouting this loudly to properly convey the hatred I have for this feature) THE DEFAULT MENU OPTION TO START A SINGLE-PLAYER GAME SHOULD *ALWAYS* START THE DEFAULT SINGLE-PLAYER GAME. heh. I know, you probably spent time and effort coding this feature thinking it was a great idea, but it's just not. This is as bad as all the "toxic settings" you hate so much when some servers or mods force upon the user. This is just as bad as a mod containing an autoexec.cfg within a pak file that force-starts you on the same map every time despite what you, the user, want to do, because just like in the case of an autoexec in a pak file, it cannot be disabled in Mark V. And no matter if I am wanting to run the dopa, terra, or iikka maps, I will get forced to start on the fvfstart map every time, because it is first alphabetically, so it's not like the feature is working well to begin with -- you can't read the mind of the user, and selecting a map alphabetically is no substitute. So just go back to the default function for the default menu, and if the user wants to do something non-default, the wonderful "Levels" menu lets him run whichever non-default mission he wants. Well, assuming you don't hide the "Levels" menu because it doesn't match new menu graphics.... But as I said, I feel the functionality is far more important than the aesthetics. 1) FVF running (-game fvf)
2) Single Player->New Game 3) fvfstart.bsp loads 99 of 100 people would call that perfect behavior ;-) IF U Have a starting map in your own gamedir then just call it start.bsp, like everyone since 1997 does it? ;)
Select and rotate pitch and yaw by selecting a single pixel on the screen and dragging it.
Video Initially was a bit frustrating, then the slightly rusty 3D math kicked back in. Have to imagine the frustum as a sphere. Combining and project and modelview matrix, the center of any pixel on the screen has an exact "pitch" and "yaw". There are shortcut cuts methods that wouldn't achieve pixel-level selection precision, but I wanted the real one. heh. for me the key to that feature is the convenience of the list. renaming the graphics isn't the worst thing. I don't have as much passion about is as gunter. I'd just start from the command line if it was picking the wrong map regularly.
lots of stuff, ie the mapjams never even had a start map. not sure if "maps" works in any other engine but it would have saved me alt_tabbing at least. AD has mod folder selection from a menu but no maps. the r_shadows 3 looks good, I would have never found it. recommended behaviour would be for mods to create startmap_sp/startmap_dm aliases that specifies exactly what to do, and for engines to invoke that instead of doing 'map start'.
that way you're not getting randomness... if only more engines+mods used that... more seriously though, what kind of weirdo actually uses the menus? :o (especially if the console's maplist dump supports clicking) Stuff like DP dies on AD, down to 7fps. Other games, ie Q2, Q4 run much better at the same resolution with HD and extra effects cranked.
I've had the best luck with this engine and quakespasm spiked. For instance ad_fuma... markv/dp = slowdown right at the start by the lift. markvDX9 = smooth. I can see why that might happen - polygon counts are absolutely insane in this part of the map. There are a combination of things going on here. Insane polygon counts. MarkV GL makes no attempt at draw call batching. That's going to mean that bigger more complex scenes will bog down more and more. MarkV D3D9 takes those GL calls and batches them, so it can handle those scenes better. It's still transferring a LOT of data to the GPU every frame though. Quake 1 map formats are working against you. There's actually not a whole lot visible in that start scene, but Quake 1 lacks the vis format enhancements that even Quake 2 had, so it's pulling in a LOT of hidden surfaces. DarkPlaces + huge data set + bad vis format + bling is not a good combination. Quake 2 doesn't have the bad vis format, so it's data set is smaller, so you can bling it without as much slowdown. Likewise more modern formats. Putting your data into vertex buffers so that it's already on the GPU rather than needing to be transferred every frame helps a LOT with bigger data sets too. It's like the Quake equivalent of death by a thousand cuts. "1) FVF running (-game fvf)
2) Single Player->New Game 3) fvfstart.bsp loads 99 of 100 people would call that perfect behavior" Maybe, but I complain louder than those other 99 hypothetical people combined! :D And the problem is that this same thing would happen no matter what mod you were running in "step 1." You'd get fvfstart.bsp no matter what mod, because it's first alphabetically.... Actually, in the FvF4 full version package, the mod is programmed to always start the fvfstart.bsp map when a player goes to start a new single-player game. Probably somewhere in the QuakeC it does that.... This is more like what Spike suggested. If the mod actually specifies a map to run, that's fine -- you give control of such things to a mod when you run a mod. Though the automatic start map picking does not seem to occur when you are just running id1 Quake.... Why is that? That actually seems backward, in a way.... I mean, if you're running a mod, the mod itself will usually contain some way of starting whatever map it want to start, if it doesn't want the default start map. But if you're running just plain Quake and you have a single-player map pack installed... then you DON'T try to select the start map via the engine ? Well, I don't understand the reasoning behind that, but I dislike the feature in either case. I do love the "Levels" menu though.
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |