Jump to content
The simFlight Network Forums

saving mouse macro settings


Recommended Posts

Hi please can anyone help,

I have a panel with toggle switches on it connected to a leo bodnar? board. Using fsuipc mouse macro i can get these switches to turn on and off the landing lights in my leveld 767. However as soon as i exit flightsim and come back to it the switches won't work even though they are still seen to be working in fsuipc, each switch is showing the right task in the menu when flicked but i doesn't have any affect on the aircraft.

Please help it's driving me nuts

fs9 : fsuip 3.93

many thanks

Ian

Link to comment
Share on other sites

I have a panel with toggle switches on it connected to a leo bodnar? board. Using fsuipc mouse macro i can get these switches to turn on and off the landing lights in my leveld 767.

I didn't think there was any need to use Mouse macros for the LevelD, what with their open use of FSUIPC offsets and Niko Kaan's nice interface program. Don't they also allow keypress assignments?

However as soon as i exit flightsim and come back to it the switches won't work even though they are still seen to be working in fsuipc, each switch is showing the right task in the menu when flicked but i doesn't have any affect on the aircraft.

Enable key/button logging in FSUIPC's logging page and operate the switches. Show me the FSUIPC log file (paste the text in a message here). Also show me the [buttons] section from the FSUIPC INI file relating to these macros, and the Macro file itself. It is all text so you can paste them into messages.

Regards

Pete

Link to comment
Share on other sites

Hi pete thanks for your quick reply, i hope these are the right bits

********* FSUIPC, Version 3.93 by Pete Dowson *********

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="Ian Loome"

User Addr="smartarze@hotmail.co.uk"

FSUIPC Key is provided

WIDEFS not user registered, or expired

[Continuation log requested by user]

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=40003605[40003605]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

121609 System time = 06/09/2009 18:59:23, FS2004 time = 00:57:58 (23:57Z)

145297 *** Entered Buttons option page ***

149515 FirstButtonChange res=00000105 (0.1, 5)

151297 FirstButtonChange res=00000104 (0.1, 4)

152031 FirstButtonChange res=00000103 (0.1, 3)

152609 FirstButtonChange res=00000102 (0.1, 2)

153562 FirstButtonChange res=00000108 (0.1, 8)

154125 FirstButtonChange res=00000101 (0.1, 1)

154656 FirstButtonChange res=00000106 (0.1, 6)

155390 FirstButtonChange res=00000107 (0.1, 7)

156125 FirstButtonChange res=00000100 (0.1, 0)

159328 *** Exiting Buttons option page ***

[Log closed by user request, and continued in new file]

245094 System time = 06/09/2009 19:01:27, FS2004 time = 00:58:02 (23:58Z)

245094 *** FSUIPC log file being closed

Memory managed: 8 Allocs, 317 Freed

********* FSUIPC Log file closed ***********

.INI section

[buttons]

ButtonRepeat=20,10

21=P1,5,CM1:10,1

22=U1,5,CM1:10,0

[MacroFiles]

1=Lights

[buttons.Level D Simulations B767-300ER]

2=P1,4,CM1:11,1

3=U1,4,CM1:11,0

4=P1,3,CM1:12,1

5=U1,3,CM1:12,0

6=P1,2,CM1:13,1

7=U1,2,CM1:13,0

8=P1,8,CM1:14,1

9=U1,8,CM1:14,0

10=P1,1,CM1:15,1

11=U1,1,CM1:15,0

12=P1,6,CM1:16,1

13=U1,6,CM1:16,0

14=P1,7,CM1:17,1

15=U1,7,CM1:17,0

16=P1,0,CM1:18,1

17=U1,0,CM1:18,0

18=P1,5,CM1:10,1

19=U1,5,CM1:10,0

[Monitor]

Display=1

Macro File

[Macros]

Module="B767oh.GAU"

1=Position=RX7e615c0*X83cc

2=red A/C=RX7e61640*X83cc

3=white A/C=RX7e616c0*X83cc

4=Wing=RX7e61740*X83cc

5=landing L=RX7e61a40*X8300

6=Landing R=RX7e61ac0*X8300

7=Nose=RX7e61b40*X8300

8=Panal=RX7e61540*X83cc

9=Logo=RX7e617c0*X83cc

10=pos=RXbf315c0*X83cc

11=R a/c=RXbf31640*X83cc

12=W a/c=RXbf316c0*X83cc

13=winglight=RXbf31740*X83cc

14=leftwing=RXbf31a40*X8300

15=rightwing=RXbf31ac0*X8300

16=noselight=RXbf31b40*X8300

17=panellight=RXbf31540*X83cc

18=logolight=RXbf317c0*X83cc

Link to comment
Share on other sites

i hope these are the right bits

No. The log isn't at all useful. Sorry. Look:

