Jump to content
The simFlight Network Forums

bigskyfunk

Members
  • Posts

    22
  • Joined

  • Last visited

About bigskyfunk

  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

Profile Information

  • Location
    Oregon

bigskyfunk's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hello Pete, I have been using a registered FSUIPC 3.X to interface my aero, engine and sensor models to FS 2004 and Project Magenta. I use FSUIPC to drive the visuals lat, lon, alt, pitch, roll and heading using external models. I have a few questions about FSX with respect to FSUIPC. 1. Is there a SDK for FSUIPC 4. I went to http://www.schiratti.com/dowson.html and downloaded the latest version, but I could not find the SDK. I would like to upgrade to FSX, but I need FSUIPC to drive FSX. 2. Does the SimConnect SDK replace the functions provided in the FSUIPC 3.X SDK? 3. Assuming there is an SDK for FSUIPC 4, will Visual Studio 6.0 work or do I need to upgrade? Thanks, Lance
  2. Pete, I am using FSUIPC to pass the attitude and position from my own 6doff simulation to FS9. This works fine, but when I try to use the "Spot Plane" view, it stutters and stays in the original position. Can I drive the "Spot Plane" view from FSUIPC? What I want to do is fly on one computer with the cockpit view and use wideview to display the spot plane view, but it is a "stationary stutter" as well. For my application, I dont use any Insturments except for Wideview. Do you have any thoughts or suggestions? Thanks for your time.
  3. Hi Pete, I am having lots of crashes when I am using FSUIPC with FS9. I have a a 3.2 P4 with 2GB ram running FS9 and my own application which interfaces a reflective memory to FS9 via the FSUIPC SDK. I run certified models on a linux system and just pass the position & attitude to FS9. I also have Project Magenta running on two additional pc via wideclient. Sometimes I can run for hours, other times I get crashes repeatedly. I have not been able to determine what is happening and I was hoping you may be able to shed some light on how one might stabilize FS9. Thanks, Lance
  4. Hi Pete, I am wondering how I might add additional views to my simulation by running FS9 on another PC using FSUIPC. Could you explain how this could be done? I have read a few other posts on the subject, but I am confused as to what I should do. Currently, I am running FSUIPC and WideFS on my FS9 PC with Project Magenta on three other PC's via Wideclient. Thanks, Lance
  5. Hello Pete, I am having problems getting flight director data from offsets: 0x2EE8 0x2EF0 I am using Project Magenta MCP to control the Flight director modes & the Project Magenta PFD to display the flight director. The stange thing is the flight director bars work fine. I can fly them in any of the FD modes and they function as expected. I would like to pass the FD roll and pitch to another display, but when I read the offsets above they are always zero. I confirmed this via FS Interogator and my own interface software. Is there another offset that would contain this information? Is there some reason theses offsets would be zero? Thank you for your comments.
  6. Hello Paolo, First, may I suggest you get a copy of FS-Interogator if you have not already. This application is a great aide in debugging applications using FSUIPC. Just go to Peter's site and you should be able to find it. I give it my highest recommedations. I think this may help. Here is the code I use to pass data to FS9 via FSUIPC. // Note vars.z is float as well float f; f = -vars.z + 23.5f; // We add 23.5 to get the eye pt where we want it f = f / METERS_TO_FEET + 0.5f; // Add .5 to round up data[1] = (DWORD) f; data[0] = (DWORD) ((f * 65536.0f * 65536.0f)); dataWrite(0x570, 2 * sizeof(DWORD), (unsigned char *) data); //... and then later fsu.Process(); Yes, in pause mode as well. Sounds just like my problem. My source is a float, the output is cast as a Double precision. Where did you get the S-Function, I would be interested in this feature. We use simulink as well and I have been tasked with creating this capability. More info would be welcome! :)
  7. Thanks to everyone for your suggestions. It turns out the problem was that I incorrectly formatted the altitude input, offset (0x570). I was only setting the upper half of the word. When I correctly set the altitude everything smoothed out and looks great!
  8. Pete and everyone, With the aide of FS Interogater and this helpful community I finally realized that I was not driving the fractional portion of altitude, 0x570. Basically I just had it scaled wrong and it was always zero. After logging and plotting the data I was writing to FS9 I looked at it with FS Interogater and saw that 0x570 was always zero. Then I applied the scaling obtained from FS Interogater and the problems is solved. I really appreciate everyones helpful input. Thanks, Lance
  9. Pete thanks for your response and your comments on my hair-brained "center of the earth" idea. I tried using 0x020 to correct my altitude, but it does not appear to be dynamic. I logged the input and it stays constant during final approach even though the flight path is over some uneven terrain and water. Then I logged the position and attitude parameters I am trying to drive. The log file shows that the altitude is only being updated about every 200ms. I am setting all the other parameters every 20ms. I have simplified the interface to FSUIPC so that all I do is read and write the position (lat,lon,alt) and attitude (phi,theta,psi), (ie offset 0x560 - 580). Do you have any ideas on how to increase the update rate of altitude offset 0x570? Also, I tried to use VDJKEY's idea about driving velocity and accelerations and letting FS9 do the integration, but it does not work at all. Thank you for your help :)
  10. Does anyone know what this altitude is referenced to? Is it center of the earth? Radio Alt? Baro Alt? I have a feeling it is radio alt and in that case I need to know the surface altitude so I can match the altitude generated by my sim which does not have a surface model. Is there a way to extract the surface height below the aircraft using FSUIPC? Thanks for you help as always. Lance
  11. Pete, Thanks for you insight, but I have a pretty hot machine. It is a 3.4 GHz Hyperthreading processor with 2GB of the fastest ram Corsair makes. Also, I am using a reflective memory board with essentially 0 transport delay to pass the data between my simulation and FS9 , (this eliminates delays due to wideview, network cards, etc...). I have a hunch it could be related to the way I am computing lat/lon. I am using the localizer antenna as my reference lat/lon coordinate. From there I compute a range and heading to the aircraft and then compute the A/C lat/lon. However, I think this calculation may create a racheting effect as I get closer to the localizer due to the higher angular rates. I am positive that the altitude data being sent to FS9 is "smooth", (I logged it to a file and plotted it). However, I am not as sure about the lat/lon calculation. I may try to implement a differnent lat/lon calculation and see if I get better results, unless someone has a better idea. Speaking of better ideas, do you know what VDKEYBUS was talking about when he said I should pass my speed, to FS9? VDKEYBUS Wrote: Thanks for any suggestions!
  12. I have implemented most of the suggestions offered and I am still getting choppy performance on "Final Approach" just before touchdown. Once on the ground it is noticeably better, but the the last 300' feet are like descending stairs. Here is the code used to pass lat, lon, and alt to FS: myLat = (latitude * 57.295779513082320876798154814105) * (10001750.0 * 65536.0 * 65536.0) / 90.0; myLon = (longitude * -57.295779513082320876798154814105) * (65536.0 * 65536.0 * 65536.0 * 65536.0) / 360.0; llat = (LONGLONG) myLat; llon = (LONGLONG) myLon; dataWrite(0x560, sizeof(LONGLONG), (unsigned char *) &llat); dataWrite(0x568, sizeof(LONGLONG), (unsigned char *) &llon); f = vars.h_agl + 30.5f; if (f < 5.0f) f = 5.0f; f = f / METERS_TO_FEET + 0.5f; data[1] = (DWORD) f; data[0] = (DWORD) ((f - ((int) f)) * 65536.0f); // Compute pitch bias as function of altitude thetabias = (float) (pow(vars.h_agl,2)*-1.285271e-010) + (float) (vars.h_agl*6.586e-006) + 0.0545f; // APPLY ATTITUDE BIAS HERE!!! // Pitch, roll, true heading data[2] = (DWORD) ((-vars.pitch1+thetabias) * RAD_TO_DEG * FLOAT_ADJ); data[3] = (DWORD) ((-vars.roll1-.01) * RAD_TO_DEG * FLOAT_ADJ); data[4] = (DWORD) ((vars.truHdg1-.009) * RAD_TO_DEG * FLOAT_ADJ); dataWrite(0x570, 5 * sizeof(DWORD), (unsigned char *) data); Thanks for your helpful suggestions!
  13. Maufus thank you for your suggestions. I will try and implement them ASAP and let you know how it works out.
×
×
  • 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.