hi,

just a question when I switch the Seat Belt on manually, I can see it displaying on the display, but when to auto although it is supposed to be switched on until 10,000 feet it doesn't display anything. normal behavior?

Noticed that, too.

hi,

just a question when I switch the Seat Belt on manually, I can see it displaying on the display, but when to auto although it is supposed to be switched on until 10,000 feet it doesn't display anything. normal behavior?

 

This is the correct behavior.

The SEAT BELTS memo message should not display when the switch is in the AUTO position.

would it be possible to simulate or switch also the fsx std switch, so addons like FSP could read it ?

 

 

JG

would it be possible to simulate or switch also the fsx std switch, so addons like FSP could read it ?

 

 

JG

 

 

A lot of addons can be configured for a non-standard switch. In FSP, for example, you can deactivate the seat belt sign penalty. (IIRC you can also define a hotkey for the seat belt sign to be toggled "in" FSP.)

thats not what i want, i want to switch exactly 1 (in words ONE) VC seat belt knob (using just the VC) and not an additional keyboard knob for that, i realy dont like that... i do that bull over years allready .... and belive me ..iam sooooooo tired of it !

 

it is working for the door and so on, why not for the belt switch... it is nothing more than as setting a FSX variable and maybe an additional belt entry in the sound.cfg (as for compatibiliy reasons ? ...not shure)

 

 

edit: ...sorry iam a bit frustrated

 

 

JG

thats not what i want, i want to switch exactly 1 (in words ONE) VC seat belt knob (using just the VC) and not an additional keyboard knob for that, i realy dont like that... i do that bull over years allready .... and belive me ..iam sooooooo tired of it !

 

it is working for the door and so on, why not for the belt switch... it is nothing more than as setting a FSX variable and maybe an additional belt entry in the sound.cfg (as for compatibiliy reasons ? ...not shure)

 

 

edit: ...sorry iam a bit frustrated

 

 

JG

 

 

Other addons than FSP are actively developed and supported. They interface with the more recent aircraft releases (like MCE, for example).

 

You really have to blame outdated and by now unsupported FSP for your frustration ...

Hi Oliver,

 

...i looked over MCE using a video on youtube, my opinion is that the voices are very robotic, the user is also telling all the steps of a flow using voice commands, commanding the PNF as he wouldnt know what to do (example prestart flow on the RW etc...) i dont like that, there is also no airline simulation but atc... i have atc allready using Radar Contact 4.3.

 

...not shure about FSCaptain, i heared good things about it.

 

...on the other hand there is FS2Crew in the pipeline, but also without an airline sim.

 

ithink for present addons, it could be so easy for all just triggering the std FSX variables (same for the strobe and landing lights ? not shure), the interace (fsx variables) is(are) there and dont need to be created, triggering those is an easy task i think.

 

...on the other hand, something new would be nice, for example a penality (chance to hurt the cabin crew) if you do a take off not waiting for this nice new 777 cabin ready ding and ECIAS announcement. as this variable is new and 777 only, it can only be done using the 777 SDK... there are so much possibilitys, the best one would be a interaction between the PMDG plane maintaince and an airline simulation, means if you want to do the PMDG plane maintaince or clear a failiure, you have to pay for it.

 

 

JG

I agree but it's not standard:

 

If an addon airplane uses custom landing lights, for example, the default (SDK) landing lights aren't toggled simultanously.

 

Easy - probably yes; common - no.

 

BTW, FS Captain and MCE both offer a trial version.

 

If an addon airplane uses custom landing lights, for example, the default (SDK) landing lights aren't toggled simultanously.

 

...thats what i meant, if using a custom system while an default system exist, why not triggering the default variable also, so addons can read it easy ?

 

 

JG

...thats what i meant, if using a custom system while an default system exist, why not triggering the default variable also, so addons can read it easy ?

 

Because it is not very efficient to have to constantly query and read the state of ALL the default FSX variables and trigger changes, even when this is not really required. Therefore, we are doing this only for variables that make sense to be used by 3rd party add-ons, but obviously we are not aware of all the FSX variables that are used by each one of the numerous add-ons in the market.

 

To be honest, it never crossed my mind that any add-on may need to know the position of the seat belts switch.

 

Anyway, we will add the seat belts switch in the next update. 

 

BTW, there was a bug setting the default FSX landing lights in the release version which will also be fixed in the next update.

Hi Michael,

 

that is what i call professional customer care (but to whom iam talking that), Thank You Sir !

 

...i know that was a good investment B)

 

 

JG

Because it is not very efficient to have to constantly query and read the state of ALL the default FSX variables and trigger changes, even when this is not really required. Therefore, we are doing this only for variables that make sense to be used by 3rd party add-ons, but obviously we are not aware of all the FSX variables that are used by each one of the numerous add-ons in the market.

 

To be honest, it never crossed my mind that any add-on may need to know the position of the seat belts switch.

 

Anyway, we will add the seat belts switch in the next update. 

 

BTW, there was a bug setting the default FSX landing lights in the release version which will also be fixed in the next update.

 

 

... which will result in some really smooth interaction between the T7, FS Captain and Flight Deck Companion - thank you very much, Michael!!!