[Message Window Position Bug?]

Hi Pete, hope you had a good holiday. 

I do run in windowed mode usually although the window is maximised and does not move. I use 2 monitors, one for P3d, with other related programs on the other. 

I'll try full screen tonight and see what happens. 

[Message Window Position Bug?]

Hi Pete,

Using FSUIPC 5.113 in P3d 4.0.28.21686.

There seems to be a possible bug in FSUIPC positioning of the green message window (used for ATIS etc). Each time P3d is run and the message window opened it's positioned further down the screen.

I see the location is held in the FSUIPC.ini, and this value is changed when P3d is exited. Here's the relevant part from 3 successive runs:

[Window.Message Window]
Docked=186, 1798, 15850, 261
Undocked=8, 661, 1894, 78

[Window.Message Window]
Docked=304, 2720, 15833, 261
Undocked=8, 661, 1894, 78

[Window.Message Window]
Docked=423, 3642, 15816, 261
Undocked=8, 661, 1894, 78

Each time P3d was run and the ATIS window opened, then the sim was exited. If I run P3d without opening the ATIS (or anything that uses that window) then there is no change to the entries in the .ini.

[P3D v4 - FSUIPC5]

Just copy the whole file, and rename it to FSUIPC5.ini.

[64 bit compatibility?]

Excellent news Pete. 

Quick question, will existing FSUIPC 4 profiles be transferable to FSUIPC 5? 

[Volunteers with multiple devices needed to test improved device detection]

Hi Pete,

 

4.964f seems to work OK here. Only a quick startup to see if things were recognised as I'm a bit short on time tonight due to family matters!

Logs & ini attached.

FSUIPC4.log

FSUIPC4.ini

[Volunteers with multiple devices needed to test improved device detection]

Thanks for your continued work on this Pete. I won't be able to test until this evening though, I'm afraid. 

[Volunteers with multiple devices needed to test improved device detection]

OK, here's the log from a 4.964 run.

FSUIPC4.log

[Volunteers with multiple devices needed to test improved device detection]

Hi Pete, I think the ini was from the 4.964e one. Been swapping back and forth and lost track a bit!

I'll mod the ini with the extra logging and report back shortly.

 

edit: Log now attached.

FSUIPC4.log

[Volunteers with multiple devices needed to test improved device detection]

Hi Pete,

I've just tried 4.964e & it doesn't recognise my 2 Thrustmaster MFD panels ( they're just a collection of buttons really). Going back to 4.964 they're seen and work fine although they're not listed in the "joystick device scan" section in the FSUIPC log. HIDScanner sees the 2 MFDs OK.

Logs from 4.964, 4.964e and HIDScanner attached along with the FSUIPC4.ini

FSUIPC4964e.log

FSUIPC4964.log

HidScanner.log

FSUIPC4.ini

[Some questions about using this with Warthog Hotas]

There are actually buttons in the Warthog throttle unit that get "pressed" when the throttle lever is lifted back over the detent. You can use these to cut the fuel when pressed and restore it when they are released.

[Linda and [E] VRI port 1 "com1" failed to open]

I believe so.

[Linda and [E] VRI port 1 "com1" failed to open]

Just a FYI, the LINDA support forum is hosted at Avsim: http://www.avsim.com/forum/424-linda/

 

The VRI comm port message is only relevant if you're using VRI hardware like their MCP. If you're just using Saitek stuff you can probably just ignore it. ( I do! )

[FSUIPC Linda Info for Pete]

You are not alone Jorge! I've noticed the same thing.

I found a lot of crash dump files while doing some tidying up on the hard drive. Looking into it, they were from P3d, but I hadn't had any notification of a crash after closing P3d. After a bit of trial and error, I narrowed it down to LINDA causing the problem. I'd been using an old version of LINDA ( I could never get the current version to sync properly) so put it down to incompatibilities between that & P3dv3. I've since swapped over to FSUIPC for all my button programming, and removed LINDA.

[Peter]

I think Pro 2016 uses FSUIPC to interface with FSX.

I'd download the latest version here:http://forum.simflight.com/topic/66139-updated-modules/

Unzip & run the "install FSUIPC4.exe" program. That should install FSUIPC into FSX. Assuming Pro2016 works with the unregistered version, you can just click the "not now" button when the registration screen for FSUIPC pops up. Manuals for FSUIPC are in your FSX\Modules\FSUIPC Documents folder after installation, although a lot of the information is only relevant to the registered version.

[4.939c P3d crash]

Blame the jet-lag Pete! :lol:

Thanks for the quick update. I'll try that later.

[4.939c P3d crash]

Hi Pete, hope you had a good holiday. :)

 

I've just tried the latest FSUIPC, version 4.939c at time of writing. With this version, P3d v2.5 with hotfix (2.5.12943) crashes on startup. Reverted to the previous version & all is good again.

I've attached the FSUIPC4.log to this post. Hope it's helpful.

FSUIPC4.zip