PDA

View Full Version : FSX-Main Exit Toggle FSUIPC Offset?



blueskydriver
05-14-2011, 03:59 PM
Looking to have the Main Exit Toggle work in FSX as an FSUIPC Offset; has anyone got an updated Offset? The past was 3367 or 3376, or using 3110 with bit number (need to verify this), but these were for FS9. Thus, the reason for looking to find an Offset for FSX.

Why? Want to have an Offset or Send Key to FS via FSUIPC (Shift-E main door toggle, with 2-4 for other doors as well). Using InterfaceIT, we set a switch to work for the On/Down state to send Shift-E to FS via FSUIPC and nothing happens (still looking into this). Therefore, want to try Offset...

BSD

fordgt40
05-14-2011, 04:59 PM
BSD

For FSX

Offset 3367 byte length 1 This byte shows doors that are open, one bit per door: 2^0 = Exit1 … 2^3 = Exit 4

David

blueskydriver
05-14-2011, 05:30 PM
David,

Is this 3367 the Output references that would indicate that the doors are opened (as in how it would indicate in the Overhead door status Annunciators)? Is there a Input reference Offset? One that would send for the door to open/close or toggle?

BSD

fordgt40
05-14-2011, 05:38 PM
BSD

Simply, I do not know :) I checked the FSX offset list and did not find any other reference to door(s)
The list says that this offset is both read/write so it might be worth trying to write to this offset and see if it works!

Regards

David

dc8flightdeck
02-25-2013, 05:10 PM
How would SIOC script be written to open exit 1? I know what I have below is not correct.

Var 0116, name doors, Link FSUIPC_INOUT, Offset $3367, Length 1 // doors
{
IF &doors = 0
{
&Door1= 0
}
IF &doors = 1
{
&Door1= 1
}
}
Var 0117, name Door1, Link IOCARD_OUT, Output 33 // Door one light

Peter Dowson
02-27-2013, 06:03 AM
Is this 3367 the Output references that would indicate that the doors are opened (as in how it would indicate in the Overhead door status Annunciators)? Is there a Input reference Offset? One that would send for the door to open/close or toggle?

You've evidently not noticed the actual amount of detail provided. The offsets reference list for FSX has two columns to the right, one for reading and the other for writing, and the entry for 3367 shows ok for both. It notes that the writing is done by sending an event to SimConnect. So you can control each door (of the 4 available in FSX) by changing its bit in 3367, OR by using the same event which FSUIPC4 would send -- "toggle aircraft exit" with 1, 2, 3 or 4 as the parameter. Of course in the latter case you'd test 3367 to see if it was already open or closed. Changing 3367 itself saves you that trouble.

Pete

blueskydriver
02-27-2013, 07:32 AM
Hi Peter,

This post was from a good while back and DC8 must've been looking along the same lines. However, if I remember right, I had a older verison of the FSUIPC Offsets List that only showed 3367 as an FS2004 offset. Later on I got an updated list and found the 3367 was as you mentioned, with the SimConnect references. So, I did manage to use 3367 as intended...

Thank you for following up on this,

John

Peter Dowson
02-27-2013, 09:07 AM
However, if I remember right, I had a older verison of the FSUIPC Offsets List that only showed 3367 as an FS2004 offset. Later on I got an updated list and found the 3367 was as you mentioned, with the SimConnect references. So, I did manage to use 3367 as intended...

There have always been two lists since FSX came out -- the "older list" you mention is for FS9 and before, only. The "FSUIPC4 Offsets Status List" is the prime offset reference for FSX and has been since FSX appeared. It started to become too confusing to include FSX in the original document which tried to cover everthing preceding FSX since FS98! ;-)

Pete

