Aircraft specific settings?

[Haldir]

Hi Pete! I have a question about aircraft specific joystick calibration settings in FSUIPC4. Are they working? I read through that section of your manual but didn't see any mention of it being unfinished. If I missed something, my apologies. I'm using version 4.02 registered.

The checkbox for them is greyed out to me and the aircraft specific checkbox for axis assignments won't allow me check it, even though it appears to be available. It brings up two setting confirmation dialogs, but won't check it no matter what combination of answers I give. Global axis assignment settings work when I set them, but then oddly FSX immediately crashes on the next session start and won't get past the spash screen. I end up having to delete fsuipc.ini to get it running again. Boggles. :)

I'm also having the same Activesky/simconnect issues as several other people, surprise surprise, so I'm guessing my TCP protocol is trashed in some way despite having no anti-spyware software or 3rd party firewalls installed. Whatever is screwing up that connection is probably causing this issue as well I guess. Maybe this is also affecting other parts of fsuipc and I haven't noticed yet.

Is the aircraft specific calibration working for you or anyone else? Haven't tried copying over my ac specific settings from FS9, but that's next.

My finger is hovering over the format C: command anyway with all these issues, and a fresh install might be my only solution unless ACES gets their act together on simconnect in a big hurry, haha.

Cheers Pete, and thanks!

[Pete Dowson]

Hi Pete! I have a question about aircraft specific joystick calibration settings in FSUIPC4. Are they working?

Yes. It's exactly the same as in FSUIPC 3.709.

The checkbox for them is greyed out to me and the aircraft specific checkbox for axis assignments won't allow me check it, even though it appears to be available. It brings up two setting confirmation dialogs, but won't check it no matter what combination of answers I give. Global axis assignment settings work when I set them, but then oddly FSX immediately crashes on the next session start and won't get past the spash screen. I end up having to delete fsuipc.ini to get it running again. Boggles. :)

I have no idea what is going on there and I cannot even picture it. Can you show me your starting settings in the INI file please (only the JoystickCalibration sections), and then ennumerate step-by-step what you do and what you see so I can try to replicate it?

I'll also need to know your "ShortAircraftNameOk" parameter setting.

Whatever is screwing up that connection is probably causing this issue as well I guess.

SimConnect itself won't be able to mess up the way the dialogue works. It is needed to supply the aircraft name, though, and of course forward the joystick values for calibration -- unless you are assigning those directly via the FSUIPC4 axis assignments.

Let me have the info and I'll try to work out what is going on.

Regards

Pete

[Haldir]

Hey Pete, thanks for the quick reply, and sorry for my slow one. I'm glad to hear that it should be working as advertised, that's the answer I was looking for, hehe. It's been awhile since I reinstalled my OS, and it's probably all garbaged up at this point, though I can't find any spyware issues or viruses to blame this issue or my simconnect problems on. I don't want to waste any of your time chasing ghosts down for me, I think you must have your hands plenty full with bigger issues at the moment. Thank you for your wonderful and timely support as always though!

I'll reformat, reinstall everything from scratch, and if I still have the issue after that (which I doubt), I'll let you know. Fingers crossed, hehe.

Take care!

[Haldir]

Fixed it. :) Not FSUIPC's fault at all.

As a last resort I ripped out all the aircraft I had added to FSX thinking that something in one of them was causing the problem, and sure enough it started working. Turned out to be a duplicate aircraft name of all silly things. Activeky works now too....boggles!

Then I went to avsim and found out someone had discovered and solved the very same problem not two hours beforehand, hahaha. (bangs head on table)

Unreal. Thanks Pete!

[Pete Dowson]

Turned out to be a duplicate aircraft name of all silly things.

Ouch.

That's something you'd think FS would spot and report. I'll need to remember that one. Thanks for letting me know!

Regards

Pete