The A2A Simulations Community

Hi A2A Team,
I have a litte Problem of the Brake axis for Left/Right wheel brake i have the CH Pedals. Calibrate the axis with Reg. version of FSUIPC.
When to Full press on both brakes, the Brake in the B17 gos to full and then full back. When half brake bress on both pedals, the pedals in the B17 spin forward and back.
Best Regards.

_________________

PIC of:
WOP: B17G/Accu-Sim - P47/Accu-Sim - Spitfire/Accu-Sim - P40/Accu-Sim - P51D/Accu-Sim
WOS: B377/Accu-Sim/COTS - PJ3/Accu-Sim

Yes, I have the same with my Saitek pedals. The simple solution - don't calibrate them and it works Just assign the pedals through the FSX controls menu and it will work fine. FSUIPC is a great utility but it also sometimes causes troubles with double assignments. HTH

Oskar

hmm okay but litte bit problem mit Standard brakes axis i have by no pressure on the pedals Brakes +-10% ever and wenn i pull full Press on the pedals only 95% brake pressure in the plane. whenn i check the config program of CH alll axis mark to 0 no press an full Press 100%.

Software says all ok, FSX work´s not correkt.

with FSUIPC calibration works all fine.(in other planes)

hope understand me, i speak a litte bit english sry.
Best Regards

_________________

PIC of:
WOP: B17G/Accu-Sim - P47/Accu-Sim - Spitfire/Accu-Sim - P40/Accu-Sim - P51D/Accu-Sim
WOS: B377/Accu-Sim/COTS - PJ3/Accu-Sim

Yes, again I think I had the same problem with my Saitek pedals. You need to tick the REVERSE box on the FSX brake setup

Oskar

Hmm no it´s not a reverse problem, i think its a problem of communication from CH software to FSX.
I have allways 10% Brakepress in all planes. wenn i press (Brake button Point) its all okay Brake press 0% can rolling fine. but i press the pedals an then will rolling I have a litte brake press allways.

_________________

PIC of:
WOP: B17G/Accu-Sim - P47/Accu-Sim - Spitfire/Accu-Sim - P40/Accu-Sim - P51D/Accu-Sim
WOS: B377/Accu-Sim/COTS - PJ3/Accu-Sim

Ahh, I see. Well, I NEVER use any software for the external controllers because I only use them for FSX. I just plug them in and wait for them to be recognized by the OS. I had all kinds of troubles even with my Logitech Extreme Stick when I used the Logitech Software. Today I have uninstalled all driver software from all components - I use 1 Logitech Extreme 3D Pro, 2 Saitek Throttle Quadrants and the Saitek Rudder Pedals - all just plugged in to an USB hub without any external software. this way I keep it troublefree for many years now. However my guess is that if you use your controllers for other games you might need their software - and that makes things more complicated within FSX.

Oskar

I have search the problem with you tipps, i found it.
Big Thank you for your help oscar. works all great now.
Best Regards Daniel

_________________

PIC of:
WOP: B17G/Accu-Sim - P47/Accu-Sim - Spitfire/Accu-Sim - P40/Accu-Sim - P51D/Accu-Sim
WOS: B377/Accu-Sim/COTS - PJ3/Accu-Sim

Hi Daniel
I have the same problem, what was the fix you found please ?

_________________


Asus P5Q3
C2D Q9650 @3.6
8Gb Corsair Vengeance DDR3 PC3-12800C9 1600MHz
GTX580 3Gb
Akasa 1000w PSU
Antec 1200 gaming case
Asus VE276Q 27" Monitor 1920x1080
Win 7 Home Premium 64bit SP1

reset the calibration reset of FSUIPC and in CH software swtich one option off.

Here is a shot, turn off this both options and the problem was gone by me.

_________________

PIC of:
WOP: B17G/Accu-Sim - P47/Accu-Sim - Spitfire/Accu-Sim - P40/Accu-Sim - P51D/Accu-Sim
WOS: B377/Accu-Sim/COTS - PJ3/Accu-Sim

Will have to give that a try, thanks for the tip.

