[WideFS Client will not connect to Server after upgrade to Windows 11]

I had the same problem after updating to Win 11 24H2 in early December. A search revealed the solution which John has shown above.

I also had problems with my two GoFlight GF166 displays. Windows recognised them but the displays remained blank. A uninstall and reinstall of the original GoFlight software resolved the problem. My saved profiles were unaffected.

Problems but far fewer than with the new MSFS which would drive me bonkers. I prefer the stability of P3Dv5. 😊

Happy New Year John!

[P3D v4 Radar Contact / WideFS Question]

@John Dowson, very informative and congratulations to @Soundman1 for his efforts.

[RC4 and QW787 D008 Crash]

17 minutes ago, John Dowson said:

No - as far as I am aware (although I have still not looked into this yet) is that this issue is specific to the QW787 with RC4.

That’s my conclusion too.

[RC4 and QW787 D008 Crash]

@John Dowson, this is a strange problem because I’m running a very similar setup to Jon.

The main difference is I run AiCompanion on a WideFS laptop and RC on a second WideFS desktop. No problems whatsoever despite Ai being set at 100% with 230+ Ai at a very busy Heathrow. I also use PMDG 777 but not QW787.

Would site of my FSUIPC6.ini help?

[RC4 and QW787 D008 Crash]

Thanks John. Been a long time since I used that option.  Hopefully he’s reading your replies here

[RC4 and QW787 D008 Crash]

Hi John,

Thanks for your post. I should add I'm running the same version of P3D v5.3 and also have the PMDG 777 and use AIG Ai aircraft at 100%. So my setup is very similar to Jon's bar the QW787 which I don't have.

I have never had this problem in RC4. I have already asked him on the RC forum to check is extra logging is occuring. Although it shouldn't cause any problems it does prevent you or me analysing the log. Is searching for Debug=Please the best way to find logging?

[RC4 and QW787 D008 Crash]

Hi @John Dowson,

I referred Jon to here as it was an FSUIPC error being reported. Jon is advising he can't upload a FSUIPC log as it's 400Mb+

That suggests logging is being enabled. Could that cause a problem in a long flight?

 

[FSUIPC and GoFlight Modules w/Windows 11]

@Carob, do yourself and your father a favour and ditch FS9 / FS2004. Buy P3Dv5 (not 6) for around 50GBP.

I have several GoFlight units - MCP Pro, EFIS, T8, P8 , GF166 and a LGT. All nearly 20 years old and working perfectly with Windows 11.

Firstly, they must be connected to USB2 ports. USB3 are meant to be backward compatible but it can be unreliable. Modern motherboards don’t have USB2 ports but they do have USB2 headers.

I bought this from Amazon. Xiatiaosann 2 Pack 2 Port USB 2.0 Rear Panel Expansion Bracket.

It connects to USB2 Header on my mobo. Then I bought a powered USB2 hub (backward compatible USB3) should be okay. Plug your GoFlight units into the hub that’s plugged into one of the ports on the expansion bracket.

All my units work perfectly. And the scenery is transformed in P3Dv5. Get an Academic Licence. That’s fine. I hope you read this and haven’t given up.

I also use the Pollypot software which has a bit of a learning curve but is very good.

[Assigning letters to Devices problem]

2 hours ago, John Dowson said:

I can't see anything assigned to device U - if you remove that entry, does it get added back?

No it doesn't. Thanks. Just some left over entry from before.

I've updated to 6.2.1 and taken your advice to edit aircraft profiles. Much neater. Thanks. 😁

[Assigning letters to Devices problem]

Hi John,

I'm still getting U=<< MISSING JOYSTICK >> in my ini file. I've  checked it but I'm struggling to find the wrong entries. It's attached. Any help gratefully appreciated.

FSUIPC6.ini

[Assigning letters to Devices problem]

3 minutes ago, John Dowson said:

Yes - not sure where that came from 😉!

Finger problems! 😄

[Assigning letters to Devices problem]

I've discovered the problem. Two opening brackets! 🙄 Amended and all is now well.

[Assigning letters to Devices problem]

Hi John,

I've been assigning letters to devices for years but this problem has me beat.

I have CH Pro Pedals as P; Fulcrum One Yoke as Y and Fulcrum One Throttle Quadrant as T.

The first two are fine. The TQ keeps showing as MISSING even though the entries in the csv file seem fine.

Can you throw some light on the problem please? The reason for the duplicate messages is because I changed the order thinking that might solve it. It didn't.

 

Ray_FSUIPC.zip

[A little help with LUA please]

53 minutes ago, John Dowson said:

Well, they won't as you never pitch down for than 20 degrees.

