Specific profile doesnt work since new 4.90 and 4.902

[Franck]

Hi, when I check the specific profile box, when I return into FSX, nothing work, I return into FSUIPC, and specific profile is unchecked. It does work only for "Axis Assignement", but not for button and macro. thank you for your help.

[Marco Aurelio]

It seems that your problem is similar to mine.....see the POST No Axis Assignments in Axis Assignment Tab for a Specific Aircraft, in this forum. This happened after I've updated to 4.90.

Peter sorry, I've forgot to mention this in my Post.

Cheers....

[Pete Dowson]

Hi, when I check the specific profile box, when I return into FSX, nothing work

By "nothing work", what do you mean? If you've not assigned anything, what do you expect to work? Please clarify. You give no details for your report to be useful.

I return into FSUIPC, and specific profile is unchecked. It does work only for "Axis Assignement", but not for button and macro. thank you for your help.

I think you misunderstand. Whilst Axis assignments are specific only (i.e no default axis assignments can also apply to a specific selection), generic Button and Key assignments apply unless actually overridden by specific assignments. If you think about it this makes sense. You don't want unwanted axis assignments affecting the wrong aircraft, but buttons and keys don't do anything unless actually pressed or switched. By having both available you can do most of the more general assignments for everything and have specific differences for different aircraft.

The manual does explain this -- perhaps you've not read enough of it? In Button and Key assignments tabs you can switch between the Generic and the Specific by toggling that checkbox off and on. try it!

It seems that your problem is similar to mine.....see the POST No Axis Assignments in Axis Assignment Tab for a Specific Aircraft, in this forum. This happened after I've updated to 4.90.

Peter sorry, I've forgot to mention this in my Post.

You don't understand this either? Does no one read the documentation? :sad:

There's been no change in this area for many many years.

Regards

Pete

[Franck]

It is possible, but I have the problem on all aircraft, tested with PMDG NGX, Majestics Dash 8 400 etc...

[Pete Dowson]

It is possible, but I have the problem on all aircraft, tested with PMDG NGX, Majestics Dash 8 400 etc...

I think you both do not understand the flexibility of the facilities you are presented with. Please refer to my earlier reply which crossed with your new post.

Pete

[Franck]

I think you misunderstand me. This was working perfectly before update. I had created a profile for my PMDG 737 NGX and Dash 8 400, with one of the livreveries. When I use another livreries, what I do is that I go to FSUPIC option, and select specific profil and choose the one for my generic¨PMDG or Dash 8 400. The problem now is that, when I do his, for axis assignement it works, the box remain check, but for button it doesnt work any more, I check the box, but it doesnt seem to save this state when I leave FSUIPC menu. So naturally, my button programmed with macro doesnt work. And when I return into FSUIPC menu, the box is uncheck and there is no profile assiociate to my livreries.

Edit :

Ok so it looks like that it works if I create a new Profile. The Dash 8 has been updated so maybe some thing is wrong due to this update.

But with a new profile I have managed to have my button work again.

[Pete Dowson]

Ok so it looks like that it works if I create a new Profile. The Dash 8 has been updated so maybe some thing is wrong due to this update.

But with a new profile I have managed to have my button work again.

Maybe the name by which the aircraft is known has changed. If you have "ShortAircraftNameOk=Substring" set in the [General] section of the INI, then just shorten the name to some part which will match all versions you wish in that profile. Do this in the [Profile.<profilename] section which lists the aircraft assigned to that profile.

Otherwise, yes, each time you have a new aircraft or fly a new livery, you need to ad it to the existing profile explicitly, or, if you wish, create a new one if things will be different.

If you still think something is wrong, please explain in detail and show me the actual INI file so it illustrates your points. All I can do is assure you that nothing has been changed in some time in the Profiles area -- review the list of changes in the History document and you will be able to locate the last relevant change. And in 4.90 the ONLY change was the removal of the signature. That was the only reason for its release.

Regards

Pete

[Franck]

Thanks for the help, I have recreated my profile, and now I can assign it to any liveries and it works like a charm.

Sorry for the disturb, since it was not a FSUIPC problem.

Franck

[Andydigital]

If you have created mouse macros with the previous version of the Majestic Q400 they will stop working when the gauge dll is updated in a new version, this is what happened in the update from 1.005 to 1.006. This is the main draw back of using mouse macros and its likely to happen again when they release another update.

This is probably why you thought your profile wasn't working.