Posts by Jet-Pack (IPACS)

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:

Thread

What happened to the a320.tmd?

@Jet-Pack (IPACS)

What happened to the a320.tmd? In which file are now the cabin (wing) views?

It would make sense to separate things from the large tmd file into smaller topic files so an update would not overwrite every time everything. I could imagine a views tmd file.

TomB

November 6, 2023 at 11:07 PM

            // 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]>
            >

How 'bout this:

Quote from Jürgen N.

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...

Please double check if the localizer is not an offset localizer in the real world. There are a lot of localizers in the real world that are not aligned with the runway centerline.

If you mean passenger bridges or jet-bridges, they are not animated yet.

Gates is where the passengers are waiting before they show their boarding pass. These places are usually in the terminal building which don't usually move.

In L.A. there are numerous rooftop helipads.

It could be that the spoilers are deployed too early, perhaps I can change that easily.

Thank you for the suggestions.

Quote from Pilot4life

Hey iPacs,

I have the airbus a320 glitch it’s just a visual it hasn’t annoyed me or anything, just thought I would show . As others might find it frustrating not sure, but it’s a visual one with the engine bleed if flashing constantly. In a flight then it had crashed the game. Didn’t bother me as I had just go a back into it and was in the same flight. Can’t upload a video, of it

It could be that your Aerofly is running too slow. Please lower the graphics settings if possible and enable limit frame rate.

The pitch trim can be set on the performance takeoff page. It's called THS FOR in percent.

The fix info page is not yet implemented.

Our tutorials for this are available on Aerofly.com:

B787 FMC Preflight | Aerofly FS

B787 Cold and Dark | Aerofly FS

Just pull the heading knob towards you. Tap on it and pull the green center down.

We describe the operation of the autopilot in our tutorial:

Airbus Autopilots | Aerofly FS

These segments are probably encoded as manual or ATC assigned directions in the database. You can fly them using the autopilot heading mode.

Quote from Osmanski

no because the screens they were working in external view when you look inside the cockpit before the last update I’m thinking to buy the new iPhone 16 Pro when release may be they will fix with the new iphone right now I’m with iphone 11

Apparently you know our code better than us... The screens are not updated when you are in the external view, they keep the last image. This means when you look inside you may see something on the screens or you may not. But this optimization has been in place for years and to my knowledge nothing has changed for a long time.

Press the clear key on the MCDU and remove the line DISCONTINUITY from the flight plan page.

This is intentional behavior and has been this way for years. It's a performance optimization that the computational expensive screen rendering is not performed when you don't look at the screens.

The texture quality depends on your device and available memory (RAM).

When the CDU already shows a lower case value for the ILS course and frequency then the auto-tuning works correctly.

LTFM and EDDB are not fully supported because they opened after the navigation database release date. So no real data is in the database.

A limited amount of data is kept in the cache so that you don't need to download it again. As far as I know Aerofly uses WIFI and mobile (if that is active). I know that you can limit mobile data usage per app on Android so that an app only uses WIFI for example, not sure what device you have...

Quote from Max.M

Thanks for the info, here's a screenshot of what i meant:

PFD shows 310 kts, FMC shows 330, MCP is blank

Now I see.

Yes the displayed values on the legs page come from the route. I have no access to the code of the route so these values remain incorrect for the time being, until the developer of the route fixes this.

I would recommend just removing the departure from KSFO or manually adding one of the waypoints along the departure route to the flight plan so that the departure route stops at that waypoint.

If the route is not drawn as a continuous line this can have several reasons: Either the procedure is coded as manual segments, in which case you need to manually change to heading mode or if you used the MCDU to enter the route you need to remove all discontinuities from the route.