Posts by IPACS Support

    I know many of you are waiting for a new Android update. The truth is, that its very difficult for us to maintain this platform, especially due to the huge difference in devices performances.

    And simply saying, lets neglect all those users with slow Android devices, you are forgetting that those users make way more than 90% of our customer base! So delivering the update like you have testing in the Alpha channel basically means Aerofly FS 2 will no longer run smooth on 90% of all of our users.

    Apple is making it much simpler for us: First of all the number of devices is much lower and Apple also allows to target newer and faster devices a lot more selectively.

    We are not banning Android as a supported platform but we cannot push updates out as fast as we want. Just adding a minor small new feature or graphic enhancement basically requires us to test a huge amount of devices again and unfortunately many of those devices do have some serious performance quirks with their 3d drivers, making live very difficult for us.


    suppose your PC running Aerofly FS 2 and your iPhone, iPad or Android devices are in the 'same' network, then you proceed as follows:

    - Find out the IP address of your PC, let say its
    - Find out the IP address of your iPhone, iPad or Android device. The first 3 numbers should be the same as the PC, lets say
    - Then for the broadcast IP address in Aerofly enter and leave the port at 49002.

    The port 49002 is not something we have chosen, its a port apps like ForeFlight are listening to.

    Of course ensure you local firewall settings allow Aerofly FS 2 to send data over port 49002

    Have a look at KINGMAN, our ground objects like runway and taxiway support vertex colors that allow you to blend through the ground smoothly. There might be a bug in our exporter right now that if you didn't specify any vertex colors at all, the whole ground is transparent.

    So please add vertex colors and see if the issue is fixed. We will check internally if we can fix this inconsistency.

    yes you can fully use AC3D for aircraft modelling. The DR400 is already included as an example. Some advanced materials in Aerofly require you to add some text strings to AC3D materials, which is a little tedious, but once you know what to do its easy.

    The size of the TGI is a mistake on our side, as we do not compress the TGI in the latest SDK. Don't worry and please verify it yourself but the exported DR400 from AC3D should look just fine.

    We will add a AC3D airport example as well, but you cannot do vertex weights with AC3D so some advanced features are not possible.

    And yes, there are dummy objects in KOKB. We haven't finished the sample yet, they are used to check if the lon lat coordinate system is working properly. The current release version of Aerofly has some issues with the positions, but we have already fixed it internally.

    Once we have feedback, that the KOKB airports works and also people can use AC3D we will officially release the new SDK version.

    we have prepared the airport KOKB in the lon lat coordinate system. A preliminary SDK is available right here:

    Please note, that all the tools and plugins have been updated as well, so you need to install them over again.

    Using the KOKB airport, it should be easier for most users to get an airport into Aerofly FS 2. Basically all that is required now on the user side is that one needs to get an aerial images for reference that is in lon lat coordinates.

    Important: As we had to fix a bug in Aerofly FS 2, please contact us for an updated version via email at mail (at) We have not uploaded this version to Steam yet as it needs further testing.

    Further note: The SDK currently does not allow the creation of your own aerial images. This will be added later. However you can integrate the aerial image yourself in the actual 3D Studio Max file, but this isn't ideal.

    we have just prepared KOKB as a 3D Studio Max file using lon lat coordinates. We will send you a sample tomorrow.

    If its working on your side, we will put this airport into the SDK as well.

    We strongly discourage the use of setting the affinity as this can lead to many bad side effects.

    The only reason why 60 FPS with VSYNC enable does not feel smooth is the already mentioned fact that whenever we load new textures or 3D models and upload them to the 3D card, we get a few frames that take longer than 1/60 seconds, thus resulting in stuttering.

    We cannot reproduce the issue mentioned here, if you have more test cases like this, please report it to us.

    No, the amount of memory of your GPU is not important, this would only be the case if the memory is not enough. Activating all graphic features and flying around KSFO however currently will not consume more than 1.3GB to 1.5GB of memory. So any card with 2GB or more is just fine.

    Unfortunately we have do direct way of getting in touch with NVIDIA or AMD driver developers, they might be able to provide more hints on what the optimal way to upload new GPU data is.