I ended up putting the toe brakes axis back into FSX (which I don't like doing as FSUIPC does a great job of handling different setups for different aircraft). Even with the toe brakes set in FSX it thought they were on slightly all the time and the deadzone/sensitivity didn't fix that. So in the CH software I adjusted it there and got them working without being partially on all the time or coming off with both pedals fully down (as they were doing in FSUIPC). But I never noticed if that centering check box was on or not. Will look tonight.

_________________
Asus P6X58D-E Intel X58 MB with onboard Realtek HD audio
Intel i7 970 3.2GHz 6 Core
Samsung 256Gb SSD for Win 7 64 bit
Corsair Vengeance 12Gb Triple Channel DDR3
nVidia 680 GTX
TrackIR 5,Track clip pro, EZDOK and a host of CH/Saitek controls and panels

Krycekuk, Oskar and others,

Here's a clip from a post I made in another thread, where both Krycekuk and Oskar have provided me with assistance, where I mentioned as an aside some problems I'm having with Saitek pedals and fsuipc:

"As far as the brakes are concerned, I'm having a similar problem with the Saitek pedals. There seems to be little or no braking power using my normal toe pressure. Yet when I press harder I'm nosing down into the runway and flipping. It's a good thing the Maintenance Hanger is so close and works so fast. I'm still trying to figure this one out. I assume there's a happy medium for the toe pressure; I've just not been able to find it yet. Perhaps I have to get into setting slopes for the brakes, something I've not bothered with before."

I was just wondering, when you set the brake axes in FSX in order to remedy this problem, as some of you have suggested, I would assume you also have to eliminate the brake assignments for the B-17 in fsuipc. Is that correct? In addition, do you also have to undo the FSX brake assignments when you want to fly another plane so that your fsuipc assignments can work without interference or conflict?

Thanks,
Robert

I'm really no expert with FSUIPC but I've had some forum discussions with Peter Dowson and you should only ever have an axis defined in one area only. If like me FSUIPC handles 99% of the work then make sure FSX or the configurator are not using the same axis otherwise you will have conflicts and problems.

In my rig, not using FSX and only using the A2A's configurators (B-17 and P-47) and FSUIPC means I can fly lots of different aircraft without redefining controls all the time. The axis/buttons and calibration are set for each different aircraft I fly. You can't do that with FSX alone so yes having the brakes configured there would really effect all the other aircraft I fly and I would have to remove my FSUIPC assignments for all of them or take them out of FSX after flying the B-17, which is why I'm keen to get it working right in FSUIPC.

So if you put something back into FSX then delete all the references in FSUIPC and vice versa.

As for nosing over make sure your throttles are in the idle position approx 1000 rpm when trying to stop I had a bit of trouble with my detents on my CH Throttle Quadrant being at the 1500 rpm position which exhibits a fair bit of pull still if trying to stop. Having moved my calibration so that my detent is now the idle helped.

Will check my brakes tonight to see if I get any nose over problems when I put the assignments back into FSUIPC. Fiddling around in the CH manager I may have limited myself to around 95% braking power and hence masked the problem. Or it may be that you should remove full braking power once the aircraft has slowed anyway to cool the brakes and avoid a nose over situation.

Of course at the end of the day we all have different hardware and we all have differing needs when it comes to what feels right with our controls so having the tools like FSUIPC and the excellent A2A configurator as well as the FSX assignments means we can tailor to our liking, no one set-up will fit all of us. But its very important not to introduce controller conflicts across the options we have.

Yes Robert,

It's actually exactly as Krycekuk said. You should never have the same axis assigned in different programs. So either use FSX' controller or FSUIPC's. Indeed I have my brake pedals assigned to FSX and blanked out at FSUIPC.

Of course there is this advantange of FSUIPC to store assignments individually for each A/C type but for me the great disadvantage is that I need to set up my individual settings for EACH PAINT MODEL included in the aircraft.cfg. So even for the B17 I have to do it four times to make sure I have it for each model.

I take a different apporach. As - contradictory to FS9 - FSX stores it's key and controller settings in a separate file called standard.XML I make a setup for maybe a group of specific A/C -let's say for twin engined A/C I have 2 throttles, 2 prop levers and 2 mixture levers and a few special key assignments. I then copy the standard.XML to a safe location ad rename it with a significant name - e.g. 2-2-2.xml for that setup. Whenever I need that setup I copy that file back to it's place (using a batch file) and at the same time rename it to standard.xml again. So I can also have unlimited individual files for each A/C type.

The main disadvantages of this method are:
-> No automatic assigning when loading the A/C. You need to "load" the file before starting FSX
-> To change an assignment file you have to close FSX

For me the main advantage of this system is that I can have a few standard setups that I can use on every A/C I like without re-calibrating and storing for each repaint. whenever you wish to try this be sure you DO NOT copy or alter the standard.XML file contained in the root directory of FSX. This one contains the default settings for initial load of FSX or whenever you killed the fsx.cfg. The "working copy" of the standard.xml is to be found in the directory C:\Users\[your name]\AppData\Roaming\Microsoft\FSX\Controls .

Oskar

Oskar, just a few comments on what you've said. I've tried swapping the standard.xml file in the past, but I found that it was unreliable and I often had to re-input my FSX controller and keyboard settings. Of course, I was doing the swap between disabled settings for use with fsuipc, and enabled settings for use without fsuipc. You, on the other hand, are working entirely within FSX, at least as far as the axes assignments are concerned, so you may not find this to be a problem. I will look into this.

I was surprised to learn that you find it necessary to setup fsuipc for each paint separately. Perhaps you don't know about the short name feature described in the fsuipc advanced user guide. It should avoid this problem. Also, there's a relatively new feature called "Profiles" that's described in the basic manual that's supposedly even easier, although I've not bothered to explore it.

With the short name feature, which you need to activate in the fsuipc.ini file, all you need to do is make sure that the first few characters of the Title entry in the aircraft.cfg for each paint (usually the name of the aircraft) are the same, and then name your fsuipc settings with those characters, making sure of course that no other plane uses the same characters. The only problem is where different paints start with a different character set, which is most common with third-party paints, but sometimes occurs even with developer paints. This obviously involves keeping track of the paint entries in the aircraft.cfg and making sure that the Title entries for all paints of a particular plane are identical, at least insofar as the first few characters used in fsuipc are concerned.

So if you ever decide to switch to fsuipc . . .

Robert

The not so nice way of doing various repaints in FSUIPC was to configure the controls once for a given aircraft and copy and paste the assignments in the FSUIPC.ini and just rename the header to the new paint.

There was a nicer way of setting it up so that all repaints could be given a global name in the .ini file and then you had one assignment list in the global name. I remember reading about it over on Peter Dowsons page but for the life of me I can't find it now.

EDIT : I should read posts more carefully as this is what you were explaining Robert, my bad !

As for unchecking the center in the CH manager that hasn't worked for me but I've done a work around and thats to set the axis in FSUIPC but instead of direct send it as a normal FS axis (that way it's still in FSUIPC) but the problem introduced here is that selecting reverse in FSUIPC now doesnt work and I've had to set that in the CH manager. So it looks like I will have to edit all my other aircraft anyway otherwise the brakes will be stuck on