ZDoom

That's indeed the best solution.

Wagi wrote:IMO, the movebob speed should be determined by the player speed, while the intensity (how far it moves up and down) should be determined by viewheight.

This is definitely what should be done.

Whatever console cvars currently exist for view bob should just by multiplied by whatever value is given by these factors.

IMO, the movebob speed should be determined by the player speed, while the intensity (how far it moves up and down) should be determined by viewheight.

It would be nice, if possible, to be able to set weapon bobbing on a per weapon basis, outside of the no bobbing flag. Some weapons you would expect to bob a lot, such as the pistol, where as the BFG would probably move very little.

I would honestly love to have more customization in general in regards to view bobbing from an author's perspective. Bobbing amount, speed, etc. And a little bit of adjustment for the weapon sway, as well, would be appreciated.

Any news on this one?

I'm in favor of this feature, as long as the player can change their bob after it's been set in PlayerPawn.

Medricel wrote:But yeah, I think the best you're going to get without modifying players' configs is a suggestion to players to alter thier movebob value in your .txt file.

Which is completely fucking stupid.

Enjay wrote:Image

*twitch*



But yeah, I think the best you're going to get without modifying players' configs is a suggestion to players to alter thier movebob value in your .txt file.

Oh god, I feel so terrible for being the guy to do this, but it's a bit pet-peevy to a certain person (me) so I can't resist...

B-O-B

That solution doesn't feel right, it's simply too hacky for my taste

What you could do, and I've seen it done before, is just copy the user's config to a custom config file (only if it doesn't exist), and launch ZDoom executing a console script to set defaults (only if the config hasn't existed before), then afterwards, the player would be allowed to set their own options from there. I know it was done with one of the more recent Wolfensttein TC's, I forgot who did it but that's what he did.

After the first run, the bat file would load the alternate config, however, it would not reload the defaults again. I suppose it could have helped if he added in an alias "reloaddefaults" or something in case players wanted it, which would run the console script again, but it's still pretty simple to just delete the alternate config file.

Sure, but in my opinion it just sucks if the player has to load a custom cfg instead of simply loading a pk3... oh well... is it possible to put a cfg in a pk3?

You custom cfg doesn't have to set everything, just the items that are important to your mod.