I use FSUIP4 to control my joysticks and have them disabled in the fsx joystick settings of the configuration page.  I put the JOYSTICKS=0 line in the [CONTROLS] section of the fsx.cfg file.

 

About 50% of the time I load FSX the JOYSTICKS=0 line is gone from the fsx.cfg and the controllers are enabled again in the program.  This cause conflicts until I go in and disable them again and put the line back in the fsx.cfg.  I have experimented with adding comments to the other lines in the [CONTROLS] section and they disappear too.  It's like the entire section gets gets replaced every so often.

 

Any ideas what causes this? Fix?

 

Thanks

Rick S.

Please check the Windows 8 forum here at AVSIM.  This is a known problem.

 

Best regards,

Oh, thanks Jim

 

Rick S.

Sorry Jim, that is a completely different issue.  Man, it took me forever to read thru that thread.  I had a similar issue with P3D but FSUIPC4 and the power management thingy in the device manager along with the changes to the registry posted somewhere around here fixed it for me.

 

My deal relates to the FSX.cfg [CONTROLS] section getting completely rewritten on occasion; no, not every time but maybe 50% or so?

 

Rick S.

Am I the only one having this problem?

 

[CONTROLS]
Controls_Default=Standard
Controls_Current=Standard
KBDAIL=64
KBDELEV=64
KBDRUD=64

JOYSTICKS=0 <<<<<<<This line DISAPPEARS about 50% of the time that I load FSX

 

When it disappears the "enable Controllers" check box on the Settings-Controls screen is ticked causing FSX to try to use the attached joysticks natively.  I want FSUIPC4 to control them.

 

Thanks

Rick S.

Maybe a permissions issue, Rick. (I'm not saying it absolutely is, but it may well be..)    

 

What you need to do is to check the Standard.xml file at (Win7, I haven't any idea where it's kept in W8)

 

C:\Users\{your user id here}\AppData\Roaming\Microsoft\FSX\Controls\        "Standard.xml" is where all controller and key settings are kept.

 

Open it up with an xml editor - even Notepad will do. (NotePad++ is a great replacement - just Google for it), - and then remove all references to the controller you're using, then save it. If you have problems with saving it - it's probably because you don't own it. In that case - Google for a little applet called "Take Ownership", install it - then you can rt-click on any file/folder, select "take Ownership" and this may well fix it for you. If not, you may have to rt-click on the file, and open up Properties, and then add yourself in, giving yourself the correct (Full Control) and then saving it.

While you're there you can also select Advanced and manually make yourself the owner of the file or folder. Of course - make a backup of the original first. You can do the same thing for the FSX folder and any other folder which is giving you permissions pain. Once you've done that - start FSX, and put the controller into FSUIPC.

 

Hope this helps.

 

pj

Thanks for answering Paul,

 

I don't have a permissions problem and I never thought about deleting the joystick references in the STANDARD.XML.

 

If I understand what you mean, delete all references to my JOYSTICKS, leaving the KEYBOARD and MOUSE? sections intact?

 

Of course, a backup is already saved.

 

Thanks

Rick S.

I deleted all of the JOYSTICK sections in the STANDARD.XML and reran FSX.  It all worked okay but after closing down FSX and looking at the STANDARD.XML file I found all the references to my JOYSTICKS repopulated?

 

The JOYSTICKS=0 line in the FSX.CFG was still there; but it is about half of the time as is my history.

 

Hmmmm...........

 

CONTROLS]
Controls_Default=Standard <<<<<WHAT is this?
Controls_Current=Standard<<<<<WHAT is this?
KBDAIL=64
KBDELEV=64
KBDRUD=64
JOYSTICKS=0
 

Other ideas?

 

Thanks

Rick S.

Yeah - I've been trying to respond, but this connection is just the worst. What I should have said, is that each controller has an entry in the controls.xml, and between the opening and closing entries are the buttons and axes which are used by the controller - though FSX.

 

