Posts by admin

@RoyPettit: Making Aerofly RC VR compatible is something we are already planning. The major issue is however, the Aerofly RC with its current GUI is not really suitable for VR, basically any desktop based menu stuff is not very user friendly. So we are still experimenting and trying to decide whats the best way to make our RC Simulators VR compatible.

Posting the tm.log here might help. Its in 'Documents/Aerofly FS 2/'

Also, try to remember what changed on your system.

We hardly delete any postings in this forum and very rarely we do modify them.

If we do this, we have a reason for this and please understand we can't justify it all the time.

The forum should be a good place for users to discuss things around Aerofly and to get help or feedback and as such we sometimes remove content to keep the forum readable to other users.

Thanks Kenneth for your posting here. Please understand, if we don't discuss this here openly, but I can assure you the IPACS and Aerofly FS are doing well.

What can you do to support us? Spread the word about Aerofly as much as you can. Each new user helps us to fund further development.

Dalfrak,

yes, this is possible, but its not officially documented as you can break the simulator with it if you do anything wrong here:

//
// this function allows you to override the VR head position and orientation
// be very careful, this function is called right in our render loop, ensure you
// are doing just a quick calculation here and no time consuming stuff!
// YOU HAVE BEEN WARNED!
//
__declspec( dllexport ) bool Aerofly_FS_2_External_DLL_VRHeadDataUpdate(
 const tm_double       time_absolute,
 tm_vector3d          &vr_head_position,
 tm_quaterniond       &vr_head_orientation_quaternion,
 const tm_uint32       vr_num_controllers,
 const tm_vector3d    &vr_controller0_position,
 const tm_quaterniond &vr_controller0_orientation,
 const tm_vector3d    &vr_controller1_position,
 const tm_quaterniond &vr_controller1_orientation )
{
  //
  // vr_head_position and vr_head_orientation are the position and orientation as returned by the VR
  // the coordinate system is:
  //   x - forward
  //   y - left
  //   z - up
  //

  ...

  //
  // these code lines are just for sample purposes, so one can output the head data in the extra window
  //
  {
    std::lock_guard<std::mutex> lock_guard{ VR_DataMutex };
    VR_Head_Position           = vr_head_position;
    VR_Head_Orientation        = vr_head_orientation;
    VR_NumControllers          = vr_num_controllers;
    VR_Controller0_Position    = vr_controller0_position;
    VR_Controller0_Orientation = vr_controller0_orientation;
    VR_Controller1_Position    = vr_controller1_position;
    VR_Controller1_Orientation = vr_controller0_orientation;
  }

  return true;
}

The problem is most likely your CPU. You only have an entry level CPU with just a dual core and fairly low Cache memory. If Aerofly loads new stuff in the background you will likely hit the limitation of your dual core CPU.

Also, it is strongly recommended to not tweak anything on your system, e.g. remove those tools that allow you to adjust some system settings, with Windows 10 this is not required at all and will likely mess up your system. Also, restore all your BIOS settings to default and also do not overclock. In most cases this does not help at all.

When running Aerofly, ensure no other program is active in the background, especially your 'tweak tools' or other things like Skype, Browsers and so on.

Please give us some time to look at the issue with FSWidgets and our Mac version. We might have to update Aerofly to get FSWidgets to work.

Sorry, we don't hold this back on purpose, we just don't have the time at this point to write a good manual.

Sorry for the late reply. We have two 'hacks' for this. If you name the objects with the following words in it

"__nocollision"
"__noshadow"

The objects will not cast shadows and will not be used for collision detection. This is probably what you want for gras stuff.

Ah ok. As fernsehturm.tsc is in 'web mercator' you have to change the following block

        <[string8][coordinate_system][web_mercator]>
        <[vector2_float64][position][8.4902 47.3514]>       // <-- change
        <[float64][height][852]>
        <[float64][size][5000]>
        <[vector2_float64][tower_position][8.49023039045754 47.3513642183328]>  // <-- change
        <[float64][tower_height][1185.552]>
        <[bool][autoheight][false]>
        <[list_tmsimulator_scenery_object][objects][]
            <[tmsimulator_scenery_object][element][0]
                <[string8][type][object]>
                <[string8][geometry][fernsehturm_obj]>
                <[vector3_float64][position][68627.19476622 45913.26755045 0]>  // <-- change
                <[float64][orientation][0]>
                <[int32][autoheight_override][-1]>
            >
        >

