Simple Motion Blur 1.04 - Bugfix & Velocity awareness

[TDRR]

Came in just to say, on an Intel HD4000, i don't have any of the issues mental and remaker were seeing. I'm thinking it's because i'm using LZDoom and not latest GZDoom, but IIRC in GZD 3.6 i didn't have such an issue either.

[Pixel Eater]

Pleased to hear it! Thanks TDRR

[AL-97]

Honestly, I liked the effect of the 1.03a version better. It was much more subtle. Is that what this velocity awareness thing does? Would it be possible to add a toggle for it in the menu?

[Pixel Eater]

Tis indeed. If you set the walk and jump strength sliders to 1 then it should have the same behaviour as 1.03.

[AL-97]

That'll do it. Thanks!

[Rowsol]

I was just playing some Guncaster and killing a shit load of spiders when I got this error. It spammed the log endlessly and I had to end gzdoom with the task manager. I'm using the latest version with dynamic mode turned on and the other settings at stock aside from the sliders.

I've put many hours into this mod and the only other time I had an issue was when I tried using the Champions mod with GC and the GC adapter. If I recall, using IDKFA cheat resulted in a crash with the log placing the blame on this mod. This was months ago so my memory's hazy so I could be remembering wrong. The reason I bring it up is because I'm not entirely sure it's this mod's fault, even though the log says it is.

For the time being I guess I'll disable it.

Edit: That didn't take long. Right after removing this from the load order I get another crash on the same level. As I thought, this mod has nothing to do with it. I'm not sure why but this mod likes to be the scapegoat.

[Pixel Eater]

Very strange. It sounds like another mod has this one built in, if you're getting that error without this even being loaded. But then I didn't think mods could share the same handler name (MBlurHandler) or GZDoom would have errored out. What happens if you remove all other mods except this one?

[Rowsol]

https://youtu.be/ms1-hLNYe_8
Here's me showing a repeatable crash. Ignore the weird slowness when it comes to showing the game properly, OBS requires about 5 seconds before it starts to show the game in action. In hindsight I should've done this a bit slower, you might have to pause to catch the first error log. As you can see adding this mod to the list only changes the error, the crash isn't caused by this mod.

I should note that I'm using an older version of Champions here, the newest 2.5 doesn't cause this crash.

[Pixel Eater]

Oh okay, I see now. It's trying to do stuff despite a crash already happening. Thanks for the vid!

I'm not sure if this will work but it's an attempt at preventing the message from looping at least:

MBlur1.041.pk3

[Rowsol]

Not only does it not repeat, it doesn't list this mod as the culprit.

[Pixel Eater]

Glad to hear it

Does this mean that the task manager isn't required to quit anymore?

[Rowsol]

Indeed.

[Pixel Eater]

Awesome, thanks for your help Rowsol

[Silentdarkness12]

Could I have permission to pinch some code out of this for an addon i'm working on for a mod? I'll give you credits.

[Nash]

I'd add additional null checks for everything referencing the "mo" of the player, as apparently some people are still getting VM aborts in rare cases.