Jump to content
The simFlight Network Forums

drnicolas

Members
  • Posts

    13
  • Joined

  • Last visited

Everything posted by drnicolas

  1. My WIdeFS-client needs a long time to connect - today I measured 4min 50 sek. At first it takes about 40 seconds for the WideFS-client window to appear, then another 4min to connect to WideFS-Server After the conect succeded it works. Are there any hints to troubleshoot ? I use the default Settings in the .ini Configuring the server (servername=werkstatt or werkstatt.xxx.yyy) name did not change anything.
  2. o.k, this is different from the FSUIPC for prgrammers.pdf As I understand you, 08c8 gives the turbines shaft RPM , not the PropRPM itself - is that correct ? Can I derive the PropRPM with a constant factor from this ?
  3. I am trying to calculate the correct Prop RPM value with this formula PropRPM = System.Math.Abs((Convert.ToInt64(JetN1.Value) * Convert.ToInt64(RPMScaler.Value)) / 65536 But, I am afraid the calculated value is much too high, should be about 1200 in Idle, but reads out as about 3400. What is wrong ? JetN1 comes from 0898, the Scaler factor from 8c8
  4. It seems, that I have to write some simple testing programs to find the reason for the problems.
  5. Just as the meteorological autumn has started, I begin to think about my Simulator-project again for the winter. My question goes to Pete Dowson and/ or the developer of the FSUIPC Client DLL. Let me first explain my goal: I am building my own small cockpit with mechanical instruments. For this, I have a program running on the FSX-PC which reads or writes airspeed, heading, bank pitch and many other values from or to the simulator and also sends data to or from the mechanical panel. On the mechanical panel, those values are displayed as pointer positions using R/C-servos. The PC program uses the combination of FSUIPC and FSUIPC client.DLL For servicing i have a program where I can test the instruments moving some slider controls with the mouse. There, the positioning of the pointers works very well - smooth and quick movements. I assume, the panel and the underlying software works fine. In the real simulation process it is different: The pointers do not move smooth but in steps. At first, I thought I have to increase the update frequency from 5/s to something higher. But it diesn't really help.. So my question is: Is there a general limitation of the update frequency in either FSUIPC or FSUIPC client DLL ?
  6. Of course this is possible - but the routines for NAV1 and NAV2 have to be different - o.k. I will think about it !
  7. Dear Pete, I am facing a problem when reading the data for NAV1 and NAV2 NAV1 has a compact block of 16 Bytes starting at 0x0c48. NAV2 starts at 0c59 Localiser needle is identical for both NAVs (Byte0) But Byte 1 (0c49/0c5a are of different meaning. For NAV1 ist means "Glideslope needle", for NAV2 it means Backcourse flags, while the glideslope is completely diffenet at 0c6e This makes it hard to process the data with the same set of functions. Is it possible to "push" the data for NAV2 in the same structure as NAV1 , so they look identical? Maybe there are several other places where multiple instances ae needed (I think of COM1-2, Engine1-4)
  8. zero values is in that case nonsense. Because all my instruments go mad within dialog boxes ! I will try it and send you
  9. Maybe the combination off 3364/65 will give the right result. Actually I would like to stop updating my panel hardware with nonsense-values as it does know.
  10. I would like to determine the different states of the flightsim. 1) FS running or not - I do this while trying to access the FS via FSUIPC. If there is an error, o.k. Is there a better way ? 2) FS in the dialiog box where missions or saved flights can be chosen. I would like to find out whenever I am in this box. the "ready-to-fly" flag seems not to be suited - it stays in the "ready-to-fly" state and seems to be "not ready" only when loading scenery Is there a better (or best) way ? Greetings
  11. Hi, I just started experimenting with FSUIPC CLient DLL for .NET. I hope the development will go on, it seems that a lot of things is getting easier under .NET My actual problem is to re-open a connection. The situation is following: FSX is up and running, I open the connection with FSUIPCConnection.Open, anythings works well. The next situation: FSX is down or loading. FSUPCConnection.Open gives an exeception, o.k, To handle this I close the connection and tr again after 5 seconds. But I am afraid, under that condition I will never get a connection even if FSX is up after some time. Stopping the program under VS2005 and restarting solves the problem (which is the first situation) Any ideas ?
  12. Hi, I just started experimenting with the FSUIPC Client DLL for .NET It is very comfortable to use - a real success for anybody programming with .NET But I see a very severe problem: Whenever I exit my program which was started in VS2005, the application stays inmemory consuming actually some 14000 KBytes !! I can't kick it off the memory manually, I have to close VS2005 after each code change and reopen it !! This costs me days !!! Somewhere else I was advised to do something like this: System.Runtime.InteropServices.Marshal.ReleaseComObject(App) App = Nothing ' Eventuell (im Notfall) noch: GC.Collect() GC.WaitForPendingFinalizers() But this didn't help Any ideas ? :oops:
  13. Hi! I am fighting with problems in a VB-Porgram. At first i use the return code of FSUIPC_Open and the dwresult to start the communication with FS2004. This works and the communication starts quite early (at the point the blue window to choose a flight appears). Now the program reads timer-controlled many values from the FS using FSUIPC_Read. The result for the first FSUIPC_Read is used to test for a succssful read. Nevertheless my program locks up whenever the FS becomes "unavailable". Is there a safe way to test for successful contact with FS ?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.