145297 *** Entered Buttons option page ***

149515 FirstButtonChange res=00000105 (0.1, 5)

151297 FirstButtonChange res=00000104 (0.1, 4)

152031 FirstButtonChange res=00000103 (0.1, 3)

152609 FirstButtonChange res=00000102 (0.1, 2)

153562 FirstButtonChange res=00000108 (0.1, 8)

154125 FirstButtonChange res=00000101 (0.1, 1)

154656 FirstButtonChange res=00000106 (0.1, 6)

155390 FirstButtonChange res=00000107 (0.1, 7)

156125 FirstButtonChange res=00000100 (0.1, 0)

159328 *** Exiting Buttons option page ***

Showing me buttons being pressed whilst you are programming them in the options dialogue cannot possibly show me why they may or may not do anything when actually applied in the program! You need the logging for the actions which are failing, not things which you already said were working!

[Macros]

Module="B767oh.GAU"

1=Position=RX7e615c0*X83cc

2=red A/C=RX7e61640*X83cc

3=white A/C=RX7e616c0*X83cc

4=Wing=RX7e61740*X83cc

5=landing L=RX7e61a40*X8300

6=Landing R=RX7e61ac0*X8300

7=Nose=RX7e61b40*X8300

8=Panal=RX7e61540*X83cc

9=Logo=RX7e617c0*X83cc

10=pos=RXbf315c0*X83cc

11=R a/c=RXbf31640*X83cc

12=W a/c=RXbf316c0*X83cc

13=winglight=RXbf31740*X83cc

14=leftwing=RXbf31a40*X8300

15=rightwing=RXbf31ac0*X8300

16=noselight=RXbf31b40*X8300

17=panellight=RXbf31540*X83cc

18=logolight=RXbf317c0*X83cc

There's a lot there. Is it only the landing lights which don't work, or are all those assignments ineffective? The numbers in those macros look wrong. Far too big. Values like 0x7e61ac0 and 0xbf31b40 should not occur, as these are supposed to be offsets from the start of the Module (B767oh.GAU) to where its fixed, predefined, mouse action table entries are. The module cannot be as big as that, so something is going very wrong I think. Perhaps it somehow generates the tables on-the-fly (unlikely I think), or is compiled in some way which allows the data to be separated from the code.

I don't have the LevelD 767 for FS9, only the old Wilco one which doesn't appear to have the same gauge names. I do have the FSX version installed, though I'm not sure whether I can get it working. It is only here for some test I did a while back. Do you know if there's much similarity? I wonder if it is worth my while looking at the FSX version.

Even if I found out what was happening, it is likely that the only action i could do would be to take steps to detect the anomaly and prevent the "TAB test" working in the first place, so you aren't misled into thinking there's a solution when there isn't.

I think you will probably need to look for more ordinary solutions -- I'm sure there must be others, as no one else seems to ask about this. I know Niko Kaan's interface is heavily used for LevelD aircraft, and I'm reasonably sure most things can be done without mouse macros. Have you looked?

I've made a note to see if I can find out what is happening, via the FSX version. If I get anywhere I'll let you know.

Regards

Pete

Link to comment
Share on other sites

ok thanks pete, don't have sleepless night over it :)

I won't, actually, as I can't get that far. The FSX version is fine, no problems with mouse macros. The Wilco 767 I appear to have installed in my FS9 test system is either corrupt or is incompatible with FS9 -- maybe it dates back to FS2000, as I have just found a Wilco 767 PIC original CD dated 2000!

No, I just checked. Whilst the panel bitmaps are all dated 2000, the Gauges fitting to them are dated 2002, go I guess it was made for FS2002, not FS2000. Maybe it nearly worked in FS9, once. But I can't find the original to try a re-install, and even if I could the real FS9 version is probably substantially re-coded.

I'm afraid without the actual aircraft to work on I'm not going to be able to do anything about this problem. Sorry.

Regards

Pete

Link to comment
Share on other sites

ok thanks for your time, i tried using the program you suggested from niko but didn't get far, i seem unable to find step by step instructions for setting the switches up with the leveldd sdk and fsuipc, also tried fsconv but again got totally confused, maybe if anyone here can help then it would be most appreciated. Failing that another attempt at making a cockpit will go out the window untill 6 months time when i decide to have another go.

anyway if anyone can help please post away

Many thanks

Ian

Link to comment
Share on other sites

ok thanks for your time, i tried using the program you suggested from niko but didn't get far, i seem unable to find step by step instructions for setting the switches up with the leveldd sdk and fsuipc, also tried fsconv but again got totally confused, maybe if anyone here can help then it would be most appreciated. Failing that another attempt at making a cockpit will go out the window untill 6 months time when i decide to have another go.

I don't know either program, but Niko's pretty good at helping folks.

Regards

Pete

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.