Comms 2 Panel, left side Intercom.
-
The knob has a rotation / click 5 stae position on it, but it does not rotate in 2D or 3D pit.
-
From memory its not used for its real purpose in BMS. IIRC in BMS its used to adjust the volume difference between AI radio and IVC, whereas in the real jet its used to adjust intercom volume between pilot and ground crew.
INTERCOM Knob
The INTERCOM knob has a cw arrow pointing to INC. Rotating the knob increases the volume of the signals available to the intercom set.
The intercom provides the following functions:
Monitoring and volume control of voice communication between pilot and ground crew or between pilot and tanker boom operator,
monitoring and volume control of AIM-9 missile tone, TWS composite audio tone, and TWS missile launch tone.
Monitoring of systems individually volume controlled from the audio control panels.
Monitoring of fixed volume warning tones (LG and low speed warning tone, TWS missile launch tone, and IFF mode 4 audio monitor) and voice messages. -
From memory its not used for its real purpose in BMS.
You are confusing with IVC balance.
Yes, Intercom know doesn’t move because we do not have Nanard 3D Pit sources file to make it work easily. (low prio to make it work just as adding the missing AIR COND knob.)
Intercom is correctly implemented and works in BMS as it should.
-
confirmed
intercom works fine with mouse, keystroke and analogue axis (the later is what i use)
but the knob does not move in the 3D pit (it’s the same for many other 3D pit knob by the way - unfortunatelty)and there is nno need to check the 2D pit, it’s obsolete and not maintained and completely fubar
-
You are confusing with IVC balance.
Yes, Intercom know doesn’t move because we do not have Nanard 3D Pit sources file to make it work easily. (low prio to make it work just as adding the missing AIR COND knob.)
Intercom is correctly implemented and works in BMS as it should.
rgr that DeeJay, can IVC balance be set from the cockpit then?
@Red:
confirmed
intercom works fine with mouse, keystroke and analogue axis (the later is what i use)
but the knob does not move in the 3D pit (it’s the same for many other 3D pit knob by the way - unfortunatelty)and there is nno need to check the 2D pit, it’s obsolete and not maintained and completely fubar
just goes to show how little I know, I had thought that the 2D cockpit was completely disabled in BMS!
-
rgr that DeeJay, can IVC balance be set from the cockpit then?
yes BUP UHF volume knob if i remember right
just goes to show how little I know, I had thought that the 2D cockpit was completely disabled in BMS!
true and on purpose
but from OPbut it does not rotate in 2D or 3D pit.
wanted to emphasize that the 2D and 3D cockpit are the same => 3D pit
-
From now, anytime we are saying 2D, there is high chance that we are talking about the “2D like” behavior of the 3D cockpit (snapshot mode).
-
Not to be an a$$, but why are these post being made? I had zero Falcon experience 2 years back and after 3 months of flying, searching this forum a million times and reading all significant documentation that comes with the install, I found out these things already. These ‘bugs’ are known to the devs and are probably backlogged somewhere on low priority. What’s the use of mentioning them all again in separate topics now?
New bugs I can understand, no software is flawless and devs appreciate such reports, but when a noob like me can find out about them being mentioned in documentation or already on this forum, why post it again? -
What’s the use of mentioning them all again in separate topics now?
Arf, probably just in case we do not have enought BMS team B-testers flying the jet almost every days … I am just waitng for the “ILS knob” and “oxygene supply lever” bug report now. :neutral:
-
Not to be an a$$, but why are these post being made? I had zero Falcon experience 2 years back and after 3 months of flying, searching this forum a million times and reading all significant documentation that comes with the install, I found out these things already. These ‘bugs’ are known to the devs and are probably backlogged somewhere on low priority. What’s the use of mentioning them all again in separate topics now?
New bugs I can understand, no software is flawless and devs appreciate such reports, but when a noob like me can find out about them being mentioned in documentation or already on this forum, why post it again?Perhaps not all noobs read all documents. I guess we learn something new everyday about falcon because I never knew about this. Everyone is noobish in different areas.
-
Perhaps not all noobs read all documents. I guess we learn something new everyday about falcon because I never knew about this. Everyone is noobish in different areas.
Well if you don’t know, that’s because you don’t use them
if you don’t use them you probably don’t rampstart (not a problem - to each his own)
if you don’t rampstart you’ll probably never need to change the volume
=> it’s not a bug relevant to your use of the simMy point is, we will always have both type of users.
imho those won don’t know, that’s because they are not concerned with this issueagain, not a problem - just explaining that it is not only related to forum search, it’s mainly related to how you use the sim
and it’s indeed backlogged as low priority and as said above, it can’t be fixed by lack of source files. The only way to fix is to recreate a 3D pit from scratch.
since it’s a massive project for such an old detail; it seems logical to be put back in favour of more urgent things. unless of course you guys are willing to wait 3-4 falcon years rather than 3-4 falcon weeks before the next release
but of course you guys wouldn’t know all this, so there’s no problem bumping this when new guys comes in. it’s normal forum behaviour where posting issues is easier than using the search engine -
“….it’s normal forum behaviour where posting issues is easier than using the search engine”
RedDog… I like your answer, thats a wise man
FalconID
-
Not to be an a$$, but why are these post being made? I had zero Falcon experience 2 years back and after 3 months of flying, searching this forum a million times and reading all significant documentation that comes with the install, I found out these things already. These ‘bugs’ are known to the devs and are probably backlogged somewhere on low priority. What’s the use of mentioning them all again in separate topics now?
New bugs I can understand, no software is flawless and devs appreciate such reports, but when a noob like me can find out about them being mentioned in documentation or already on this forum, why post it again?Gyro has a point to prove?