[FSUIPC7 closes]

Does this only happen with the FBW A320? If so, which version (dev, stable or experimental) are you using - and is it up to date?

[Lvar & Hvar greyed out]

16 hours ago, KDog88 said:

It was just that one time, but I though I would mention the error just in case.

So this just happened the once?

Your log shows that the WAPI interface was not started. I'm not sure why this happened - the next version will have additional messages relating to the WASM/WAPI - you could try this (attached) and show me your FSUIPC7.log file if this happens again.

21 hours ago, KDog88 said:

I thought the WASM file was part of the install (at least I recall it asking me to check the box if I wanted WASM).  I don't even know what WAPI is or how to enable it.

The WASM is the module in your Community folder that runs with MSFS, and the WAPI is the interface in FSUIPC7 that communicates with the WASM. The WAPI is now enabled by default if the WASM is installed, and your ini file shows this is enabled anyway:

[WAPI]
EnableWAPI=Yes

So I'm not sure why it didn't start...

John

FSUIPC7.exe

[Can not get offsets to work with overhead]

3 minutes ago, jphere said:

do you think FSUIPC7 and MSFS will interfere with FSUIPC4 and FSX? 

No, they are completely separate and will not interfere. I run FSX, MSFS, P3Dv4 and P3Dv5 all on the same machine with different versions of FSUIPC.
You can only have one FS/version of FSUIPC running at a tune though.

John

[FSUIPC7 closes]

For the auto-start issue, and if FSYUPC7 is not just auto-starting and then closing, please see 

 

If FSUIPC7 closes after starting, please show me your FSUIPC7.log file.

John

[FSUPIC crashing MSFS2020 on long flights]

You are using an extremely old (and unsupported) version of FSUIPC7 (7.0.3). The latest version is 7.3.8 - please update.
Also, if you think that FSUIPC is crashing, I need to see your FSUIPC7.log file,

John

[Help FSUIPC 7 PMDG MSFS]

Can you check that you have the following in your FSUIPC7.ini file and if not add it:

[WAPI]
EnableWAPI=Yes

The WAPI is now enabled by default, but if that section isn't there then the presets will not be loaded. I will fix this in the next release.

[Brake Release Issue / P3d 5.3]

10 hours ago, bhorv67 said:

I've tried assigning the brake assignments in FSUIPC either as a direct P3d assignment or via FSUIPC. In the calibration area, I can see the pedals going from 0-to full value, then to 0. I've tried 'Rev'. 

This sounds like the rudder axis has been changed to a digital on/off axis in the registry. See the following FAQ entry to resolve this:

 

John

[FDS interface boards and MSFS2020]

I think that depends on the dll. There seem to be various solutions around for using dlls with lua - for example, see
    https://stackoverflow.com/questions/2835716/how-do-i-call-functions-inside-c-dll-from-lua
    https://blog.devgenius.io/how-to-add-your-c-library-in-lua-46fd246f0fa8
    https://lua-users.org/wiki/LuaProxyDllTwo
I don't see why this wouldn't work in an FSUIPC7 lua script, but best to try it - there is a trial license available at the top of this sub-forum if needed.

John

[Can not get offsets to work with overhead]

13 hours ago, jphere said:

On the FSUIPC7.log, item 312 "WARNING: Joystick ID 10 is duplicated in Registry", not sure if this is a problem or not.

No, that is just a warning - you should be fine as all your 11 devices are identified correctly.

13 hours ago, jphere said:

I am going to try the the item

Maybe try using presets first - there are presets available for most most Rotor  Brake controls which are easier to use. check the preset link I previously provided (has a good search interface for finding presets).

John

[[MSFS] [DEPRECATED] How to program joystick buttons and keys to control PMDG aircraft]

12 hours ago, TheAgileBA said:

I guess in the PMDG folder I would create the SDK folder and place the file in there?

I wouldn't do that. Just keep it anywhere for now - the official version should be released at some point.

12 hours ago, TheAgileBA said:

Is there anything to edit in that file to specify the 600 variant rather than the NG3 or does this not matter? 

No. That file is not used at run-time - you just need it to determine the Rotor Brake parameters.

12 hours ago, TheAgileBA said:

EDIT: 4 hours later, I have managed to get the Couger MFD buttons to now work some of the OHP on the 737-600. The above steps were correct, I just misread and missed out the whole Rotor Break bit. I'm too tired! Thank you for supplying that file, I'm now configuring the rest of the setup!

👍

[fuel levers idle/cutoff for the new PMDG 737-700 MSFS]

A compound button condition applies to the actual state of a 2nd (or more) button (or latch flag) when the assigned button is pressed or released.
This is described in the Advanced User guide, page 21.
This functionality is normally used, for example, to control what an increase/decrease knob sends depending in the position of another selector knob (e.g. the Alt, VS, HDG, etc selector knob on the Bravo).

[Can not get offsets to work with overhead]

I cannot tell much from that log - and I have no idea what you mean by "I think it might be a dupilcate listing in the registry, there seems to be an item 10 listed 2 times."
Please also attach your FSUIPC7.ini file when you attach a log.

56 minutes ago, jphere said:

I can not seem to get toggle switches working,

What toggle switches? For many switches, you need to use the Rotor Brake control (the PMDG 737 custom controls are using this, different from the FSX/P3D versions) or presets - please see https://hubhop.mobiflight.com/presets/.
Also see the following FAQ entry: 

There are also many existing posts on the PMDG 737 for MSFS - maybe review some of those.

Any further issues, please be more specific and show me your .ini as well as .log files.

John

 

[[MSFS] [DEPRECATED] How to program joystick buttons and keys to control PMDG aircraft]