The entry in the cfg:-

 

Controls_Default=Standard <<<<<WHAT is this?
Controls_Current=Standard<<<<<WHAT is this?

 

Each is a pointer to which file to use. I almost all cases it is the default - but it could be changed, and that would be reflected in the current.

 

C:\Users\{your user id here}\AppData\Roaming\Microsoft\FSX\Controls\Standard.xml

 

The bits that should be deleted are the linne entries which you are going to add into FSUIPC. Below we will delete the entries in bold, and then assign them in FSUIPC:-

 

<SimControls.Map>
        <Name>DTA Rotary Encoder SLEW {9265A6E0-7C66-11E2-8006-444553540000}</Name>
        <Axis>
            <AxName>XAxis</AxName>
            <Index>0</Index>
            <AxEvent>AXIS_SLEW_SIDEWAYS_SET</AxEvent>
            <AxScale>127</AxScale>
        </Axis>
        <Axis>
            <AxName>YAxis</AxName>
            <Index>1</Index>
            <AxEvent>AXIS_SLEW_AHEAD_SET</AxEvent>
            <AxScale>127</AxScale>
        </Axis>
        <Axis>
            <AxName>RxAxis</AxName>
            <Index>3</Index>
            <AxEvent>AXIS_SLEW_HEADING_SET</AxEvent>
            <AxScale>127</AxScale>
        </Axis>
        <Entry>
            <Index>0</Index>
            <Down>SLEW_RESET</Down>
        </Entry>
        <Entry>
            <Index>1</Index>
            <Down>VIEW_MODE</Down>
        </Entry>
        <Entry>
            <Index>2</Index>
            <Down>SLEW_ALTIT_PLUS</Down>
        </Entry>
        <Entry>
            <Index>3</Index>
            <Down>SLEW_ALTIT_MINUS</Down>
        </Entry>

 

This one below has a five-axis controller, with eleven of 12 buttons used. The Axes have all been deleted, and are now in theFSUIPC.ini file.

 

<SimControls.Map>
        <Name>5-Axis,12-Button with POV {92657FD0-7C66-11E2-8005-444553540000}</Name>
        <Entry>
            <Index>0</Index>
            <Down>BRAKES</Down>
            <DownRpt>1</DownRpt>
        </Entry>
        <Entry>
            <Index>1</Index>
            <Down>VIEW_MODE</Down>
        </Entry>
        <Entry>
            <Index>2</Index>
            <Down>ELEV_TRIM_DN</Down>
            <DownRpt>1</DownRpt>
        </Entry>
        <Entry>
            <Index>3</Index>
            <Down>ELEV_TRIM_UP</Down>
            <DownRpt>1</DownRpt>
        </Entry>
        <Entry>
            <Index>4</Index>
            <Down>FLAPS_INCR</Down>
        </Entry>
        <Entry>
            <Index>5</Index>
            <Down>FLAPS_DECR</Down>
        </Entry>
        <Entry>
            <Index>6</Index>
            <Down>RELEASE_DROPPABLE_OBJECTS</Down>
        </Entry>
        <Entry>
            <Index>7</Index>
            <Down>GEAR_TOGGLE</Down>
        </Entry>
        <Entry>
            <Index>8</Index>
            <Down>VIEW_MODE</Down>
        </Entry>
        <Entry>
            <Index>9</Index>
            <Down>GEAR_TOGGLE</Down>
        </Entry>
        <POV>
            <Index>0</Index>
            <Down>PAN_VIEW</Down>
            <DownRpt>1</DownRpt>
        </POV>
    </SimControls.Map>

 

 

Here are three or four full examples. Most don't have any axes listed.A script will call and rename them depending upon the flight type.

 

I hope this is clearer.  Sorry for the delay.

 

pj

Okay, delete sections between <Entry>'s that are used by FSUIPC4?  Correct?

 

