Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About juengelj

  • Rank
  1. LOL! Yeah and send me your 10ft screen while you are at sending him the registration keys for products, free of charge, of course! :)
  2. As always, very informative. Thank you again for taking the time to help me out with this. I think I am once again off and running on this adventurous CRJ project. The help/support you provide in invaluable. Keep up the great work! God Bless -Jeremy
  3. Hey Mr. Dowson, WOW! After doing some more reading and research, I have come upon the solution to this problem... Again I must say that FSUIPC is absolutely amazing, thank you so very much for a wonderful tool. Here is a snippet that I hope other people who are trying to figure this stuff out for cockpit building, will find very useful. It looks like you can directly access the controls for FSUIPC through SIOC after all! YEAH! I am so very excited about all that I still have not learned. Can't wait... Anyways, This information was obtained at http://www.lekseecon.nl/howto.html very good source of info... enjoy. Thanks again for helping me sort this through.
  4. Sorry, just a bit of humor... anyways, thanks again for the prompt reply. From the top: Sorry, I wasn't making my intentions clear. I am aware of the other "features", at least mostly, of FSUIPC and I use a lot of them. What I am looking at now, is expanding my simulator to include hardware. The goal is to build a full blown CRJ-700 cockpit as real to life as I can get, using FSUIPC, IOCards, and a lot of time learning new skills! :) So, everything I am asking is from that perspective... sorry for the confusion. Whoa! :) Ok, I think perhaps again I stated this incorrectly... yikes. What I meant to say/presume, which may be entirely incorrect as well, but at least it will accurately state my assumption, is whether or not certain memory locations are reserved to hold the specific "data" that the "events" act upon? In any case, this is precisely what I am trying to figure out. The "Offsets" are the locations where certain data starts, and can "sometimes" be manipulated to insert the data relating/resembling an action that can be used to drive an "action" (IE 0000 becomes 0001 to turn on a light), or just sit there and be readout at a later time. This you also explained below... Right! Am I still looking at this wrong, or is this solution easier than I think. In order change the data(HDG) for the HDG_Bug to the current HDG being flown (let's just say 145), does one need only to "Read" the value of HDG_Current at (0x0580) and the assign that same value to "HDG_Bug" at (0x07CC)? The only potential problem that I see, as I am not a programmer, is that the size allocated at each offset is different... one is 2 bytes, the other is 4. Basically, I am trying to manipulate the data related to the "AP_PANEL_HEADING_SET 66108" control that is listed in your FSX controls document. Remember, I can NOT actually utilize FSUIPC to assign the button to that control listed, because for now, I am trying to find an implementation using these IOCards and SIOC. As such, I have to be able to read and manipulate data using offsets, rather than direct controls within FSX using FSUIPC. Ok, now I get what you meant by the dating back to FS98. It was the original implementation used (utilizing offsets)... Thanks. And again, I thank you for all the hard work you did, and continue to do. I definitely appreciate the fruits of your labor. I also find it amazing that you support the product the way you do in these forums, absolutely fantastic! I couldn't get that level of support from any other software I buy! :) Wait... by "...it changes the offset containing the Heading...", do you mean it changes the data at the offset for the Heading? Because if it changes the actual offset location (from 0x0001 to 0x00A0), I am really confused and will likely toss myself off a bridge! Thanks again Mr. Dowson! V/R Jeremy
  5. Oh! OKAY. So... in other words.... "Controls" and "Offsets" are two ways of saying the same thing? I like turtles... :)
  6. Thank you, Mr. Dowson, for such a timely reply. I am still digesting what you said. I have a tremendous amount of respect for programmers like yourself, and hope one day to be half a good as you... So, if I understand you correctly. (FYI, I am using SIOC to interface with FSUIPC, which is an event driven scripting "language", that you may or may not be familiar with. I don't intend to insult your intelligence, nor breadth of experience, only stating possibly pertinent information.) Basically, 1) FSUIPC interfaces with FSX via the Microsoft predetermined list of simulator "controls" for possible "events". 2) When one maps a hardware action from an input (controller, switch, etc...) recognizable by FSUIPC as a controller input, FSUIPC tells FSX to perform the "event" that the user assigned to it via FSUIPC. (USER_INPUT --> FSUIPC --> FSX) 3) FSUIPC has it's own controls, that it can tell FSX to perform? (I don't understand that) Wouldn't FSX need the control listed to perform it? Sorry for my ignorance. 4) (Memory Allocation) - Events have predetermined memory locations assigned to them. Of which, they hold the data that contains the current state of any given event? If an event occurs, the information starting at that location (offset 0x0000) updates to reflect the change, if applicable. I am assuming this is why you have to define the size of the word? (1, 2, 4, etc...) Ok, if those assumptions are true... then here is where SIOC comes in. From what I understand, SIOC is an interface between hardware and FSUIPC via offsets. So, if I understand this correctly... SIOC is basically poking the information at a given memory address that FSUIPC uses to update simulator events. Since SIOC is event driven, it responds to changes is the data contained starting at the referenced offset. (SIOC Example - Var 1, named FSX_LIGHTS, LINK FSUIPC_INOUT, Offset $07DC, Length 4 If &LIGHTS_SWITCH = 1 &FSX_LIGHTS = CHANGEBITN 0 &FSX_LIGHTS Var 2, named LIGHTS_SWITCH, LINK IOCARDS_SW, Input 1, Type P ) All that said, I don't think I am fully understanding the derivative of the offsets. The list of offsets that you provide in the SDK are those defined by You (FSUIPC)? or by FSX? In other words, is there a 1 to 1 correlation between the FSUIPC events list, and the Offsets List, meaning for every "possible" event there is a predefined memory address or offset assigned to it? Because I cannot find an applicable offset, for an event that FSUIPC references. I know you do not "support" IOCards nor SIOC... That information is given for reference only to help clarify my question. Anyway, I hope that I have NOT confused anyone with my ramblings... As always, thanks in advance for all your help! I really do appreciate it. -Jeremy
  7. Hey All, First of all I would like to thank Pete Dawson for developing a VERY useful tool for sim builders to use. Thanks! Ok, I am somewhat off and running on my first simulator build. I have decided to model my simulator after the CRJ-700. The first this I have done is mapped all the Auto Pilot buttons to hardware buttons using FSUIPC and IOCards. They work great. The problem I am having, is that the center button in the rotary encoders are to be mapped to the CRS, HDG, SPD, ALT "set" functions respectively. They should work like this: 1) The CRS button will change the CRS pointer to the current heading, and the readout should display zero-wind direction to VOR. 2) The HDG button will change the HDG bug to current heading. 3) The SPD button will change the SPD hold to the current SPEED or MACH value. 4) The ALT button will change the ALT hold to the current Altitude. I cannot seem to find these offsets in the offset list documentation. However, they do show up in the FSUIPC event/control drop-down menu's. Can anyone point me in the right direction? Thank you very kindly for your help, in advance. -Jeremy
  • 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.