Jump to content
The simFlight Network Forums

lordofwings

Members
  • Posts

    108
  • Joined

  • Last visited

Everything posted by lordofwings

  1. Just wondering, is it possible to write an in-process module for the flight simulator so that it appears on a Menu? For example if I write my application in C#, would it be possible for my app to add a menu entry to start/stop my application? or is that only possible if you use C++ ?
  2. Nope, I was hoping I would not require my users to "now you have to reload your aircraft" or "press the key you defined to reload the aircraft" :( but well, what can I say it is a FS limitation :'(
  3. Ivap 1.92 (or 2.0 alpha) is fully based on SimConnect. It however installs FSUIPC 4.x, why I don't know but probably for some functionality that SimConnect does not provide (doubt that). As for your problem not getting it to work, that is normal. I spent a week trying to get IvAp 1.92 to work in a multi PC configuration with FSX without success. I simply gave up on it until they come up with something more stable.
  4. - Are the payload stations available via FSUIPC read/write? or just read-only? - If I change the AIRCRAFT.CFG of the currently selected aircraft when FS is running, does FS automatically reload it? if not, how can I have FS reload the aircraft configuration file without having to exit?
  5. Ah, got it: in C# use the BitConverter.ToDouble(byte[]) method, that does it.
  6. I am playing with the C# version and noticed it does not have a member to read doubles (Float64) items from FSUIPC. I am trying to read the payload stations, and for example while the weight of the first station (0x1400) displays on FS as 2720, when I read an 8 byte array (don't know how to convert that) I get [0] = 0 [1] = 0 [2] = 0 [3] = 0 [4] = 0 [5] = 64 [6] = 165 [7] = 64 I come up with numbers much much greater than 2720 pounds! How can I read doubles from what FS returns?
  7. Not quite related to FSUIPC butI wondered why it is that many aircraft model designers position all the payload stations at the same level, including those that are supposed to be passengers. For example I looked at the 747-400 AIRCRAFT.CFG (which is then provided in the payload data of FSUIPC) and even though there are three decks (cargo, passenger, lounge/cockpit) all the payload stations are shown with the same vertical value (0.0).
  8. I see that neither FSUIPC nor the Aircraft.CFG have sufficient (or any at all) information to get the dimensions of the currently selected aircraft. At best you get wingspan and tail longitudinal distance as approximations. Any other way to get them?
  9. Thanks! that indeed solved the problem. For reasons unknown to me the FS9.CFG had a very weird value (as shown in the original post). I have corrected it as indicated and the problem is solved.
  10. I noticed there are several Fuel items such as Capacity and Level (%) for the several fuel tanks (left:tip,main,aux), right, center1, center2, center. However FSUIPC seems to be missing some important items such as the Center of Gravity locations of the fuel tanks Sure, that can be read/parsed from the AIRCRAFT.CFG but then that takes away the compatibility thing.
  11. When I use FSInterrogate I see tha the entry 0x012C (Log Book Name) shows the following: A Design)\nLOD1 polygons: 108\nLOD5 polygons: 3615\n\nTHESE FILES MAY NOT BE UPLOADED TO ANY OTHER SITE WITHOUT THE AUTHOR'S WRITTEN PERMISSION. THESE REPAINTS AND MODELS ARE FREEWARE AND MAY NOT BE SOLD, OR PUT ON ANY SITE THAT CHARGES FOR DOWNLOADING FRE and the same is shown when I exit FS2004, it tries to save the logbook entry (or go into that dialog) but presents me with an error showing exactly the same thing above. I think this is being garbled from somewhere. The only Add-on that I have on my FS2004 is FSUIPC and this started happening recently.
×
×
  • 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.