The SDK for the MSFS PMDG 737-700 has still not been released, and so there is no SDK header file (*.h) at the moment. Folks are using the PMDG header file at the moment, which I have attached. Although you may be better looking on the PMDG support forums - I believe there is more information there on the Rotor Brake parameters, although I haven't checked for a while...

John

PMDG_NG3_SDK.h

[fuel levers idle/cutoff for the new PMDG 737-700 MSFS]

I can see the issue, in fact it the aircraft jumps quite suddenly from reverse to forward motion (not just thrust!) for me when de-activating the reversers. I have also tried with the eng1/2 reverse thrust kill presets but the same thing happens. It should be possible to go to reverse idle before cutting - I will keep looking. If anyone else has this working more correctly/efficiently, please advise!
Note that I also found it useful to add a compound condition to the thrust detent, so the throttle decr isn't sent unless the reverser button is on. If you don't do this, the reversers are also activated when you move down through the detent without activating reverser lever first.

 

[fuel levers idle/cutoff for the new PMDG 737-700 MSFS]

16 hours ago, rondon9898 said:

I’ve tried configuring it as one of the posts above but it has not worked. I can get to full reverse, but i can’t then get back to reverse idle

But how have you configured? Maybe attach your FSUIPC7.ini file and I can take a look...

Assign as follows for Throttle1 (and mimic for throtttle 2):
    - assign your throttle1 axis to the 'Direct to FSUIPC calibration' control Throttle1
    - calibrate throttle 1 - set the min/max and you will also need to reverse
    - go to the button assignments panel and activate throttle1 reverser (this will show up as button 8 ) and assign the press to Throttle1 Decr with a parameter of 1 (no repeats!), and release to Throttle1 Cut.
   - move throttle 1 through the detent. This will register as button 24, and assign to Throttle1 Decr with a parameter of 1 and select for repeats.

With this config, you can activate reverse idle with the reverser, then push the throttle down to increase to max reverse thrust, and also use the reverser off to kill reverse thrust.

Let me know how it goes.

John

[P3d 5.3 and WideFS issue]

I can't help without seeing your log and ini files... Please show me your FSUIPC6.log, WideServer.log. WideClient.log and WideClient.ini and FSUIPC6.ini files.

5 hours ago, mulchekp said:

No widefs log file was generated.

I don't understand this - there must be a WideServer.log in your FSUIPC6 installation folder, and a WideClient.log in your WideClient installation folder...

John

[Honeycomb throttle PMDG 737 reverse thrust settings]

It would help if you could attach your FSUIPC7.ini file so that I can see what assignments you have made,,,

I've installed the PMDG 737-700 on my system with the Bravo attached now, and will look into configuring the throttle later today and will report back.
I will use the other thread for this issue, and will close this thread now, so please use that topic/thread going forward.

John

[Lvar & Hvar greyed out]

5 hours ago, KDog88 said:

I tried to attach my log, but it's 30 KB so it won't let me, but I could attache the prev.log if that is any help.

You can always compress/zip a log file if too large to attach...

From the log you attached, it looks like either the WASM hasn't been installed or the WAPI has not been enabled. Please check both, and attach your InstallFSUIPC7.log and FSUIPC7.ini files (as well as your latest FSUIPC7.log file) if you  still have issues.

John

[FSUIPC not creating his folder on the Community Folder]

11 hours ago, josemgtz777 said:

Please help me with the correct step by step. I'm kinda lost.

For the third time, you need to delete (or rename) the file
    C:\Users\josem\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt
and then install FSUIPC7 again.

As that file exists, the installer thinks you have a Steam installation, when you in fact are using an MS Store installation.
I presume that at some stage you installed via steam, and that file is a remnant of that installation and needs to be removed.

[FSUIPC WASM not always loading]

Just now, tdenbrock said:

What I mean is FSUIPC7 is not autoloading on initial startup of MSFS

Again, what do you mean by autoloading? If you mean FSUIPC7 is not loading/receiving the lvars/hvars from the WASM then I have told you what you need to do. If you mean FSUIPC7 is not auto-starting, I have provided you with a link on how to resolve this. I have explained where the MSFS menu is so that you can disconnect/reconnect.
If none of this helps, then please explain what your issues is.

[FSUIPC WASM not always loading]

6 minutes ago, tdenbrock said:

I am having the same issues of FSUIPC not loading on initial startup in MSFS

What do you mean by "FSUIPC not loading"? If you mean that FSUIPC7 is not auto-starting, please see 

 

Or do you mean that FSUIPC7 is not loading/receiving the lvars/hvars from the WASM? If that is the case, follow the instructions in this thread and show me your log (with appropriate logging enabled) and ini files if you want me to take a look.

11 minutes ago, tdenbrock said:

I am not sure how to find the disconnect/reconnect in the MSFS menu. Where is it located?

Strange question...The MSFS drop-down menu is in the FSUIPC7 main window menu bar. Please see the FSUIPC7 User guide.

John

[Fsfo]

The latest WASM release is 0.5.9, (0.5.9a was the beta release of 0.5.9) available in the latest fsuipc7 installer (v7.3.8) or as a separate download - see www.fsuipc.com.
I do not know the requirements for FSFO,

John

[Using Lvars in fsuipc7.ini and or lua scripts]

You can try the attached version - this is the same as the released version but with the lvar creation issue hopefully fixed...please report any issues.

John

FSUIPC7.exe

[Using Lvars in fsuipc7.ini and or lua scripts]

👍

[FSUIPC and possible Tobii background processes?]

The only thing that could be interfering, as far as I can see, is if MCE or Tobi are using the same custom event numbers as used by FSUIPC. You can try changing the ones used by FSUIPC to see if that makes a difference - see the description if the StartEventNo  ini parameter on page 49 of the Advanced User guide.