Example:  <Entry>

            <Index>2</Index>

            <Down>ELEV_TRIM_DN</Down>

            <DownRpt>1</DownRpt>

        </Entry>

        <Entry>

            <Index>3</Index>

            <Down>ELEV_TRIM_UP</Down>

            <DownRpt>1</DownRpt>

        </Entry>

 

Deleting these two sections allows me to rewrite the trim to FSUIPC4? 

 

And they will not be rewritten in the XML?

 

 

 

A script will call and rename them depending upon the flight type.

 

I don't understand this, what script?

 

Thanks

Rick S.

Wait, by removing some entries and leaving others I will have an effect on the JOYSTICKS=0 problem?

 

That doesn't sound logical?

 

I am not having any problem assigning, and keeping, the functions in FSUIPC4.  Even if the box gets ticked to enable controllers in FSX and the line disappears from the CFG; I only need to delete the tick-mark again before taking off (or not).  The controllers still work, although not as good as if just FSUIPC4 were controlling them.

 

It's just an nuisance that I would like to deal with.

 

Thanks

Rick S.

Okay, delete sections between <Entry>'s that are going to be used by FSUIPC4?  Correct?   Yes

 

Example:  <Entry>

            <Index>2</Index>

            <Down>ELEV_TRIM_DN</Down>

            <DownRpt>1</DownRpt>

        </Entry>

        <Entry>

            <Index>3</Index>

            <Down>ELEV_TRIM_UP</Down>

            <DownRpt>1</DownRpt>

        </Entry>

 

Deleting these two sections allows me to rewrite the trim to FSUIPC4?   Exactly

 

And they will not be rewritten in the XML?   No - but to verify - go into FSX Setting ->Controls->Control Axes and delete every single one that you want moved into FSUIPC. You can do this in the Controls.xml, or you can do it via the FSX GUI.

 

I don't understand this, what script?   I run a Visual Basic application (like Orbx's "FSX Go" application), and this calls custom fsx.cfg's, custom xml files, custom scenery cfg's etc..  My rational is "Why load and run FSDT's KLAX if I'm flying in EU-ENG?"

 

Wait, by removing some entries and leaving others I will have an effect on the JOYSTICKS=0 problem? Yes. FSX wil load and run whatever is in the Controls "Standard.xml file. It doesn't know about FSUIPC. If you still have these Axis entries in the Standard.xml file - they will  be loaded, along with whatever (Axes) is/are in the the FSUIPC.ini file. Obviously - you can't have both, and if there's an axis stil in the Standard.xml file - your Joysticks will alway get changed to "1".

 

You only need not to have a conflict between the same entry in both places. Either the controller_one "Z-Axis"  (etc.,) is in the Standard.xml, or it is in FSUIPC. It cannot exist in both.

It's just an nuisance that I would like to deal with. Wait 'till you have multiple controllers!  :lol:

 

All the Best,

 

pj

Okay, if I understand; FSUIPC4 already has the controller assignments I use in it's INI file.  So, if I delete the assignments in the STANDARD.INI file I will have solved my problem?

 

I guess I already have multiple controllers, but not ones that conflict with each other.  Not going there any time soon.

 

Thanks

Rick S.

Okay, if I understand; FSUIPC4 already has the controller assignments I use in it's INI file.  So, if I delete those same assignments in the STANDARD.INI file I will have solved my problem?  Yes - completely.

 

Life is good, once again!

 

pj

 

 

Thanks Paul,

 

I will go thru all of the assignments in FSUIPC4 and delete them in STANDARD.XML.

 

I am curious how FSX will know that they are assigned and not keep deleting the JOYSTICKS=0 line in the CFG.

 

I will let you know tomorrow.

 

And YES, life is good.  This doesn't even register.

 

Thanks Again

Rick S.

I think that as long as there is an axis assigned in FSX - it will remain as a "1", Rick. I'm not 1000% sure because I have three of the DeskTopAviator USB modules plus a regulat stick (axes removed, only used for switches) and all axes are assigned to Pete's nice little app.