FFR Suggestions

[Velocity]

Originally Posted by Izzy

Instead of making that part of the database can't you just put that in the replay text?

That's what I mean.

[Shikari]

Not a great deal, but maybe it'll be good for profiles: Raising filesize limit from 512KB to, I don't know, 1 MB. Or a 700-ish number.

[Izzy]

Velocity says there has been storage space issues recently. I think limiting file sizes is one of the easiest ways to combat this problem. Probably wont change until they have a ton of extra space.

[TC_Halogen]

Originally Posted by Shikari

Not a great deal, but maybe it'll be good for profiles: Raising filesize limit from 512KB to, I don't know, 1 MB. Or a 700-ish number.

You can use JPEGs for profiles too - the one on my profile is pretty detailed but it's only around 470KB.

I heard from someone on staff that there was going to be plans on some sort of a storage expansion to 3TB total space?

[Shikari]

Originally Posted by TC_Halogen

You can use JPEGs for profiles too - the one on my profile is pretty detailed but it's only around 470KB.

Yeah, I thought JPEGs were smaller than PNGs, but I was wrong. That profile image I showed at DF's chatroom is bigger at JPEG than PNG, but I'll try it anyway.

foxfire667 compressed this image to 507 KB, but FFR keeps saying that "filesize is too large".

[Izzy]

In general jpegs are smaller file sizes then equivalent uncompressed png's, but isn't always true.

[jimerax]

usually pngs look a lot better than jpgs though.

[spm515]

Just had a good idea but the coding involved might be complicated. Make a varient on the auto-fail system that deals with points instead of accuracy. I.E. I'm in a tourney and need to get x amount of points to stay in. I set the point autofail to that amount and if at any point in the song it is no longer possible to acheive that goal it quits.

[Izzy]

I could write the psuedo code for that if we used Raw Score...

[Velocity]

My engine already has points autofail.

[bmah]

For some reason, if I press the enter key when using the search function for Velo's engine, then try to search a song, my results will always remain blank. That is, until I either restart the engine or play a song and go back to the main menu. (I pressed the enter key because I thought that would execute my search, but it doesn't.)

Also, the arrow buttons when scrolling through the genre wheel seem less responsive; I have to click a few times (or click within a few seconds of each other).

Finally, if you were looking through the settings menu while you are loading a song, and that song loads, the game will commence, despite the fact that the settings menu is still in the way. You can't remove the settings menu until you press the "settings" button again which is only available at the main menu. If one hasn't decided on the settings, the settings menu should disappear if a song has loaded (presumably with the previous settings you've had).

[XCV]

(past most of the boring object-creation)

NumGoods * 25 + (NumAvgs + NumMisses) * 40 + NumBoos * 5 = CurrentScoreDeficit
Lbl thisdoesn'tneedaname
If Keytap {
NumArrows * 50 - CurrentRawScore = ScoreDeficit
If ScoreDeficit > MaxScoreDeficit {
Fail()
}
}
Goto thisdoesn'tneedaname

Some minor errors in the code, I'm sure, and it's written in some bat**** combo of calculator BASIC and JS, which is the way I think, but eh the idea gets across

Course, if Velocity just copies and pastes whatever he does in his engine, then that's totally unnecessary.

[Izzy]

Originally Posted by Velocity

My engine already has points autofail.

But I don't think it's the way he is asking. His idea is rather complicated.

[spm515]

Originally Posted by Velocity

My engine already has points autofail.

I don't quite get how it works though. I tested on 'Infection'. The AAA score being 886450. So I set the points autofail to 886449, meaning that if I get anything less that perfect it should fail me, but it didn't. Conversely I set is to 10,000 and reached that amount and also didn't fail like the accuracy autofail would.

Edit: How would this coding work as far as lag btw? Running a multistep calculation at every keystroke can't be good. vROFL is gonna start crashing computers.

[Izzy]

Once the game is loaded it is running from your own cpu. It would be a negligible amount of calculation for any computer made in the past 5 years. It could easily lag on older computers though.

[duddychuck@yahoo.com]

6 key engine please

[colt.45]

Just a suggestion but maybe, the amount of arrows we've hit TOTAL, out of all of our games ever played.

Not sure if this would be possible at this point, but just an idea!

[Velocity]

Originally Posted by bmah

For some reason, if I press the enter key when using the search function for Velo's engine, then try to search a song, my results will always remain blank. That is, until I either restart the engine or play a song and go back to the main menu. (I pressed the enter key because I thought that would execute my search, but it doesn't.)

Also, the arrow buttons when scrolling through the genre wheel seem less responsive; I have to click a few times (or click within a few seconds of each other).

Finally, if you were looking through the settings menu while you are loading a song, and that song loads, the game will commence, despite the fact that the settings menu is still in the way. You can't remove the settings menu until you press the "settings" button again which is only available at the main menu. If one hasn't decided on the settings, the settings menu should disappear if a song has loaded (presumably with the previous settings you've had).

I haven't added enter key search as you stated, the reason why it fails after using a enter key, is it's trying to match songs including the line break.

Genre arrows have indeed slowed down, not sure what's causing it, but I'll look into when I get home.

The autoclose of settings broke at one point and needs to be fixed, should be easy.

Originally Posted by spm515

I don't quite get how it works though. I tested on 'Infection'. The AAA score being 886450. So I set the points autofail to 886449, meaning that if I get anything less that perfect it should fail me, but it didn't. Conversely I set is to 10,000 and reached that amount and also didn't fail like the accuracy autofail would.

Score is done differently, it's a total amount that you have missed in raw scoring, one way to view this is to hover over the score while playing a song to display the raw score missed. This is also the number that shows up on the score screen as missed. If you were to set the score fail to 1, you would fail out for anything besides perfects as anything else adds to the lost total.

[8 Hour Whore]

I want that Perfect/Good/Avg/Miss/Boo pull down on the replays to be implemented in the real thing.. Make it optional or something.. Would be awesome cause I fail at seeing my goods cause I actually have to read "good" in order to know it happened.

[Velocity]

Originally Posted by 8 Hour Whore

I want that Perfect/Good/Avg/Miss/Boo pull down on the replays to be implemented in the real thing.. Make it optional or something.. Would be awesome cause I fail at seeing my goods cause I actually have to read "good" in order to know it happened.

Both replays and the engine use the same swf. In the settings it's called "PA Window"