the value displayed on music select is generated and saved along with the cache file written to the disk however the score specific rating at evaluation is recalculated specific to the score percentage you attained and for whatever specific set of notes you played (in case cache isn't updated or you use file altering mods like no jumps etc)
the latter is what is used to aggregate into your player score
if you can compile the game you can get the updates now
xwidget is on vacation or some shit so there wont be another full release for at least a few days minimum
or
technically the current release has the capability to already do what you want
but the theme is still coded to pull values from the old lua chartkey system not from the game
so you could just make minor edits to the theme
I might go full autism tomorrow and look into your code and fix it so it calculates things for 6k. before waifu, sitting on a 6k chart would show full data for it. now, i can't see notecounts and graphics don't load at all. this has been an issue for a while but I don't think I ever brought it up because I think that I'm the only person that plays 4k at a level high enough to warrant the use of wife scoring and j5 play, AND plays 6k at a level high enough to warrant the use of wife scoring and j5 play. I know what to expect out of nearly every 6k chart, given that I've probably played the majority of them. not seeing notecounts is a non-issue to me. but it could be an issue to those that use your fixes/builds and would like to try playing 6k here and there.
unless looking into your code to fix things for 6k is an effort in futility; if so, pls let me know so I can spend my day off drinking a lot of coffee and posting a 4k score thread before I crash.
eyy yeah i haven't forgotten about your proposal, i meant to setup different curve approaches earlier on before getting sidetracked with the work on the custom build and compare them side by side
the good news is now that i'm requiring the custom build for my theme anyway i can just build the ms scoring system into the base game, the bad news is i have to build the ms scoring system into the base game
after the trial run with the current system i'll say i'm not particularly thrilled with the result and i think a better solution can be found (i originally wanted to model off normal distributions and both you and another person have suggested methods based on it) so building them into the game and running them side by side is the next step to be taken
but im not gonna lie its prolly gonna be another month before i get any tangible work done there
For the Waifu system, I proposed using a Normal Distribution to fit the distribution of hit timings, and use the fit to give a value that represents the overall performance in a play. This post will explain that system with more detail.
In each chart there are both objects that have timings (regular arrows), and objects that have no timing window (hold notes, mines, etc...). Notes that have no timing windows remain unchanged in this proposed system (except for changing their point values, like the current Waifu system does with respect to the old DP system).
The total points obtained from objects that have a timing window is:
Number_of_Timed_Objects * Representative_Points
"Representative Points" is a value that represents the overall accuracy of the notes hit on the play. It's max value is 2 (hitting everything perfectly), and goes down to -8 (missing everything).
Calculating the Representative Points
1) Take the error in milliseconds of each note that was hit.
Take the sum of the squares of those errors (that value will be referred as "s"), and the count of the hits and releases that weren't misses (referred as "k").
2) Count the amount of misses notes (referred as "m").
3) With that information, calculate the Normal Distribution with zero mean that fits the data the best, obtaining the standard error Sigma (details of the calculation below).
4) Use sigma to calculate the "Representative Points"
Erf is the Error Function (while Erfc, appearing below, is the complementary Error Function). Each variable is the upper limit of the timing windows of a certain Judge setting (for example, the BOO timing window is 150ms in Judge 5). The value is equal to the average amount of DP points obtained per object with the Normal Distribution we found.
Note that this formula just defines a scale for what we are trying to measure, and the only way it affects balance is how Objects that have timing windows are weighted against objects with not timing windows (the function was chosen so the balance between both kind of objects remain the same as in the previous system). For making scores directly comparable between different Judge settings, it's better to use constant values for the timing window values (for example, the ones belonging to Judge 5), regardless of the setting the user set.
Using the parameters of Judge 5, the scale looks like:
Typical AAAA scores have a sigma of about 7ms (7ms has a value of 1.999999915 RP).
Typical AAA scores have a sigma of about 12ms (12ms ->1.998221949 RP)
Typical AA scores usually are about 25ms or less (25ms -> 1.863658612 RP)
Calculating the Standard Error "Sigma"
The variables are:
s = Sum of the squares of the timing errors of hits that weren't a Miss.
k = Count of hits/releases that weren't a Miss.
m = Count of Misses.
T = Upper limit of the timing window for a BOO, in ms. This timing window represents the limit of the error for a note to be considered "hit", any note hit outside this window, or not hit at all, is considered as "being hit anywhere outside the window" for the Maximum Likelihood Estimation.
Case without Misses or Hits
This is undefined, default to 0 Representative Points or something.
Case with only Misses
In this case, Sigma approaches infinity, the Representative Points are -8.
Case with only Hits
Sigma is simply
Case with Misses and Hits
Sigma is the positive number that solves the equation:
The equation doesn't have a simple closed form solution, but it can be easily solved numerically with Newton's Method (since the function to find a root for is convex and monotonic).
A first approximation of Sigma (that always is smaller than the real solution) is:
With BS = T/Sigma.
Function to find the root for:
It's derivative:
Note: Because of numerical errors while using double floating-point numbers to calculate the functions, for high values of BS, it's more accurate to use a series expansion near Sigma=0, instead of attempting to calculate their values with the exact formulas.
If BS > 7, then:
If BS >20, then:
The, starting with the initial approximation for sigma, iterate with Newton's Method until F[Sigma] is small:
Sigma[n+1] = Sigma[n] - F[Sigma[n]] / F'[Sigma[n]]
Testing this algorithm, it takes about 0.8ms in average to find an accurate value for Sigma (with an absolute error of 10^(-7)).
Check up in the thread, to me it sounds like you have SM set to uncapped FPS in the menu, so its getting real high and making your gfx card overwork (I'd feel thats why it makes the high pitch noise). (that also explains why it only happens with the mod and not default 5.0.12)
I believe theres a setting in the theme.ini to cap FPS in menu, Mina recommended 300 i think
EDIT: np mr one post, see ya later fam.. maybe someday u will post again, i hope it fixed it, god bless <3
I see, that makes sense. Set it to 300 and the noise went away, thanks.
I rewrote your noteskin to make it 1 file, if you find any bugs with like I did the port wrong or you want to change anything please tell me and I'll do it for ya
oh shit thanks i was going to do this but never got around to it
@youngjii dinglesberry pretty much nailed it
basically the game spends much less time figuring out what to render and a lot more time actually rendering it, the result is higher fps and smoother gameplay however if you leave the fps uncapped it'll basically tax your gpu to the maximum, particularly at the menu screen where nothing is going on and you might hit 5000+ fps
i'll see about having the non-gameplay framerate capped by default
Got a weird issue with this custom build that's not related to gameplay or anything like that but actually my computer itself. On the main menu with this custom build (screen that says Til Death with the various options) and only while the window is active, my computer hardware outputs a quiet high pitch sound that sounds like a tea kettle going off, albeit much quieter. Only happens on the main menu screen (none of the options, gameplay, etc.) when the window is active, and only on this build. I can click out of the window and the sound stops, then click back in and it resumes. Cycled through different themes and the issue persisted with some themes having a quieter or louder sound than others, with the default theme being the quietest and Til Death being the loudest of what I looked through. On normal 5.0.12 this issue isn't present. Obviously not a big issue at all but it's just something I happened to notice when I had Stepmania open without headphones on for the first time in a while.
Check up in the thread, to me it sounds like you have SM set to uncapped FPS in the menu, so its getting real high and making your gfx card overwork (I'd feel thats why it makes the high pitch noise). (that also explains why it only happens with the mod and not default 5.0.12)
I believe theres a setting in the theme.ini to cap FPS in menu, Mina recommended 300 i think
EDIT: np mr one post, see ya later fam.. maybe someday u will post again, i hope it fixed it, god bless <3
Last edited by Dinglesberry; 09-30-2016, 05:27 PM.
Got a weird issue with this custom build that's not related to gameplay or anything like that but actually my computer itself. On the main menu with this custom build (screen that says Til Death with the various options) and only while the window is active, my computer hardware outputs a quiet high pitch sound that sounds like a tea kettle going off, albeit much quieter. Only happens on the main menu screen (none of the options, gameplay, etc.) when the window is active, and only on this build. I can click out of the window and the sound stops, then click back in and it resumes. Cycled through different themes and the issue persisted with some themes having a quieter or louder sound than others, with the default theme being the quietest and Til Death being the loudest of what I looked through. On normal 5.0.12 this issue isn't present. Obviously not a big issue at all but it's just something I happened to notice when I had Stepmania open without headphones on for the first time in a while.
I rewrote your noteskin to make it 1 file, if you find any bugs with like I did the port wrong or you want to change anything please tell me and I'll do it for ya
Leave a comment: