Dear Peter,
Where to begin?
First of all, thank you for your work that I appreciate since FS98
Now that I'm with FSX, I decided to realize my old dream: making a "home cockpit", using macros files in FSUIPC, and I want to do so on the basis of the Wilco/FeelThere A320 that I like better in the meantime.
Immediately, YES, it works very well with the majority of buttons, encoders and the library for this special plane : A320CFM_feelThere.DLL.
But here is a problem that I is not moving past week:
Some commands of this VC panel work with the library window.dll. This applies, for example, the EFIS for orders "ND Mode" or "ND Range", normaly action this the wheel mouse (+/-).
I detect my command in FSUIPC and window.MCRO a file, then the change in FSUIPC4.ini well done:
FSUIPC4.ini (extract file)
[MacroFiles]
1=747 OHD
2=APchart
3=A320CFM_feelThere
4=window
[buttons.Feelthere A320 CFM Air France]
0=P64,0,K97,10
1=P64,1,K98,10
...
...
32=P65,0,CM3:15,0
33=P65,1,CM3:16,0
34=P65,2,CM4:2,14
35=P65,3,CM4:1,13
window.MCRO (total file)
[Macros]
Module="window.dll"
1=JOY65_3_SW=RXedb0*X8bcc,13 ;EFIS ND MODE – (wheel mouse)
2=JOY65_2_SW=RXedb0*X8bcc,14 ;EFIS ND MODE + (wheel mouse)
At this point, I wonder if this library standard Windows can not escape your control via FSUIPC. Can you give me your feelings, because, I do not know what to do!
In any case, thank you again for your continued work on this important interface.
Cheers,
Philippe, Montpellier - France