But it has occurred with shallower descents. My eyes aren’t deceiving me, honest. 😁

Thanks for your insight John. Have a well deserved break. 👍

[A little help with LUA please]

Hi John,

I had two flights today and in neither did the pitch calculations misbehave. I’ll try with a different aircraft tomorrow but given you’re busy with MSFS I won’t take up any more of your time.

Thanks.

[A little help with LUA please]

Hi John,

How strange. I've never seen values like 337 etc. If my aircraft pitched up that much I'd be virtually dead especially with a B737 or Concorde.

As I said it was only on occasions the lua code would result in 8 decimal places or more. I'll try and replicate the situation and report back.

It's like an itch you need to scratch isn't it? 😁

[A little help with LUA please]

Thanks John. I’m guessing the variables in MSFS are different. No idea about that IF condition. I’ll remove it and see what happens.

I’ll try the above tomorrow and report back. 👍

[A little help with LUA please]

Hi John,

I pasted your code in and tried a flight. During the climb it was showing a value like -350 which appeared to equate to 10° nose up.

To answer your question, yes, climbing should show a positive pitch value. Nose down during descent will show a negative value.

During descent it showed -3.5 which appears correct.

I looked at your code but couldn’t figure out what to change. So I reverted to my original code and both climb and descent values were correct despite your suspicions about my code.

Incidentally I don’t use c1 or c2 elsewhere so I’m not sure they’re doing anything.

I can live with what I have as the numerous decimal places are only an occasional nuisance. Thanks for your help nevertheless. 😁

[A little help with LUA please]

Hi John,

I wrote this code several years ago and it appeared to deliver what I wanted but with the exception of multiple decimal places being displayed under certain conditions.

What those conditions are I can’t determine but think it was only when the aircraft was descending.

To answer your question on why mpit changes when <=20 I can’t honestly say. Too long ago.

During the descent today the pitch value remained positive. Around 1.2. I would have expected it to be a negative number.

43 minutes ago, John Dowson said:

Do you want to show +ve pitch for ascending, and -ve pitch for descending (i.e. opposite of what offset 0x0578 holds? Or do you always want to show +ve values for both

I’m not sure. Could you give an example of both and I’ll use whichever seems best.

Thanks.

[A little help with LUA please]

Hi John,

The code is working but not quite as I want. See attached image.

This is when the aircraft is climbing so I would expect a value of 10-15 degrees.

[A little help with LUA please]

It’s displayed in a small window on a WideFS PC. I have other sim values shows such as sim local time, sim UT time, number of Ai aircraft on the ground and airborne.

It’s updated once per second. Your second example looks like what I need. I’ll use that and report back tomorrow. Thanks John. 👍

[A little help with LUA please]

Hi John,

Thanks for your quick reply. “mypit” just refers to the quick ‘n dirty name I gave to the Pitch Angle of the aircraft. It’s especially critical for Concorde as it’s quite possible to stall even with full power plus reheat. 🤣

I’m looking to display a number to one decimal place such as 8.9. Would a string still be the most appropriate?

 

[A little help with LUA please]

Many years ago Pete Dowson gave me his lua file for monitoring various values in FSX and then P3D.

I've added to it but one small problem remains and I can't solve it. Here's the code...

--Display Pitch Angle...
    pit=ipc.readUD(0x0578)
    mypit = pit*360/(65536*65536)
    if mypit <= 20 then --descending
      mypit = math.floor(-mypit *10) / 10
      cond="c1"
    else --ascending
      mypit = pit*360/(65536*65536)
      mypit = 360 - math.floor(mypit *10) / 10
      cond="c2"
    end

A value is displayed but sometimes shows decimal places to 8 or more places. I'd like just 1 please.

What is wrong with it? Any help gratefully appreciated. 😁

[FSUIPC not recognising GoFlight T8 switches]

Hi John,

I found out a long time ago you can’t mix commands for a GoFlight unit between those assigned via the GoFlight program or FSUIPC and Pollypot GIT if you want the LEDs to light up. It’s all or nothing.

I have programmed my hardware for the PMDG737 using their SDK and a post here on your forum describing how to do it. It’s worked perfectly well for several years. I have other aircraft also programmed the same way but are far less complex than the PMDG.

A couple of switches or buttons have more than one command assigned to them which requires manual editing of the FSUIPC6.ini. Very powerful and rewarding. 😄

Of course it all means nothing when the DLL isn’t there! 🤣

[FSUIPC not recognising GoFlight T8 switches]

John,

I still use the GoFlight software to arrange my modules and for assigning default commands to switches / buttons. Maybe if I didn't have that I couldn't assign commands to different aircraft.