Has the problem of exaggerated bobbing been fixed yet?

[winz]

I was making a project back then, I was really inspired and making quick progress, but I got stuck with a problem: I wanted the player to walk slower after crossing a linedef, using namely "SetActorProperty(0, APROP_Speed, 0.1);", the problem was that after the player went at 0.1 speed, the bobbing looking pretty stupid, since it retained the default bobbing movement and doesn't adapt to the decreased speed. This was like 2 years ago.
My question is: Has this hell been addressed yet, or we can't still do nothing about this? because stuff like it kills my creativity and makes me abandon projects.

[Nash]

Not yet, we are still waiting for moddable movebob...

[winz]

Holy hell, what are they waiting for? its a pretty demanded feature and it shoud be easy to implement.

[Caligari87]

Holy hell, what are they waiting for? its a pretty demanded feature and it shoud be easy to implement.

I've learned through experience and observation that "demanded","should", and "easy" are famous last words when talking to developers. Tread carefully here, because it's pretty obvious you don't actually know how easy it is.

[maseter]

We had a "swear jar" at work for everyone who said "easy".

[winz]

What could be so difficult? we have running and walking, it would be a matter of seeing the ratio of how much bobbing decreases when walking compared to when running. It's just the camera going up and down and the sprite of the weapon swinging around ffs.

[wildweasel]

Yes. But what source file controls this? What other source files are affected by changes to it? Are there any compatibility problems introduced? Unforeseen glitches? What happens if a player is using a controller or some other method of analog movement? You (and I) have no clear idea of what the actual procedure of it is like.

I mean, don't get me wrong, I'd like to see this made more customizable as well, but I'm not about to assume that it's trivial to do by any means. If it were that easy, I would do it.

[amv2k9]

Also, what happens when the player is moving at an augmented speed? What happens when the player is flying, or in water? What happens when the player's viewheight is changed? Probably a ton of other things besides.

[edward850]

You even have greater problems, like motion sickness compensation. There's a reason why movement bobbing is a user function first and foremost, and thus whatever control you give to a mod cannot be absolute.

And of course the pinnacle: Who is going to dedicate time to implementing it? Or even has the time?

[Caligari87]

You even have greater problems, like motion sickness compensation. There's a reason why movement bobbing is a user function first and foremost, and thus whatever control you give to a mod cannot be absolute.

My opinion, for what it's worth: If this is done, I think the user variable should be a multiplier, and the mod can set the actual mapunits bob value. That would seem to be the most reasonable option so players can turn it down by a factor, and modders can set their exact intent in the light of their other design decisions, like player height.

Just food for thought.

[winz]

It's depressing that I have to put my project on hold until this is ever implemented. When I started (2 years ago) I assumed 2 years later something would have been done about it already, but no

[Xaser]

Has the problem of exaggerated posting been fixed yet?

[edward850]

It's depressing that I have to put my project on hold until this is ever implemented. When I started (2 years ago) I assumed 2 years later something would have been done about it already, but no

And just who was supposed to have done anything? Nobody here owes you a thing. Let's review what everyone has been doing for the past 2 years:

• Randi: Scripting branch, rewriting mobjs to be compiled into byte code.
• Graf: GZDoom, general maintenance, OpenAL.
• Blzut3: general maintenance, platform compatibility maintenance. Plus I believe he codes GCC.
• Xaser: movement bobbing is not railguns.
• Edward850: nobody actually knows. Who the hell is this guy, and why is all the coffee gone? Netcode and gamestate determinism.
• Edward-san: 64bit/Linux maintenance, also zandro.
• Major cook: A whole bunch of random things, plus his changes are now being closely supervised?

Sans any possible people I likely have missed, which person here was supposed to implement your movement bob control?

[winz]

It's depressing that I have to put my project on hold until this is ever implemented. When I started (2 years ago) I assumed 2 years later something would have been done about it already, but no

And just who was supposed to have done anything? Nobody here owes you a thing. Let's review what everyone has been doing for the past 2 years:

• Randi: Scripting branch, rewriting mobjs to be compiled into byte code.
• Graf: GZDoom, general maintenance, OpenAL.
• Blzut3: general maintenance, platform compatibility maintenance. Plus I believe he codes GCC.
• Xaser: movement bobbing is not railguns.
• Edward850: nobody actually knows. Who the hell is this guy, and why is all the coffee gone? Netcode and gamestate determinism.
• Edward-san: 64bit/Linux maintenance, also zandro.
• Major cook: A whole bunch of random things, plus his changes are now being closely supervised?

Sans any possible people I likely have missed, which person here was supposed to implement your movement bob control?

*your

a lot of people has requested this as well.

[edward850]

a lot of people has requested this as well.

Cool. How does this mean that we are supposed to drop everything and implement this one incidental function? Who the hell are you to demand this?