I understand that everyone is looking forward to updates, but do we have the right to charge developers that way?
When we buy the software, we agree with what it is at the moment. Any news made by the developer without charging anything for it is a bonus.
Only what is a correction can be charged by us. The rest is a bonus.
Try to not use Vulkan (of course, if you are using Vulkan mode...)
Poderíamos tentar criar nossos cenários, topam?
Something tells me that there is a problem with Vulkan related to the use of ram. This has already been reported from other users.
Try to reduce the graphic options, especially texture quality and test again. A good location to test is Denver and San Francisco.
I hope they fix it one day.
I saw it too... 
Hi Jan,
I think you forgot it in the last update... 
Did you select an ILS approach on your flight plan?
Did you check if the ILS frequency is correct?
It worked, Larry. Thank you very much!
If I'm not asking too much of you or anyone who knows, how do I convert a wav file to TSB? It should be simple to use the AF2 converter, but I don't know ....
It's amazing! Really nice!
Hey Christiano!
I'd die for:
- "blang" sound at touchdown
- "bling cling..." vibrating sound when rolling
Something like:
External Content youtu.beContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
Would be amazing, and a better engines starting sound too...
I have the SDK to convert some wav sounds but I don't know how to do it... 
Hello Aeroflyers,
Does anyone have any tips on how to increase the volume of the A320's rolling sound and also the touchdown onboard. This would be quite useful during landings, and would give some greater realism as well.
Thanks
Hi Jan/iPacs,
Some good news about this issue?
Ty!
Another crash in this region with the texture in High, this time on this screen when I went to select the starting point of the flight. It doesn't happen with texture in medium:
This time I received it too. Same point, now different aircraft:
Please attach a tm.log file from right after the crash.
I have tested a few more changes here, and I am sure the problem is related to the region. I found an exact point where the crash always happens when using Vulkan + Texture Quality High.
I moved the installation to the SSD, made and remade this flight countless times and the crash always occurs there, as long as the combination (Vulkan+Texture High) happens.
I do not believe that it is something of RAM memory because I also reduced other factors, including the video resolution.
And I had no problems with other regions, only in Switzerland some time ago. I need to find the location.
What is certain is that I cannot use textures in High if I want to fly "safely" in these areas. If I could at least put texture high working only in the cockpit, I would be happier already.
Ty again, Overloaded. I have the same memory then you in PC and video (8/2).
So I don't if it's a PC limitation or an AF bug. I am having excellent fps when using Vulkan. I can fly using OpenGL, but I have some strange stutters flying outside views or when looking for the ground...
Thank you, Overloaded. How can I do it? I believe the ram of my PC isn't shared with GPU since the GPU have its own ram. Can I change it?
