[FSLabs and FSUIPC issue]

What sim/fsuipc version are you using? And what aircraft - is it the FSLabs A320/A321? Maybe try with a default aircraft first, as it may be a a problem specific to this add-on.

Presumably your button 'down' and 'up' are actually different buttons (or button numbers). Are you assigning to button press or release? Maybe switch to the other (or try on both).

Could you also please post your FSUIPC5 (or 4) ini file.

Thanks,

John

 

[cannot link fsuipc with fsx-se]

Glad its now working - thanks for the update.

Regards,

John

[cannot link fsuipc with fsx-se]

Hi Fred,

Try to install SimConnect (for FSX-SE) by running the SimConnect.msi (as admin) in these two folders:

C:\Program Files (x86)\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-RTM

C:\Program Files (x86)\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1

Then re-run the FSUIPC4 installer.

Regards,

John

[One script for all joystick buttons question]

Its in the 'FSUIPC Lua Library' document, page 9:
 

Quote

 

x = ipc.testbutton(joynum, btn)

Tests a scanned button. “joynum” is a joystick number, the same as shown in FSUIPC’s Button assignments tab.
Provided the joystick is one being scanned by FSUIPC (i.e. it has a button assignment), this function returns
the state of the specified button number (0–31) as TRUE or FALSE. 

You can test for the POV position too using button numbers 32-39, but you might want instead to read the POV state using ipc.readPOV .

 

 

[Help Interpreting this Message]

Hi William,

Certainly nothing to do with FSUIPC - contact the support forum for whatever is producing that log file extract (VABase / VA Acars).

Looks like its trying to find FSUIPC but can't - maybe a (unregistered) version is required - have you installed one?

Cheers,

John

 

[One script for all joystick buttons question]

Its always better/more efficient to have scripts auto-ran and monitoring something to re-act on, rather than starting on a button press. As to the number of scripts, its probably better to have a reduced number but this is less important really - you just get an additional thread per running script.

Adding lua autostart + visibility via profiles is on my list to add to the features this year, so hopefully that will also reduced the number needed for those who separate luas via aircraft.

Cheers,

John 

P.S. Spokes: Rush I'm guessing - remember it from 35 years ago, will have to dig it out...!

P.P.S. And yes, 'Temple of Syrinx' reference missed me..

[cannot link fsuipc with fsx-se]

Hi Fred,

its not very clear where your error is - is it with ADE, when you install FSUIPC or when you run FSX-SE?

Does FSUIPC install/run ok without ADE? If so, then you probably need to contact ADE support.

I don't have/use ADE, but this post suggests that you need to uncheck 'Connect only to Matching FS Ver' - can you check this?

Are you also sure nothing has changed on your system between Friday and Sunday?

Regards,

John

[EVENT Automatically Running]

Seems to me that A2A re-purpose/re-use a lot of sim events/commands. I generally fly A2A and have quite a few log exclusions to keep a cleaner log file when flying with such aircraft.

Look at the DontLogThese parameter, documented in the advanced user manual, page 8.

Cheers,

John

P.S. Of course, applies to all aircraft - add the exclusions from the 'noise' events for any aircraft. Thinking about this, probably a good idea to make profile specific...I'll look into this

[No pause on task change]

Hi Achim,

yes, the sim should be paused - can you verify that its in the same state/position after you close FSUIPC? The sim going into pause state when you exit FSUIPC is due to P3D - I don't think it does this in v4.4 though (I'm away from my main pc until Tuesday now, I'll check when I return).

BTW, you should update the the latest FSUIPC5 version, 5.15 when you get a chance - only the latest version is supported.

Regards,

John

 

 

[No pause on task change]

Hi Achim,

What version of P3Dv4 and FSUIPC5 are you using?

The 'pause on task switch' tick-box only comes into affect when switching from P3D to an external program (FSUIPC is embedded in P3D).

However, opening up FSUIPC sets the sim to 'Dialog Mode', which *should* blank the visuals and stop the sim. When you close FSUIPC, the sim should restart in the same mode as it was in before you entered the FSUIPC dialog. Sometimes you still here some sim sounds when the FSUIPC dialog box is visible (if a wav file is being looped), but the sim is not running.

Is the screen blacked-out when the FSUIPC dialog box is displayed?

Regards,

John

 

 

[Mouse macros not working with Carenado Phenom 300]

Hi.

mouse macros do not work with xml gauges in FSX, only those build using the C/C++ Guages SDK.

You should maybe investigate if any L:vars  are available instead.

Regards,

John

[Spot view P3D]

You will lose the pedestal view as you have removed it! Did this not leave the default P3D camera view for that definition?

Did you try the other 'View select' controls? It also seems strange that the camera definition 4 is mapped to view select 3 - I would have thought that the numbers would match as they both start from 0...

[Spot view P3D]

So the [CAMERADEFINITION.004] is overriding the default P3D spot view. I guess you would need to remove (or comment out) the whole section so that the original view is still available.

Did you try some of the other camera's with the 'View Camera Select x' control? If other camera's are (locked) spot, you could use them instead.

[Spot view P3D]

If F11 is sending 'View Camera 3' when you press F11, then your add-on aircraft is using 'View Camera 3' for 'Pedestal / Radio' and you won't be able to use this control. Similarly, if you have mapped your button press 'View Camera Select 3' and this works for default aircraft but not for your A320/A321, then that control is being remapped by the add-on aircraft. Alternatively, your add-on aircraft may have remapped F11 for its own use (and is sending a different control).

