Need a little help 2 issues

[thommydogg]

the first issue I have is :

I program buttons in game and none of them seem to follow me into the game, am I missing something and will profiler (x52) work in game, if so how do i get it to work?

2ns issue is:

I have tried setting up a co-op with my buddy but he can't start his plane, and again my programmed buttons dont seem to work...any help would be great, this seems like a kick-butt game but i am getting discouraged here.:cry:

[cichlidfan]

the first issue I have is :

I program buttons in game and none of them seem to follow me into the game, am I missing something and will profiler (x52) work in game, if so how do i get it to work?

2ns issue is:

I have tried setting up a co-op with my buddy but he can't start his plane, and again my programmed buttons dont seem to work...any help would be great, this seems like a kick-butt game but i am getting discouraged here.:cry:

 

1. Assuming the installation is OK then the most likely cause for the first issue is setting controls for one mode and playing in another. When you are in the Options>Controls screen, there is a pulldown in the upper left. Choices are Free Camera, Game Mode and Sim Mode (or something similar). If you set your controls in Game mode and the play with realism settings for Sim mode then your controls will not work.

 

2. Create your profile for the X52. Load the profile. Start the sim. You will, of course, need to clear all joystick button settings in Options>Controls to avoid conflicts. Get and read the manual for Saitek's SST software for more details.

 

3. It would be difficult to guess what your friends startup problem is but if you mean the engine won't start with the appropriate keyboard command...then the first thing I would check is to make sure his throttle is all the way back to idle. The engines will not start if the sim senses that the throttle is not in the correct position.

 

Hope that helps and welcome to the forum.;)

[EtherealN]

To figure out what is happening with the startup, have your friend do this:

 

1) Start cold and dark.

2) Open control display (Right Control and Enter).

3) Perform start attempt (slowly and carefully to make sure we can follow what's being done).

4) Exit flight.

5) In the debrief screen, select "Save Track".

 

Upload that track here and we can look. There's a lot of things that can cause a startup to fail, cichlidfan's suggestion being one of them but there are others as well. So seeing it is better than running through a list of plausible guesses. :)

[thommydogg]

thanks folks...turns out was operator error on his end