FSUIPC 5.15 MACRO ISSUES

[galeair]

I would firstly like to thank Peter for all the hard work he carries out in updating FSUIPC for all the new versions of Prepar3d that materialise. What we would do without all his support and efforts I do not know.

I am a registered user of FSUIPC version 5.15 and using it in conjunction with P3Dv4.4 to calibrate controls for the Qualitywings 146 aircraft.

I am experiencing some problems with Macros, which I thought might be of interest.

I have assigned Macros for various controls to buttons on Logitech throttle units and keyboard keys.

I firstly created a profile for the AVRO and then created an AVRO series of Macros and assigned these for the Avro 85 aircraft, of which I have several liveries installed. No problems they all work as advertised.

I then assigned the same profile to the AVRO 70 and AVRO 100 aircraft. All the AVRO aircraft use the same AVRO_HD panel which is contained in a common AVRO folder. All the AVRO aircraft CFG files link through to the same panel.

The strange thing is that around 60% of the assignments change when I select an AVRO 70 or an AVRO 100, despite using the identical panel.

So I am getting around this by creating a different profile for the AVRO 70, AVRO85 and AVRO 100 aircraft, and separate Macros for each aircraft type. As an example these are the different Macro's I have had to create so far in order to get the AVRO 70 to work. The other Macros from the AVRO 85 list work in the AVRO70. I haven't yet started on the AVRO100 Macros, but initially it seems that it is the same Macros which did not work correctly in the AVRO70 which will need correcting for the AVRO100. 

New AVRO70 Macros     

                                                                   
1=ENG1ICE=RX40000096,3
2=70ENG1ICE=RX40000096,3
3=70ENG2ICE=RX40000095,3
4=70ENG3ICE=RX40000094,3
5=70ENG4ICE=RX40000097,3
6=70OUTWINGICE=RX4000009a,3
7=70INNWINGICE=RX40000099,3
8=70TAILICE=RX4000009b,3
9=70SEATBELT=RX400000c7,3
10=70LNAV=RX20411800,3
11=70VNAV=RX20412000,3
12=70VORLOC=RX20414800,3
13=70APP=RX20409800,3
14=70ANTICEALL
14.1=RX4000009a,3
14.2=RX40000099,3
14.3=RX4000009b,3
15=70ENG1FUEL=RX40000086,1
16=70ENG2FUEL=RX4000008a,1
17=70ENG3FUEL=RX40000088,1
18=70ENG4FUEL=RX40000084,1
19=70APUSTART=RX400000b4,3
20=70APUSTOP=RX400000b4,3
21=70PARKBRAKE=RX4000008e,3

 

Original AVRO85 Macros, with the different Macros highlighted.

1=GLARE=RX40000036,3
2=OVERHEAD=RX40000014,3
3=PANELBACKLIGHT=RX40000025,3
4=ENTRY=RX40000079,3
5=NAV=RX4000007d,3
6=LOGO=RX4000007c,3
7=CABIN=RX40000078,3
8=BEACON=RX40000076,3
9=TAXI/LAND=RX4000000c,3
10=STROBE=RX4000007e,3
11=SEATBELT=RX400000c6,3
12=LNAV=RX20411800,3
13=VNAV=RX20412000,3
14=VORLOC=RX20414800,3
15=TOGA=RX20417800,3
16=ENG1ICE=RX40000095,3
17=ENG3ICE=RX40000093,3
18=ENG4ICE=RX40000096,3
19=A/PENGAGE=RX2040b000,3
20=A/PDISENGAGE=RX4000006d,3
21=ENG1FUEL=RX40000085,1
22=ENG2FUEL=RX40000089,1
23=ENG3FUEL=RX40000087,1
24=ENG4FUEL=RX40000083,1
25=APUSTART=RX400000b3,3
26=APUSTOP=RX400000b3,3
27=ENG2ICE=RX40000094,3
28=OUTERWINGICE=RX40000099,3
29=INNERWINGICE=RX40000098,3
30=TAILDEICE=RX4000009a,3
31=AUTOTHROTTLE=RX4000006e,3
32=APP=RX20409800,3
33=PARKINGBR=RX4000008d,3
34=ANTICEALL
34.1=RX40000099,3
34.2=RX40000098,3
34.3=RX4000009a,3

