The smartest person in the world wrote:Remember me? I'm the one blah blah blah
errorboy6090 wrote:The smartest person in the world wrote:Remember me? I'm the one blah blah blah
I said you need 500 MB of RAM. That is not the only solution. (I recently figured out my Mac has over 700 MB.)
But I need help. I need my vocals. I tried everything, yet my vocals are extremely laggy.
How do I get my vocals to be less laggy!?!?!?!?!?!? I'd hate for people to ignore me once again,
Ambiguity wrote:errorboy6090 wrote:The smartest person in the world wrote:Remember me? I'm the one blah blah blah
I said you need 500 MB of RAM. That is not the only solution. (I recently figured out my Mac has over 700 MB.)
But I need help. I need my vocals. I tried everything, yet my vocals are extremely laggy.
How do I get my vocals to be less laggy!?!?!?!?!?!? I'd hate for people to ignore me once again,
What do you mean by laggy? Just so you know, the current way FoFiX handles vocals isn't very stable, it causes bunching of words, missing pitch bars, and the needle is kind of jumpy.
errorboy6090 wrote:Not very stable is right. On my faster computer, I have to be off-key to get 100%.
Under audio settings, there are two options: "pypitch" and "pypitchanalyser".
I changed it, still using my Logitech mike, and it works fine now.
Though the arrows are still kinda jumpy, but at least the pitch is on.
onmouseout="this.style.cursor='default'" alt="" /> Ambiguity wrote:errorboy6090 wrote:Not very stable is right. On my faster computer, I have to be off-key to get 100%.
This won't improve the other stuff I mentioned but someone said this on the vocal issue:Under audio settings, there are two options: "pypitch" and "pypitchanalyser".
I changed it, still using my Logitech mike, and it works fine now.
Though the arrows are still kinda jumpy, but at least the pitch is on.
I believe analyzer is the one he changed it to.
errorboy6090 wrote:OK, Where can I find these two options?
onmouseout="this.style.cursor='default'" alt="" /> Ambiguity wrote:errorboy6090 wrote:OK, Where can I find these two options?
Options>Advanced Options>Debug Options> The last option is the one you want to modify.
No Way wrote:Answer wrote:Ask Questions wrote:OK, Where can I find these two options?
Options>Advanced Options>Debug Options> The last option is the one you want to modify.
Woah, I was just there. I'll try it.
Bad Error! wrote:Runtime Error!
Program: <File where FoFiX is>
The application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
errorboy6090 wrote:Ambiguity wrote:errorboy6090 wrote:OK, Where can I find these two options?
Options>Advanced Options>Debug Options> The last option is the one you want to modify.
Woah, I was just there. I'll try it.
-- Edit: Sat May 29, 2010 8:11 am --
2 problems.
1: Way harder for the mic to get signal. It is getting all jumping
2: In the middle of the song, I got:Bad Error! wrote:Runtime Error!
Program: <File where FoFiX is>
The application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
At least I did Better at the song
onmouseout="this.style.cursor='default'" alt="" /> slashfan7964 wrote:I personally have a bad graphics card, and I can get it to run at heavy settings really smooth. Here's how.
Note: You must download everything here or this will NOT work.
Required Stuff
FoFiX v. 3.121 (Installer)
Animated Stages Part 1 (Self-Extracting Archive)
Animated Stages Part 2 (Self-Extracting Archive) [Combine Part 1 and 2 in the same folder. Name the folder "animated stages" without the quotes.
Rock Band 2 Theme (Not What You Think It Is) Self-Extracting Archive----This theme has been heavily modified for this project only. Download for other use is ok.
Guitar Hero 5/Band Hero Behind Neck, With Rock Band 2 Overdrive String Flash Overlay
halberdmetal wrote:Okay this doesn't work.
I've installed and ran gamebooster before playing the game. I use the uberlight theme with 400x300 resolution, "high" process priority, "pure speed" performance and the game still sucks cancerous testicles.
onmouseout="this.style.cursor='default'" alt="" />
blazingamer wrote:I still don't like you people that say Python is the reason why the game goes slowly. It's not python that makes the game slow, the only thing that is slower in python than c is the compile time and the variable type signing (since it's dynamic) but if you keep variables the same type the whole time then it won't go slower than c. The only reason why these C versions that people keep making are faster is because the code is seriously bare bones. If you look at all the different passes and modules that FoF has to go through compared to one of those games, in addition to the way math is handled, you'll see why FoFiX lags so much. The code is written from an excessively modular base that is poorly written for what it needs to do, it could be simpler and as a result faster. Not only that, but most of these C games are written in directX and are windows only, most graphics cards are optimized for directX over openGL, so of course it's going to run faster if it's directX, the only reason why FoF is openGL is because the developers wanted it to be cross platform.
So, before you start blaming python for the reason why FoF is slow look at the code yourself and see why. If it was written in C except everything was kept in tact the same way it is written in python, it will go just about as slow, maybe a just maybe little faster just because C can do math faster.
Asskickulater wrote:that leads me to ask this.. why dont you guys go back and start fixing the bad coding issues before adding more features?
onmouseout="this.style.cursor='default'" alt="" />Users browsing this forum: Bing [Bot] and 5 guests
