What keeps you using 3.95?

[Kyzentun]

Originally Posted by Frank Munoz

you nitpicked an entire post made from halogen and targeted minacious, about an aspect ratio complaint.
ignoring the entirety of what the whole post was about.

I picked out the stuff that could be identified as an actual issue. And ignored the part where apparently Halogen thinks every problem he had with SM4 6-7 years ago applies to SM5.

Then Minacious comes along and says that SM5 has absolutely no improvements. When someone says that, it's clear they aren't going to consider anything that is done to be a reason, because they're not looking. So what is there to actually do for someone like Minacious? I try to pick one thing that might be fixable, and he responds with personal insults. This isn't a guy trying to solve problems, or someone who even wants problems to be solved. He is however, a prime representative of the FFR community.

I could list improvements made to SM5. The list would be longer than this thread just to cover the last 2-3 years. 90% of the features you guys cheer about in ca25nada's theme thread wouldn't even be possible without the work I personally put into improving the engine. Most of them were made because I wanted some improvement in my own theme and the engine got in my way.


Halogen: Your insight didn't list much of "this is an actual problem". It was "people use 3.95 because they use 3.95". Not even a single customization listed in detail, then you invented a problem that doesn't even exist as a reason not to use SM5's edit mode.


Basic modifications: In 5.1, there's an entire submenu dedicated to adjusting the notefield. Hidden/sudden, offsets for both, receptor offset, field zoom (on all three axes), field rotation (on all three, though only x rotation is useful), disabling the white flash on hidden/sudden (it's not hardcoded anymore), and other more obscure stuff.

Online mode: I don't play it, personal insults aren't going to make me want to work on it. If this was a paying job, I'd ask my boss to throw you out of the building.

Windows optimizations: One guy reported a crash that went away when he manually specified a sound driver that besides WaveOut. Now he's gone and I have no way to investigate why WaveOut crashes for him. This is typical of problems that occur only for windows. I can't reproduce them for myself, the person experiencing them can't test, explain, or investigate enough to make it possible to fix the problem. So it doesn't get fixed.

This probably bears repeating: I don't work on things I can't test. If I can't test something and make sure it works, or find someone reliable to test it for me, I don't make it or touch it. If that means you're left out in the cold, tough luck. Find a windows dev to solve the problem, or step up and do it yourself (like I did for every feature I wanted).

Timing: Some day, when I have nothing useful whatsoever to do, I'll investigate why this judgment graph has weird spikes instead of a smooth curve. If Minacious and Halogen are typical examples of the competitive scene, it's not worth investigating something that might indicate presses being misjudged by a few random milliseconds. The insults do you no favors.

SM6: I make no promises about something I haven't even started work on yet.


There, I wasted some time addressing more issues in detail.