problem when trying to create a mouse macro

[Sumpy]

I am experiencing a problem when trying to create a mouse macro in FSX.  I'm using a third party aircraft.  When I open FSUIPC, the screen goes black so I'm unable to see the switches I wish to create the macros for.

Would you know if this is an issue with Windows, FSX, the aircraft model or FSUIPC.

I've spent some time searching the Forum to see if anyone else has had this sort of problem, but so far not found anything  (555 pages will take a lifetime!).

I'm using a registered version of FSUIPC Version 4.929, FSX Deluxe 10.0.61637.0 (FSX-Xpack.20070926-1521).

OS is Windows 10 Pro - Version 1607  OS Build 14393.351 (strangely the Log File thinks it's Windows 8)

I'd be grateful for any suggestions/help.

Regards

Barry

Log File:

********* FSUIPC4, Version 4.929 by Pete Dowson *********
Reading options from "D:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 8
Module base=50810000
User Name="Barry Fryett"
User Addr="bj746@btinternet.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       78 System time = 01/11/2016 16:02:08
       78 FLT path = "C:\Users\Barry\Documents\Flight Simulator X Files\"
      531 Trying to connect to SimConnect Acc/SP2 Oct07 ...
      547 FS path = "D:\FSX\"
      891 LogOptions=00000000 00000001
      891 SIM1 Frictions access gained
      906 Wind smoothing fix is fully installed
      906 G3D.DLL fix attempt installed ok
      906 SimConnect_Open succeeded: waiting to check version okay
      906 Trying to use SimConnect Acc/SP2 Oct07
    15969 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
    15969 Initialising SimConnect data requests now
    15969 FSUIPC Menu entry added
    16000 c:\users\barry\documents\flight simulator x files\nimrod - UKM - cold.FLT
    16000 D:\FSX\SimObjects\Airplanes\UKMIL Nimrod MR2 v2 On Ops\Nimrod v2.AIR
   251750 Aircraft="UKMIL Nimrod MR2 v2 XV229 2008"
   251750 System time = 01/11/2016 16:06:20, Simulator time = 16:02:24 (16:02Z)
   252734 Starting everything now ...
   254063 Advanced Weather Interface Enabled
   469250 Sim stopped: average frame rate for last 218 secs = 34.4 fps
  1581391 Sim stopped: average frame rate for last 1042 secs = 39.8 fps
  1872750 Mouse Event=66240
  1874406 Mouse Event=66240
  1920969 Sim stopped: average frame rate for last 20 secs = 39.3 fps
  2449359 Mouse Event=66240
  2503734 Sim stopped: average frame rate for last 42 secs = 39.5 fps
  2621422 Sim stopped: average frame rate for last 116 secs = 39.5 fps
  2708281 Sim stopped: average frame rate for last 23 secs = 38.2 fps
  2791313 Mouse Event=66240
  2799484 Mouse Event=66240
  2803797 Mouse Event=66240
  2810266 Sim stopped: average frame rate for last 25 secs = 39.2 fps
  2937875 Sim stopped: average frame rate for last 119 secs = 38.5 fps
  3991578 Sim stopped: average frame rate for last 261 secs = 39.7 fps
  5060969 Sim stopped: average frame rate for last 396 secs = 39.4 fps

[Thomas Richter]

Hi,

that is mostly related to graphics card, if I remember correct it was mostly and Radeon problem (only if I remember correct).

Just leave the full screen modus (Alt + Enter), it should be ok in windowed mode.

Thomas

[Sumpy]

And that's what I've got!  Radeon HD7850.

 

will try your suggestion.  Many thanks Thomas.

 

regards

 

Barry

[Pete Dowson]

51 minutes ago, Sumpy said:

When I open FSUIPC, the screen goes black so I'm unable to see the switches I wish to create the macros for.

FSX always sets the screen black. You don't need to see it when you start macro making. All you do in the FSUIPC options is start it and give a filename for the macro file. The macros themselves are created whilst you are in normal flight modes -- else FSUIPC cannot trap what your mouse click does!

When you've finished making macros, you just got back and tell it you've finished.

All this is explained in the User Guide which you'll find in your FSUIPC Documents folder.

Pete

 

[aua668]

... and btw: 4.957b is the current Version with a fix to 4.957c. You definitely should upgrade to the actual version, whenever you face a problem.

BR
Reinhard

 

[Sumpy]

Thanks Pete

I had read the User Guide but didn't appreciate that the mouse recorded operations were just within the sim.

However, RTFM again and re-started using the 'Buttons + Switches' option.  I found that some of the switches I wanted to operate did not generate the 'Making Macro File:' prompt so I suspect these may be ones that you say may not be supported, these being taxi, beacon and nav lights (can't understand why FSX does not include them individually).  The process worked with the remaining selections (AP/FD switches and buttons).  I ended the macro and checked the FSX Modules folder but the .mcro file has not been produced.  I've followed the 'Mouse Macros' instructions to the letter, so I'm not sure what's going on here.

Barry

[Pete Dowson]

6 minutes ago, Sumpy said:

 these being taxi, beacon and nav lights (can't understand why FSX does not include them individually).

But why do you want mouse macros for features supported by standard FS controls. Those all have their own assignable controls:

TOGGLE BEACON LIGHTS
TOGGLE NAV LIGHTS
TOGGLE TAXI LIGHTS

To find the name of controls instigated by switches on a panel, just enable FSUIPC's Event logging (in its Logging tab). When you operate anything which uses an FS control, it will be logged with its name. You can even see this is real time if you run FS in Windowed mode and enable FSUIPC's log console.

11 minutes ago, Sumpy said:

I ended the macro and checked the FSX Modules folder but the .mcro file has not been produced.  I've followed the 'Mouse Macros' instructions to the letter, so I'm not sure what's going on here.

It actually starts creating the file immediately you enter the mode, so I don't know why you aren't seeing it. If the macro file listed in the Macrofiles section of the FSUIPC4.INI file?

Pete

 

[Sumpy]

Ah, didn't realise there were options listed under 'Toggle' in the FSUIPC dropdown list and didn't think to look that far down the list.  My apologies for that.

I've had a look in the FSUIPC.INI file but there's nothing with the heading '[Macrofiles]' listed.

Have just tried your suggestion about FSUIPC Event logging.  When running, it shows on key down = 'Key not programmed - passed on to FS'.

Barry

 

[Pete Dowson]

2 hours ago, Sumpy said:

Have just tried your suggestion about FSUIPC Event logging.  When running, it shows on key down = 'Key not programmed - passed on to FS'.

When you operate a switch on the displayed cockpit panel? Surely you mean when you press a key? What key are you pressing, and why? What has this got to do with assigning ot those Lights switches?

Pete

 

[Sumpy]

Pete

Just to clarify.  I’ve built a switch panel to enable me to operate regularly used functions on a third party model without having to point and click (and add a bit of realism at the same time).   The functions I’ve chosen to use at this stage are lighting and autopilot, controlled by switches on the displayed flight deck panel.

The homebuilt switch panel operates through a USB keyboard PCB, thus emulating key presses for those functions assigned to keyboard characters.  I’ve set up the switches to produce a particular character when operated.

Thanks to your advice, I’ve now been able to assign all of the lighting functions via FSUIPC, so  that is no longer a problem.

The AP functions are were causing difficulties though as some of the switch functions are not listed in the assignment dropdown in FSUIPC.   This is why I’ve been trying to produce the mouse macros.

Following the guide, the mouse macro process works as advertised, with the operation confirmed by using the TAB test, but the .MCRO file had not been produced.  I've re-read the guidance and realise that I’ve not been pressing ‘Enter’ after completing the macro.  So now  the .MCRO file has been produced and all functions have been tested satis.

FSUIPC is a brilliant powerful tool that is taking time to get to grips with, so many thanks for your patience in dealing with this old codger.

Regards

Barry

 

[Pete Dowson]

50 minutes ago, Sumpy said:

The homebuilt switch panel operates through a USB keyboard PCB, thus emulating key presses for those functions assigned to keyboard characters

Ah, ok. So you can use the FSUIPC Keys tab to assign keypresses to FS controls. mind you, of course, many such functions are already assigned to FS controls n FS itslef.

51 minutes ago, Sumpy said:

The AP functions are were causing difficulties though as some of the switch functions are not listed in the assignment dropdown in FSUIPC.   This is why I’ve been trying to produce the mouse macros.

What aircraft is this with? I assume an add-on, because very few of the default aircraft panels are amenable to Mouse Macros in any case.

52 minutes ago, Sumpy said:

Following the guide, the mouse macro process works as advertised, with the operation confirmed by using the TAB test, but the .MCRO file had not been produced.

Okay. I've re-checked this, and the only way it doesn't create a macro file is when you haven't actually created any macros. Otherwise, if you've entered macro names in the semi-transparent window where you use TAB to test your macro, and confirm, it has nothing to write, so it doesn't.

1 hour ago, Sumpy said:

I've re-read the guidance and realise that I’ve not been pressing ‘Enter’ after completing the macro.  So now  the .MCRO file has been produced and all functions have been tested satis.

Ah, right. Good. Yes, you must confirm each named macro or it won't get written out.

Pete

 

[Sumpy]

1 hour ago, Pete Dowson said:

What aircraft is this with? I assume an add-on, because very few of the default aircraft panels are amenable to Mouse Macros in any case.

Its the UKMIL Nimrod MR Mk2 by Matt Baker.

Many thanks for all your help.

Barry