dc8flightdeck
02-27-2013, 10:55 AM
You've evidently not noticed the actual amount of detail provided. The offsets reference list for FSX has two columns to the right, one for reading and the other for writing, and the entry for 3367 shows ok for both. It notes that the writing is done by sending an event to SimConnect. So you can control each door (of the 4 available in FSX) by changing its bit in 3367, OR by using the same event which FSUIPC4 would send -- "toggle aircraft exit" with 1, 2, 3 or 4 as the parameter. Of course in the latter case you'd test 3367 to see if it was already open or closed. Changing 3367 itself saves you that trouble.

Pete

I did notice the detail but with my near zero programming skills I dont understand how to turn it into SIOC script. When the offset is a simple on/off 1 or 0 I can write script to read/write.

John, would you mind posting your script for me to see? Thanks.

dc8flightdeck
03-06-2013, 06:35 PM
I found this SIOC script works nicely to read the status of Exit One and to toggle a corresponding output on an OC USB outputs card.

Justin

// * FileName : Door.txt
// * Date : 3/6/2013



Var 0001, name Exits, Link FSUIPC_IN, Offset $3367, Length 1 // Exit offset
{
&Exit1 = TESTBIT &Exits ,0 // bit 0 is for exit number one. 1 would indicate exit two.
}
Var 0002, name Exit1, Link IOCARD_OUT, Output 8 // Exit 1 indicator

neuman5022
01-05-2014, 08:04 PM
Hi guys,

If I wish to have the doors LIGHTS (indicators) to work with FSUIPC - which offsets will do this ?

Where can I find the LIST Pete is talking about ?

Cheers

Isaac

blueskydriver
01-05-2014, 10:29 PM
Hey Issac,

It has been along time since posting on this, but you're talking about the door open indicators offsets on the B737 FWD Overhead right? If so, I'll dig them up for you...

John

dc8flightdeck
01-06-2014, 02:33 PM
Hi guys,

If I wish to have the doors LIGHTS (indicators) to work with FSUIPC - which offsets will do this ?

Where can I find the LIST Pete is talking about ?

Cheers

Isaac


It is FSUIPC Offset $3367, Length 1

with this offset 0 is for door 1, 1 is for door 2, 2 is foor door 3, etc

See my SIOC script below for door one and two.

Var 179, name glare_ex_1, Link FSUIPC_INOUT, Offset $3367, Length 1 // Exit Offset
{
&G_Door1 = TESTBIT &glare_ex_1 ,0 // Exit 1
}
Var 180, name G_Door1, Link IOCARD_OUT, Output 56 // Glareshield Door one light

// ---------------------------------OVERHEAD EXIT 2---------------------------------------------
Var 181, name glare_ex_2, Link FSUIPC_INOUT, Offset $3367, Length 1 // Exit Offset
{
&G_Door2 = TESTBIT &glare_ex_2 ,1 // Exit 2
}
Var 0132, name G_Door2, Link IOCARD_OUT, Output 56 // Glareshield Door 2 light

neuman5022
01-06-2014, 06:30 PM
Hi guys, thank for your replies.

Yes my aim is to have the Prosim OVHD doors indicators reflect the state of the FSX doors.

I tried this offset 3367 via Prosim so I put there 0x3367.0 for the entry doors, and also 0x3367.1 etc, but nothing happend.

At Pete Dawson docs I have found 3367 2^0, 2^1, 2^2 and 2^3 - as I understand it, then the bits should be 1,2,4,8 respectively - so I tried this also and nothing still. Also tried PM offsets 56F1.0 for entry etc - still no joy.

Can someone please let me know what should I put in Prosim Indicators config lines ? Is it FSUIPC 8 bit U, or perhaps FSUIPC 16 bit U or S ???
Should it be 0x33367.0 or 1,2,3, or 0x3367.1 ,2,4,8, ?

Since I am not using SIOC, FSUIPC is my only choice - but have no idea how to do this.

Many thanks again

Isaac

dc8flightdeck
01-06-2014, 07:45 PM
I havent used Prosim so Im afraid I cant be much help :(

Justin