Birdovous

Well... I also have the Saitek Pro Flight Yoke with two throttle quadrant modules... So in theory that gives me 6 analog axis exactly for 4 engines, speed brake and flaps... But at the same time I would be missing all the buttons and switches that are on the Warthog... dilemma... 🙂

I like the fine control over the zoom level that can be achieved with the slider instead of just zoom steps with buttons. I know... I'm odd 😉

Right now for zoom control.

So I tried a different approach, which may not be ideal, but it actually does what I want and enables me to control the speed rake lever using a three-way switch using FSUIPC. Since I failed with the SDK offsets I mapped the two buttons the three way switch controls to the "Axis Spoilers Set" FS Control via the FSUIPC in the following way (perhaps it may save someone some time in case they would like to achieve the same): Switch UP (speed brake lever fully down (on button 1 pressed)): Action: Axis Spoilers Set Value: -16380 Switch MID (speed brake lever in ARMED position) (on button 1 and 2 released)): Action: Axis Spoilers Set Value: -12000 Switch DOWN (speed brake lever in FLIGHT DETENT position (on button 2 pressed)): Action: Axis Spoilers Set Value: 2500 Not ideal, but seems to get the job done. The spoiler axis is not mapped to any axis in P3D or FSUIPC and in FSUIPC it is set to "Not Processed" under the Joystick Calibration tab. I have it mapped to the FLAPS switch on the Thrustmaster Warthog throttle. Of course if anyone has a better idea/way to do this then please share 🙂

Well, yeah... that would probably be a solution... If I had a spare axis 😉 Without one, I'm just trying (and in this particular case also failing) to make the most of what I have. 🙂

I'm trying to map a three way switch on my throttle quadrant to set Speed Brake lever to Down (switch UP position), Armed (switch MID position) and Flight Detent (switch DOWN position) via FSUIPC and offsets from the SDK file that comes with the 747. For all other functions I tried so far it worked without any problems, but now, the speed brake lever setting simply does not work. I'm trying the following offsets: #define EVT_CONTROL_STAND_SPEED_BRAKE_LEVER_DOWN (THIRD_PARTY_EVENT_ID_MIN + 990) #define EVT_CONTROL_STAND_SPEED_BRAKE_LEVER_ARM (THIRD_PARTY_EVENT_ID_MIN + 991) #define EVT_CONTROL_STAND_SPEED_BRAKE_LEVER_FLT_DET (THIRD_PARTY_EVENT_ID_MIN + 992) So in the FSUIPC I have a profile specific button action defined to send value of 1 to the offset 70622 (69632 + 990) when the switch is flipped to the UP position. Then I'm setting offset 70623 (69632 + 991) to 1 when the button is released (switch in MID position) and when the switch is flipped to the DOWN position I'm sending value of 1 to the offset 70624 (69632 + 992) and again when the button is released - which means that the switch is returned back to the middle position I'm again setting offset 70623 to 1. When I check the log of the FSUIPC it shows that the values are sent to the above mentioned offsets and when I use the same method for other buttons and switches it works just fine. I tried the same in the NGX where the offsets in the SDK look slightly different but in general, the result is the same with one slight difference. In the NGX when I map the offsets using the FSUIPC and then start flipping the switch on the joystick the speed brake lever does not move. However, whenever I flip the switch, the mouse cursor changes from an normal arrow to a hand as it does when you hover it over the speed brake lever click-spots. But that is about it... Can anyone please confirm, that what I'm doing is actually correct, or is what I am trying to do not possible? Also I do not have any axis mapped to spoilers either in the P3D or FSUIPC. Thank you 🙂

So... As I did some more digging into the subject I suspect that those may be ADF antennas. In a document I found using the all-knowing Google I found that those are located on top of the fuselage and their covers do have a precipitation-static coating. No color is mentioned in the document but yeah... that is the most I was ale to discover so far. So perhaps black is in fact the way they should be 🙂

Ahh... OK. I was looking at images of 747s and none I found so far were either taken from the angle these antennas would be visible or on those whey there are, they appear to be white/or in the color of the fuselage. So, maybe they are black in real life, which is fine, but then I would really like if there is someone who has the knowledge of why are they so "special" that they are not being painted? Basically out of pure curiosity :) So I thought that I ask around here first, before opening a ticket for something that as it seems is no issue at all 🙂

Yeah, sorry about the signature! I knew I forgot something - corrected 🙂 And yes, I checked the position of the top fuselage beacon and it really is a lot more forward than these two... antennas. As I wrote in the OP, it is nothing critical it just caught my attention and because one of many numerous personality flaws is, that when I look at something, then the first thing I notice are the tiniest flaws and once seen, those can't be unseen 😉 As far as the radome is concerned, it appears that it can be painted. But due to the way it is UV unwrapped it may be a bit tricky to get the perspective right in case one would want to paint a more complex shape on it instead of a uniform color. The above being said about my character flaw... It bugged me so much that it forced me to find the bit of the template responsible for texturing this part of the model! So it is no longer black... It is super green! 😄 Yay! I can go to bed now...

Hello everyone! I was just working on a custom fictional livery for the 748F and I noticed that there are two antennas on top of the fuselage that are just black. Then I started downloading other liveries through the operations center to compare and I realized, that basically in all of them these two pieces of the 3D model are always black. Then I went further and realized that it also applies not only to the F version but to the PAX and 744 (all versions) as well. I know that this is something that is absolutely non critical but I thought that I point that out it actually is a bug and if it is not a bug then I would at least use this opportunity to ask why are they lack and what is their purpose so they have to be black? And in order to be clear about what do I actually mean, here is a screenshot from the default livery: Edit: now when thinking about it, they may be beacons... But then the color should not be flat black... *mind explodes* 🙂 Zdenek