What I can't get my head around is why some of the Macro's are different and some the same, when its an identical cockpit panel which is being loaded. If there is any way I can use a standard set of Macros for all three models of the AVRO, when they use the identical panels, then that would greatly simplify matters. I attache a JOYSCAN file if it helps.

Many thanks

 

FSUIPC5.JoyScan.csv

[Pete Dowson]

1 hour ago, galeair said:

I then assigned the same profile to the AVRO 70 and AVRO 100 aircraft. All the AVRO aircraft use the same AVRO_HD panel which is contained in a common AVRO folder. All the AVRO aircraft CFG files link through to the same panel.

The strange thing is that around 60% of the assignments change when I select an AVRO 70 or an AVRO 100, despite using the identical panel.

This must be a  result of the way L-M have implemented the Mouse Rectangle numbering system.

1 hour ago, galeair said:

As an example these are the different Macro's I have had to create so far in order to get the AVRO 70 to work. The other Macros from the AVRO 85 list work in the AVRO70

But in your highlighted differences, you have

23=ENG3FUEL=RX40000087,1
24=ENG4FUEL=RX40000083,1

17=ENG3ICE=RX40000093,3
18=ENG4ICE=RX40000096,3

So, one was a 2-engined aircraft and the other 4-engined, so I really can't believe all the panels are the same in both? Poor design if so.

2 hours ago, galeair said:

What I can't get my head around is why some of the Macro's are different and some the same, when its an identical cockpit panel which is being loaded.

As I said, how can they be identical? The parts where the macros are the same will be those which are from the common gauges.

FSUIPC has no control over how P3D numbers the mouse rectangles in the panels. I doubt whether the folks who design the aircraft could do it either. 

BTW what is a common "panel" file?  Is it an added DLL? Normal panels are configured by a PANEL.CFG in the Panel subfolder of the aircraft, and it specifies which gauges are to be loaded from the Gauges folder (which I assume, with the new AddOns install method, can be outside the P3D folder).

Pete

 

[galeair]

Hi Pete,

Thanks for your comments. How can they be identical?  The only difference between the various AVRO's is fuselage length, they have the same number of engines, identical panels and gauges.Well...

Every QW aircraft CFG file, regardless of whether its an AVRO 70, 85 or 100. has the following identical panel line:

panel=RJ_HD

Every QW aircraft folder contains a subfolder named panel RJ_HD which contains the following:

alias=QualityWings Avro Common\panel.RJ_HD which links to one folder containing the RJ_HD panel.

There was a non HD panel in the Qualitywings common folder, but I have temporarily removed that in order to eliminate that option from the possible reasons.

So reagrdless of AVRO model, they would all appear to link to the same common panel folder. I have just tested the AVRO 100 aircraft, and they appear to use identical MACROS to the RJ70 aircraft, but the AVRO 85's use different ones.

Please don't waste a lot of time on this as I have solved my problem by creating two sets of MACRO's. I was just wondering if there was a better solution. QW are still working on panel/gauge issues so there will be an updated panel at some stage, so I may have to start all over again. I always prefer a simple solution rather than a complex one if possible.

Many thanks

[Pete Dowson]

17 minutes ago, galeair said:

How can they be identical?  The only difference between the various AVRO's is fuselage length, they have the same number of engines, identical panels and gauges

Strange then that you have macros for 2 engines in one and 4 in the other? That was what I was going by. I know nothing of those aircraft.***

18 minutes ago, galeair said:

So reagrdless of AVRO model, they would all appear to link to the same common panel folder. I have just tested the AVRO 100 aircraft, and they appear to use identical MACROS to the RJ70 aircraft, but the AVRO 85's use different ones.

Please don't waste a lot of time on this

There's nothing I can do. According ot L-M, since the fixes they made for version 4.4., the same panels/gauges will always have the same rectangle numbers. If thst isdn't working it is an L-M problem, as i can't do anything about P3D internal coding. Please submit your evidence, including probably the Aircraft CFG and Panel files, in a bug report to L-M. There's no point in me acting as an intermediary.

Pete

P.S. I've just looked up those aircraft. I didn't reallse they are really sort of later versions of the BAe-146 "whisperjet" design. Nice to see that really hasn't died -- it was shocking to see photographs of so many lined up in that desert in the USA as unwanted and disused.

 

[galeair]

OK Pete, wilco. Thanks for your help.

I miss the 146's as well, last of the UK made civil aircraft.

Have a good Xmas