If you can't deal with web mercator, use lonlat instead so it would look something like this

        <[string8][coordinate_system][lonlat]>
        <[vector2_float64][position][7.52916739045754 46.9791672183328]>       // <-- change
        <[float64][height][941]>
        <[float64][size][5000]>
        <[vector2_float64][tower_position][7.52916739045754 46.9791672183328]>  // <-- change
        <[float64][tower_height][1185.552]>
        <[bool][autoheight][false]>
        <[list_tmsimulator_scenery_object][objects][]
            <[tmsimulator_scenery_object][element][0]
                <[string8][type][object]>
                <[string8][geometry][fernsehturm_obj]>
                <[vector3_float64][position][7.52916739045754 46.9791672183328 YOURHEIGHTOFFSET]>  // <-- change XXXXX
                <[float64][orientation][0]>
                <[int32][autoheight_override][-1]>
            >
        >

But the fernsehturm is modelled with autoheight false so to adjust the position add a height offset to the line marked with XXXX

The height parameter has no effect for object placement.

The Tower position in the TSC does not place a 3D object there, its just for properly handling the 'tower view'.

The tower is usually inside the TMB file as a virtual name which is then pulled from our XREF object library. You cannot modify this.

@Kerry: Its definitely something outside of Aerofly. Having Icons on Windows with checkmarks looks like a virus, spy ware or some other addon software that shouldn't be on your system. Maybe consider a clean installation of Windows to get rid of this.

You have lots of programs installed so you probably installed this 'piece of software' while installing another program.

@pkaser: Using our SDK there is no problem in making Yaw VR compatible with Aerofly. So maybe ask the developers if they are interested in supporting Aerofly.

If you ask us, the developers, we must also ask you: what can you do wrong with Aerofly? Adding all available AddOns, the sum of all your purchases for FSX is still significantly lower everything you can purchase for Aerofly. So why don't you give Aerofly a try and enjoy it for what it already offers? At its current state, we of course do not offer many things other simulators have, but on the other side we also have strengths where we excel existing simulators and its not only VR!

Also to answer a few of your questions: No, we do not only focus on VR and we personally don't think it takes 80 GB to create a good looking scenery of England!

Behind the scenes we are working on many other features like new regions, new airplanes ( and helicopters ) and of course new features. Aerofly is an evolving simulator so expect to see many exciting features. We can't promise anything at this point, but we can tell you we are fully dedicated to enhance and improve Aerofly FS.

Did you install C++ support for Visual Studio 2015 or 2017? It seems like this is not the case?!

You need to add an

#include <assert.h>

at the top of the file but that should already be the case in our sample, so check that you haven't modified anything by accident.

XRef objects from our USA set referenced lets say in Europe are not always working as we load those XRef objects only if we are close to the USA region.

One can manually fix this by editing the ref TSC file but this will not work after an update.

We are aware of this and we change the XRef system, so more objects of our library are available all over the world.

We also offer this update right here: https://www.aerofly.com/support

This question cannot be answered, it depends on an enormous amount of factors.

It really depends on how the object is being used. If you use the hangar on your airport lets say 1 to 5 times, there is no issue using 2000 polys for it. If you use this hangar 100 times on a single airport you might want to reduce the poly count. Also if adding more polys gives you the chance to maybe save on a few textures, this is also a consideration.

As always, you should consider your overall project and ensure the total polygon count is within reasonable limits, e.g. 100000 to up to 1000000 for complex airports.

No, this should not be the case. The base Aerofly FS 2 on Mac and Windows are the same. They just differ in some quality settings, but not in the quality of the aerial images. We intend to offer our Windows DLCs on the Mac as well, its slightly difficult however using the Mac App Store.