I don't know of any official Facebook group. We have a FB page but it's not being used at the Moment.
Most of the users have found us here in the Forums and it's one of the easiest ways to reach us as well.
Personally I don't use Facebook for privacy concerns.
I think our EC135 just has a single ADF.
Afternoon Master and apologies for the delay, Doctors appointments.
I have not yet done the coding for this as I was initially stumped as we basically have three switches into one. From what I understand above, a basic input switch and single rocker should enable the logic. As you say the animation is problematic.
Can we use 3 axis's on a single graphical switch ? ie change the axis of rotation of the switch for each output from the logic. For VR the rocker could be positioned higher and between the open/close and the auto point positioned lower than the actual switch to give them separation.
From memory, which I admit is rather suspect most of the time these days
, I believe the KA50 (Blackshark) has similar switches.
Yes, you can link any combination of graphics transformations (rotation and translation) in a chain, including three different rotations. It's just a matter of sending the right input angle to each rotation and making the angles mutually exclusive (only one can be non zero).
Rocker switches are easy and so are two-position switches. What he is asking for is the combination of the two merged into one switch which he have not had in any aircraft yet.
The hotbox for the wheel is messed up, it's inside the panel, so right now you need to aim left of the visible wheel if you sit in the pilot seat.
I have the fix lined up but I'm not sure when it will be merged into the release version.
Ok so the primary function is auto or fixed (center), right? Then I would implement that first as an input switch. Then you can add a rocker switch function which uses the Direction2 property in the controls.tmd (check out the flight stick and/or hat switch of the F18 for example).
Whenever the rocker switch is moved you can then reset the normal auto/fixed switch using the Events of the switch.
The more difficult part will be the animation and the VR compatibility.
If you send me the files I can take a look at it and post an example.
I haven't seen that before but it could be implemented just like a selector knob. You probably won't be able to see the switch being rotated so it won't be apparent that it's rotated along an axis perpendicular to the panel.
After starting the one and only engine of the R22 you need to close the red cover of the clutch switch and wait. Make sure the rotor brake is off. After a bit of a delay the rotor starts spinning and accelerates to idle rotation speed. Then you can throttle up to about 50% which accelerates the rotor. When the RPM reaches 100% you can take off.
As long as the lower left "destination" field is showing dashes there is no destination set.
Click on the airport and select "set as destination" or click on the destination field in the lower left and search for the airport.
What do you mean by split?
The A380 only has thrust reverse on the inboard engine in the real world...
I think the route is missing a destination to be valid.
I assume you are pulling the brake slider down for this or the auto brake is active? With wheel brakes the A380 slowes down quickly and it has to be able to do this for a rejected takeoff.
My recommendation would be to use little to no reverse and use auto brake low or medium. The auto brake is controlling for the real world deceleration rate so it's the most realistic option.
Yea bro its becoming annoying now and ipacs team isn't even responding
We literally responded yesterday... and it's the weekend. No need to remind us every few hours.
It depends on the device how many buildings you can load and see on screen. Devices with only 3 GB of RAM can obviously not display as much as devices with 8 or 12 GB.
What device do you have and are you seeing global airports?
In which country are you currently located in?
The files exist in theory but depending on your device it may not be possible to modify things on mobile. We recommend not changing the mobile app because it could crash your phone and you may potentially loose data in the process.
Please restart your device and see if that helps. Perhaps it also helps if you have a stable WiFi connection, go closer to your WiFi router/modem.
You can also check if other apps use up all the available memory (RAM) on the device. Try clearing the cache from Aerofly FS first, then clear the cache of other large apps to free up some memory. Then try it again.
The camera names are pretty much identical to any other aircraft (see below).
Just create a new option in the user folder like we previously have shown for the a320 custom cameras in another thread:
// cameras start
<[camera][Follow][]
<[string8][Body][Fuselage]>
<[tmvector3d][R0][ -17.0 0.0 2.7 ]>
<[tmvector3d][Direction][ 1.0 0.0 0.0 ]>
>
<[camera_head][CameraPilot][]
<[string8][Body][Fuselage]>
<[tmvector3d][R0][ 1.816 -0.414 0.34 ]>
<[tmvector3d][Direction][ 0.98 0.0 -0.25 ]>
<[bool][InCockpit][true]>
<[bool][Overhead][true]>
<[string8][Tags][cockpit pilot right]>
>
<[camera_head][CameraCopilot][]
<[string8][Body][Fuselage]>
<[tmvector3d][R0][ 1.916 0.414 0.34 ]>
<[tmvector3d][Direction][ 0.98 0.0 -0.2 ]>
<[bool][InCockpit][true]>
<[bool][Overhead][true]>
<[string8][Tags][cockpit copilot left]>
>
<[camera][CameraPassengerRight][]
<[string8][Body][Fuselage]>
<[tmvector3d][R0][ 0.76 -0.4 0.35 ]>
<[tmvector3d][Direction][ 0.98 0.0 -0.2 ]>
<[bool][InCockpit][true]>
<[string8][Tags][cabin window passenger right]>
>
<[camera][CameraPassengerCenter][]
<[string8][Body][Fuselage]>
<[tmvector3d][R0][ 0.76 0.0 0.35 ]>
<[tmvector3d][Direction][ 0.98 0.0 -0.2 ]>
<[bool][InCockpit][true]>
<[string8][Tags][cabin passenger center]>
>
<[camera][CameraPassengerLeft][]
<[string8][Body][Fuselage]>
<[tmvector3d][R0][ 0.76 0.4 0.3 ]>
<[tmvector3d][Direction][ 1.0 0.2 -0.2 ]>
<[bool][InCockpit][true]>
<[string8][Tags][cabin window passenger left]>
>
<[camera][CameraGearView][]
<[string8][Body][Fuselage]>
<[tmvector3d][R0][ -5.452559 0.4 -0.610422 ]>
<[tmvector3d][Direction][ 1.0 0.0 0.0 ]>
<[float64][Cone][-0.1]>
<[bool][InCockpit][false]>
<[string8][Tags][gear]>
>
<[camera][CameraStabilizer][]
<[string8][Body][Fuselage]>
<[tmvector3d][R0][ -6.018798 0.0 2.088263 ]>
<[tmvector3d][Direction][ 0.95 0.0 -0.3 ]>
<[float64][Cone][-0.1]>
<[bool][InCockpit][false]>
<[string8][Tags][tail stabilizer]>
>
<[camera][CameraLeftFuselageView][]
<[string8][Body][Fuselage]>
<[tmvector3d][R0][ 0.480741 3.654212 -0.399291 ]>
<[tmvector3d][X0][ 0.0 -1.0 0.0 ]>
<[tmvector3d][Direction][ 0.2 -1.0 -0.1 ]>
<[float64][Cone][0.0]>
<[bool][InCockpit][false]>
<[string8][Tags][fuselage left]>
>
<[camera][CameraRightFuselageView][]
<[string8][Body][Fuselage]>
<[tmvector3d][R0][ 0.480741 -3.654212 -0.399291 ]>
<[tmvector3d][X0][ 0.0 1.0 0.0 ]>
<[tmvector3d][Direction][ 0.2 1.0 -0.1 ]>
<[float64][Cone][0.0]>
<[bool][InCockpit][false]>
<[string8][Tags][fuselage right]>
>Surprisingly the English language seems not to be supported in the language choice in the homepage.
For your problem I suggest this address:
ikarus.net/rc8-support/
Kind regards from rainy Switzerland
Jürgen
It is, you can switch to English in the top right corner...
