I just noticed the game lets you restart a song with the options open. I set the restart key to 4 and then typed a 4 in the current speed and then the song restarted lol. And then the mouse disappeared but I couldn't see anything useful with the options in the way. Then I changed the restart key to Q and then that also restarted the song. Can you please disable the restarting of the song with the options open?
So... I stopped playing much FFR for awhile as my life got very busy. Now that I have a bit more "spare time" I decided to take a hiatus from my hiatus. When I returned I cranked up Velocity (my engine of choice) I noticed that I had some serious lag going on and nothing I did seemed to help except playing on the new R^3 engine. In the end I blame my internet connection.
So I decided that now was the time to switch to R^3 since I would have a skilldrop anyway... and OMG. I feel like it is 2010 all over again. I get 50+ Goods on mid-50's and can't even FC Macau Underground (a 63). I played {Firestorm} just now and I ended up with a beautiful 27-2-0-2 or something. I am a mid D4 player, bear in mind. (at least... I was.)
Did it take others awhile to adjust to the new engine? Because i've been at it for awhile now and.... skilldropping this far is alarming!
Raining Nails: did you change your offset appropriately? By default, a user with an offset of 0 on the Legacy/Velocity engines will have a global offset of 2 and a judge offset of 1.
Receptor spacing and screencut, as YOSHl mentioned, can be used to replicate the engine.
Also, a potentially impossible suggestion for arcnmx: a lot of people might be having issues moving over from Velocity due to visual differences that may be attributed to things like:
- receptor flashing: when an arrow is properly timed and hits the receptor, it makes a noticeable gain in size
- screen size: while the vertical game size can be manipulated, the horizontal size cannot be manipulated in a way that doesn't scale overall game downward, giving it the same long feel
- noteskin seems a bit more sharp and people might not be used to that either
Would it be possible to make an "old" style function that reduces the window size/receptor flash to more appropriately emulate the Velocity/legacy feel? It might seem like a dumb suggestion, but the intent is to get everyone using the new engine -- bringing the old appearance/feel of the older engines to the newer engines presents the opportunity to remove engines with deprecated coding methods.
Also, a potentially impossible suggestion for arcnmx: a lot of people might be having issues moving over from Velocity due to visual differences that may be attributed to things like:
- receptor flashing: when an arrow is properly timed and hits the receptor, it makes a noticeable gain in size
- screen size: while the vertical game size can be manipulated, the horizontal size cannot be manipulated in a way that doesn't scale overall game downward, giving it the same long feel
- noteskin seems a bit more sharp and people might not be used to that either
Would it be possible to make an "old" style function that reduces the window size/receptor flash to more appropriately emulate the Velocity/legacy feel? It might seem like a dumb suggestion, but the intent is to get everyone using the new engine -- bringing the old appearance/feel of the older engines to the newer engines presents the opportunity to remove engines with deprecated coding methods.
Comment