Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: asyikarea51 on May 12, 2007, 03:03:10 am

Title: What the hell... (Comm window)
Post by: asyikarea51 on May 12, 2007, 03:03:10 am

I don't know what is going on or how (let alone when) it happened, but recently whenever I play FSO, my comm window keeps popping up at random, and in random menus too. Sometimes the main "Message What" menu appears, other times it shows a list of ships (or wings).

Totally random frequency and menu. Sometimes the menus show up a good 15-30 seconds apart, other times it comes up once every 0.5 seconds.

It's getting on my nerves since it happens on both multi and SP (even worse when I'm typing or receiving messages and I can't see them). :mad:

Anyone have an insight to the issue?

Title: Re: What the hell... (Comm window)
Post by: jr2 on May 12, 2007, 03:15:25 am

Check your config (F2)... is there a joystick/mouse button bound to the comm menu?  Is the "C" key on your keyboard damaged?

Title: Re: What the hell... (Comm window)
Post by: asyikarea51 on May 12, 2007, 03:20:36 am

I unbinded my C key already, but randomised menus keep coming up... randomly.

AFAIK I do not use a joystick, and my mouse is only used for turning and attacking (I did try pressing buttons, but nothing that affects the comm menu took place).

EDIT: Though I did not unbind the Shift+(so-and-so button) key commands off my profile, I loaded up NFSMW and tried both Shift keys (which I use for nitrous).

No mysterious self-triggering going on. :doubt:

Title: Re: What the hell... (Comm window)
Post by: jr2 on May 12, 2007, 03:47:20 am

So, in the Launcher, Joystick is set to no device?

Title: Re: What the hell... (Comm window)
Post by: asyikarea51 on May 12, 2007, 03:50:56 am

Usually I left it at Force 0 (default - to resolve problems only), but now I set it at "No Joystick".

I'll go test that out now, see if it matters. :)

edit: Nope, no luck. :doubt:

Title: Re: What the hell... (Comm window)
Post by: asyikarea51 on May 13, 2007, 09:58:30 am

Update: Though I'm still not certain, I think the problem is related to the "Voice recognition" checkbox in the Launcher. I turned it off and didn't get any mysterious auto-comm coming up... well, at least until I force-quit out of the game.

Come to think of it, I think the menu went beserk on the AI comm messages... must be my cable connections. But then again shouldn't it be impossible? I mean, I left my microphones on mute...

Which reminds me - does anyone know how to get voice working in FS2O? As in, voice messages for multi games, like in HL2 or CSS where you hold down +voicerecord for a constant feed and stuff? The in-game menus complain of DirectSoundCapture among other things.

Title: Re: What the hell... (Comm window)
Post by: jr2 on May 13, 2007, 02:11:41 pm

Quote from: asyikarea51 on May 13, 2007, 09:58:30 am

Update: Though I'm still not certain, I think the problem is related to the "Voice recognition" checkbox in the Launcher. I turned it off and didn't get any mysterious auto-comm coming up... well, at least until I force-quit out of the game.

Come to think of it, I think the menu went beserk on the AI comm messages... must be my cable connections. But then again shouldn't it be impossible? I mean, I left my microphones on mute...

Which reminds me - does anyone know how to get voice working in FS2O? As in, voice messages for multi games, like in HL2 or CSS where you hold down +voicerecord for a constant feed and stuff? The in-game menus complain of DirectSoundCapture among other things.

Hmm... fiddle with these settings; I bet one isn't set right: (prolly something like having the AUX unmuted or something... I'm not sure, anyone who knows more about this feel free to input / correct me.)

(http://img258.imageshack.us/img258/893/volume1sg0.th.jpg) (http://img258.imageshack.us/my.php?image=volume1sg0.jpg)

(http://img107.imageshack.us/img107/1640/volume2yz9.th.jpg) (http://img107.imageshack.us/my.php?image=volume2yz9.jpg)

(http://img474.imageshack.us/img474/2391/volume3mq0.th.jpg) (http://img474.imageshack.us/my.php?image=volume3mq0.jpg)

Title: Re: What the hell... (Comm window)
Post by: Nuke on May 13, 2007, 03:05:32 pm

or perhaps you have voice control on and didnt know about it :D

*reads* wait youve figured that out already. good. anyway to get voice rec to work, you need the speech sdk, not sure where you get it, and you have to train a profile. after about 15 minutes of training, it should be enough to work properly.

Title: Re: What the hell... (Comm window)
Post by: asyikarea51 on May 13, 2007, 11:40:01 pm

You mean I still need the speech SDK and stuffs, even for player-to-player chatter? I'm not interested in player-to-AI communications (but I might try it at least once for kicks :lol:). :doubt:

Guess I've figured out my problem - I had voice recording turned on, and at the same time I have (yet another) finicky wire connecting the speaker jack to the microphone jack. This board has two speaker jacks and two mic jacks and they can be configured in several ways based on options available in a setting program.

So when MSN voice conversations aren't enough, I can just go play FS2 with MSN on and let my friend listen to a missile frenzy while he's in the middle of class break... LOL

Should be it, but nevertheless I'll keep a mental note of the problem. Basically my error, not an SCP one. I love analog.

Title: Re: What the hell... (Comm window)
Post by: Mongoose on May 14, 2007, 12:30:58 am

No, you don't need the speech SDK for the multiplayer audio chat function.  It's only necessary if you want to use the voice recognition feature to give orders to your wingmates.

Title: Re: What the hell... (Comm window)
Post by: asyikarea51 on May 14, 2007, 12:33:15 am

Quote from: Mongoose on May 14, 2007, 12:30:58 am

No, you don't need the speech SDK for the multiplayer audio chat function.  It's only necessary if you want to use the voice recognition feature to give orders to your wingmates.

Noted. But the game says that my microphones don't support DirectSoundCapture or whatnot and I haven't been able to get around it. Any ideas? :confused:

Title: Re: What the hell... (Comm window)
Post by: jr2 on May 14, 2007, 01:02:26 am

Right-click volume control > Adjust Audio Properties
Under the "Audio" tab, what is your Sound Recording Default Device?  How about in the "Voice" tab?
I don't know exactly, but I'm just running through the same things I would check if this was my problem.  This may not help at all, but perhaps...

Title: Re: What the hell... (Comm window)
Post by: Nuke on May 14, 2007, 04:45:28 am

you only need the sdk if you want to use voice recognition. actually you dont need to have it if you have office xp or anything else built with the ms speech engine. all it does is provide the control panel interface for the voice trainer. it has nothing to do with voice messageing that came stock with freespace. i dont know if the built in voice communication system still works or not.

but if you cant make it work, just disable the feature in the launcher. that should stop the erratic comm panel behavior.

Title: Re: What the hell... (Comm window)
Post by: asyikarea51 on May 14, 2007, 11:10:33 am

Quote from: jr2 on May 14, 2007, 01:02:26 am

Right-click volume control > Adjust Audio Properties
Under the "Audio" tab, what is your Sound Recording Default Device?  How about in the "Voice" tab?
I don't know exactly, but I'm just running through the same things I would check if this was my problem.  This may not help at all, but perhaps...

(Brand name) high-definition audio input. Same thing in the voice tab, but no luck in getting player-to-player voice messaging working.

If there's no solution to the problem, I don't mind. I can type out the messages anyway, unless I'm playing in a server where I do not recognise the people in person (usually pros, where I get shot down while typing, but at least the person who did that to me on my previous game apologised, so that's okay for me so long as he/she's sincere about it. :) :doubt:)

@ Nuke

Yep, feature disabled, so far so good. :)