Thomas Richter
-
Posts
1,506 -
Joined
-
Last visited
-
Days Won
26
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Thomas Richter
-
-
Hello Pete
This might not be the right place for this topic but hopefully you'll have the answer!
After calibrating all the controls I was testing in FS to make sure all worked ok and noticed in flight with the A/P engaged, moving the rudder pedals
caused the rudder to move. Am I right in thinking this shouldn't happen whilst in A/P mode?
Thank you
Regards
Alan W
Hi,
Autopilot doesn't control the rudder, it is the Yaw Damper that does. If the Aircraft's Autopilot you use doesn't support have a Yaw Damper then it is uncontrolled.
But in any case also with Yaw Damper ON you will be able to overwrite the rudder with you rudder input but not fully, just damped.
-
Hi,
there are couple Offsets special for FSX only and also couple FS9 Offsets they don't work in FSX, but those are clearly highlighted and described.
You will find under ->Download Links -> Documention the link for FSUIPC3.999 (Documention Only). The PDF 'Documention for Programmer' is for FSUIPC3, it should be the same you will find after full installation in FS9 Moduls/FSUIPC Documents folder. Also with any update you get a PDF file that contains all changes since last document update
-
Attached is version 2.4 of the DLL which will only be of interest to those addressing multiple instances of WideClient on the same machine.
1. Fixes a bug where you couldn't open a connection for any other class instance unless you had a class 0 wideclient/FS running.
2. Enables Payload, AITraffic and UserInput services for class instances > 0.
To get a reference to the Payload/Traffic/UserInput object for a class instance use the new ...ForClass methods. E.g. to get the Payload services that's attached to class instance 2 use:
PayloadServices ps2 = FSUIPCConnection.PayloadServicesForClass(2)
Paul
Hi Paul,
that's really fast !!
Works perfect, fantastic.
Thanks again.
-
Hi Thomas,
I can confirm this is a bug in my DLL. It seems that some of the higher level components like payload and AITraffic services are not aware of 'classes' and so always use the default class 0. Even if your code does not use them they do make a call to FSUIPC when the DLL initialises. So, if there is no class 0 connection then they throw an error.
It'll take me a few days to sort this out properly. I'll post the fix here.
Paul
Hi Paul,
that sounds great (the fix of course) :-)
Thanks a mill!
-
Hi Thomas,
There is no overload that takes only the class number. The overload that takes only an integer is for requesting a specific version of flight sim without using the FlightSim enum.
This is a bit confusing I admit, but not many people use multiple classes.
To connect to a specific class, always use the overload that takes the class number and the flight sim version. You can pass 'any' if you want to work on all versions.
e.g. to connect to class 1 for any version of FS use this:
FSUIPCConnection.Open(1, FlightSim.Any);
Paul
Hi Paul,
thanks for fast answer.
Ups ... Tried that but that doesn't work either
If I use FSUIPCConnection.Open(0, FlightSim.Any); for WideClient Class0 or local FS it is OK. But when I use FSUIPCConnection.Open(1, FlightSim.Any); for WideClient Class1 I just get the following exception
[5132] FSUIPC - FSUIPC.FSUIPCException: FSUIPC Error #9: FSUIPC_ERR_NOTOPEN. The connection to FSUIPC is not open.
[5132] bei FSUIPC.FSUIPCConnection.Process(Byte ClassInstance, IEnumerable`1 GroupNames)
[5132] bei FSUIPC.FSUIPCConnection.Process(Byte ClassInstance, String GroupName)
[5132] bei FSUIPC.UserInputServices..ctor()
[5132] bei FSUIPC.FSUIPCConnection.Open(Byte ClassInstance, Int32 RequiredFlightSimVersion)
[5132] bei FRM_IO.IPC_try_00_Tick(Object sender, EventArgs e)
-
Hi Paul,
to connect to a different Class other than the local or 'Class 0' you 'need' to have a connected local or 'class 0'. If not than you can not connect to a different class?
Lets say you have FS running local and a WideClient local that connects with Class 1.
FSUIPCConnection.Open(); or FSUIPCConnection.Open(0);
and when it is connected you can connet to any other class
FSUIPCConnection.Open(1);
But to connect direct to Class 1 or any other than zero doesn't work?
FSUIPCConnection.Open(1);
Thanks
-
Hi Thomas,
It seems the DLL I uploaded was targeting the .NET 4 Framework so wouldn't have been usable in a .NET 2 project.
I've edited that post with two versions, one for .NET 4 Client Profile and one for .NET 2.
Paul
Hi Paul,
perfect!
Thanks a mill.
-
Hi Paul,
thanks for the updated version 2.3.
I'm working with both .Net2.0 and .Net4.0. The latest version is recognised in .Net4.0 but not in .Net2.0?
-
I downloaded FSUIPC 3.999z and it will not install the file. I followed the directions but what happens is the FSUIPC installs than dissapears right away??? I can't figure it out. Please help.
Hi,
make sure you install with latest Install FSUIPC 3.999z2 not any version before like you may be did with 'FSUIPC 3.999z'. As there were windows updates two days ago it might be that windows removes the FSUIPC.dll because of the signature problem (used by a virus).
-
8=CP(+A,23)A,21,K52,9 ;//2D Throttle-Unit (Cessna)
9=CP(+A,23)A,22,K53,9 ;//2D
11=CP(+A,24)A,2,C65724,0 ;//Autopilot App ;//Mode2
12=CP(+A,24)A,3,C65726,0 ;//Autopilot Alt Hold
13=CP(+A,24)A,19,K54,9 ;//2D Throttle Quadrant (Beech-Baron);//Mode2
Hi
Did yoy see the missing number 10 (ten), should be in line I think (8 - 9 - 10 - 11 - ...).
-
I have a PFC-142 PCATD using Elite GENVIEW V8.0. I am attempting to interface FS2004 to the PFC-142. FS2004 was chosen because the PC currently supporting the PI-142 does not meet the video requirements needed for FSX. The PC is an AMD Athelon running W2000 PRO service pack 4.
I downloaded and installed FSUIPC.dll (v3.99) and copied PFC.dll (V2.307) into the Modules folder for FS2004. When I start FS2004 I get the message, "Flight Simulator unable to load some aircraft or software. File: FSUIPC.dll". There appears to be no other information to help diagnose the problem or determine the exact nature of the error. I sure could use some help!
Hi
1. Did you use the Installer for FSUIPC to install?
2. Is your FSUIPC registered? I "think" you will need to to use PFC.dll.
3. Did you try to run without the PFC.dll, because of above?
-
Hello,
today i bought and installed the 737 brake pressure gauge from flight illusion.
the installation was normal and the test works fine.
now i want to use the gauge with TSR Autobrake but i have no clue how i must configurate this.
can please anyone help me?
thank you very much.
Hi
If you have a registered program version of TSR you can contact TSR support direct please.
support@technicalservicerichter.com
-
Hi
Somewhere an 737 pro sim in Ireland for private use in real pro conditions?
Thanks
-
Hi
Just check this
It is may be what you are looking for and VB.NET is just similar to C#.NET.
-
Hi Paul
I'm writing in C# by using Visual Studio 2005 Pro version. For this your FSUIPCClient.dll works really perfect
Just now I'm trying to use VC++.
I just got it to work and it seems to work here as well okay :-)
-
Hi Paul
Is it possible to use the DLL as well in VC++ like in C#?
-
Hi Folks,
I have a general question about using the variables from FSUIPC.
I use Visual Basic 2008 Express Edition. In an example Code I found this to use the Variables:
Public FlagReadyToFly As Offset(Of Byte()) = New FSUIPC.Offset(Of Byte())(&H3364, 256)
But I don´t get the correct values, which should be....
If you are in the initially menu, it should give you 255.
FSInterrogate says. it is a U8-Type with size 1. How else can I use the variable 3364?
Please Help me! I think I make a general mistake.
Thank you, Tobias
Hi
What you are using is the FSUIPC Client DLL by Paul Henty for Visual-Basic .NET.
With (&H3364, 256) you try to read the Offset 0x3364 with 256 Byte length.
Just read the Documention from Paul Henty and try the examples what is really very well described.
The example code gives you also a clear way to follow to get anything you need to read from or write to FSUIPC.
-
Hi
BCD is the Hex format!
The current version of FSUIPC I use is 3.811.
The HiWord 3306, 2 Byte length gives the value 14353
14353 to Hex gives the result 3811
:D
-
Hi
I think you mean version 4.28 but anyway.
Just check the below link where it is described what is to do to get the correct Simconnect installation.
viewtopic.php?f=54&t=58095 (Help with FSUIPC4 code signature problem)
-
Hi
This values just display how far you are out of Center (value = 0), as long the GS is captured.
You need to read the GS available Offset as well to know that value zero means it is in Center or just that GS is not captured, then the value is of course zero too.
-------------------
Best Regards
Thomas Richter
Info@technical-service-richter.de
-
Of Course yes, with Key assignments. That is all clearly described in the FSUIPC documentation.
-
There is the program GFDisplay from Pete that can control this.
-
Just use the Offset 0x31E8, Water = value 2.
-
This is Graphic Card related. Do you use its latest driver?
Reading 0E80 offset issue
in FSUIPC Support Pete Dowson Modules
Posted
Hi,
make sure you use FSX because this is for FSX (P3D) only.
If you just monitor in FSUIPC the Offset you should see it works ok as you can see below where the AC is placed in EGCC.
77970 Monitor IPC:0E80 (AsciiZ) = [4]"EGCC"
80310 Monitor IPC:0E80 (AsciiZ) = [4]"EGNM"
82634 Monitor IPC:0E80 (AsciiZ) = [4]"EGNE"
83804 Monitor IPC:0E80 (AsciiZ) = [4]"EGNX"
84974 Monitor IPC:0E80 (AsciiZ) = [4]"EGCC"
86144 Monitor IPC:0E80 (AsciiZ) = [4]"EGWC"
87314 Monitor IPC:0E80 (AsciiZ) = [4]"EGOS"
88453 Monitor IPC:0E80 (AsciiZ) = [4]"EGNR"
89623 Monitor IPC:0E80 (AsciiZ) = [4]"EGNH"