First try assigning your button directly to the control  'View Camera Select 3', not the keypress (F11). If that doesn't work, you can try some of the other 'View Camera Select' controls to see if they provide what you need. Otherwise check the aircraft documentation (or support forums) to see if provides any other method/control for view selection. If not, you may have to live with using the view mode, sub mode, and next/prev controls.

Sorry but I don't have the A320 /A321 so can't really help any further with the specifics of this aircraft.

[Spot view P3D]

Also look into the P3D Options -> Key Assignments. By default' F11 is mapped to 'View Camera 3 (select)'. You could try assigning another key (or key combination) to this, and then assign your button press to that key (or key combination). Or, better still, assign direct to control 'View Camera Select 3' (66853).

John

[Spot view P3D]

You could try assigning to keypress F11 which is for 'Locked Spot view' (see http://www.prepar3d.com/SDKv3/LearningCenter/getting_started/view_system/using_views_and_windows.html).

[Problems Connecting to VRI Combo MCP Panels]

Hi Andrew,

thanks for the update. This patch will be officially released with a few other minor updates within the next week or so.

Cheers,

John

[Compatibility]

CPFLight MCP - don't know, sorry - you should probably ask them or on their support forums. If 'PM' is Project Magenta, then that would need FSUIPC, but again you are better off asking the suppliers/developers. There are these following (old) posts related to these items (although I'm not sure this helps):

Cheers,

John

[Mouse Macros procedure]

FSUIPC only records the first click. Thats why you need to edit the macro file to change the action, or if you want to change the action to a compound action (i.e. click & drag followed by release). Also, when you assign the button press to the macro, you can assign a different action on the press and release, which is why I suggested two macros, one for the left click and drag (action 9) assigned to the button press, and another for the release (action 13) for the button release. Thats just one thing to try - you could try other compound actions, activated either on a press, a release or both. 

Good luck with your investigations!

[Mouse Macros procedure]

Quote

is there a difference between these two strings (example)?
1[space]=[space]sb-full-press[space]=[space]RX40000170,9
1=sb-full-press=RX40000170,9

Yes, sorry - no spaces.

As Pete says, you need to play around with different (compound) codes/actions to see what, if anything, works. Otherwise investigate an L:var solution if the standard controls don't work. You can use the provide lvar plug-in to see what L:vars are available. I think there are also Linda scripts available for the A320 - these will be based on Lua & L:vars so may give you some insight, even if you do not want to use the Linda framework. As Pete suggests, the Aerosoft support forums may be the place to ask about this.

Cheers,

John

[Lvar interfacing with arduino and mobilight]

In your scripts you have infinite loops, so the first loop, eg

Quote

-- test RPM 
while 1 do
    RPM = ipc.readLvar("L:Eng1_RPM")
    ipc.writeUW(0x66c1, RPM)
    ipc.sleep(100)
end

will never end, and so the second loop (while) will never be reached. Thats why they work in separate scripts but not together. If you want them in one script, you could try a single loop, e.g. something like

-- test RPM and IAS
while 1 do
    RPM = ipc.readLvar("L:Eng1_RPM")
    ipc.writeUW(0x66c1, RPM)
    ipc.sleep(50)
    IAS = ipc.readLvar("L:AirspeedIndicatedNeedle")
    ipc.writeUB(0x66c0, IAS)
    ipc.sleep(50)
end

Better still, look into using the  'event.lvar()' libarary function and have two functions that get called only when the lvar changes (see the FSUIPC Lua Library.pdf, page 26).

Cheers,

John

 

[Mouse Macros procedure]

Also note that mouse macros will not work if the gauges haven't been written strictly in accordance with Microsoft's C/C++ gauge SDK and you may need to try looking into using lvars instead, if available. However, I also see this comment from 2016 on lvars - not sure if still valid:
 

Quote

If I may add my 2 cents to this, the FSL A320X LVars that have been exposed so far are of no use if the objective is to make an input to a switch or a knob control. So we would have to wait for the SDK and the associated Event ID's.

[Mouse Macros procedure]

...or you can also try programming one macro for the press and one for the release:

[Macros]
1 = sb-full-press = RX40000170,9
2 = sb-full-release = RX40000170,13
 

[Mouse Macros procedure]

You can try that for the left click and drag. You may also want to add the button release, so it would be

[Macros]
1=sb-full
1.1=RX40000170,9
1.2=RX40000170,13

[Mouse Macros procedure]

Hi,

the mouse macro will only contain the mouse press (left single click code 3), so if you call it on a button press or release, it will still be sending the mouse (left single) click only.

What you probably want is a  left button and drag then a mouse release. Do do this, you will have to manually edit the macro file. See page 32 of the FSUIPC User Manual for the mouse action codes, and page 37 of the Advanced User Manual for 'multiple actions in one macro control'. If that doesn't work, try a few other combinations.

You could also see if there is a control or lvar you can use for this by activating logging.

Cheers,

John

P.S. If its the Aerosoft A320 you are trying to set-up, there is also a discussion on setting up the speedbrake on an axis or buttons in this (ongoing) thread that may be of interest (half way down):