Jump to content
The simFlight Network Forums

Macro - copying for different liveries


Recommended Posts

Peter,

I have mapped all the Ifly overhead switches to a Macro file, but have had to make this Aircraft specific as I use primarily the PMDG models/macros.

My question is this, I have created the macro for one specific liveried aircraft which works fine. I now wish to use another aircraft livery, so I have then copied the section in the fsuipc.ini file for the aircraft that works, and pasted it below the first one. I then changed the title of that section to the same as the new aircraft name as detailed in the corresponding aircraft.cfg. However, the macro does not work. Am i doing the wrong thing here by copying the button section, or do I have to remap the swicthes again for each individual aircraft?

I hope I have made myself clear

thanks

Keith

Link to comment
Share on other sites

I now wish to use another aircraft livery, so I have then copied the section in the fsuipc.ini file for the aircraft that works, and pasted it below the first one. I then changed the title of that section to the same as the new aircraft name as detailed in the corresponding aircraft.cfg.

Phew. Much easier to use profiles, or even just using the "ShortAircraftNameOk=substring" facility so you can use shortened names for all aircraft with similar names, like "B737" to cover all of those. There's a Chapter on Profiles in the User Guide, and an Appendix giving detailed instructions, supplied by a user, for using short names.

However, the macro does not work.

Is the other aircraft the same identical aircraft except for livery -- i.e. all the gauges you are covering in macros are the same? It's the same Aircraft.CFG? If not, you'd need to generate new macros because the code being called wil be different.

If it's the same aircraft however, it should work unless you used the wrong name from the Aircraft CFG file. Best really to create an aircraft-specific section automatically via FSUIPC before copying other assignments into it. Then you know the name is correct. Better still to use an appropriate abbreviated name and only have one section in the first place.

You can easily check what is happening when you press your buttons by enabling Button logging (FSUIPC options, Logging tab), and looking in the FSUIPC Log file after pressing them.

Regards

Pete

Link to comment
Share on other sites

Peter,

Thanks for your help, I am now using profiles as you suggested. I wasnt even aware of that option! :oops:

Anyway, I have set up a profile for the PMDG 737 and that works superbly for all models using the macro supplied within FSUIPC. However, I have now set up a profile and macro file for the Ifly 737 and called this Ifly.

This works fine for all the 800 models, but when I choose the other models the macro does not work. Will I have to setup macros for each model for the Ifly?

It just seesm strange that I dont have to do this for the PMDG models.

thanks

Keith

Link to comment
Share on other sites

Anyway, I have set up a profile for the PMDG 737 and that works superbly for all models using the macro supplied within FSUIPC. However, I have now set up a profile and macro file for the Ifly 737 and called this Ifly.

This works fine for all the 800 models, but when I choose the other models the macro does not work. Will I have to setup macros for each model for the Ifly?

It just seesm strange that I dont have to do this for the PMDG models.

PMDG have used the same Gauge and DLL coding for each model -- I think only the performance, loadings etc change for the NG series they've implemented. The iFly 737 series may be different? Have they got different gauges for each model? You can tell by comparing the Gauge names in the PANEL.CFG files.

Maybe some of the gauges are common and some aren't. The "mouse" macros generated by FSUIPC rely on finding the correct place within the actual gauge code to call to perform the required function. Two different gauges only need to have this location one byte shifted in either direction and the known address to be called no longer applies. In such cases the only way is to make new macros. You may have to have more than one "iFly" profile.

Regards

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.