FoFiX v3.1xx development thread

[kristijan_mkd]

.........mic_features_enabled = false"...........

It has to say : mic_features_enabled = true.

Coders, come on, we already have kind of gameplay, Remove this...

[Dakren]

yeah I know what it is supposed to say, and if you read the post correctly (I know it was long sorry) I said I changed it, I didn't write out what I changed but I did change it to true, and nothing happened.

[blazingamer]

When in doubt, use this.

Code: Select all

[controller]
analog_drum = 0
analog_fx = 0
analog_kill = 0
analog_slide = 0
analog_sp = 0
analog_sp_sensitivity = 4
analog_sp_threshold = 60
key_1 = None
key_1a = None
key_2 = None
key_2a = None
key_3 = None
key_3a = None
key_4 = None
key_4a = None
key_5 = None
key_5a = None
key_action1 = None
key_action2 = None
key_cancel = K_ESCAPE
key_down = K_DOWN
key_kill = None
key_left = K_LEFT
key_right = K_RIGHT
key_star = None
key_start = K_SPACE
key_up = K_UP
mic_device = -1
mic_passthrough_volume = 0.0
mic_tap_sensitivity = 5
name = Mic
two_chord_max = 0
type = 5


Save it as mic.ini within your data/users/controllers folder in FOFiX, then see if you can select it from the controller selection menu (The one in settings, not the lobby one)

[Dakren]

That didn't do the trick, I wasn't able to select it as a controller type, I was able to then set mic to cotroller 1,2,3,4. I am going to just try to competely unistall and reinstall everything, I must have missed something along the way

[jstump91]

mic_features_enabled is no more as of r1637. Microphone features are always available now, as they should have been from the start.

[Dakren]

Ok reinstalled and started fresh, got everything to go, wanted to test the vocals by going to RB Co-op, but seemingly the controller was still disabled in that mode? But, not a big issue I guess, now that everything works well I look forward to contributing, but if anyone knows anything about the microphone controller disabled things, I have searched through the thread and saw some people weren't playing in RB co-op well I have gone there and the same issue still appears.

[jstump91]

r1638 should fix the crashes on multiple instantiation of GuitarScene.

(We still don't know why that happens...)

[blackfish55]

i think that problem relates to my current error. Every time i load a multiplayer game now I get hit with "connection failed" followed by "index out of range" errors as soon as it loads.

latest svn.

[Borisdsp]

i think that problem relates to my current error. Every time i load a multiplayer game now I get hit with "connection failed" followed by "index out of range" errors as soon as it loads.

latest svn.

I have had the same problem in Ubuntu, cause the medata caching, of the setlist. Go to setlist options (in advandec mode) and put it to False.

[blackfish55]

Cache song metadeta turned to off doesnt fix it. and now, probably b/c of latest revision, the setlist goes really slow when trying to select a song.

[Dakren]

I noticed the set list problem also

[jstump91]

• Know your log file. It's called fofix.log and can be found on Windows in the folder you are running the game from, on GNU/Linux in ~/.fofix, or on Mac OS X in ~/Library/Logs. It often contains helpful information about how we can fix the error. Do not post a bug report without it! (If it's long, use the [spoiler] tag so as not to vertically stretch the page.) Posts that simply say "My game is broken please help" are not even a little bit helpful. Please don't do that.

[evilbobthebob]

Sorry, jstump, I don't think that's big enough. Maybe double the size in neon and flashing, people might notice it.

Oh, and I've reported the setlist problem and Qstick is looking into it. Use the issue tracker people. It's not difficult to add an RSS feed to your browser so you can check every issue and revision.

[blackfish55]

sorry!

anyway i resolved the connection lost issue by forcing windows 7 to use capability mode as vista sp1. it's odd considering I didnt have to do this before.

Also, may I suggest for your Python26 guide that for Windows 7 RC users to force all the installations to Windows XP SP3 capability mode? This might be obvious to some but it'd be nice if that were to be documented.

[death_au]

I request an amendment to the FoFiX forum rules (slightly off-topic, but that thread's locked).

• Never tell us you are running the latest version. Always specify the revision number if you are running from svn.

For anyone who's mic isn't showing up, double-check that all the modules are installed correctly. Specifically pyAudio.
(this was my mistake the first time I tried to use mic features. Just putting it out there)