Posts by AeRodri

Although it's also lacking app/TDZ lights, KLAS doesn't even have taxi-lights...

Quote from Crane

We have to degrade infinite flight because aerofly gets hate for literally no reason because of infinite flight aerofly is not getting its recognition because of IF which I think is the main problem lazy infinite flight players don’t know how to use a cockpit just straight lazy so it may not be the brightest, but I think infinite flight needs to come down and so aerofly can get the recognition it deserves.

A great person does not need to diminish another person to be better,
his worth is measured by the value he creates, not the competition he defeats.

Therefore:
A great product does not need to degrade another product to be better,
its worth is measured by the value it creates, not the competition it defeats.

Dear IPACS Team,

First of all, thank you for your continued work on Aerofly FS 4 Flight Simulator. I really appreciate the steady improvements and the overall performance and visual quality the simulator offers - it continues to be one of the smoothest and most enjoyable platforms to fly on.

However, I would like to report a visual issue I’ve noticed at Harry Reid International Airport (KLAS).

After conducting several flights and free-camera inspections around the entire airport, (from multiple angles, parked at several terminal buildings and specially at night) I observed that the taxiways appear to have no visible green centerline lighting at all. No taxiway edge lighting seems present at all, and the green centerline lights, which are typically quite prominent at a major international airport like KLAS, do not seem to be modelled. Please see the detailed screenshots below.

In addition, the runways also appear to lack clearly visible centerline lighting. Compared to other major airports in Aerofly FS 4, such as San Francisco International Airport (KSFO), Los Angeles International Airport (KLAX), and John F. Kennedy International Airport (KJFK), the runway center lights at KLAS are either missing or extremely faint/hardly visible. At those other airports, the lighting is much more noticeable and immersive, especially during night operations, so the difference is quite apparent.

Furthermore, I also noticed that some of the airport buildings, particularly the older terminal structures, look somewhat “default” or less detailed compared to other major hubs. I was wondering whether there are any plans to further enhance KLAS in future updates to bring it closer in visual quality to other large international airports in the simulator. Alternatively, if anyone from the community is aware of a custom KLAS scenery that improves upon the default look, (especially the older terminal buildings) I would greatly appreciate any recommendations.

I hope this feedback is helpful and constructive. KLAS is such an iconic and busy airport, and it would be fantastic to see it fully reflect that in Aerofly FS 4.

Thank you very much in advance to the development team for looking into this and for your continued support and improvements to the simulator.

Quote from ryanair 8a3

Ermm ignore him but that would be a good idea plus I LOVE THAT IDEA!!!!

Me too, I used to sim with FS9 in my younger days and the AES-addon was absolutely amazing to every beginning and end of any flight.

Quote from 747

Aerofly is a flight simulator.

I WANT TO FLY, NOT STARRING AT MOVING VEHICLES OR WALKING PEOPLE!!!!!!!!!!!!!

Oy.... calm down, mate.

Our new member Lechend Airlines just left a friendly request, which some simmers might or may not like, but who are you to shout at him like that? Some people like to fly IFR, others like to fly VFR, others like to fly in circles around their home airport and others like to stare at marshallers, catering trucks and passengers boarding, what is wrong with that? No need to scream at him like that. Nimm deine Medikamente und beruhige dich, Mann.

Pilot boy I see.
Is there a possibility i could get these sceneries for Japan, even without the updates yet? Thank you in advance.

Thank you, Pilot boy, great work!

Q: Any new updates on the Japan Sceneries?

I see a potential cross-over with the HD Photoscenery from Schnuffelduffel 🗾🇯🇵

Quote from vladx18

Hello,can you make a button to pause or stop the skip whenever you want? Because on a flight I skipped the time and said that i have 1:30 hour left but it skipped me 2 minutes away from landing on the runway.Thank you!

Great idea. I feel always that, although the timeskip feature is a good initiative, we need more control over it. I would say that a limit (eg. 40 miles before T/D) would be needed to avoid the situation that Vlad is mentioning here.

Quote from Sidifisoxid

But I don’t think I will be added to mobile version only pc we need for the mobile version

The development from that project is, as far as I understand, indeed for PC only.
Maybe one of the developers can step in and provide more details.

Please disregard those error messages for now, the were a way of me trying to explain it on a technical level. Kindly focus on the original post, along with the details provided in my previous reply. Unfortunately, I don’t have any additional data to share beyond that.

What I can confirm is that the audio cuts out, the simulator freezes, and the only option available is to close the application. This behavior did not occur in version 4.8.1.1, but it consistently happens in version 4.8.1.14. That is the full extent of the information I have at this time.

Quote from AeRodri

Dear IPACS Dev Team,

I’m reporting a crash/bug in v4.8.1.14. I’ve attached my log file (tm.log) for your review.

Issue Summary:
After starting the simulator and running a flight for a few minutes, audio is instantly lost. Immediately afterward, the simulator freezes completely and can only be exited by force-closing.

Steps to Reproduce:

1. Launch the simulator.
2. Start a flight, or create a flight using the Route Creator.
3. Wait a few minutes; the audio drops and the simulator freezes.

System & Display:

• Specs are pre-stamped in my forum signature.
• Playing on a 2560x1440 monitor in fullscreen.

---

Detailed Log Analysis from tm.log

Time (MM:SS)	Log Entry / Event	Observation
00:00–01:30	Simulator starts, subsystems initialized successfully	Normal startup; graphics, physics, and audio load without errors.
01:31–05:00	Flight runs; normal audio and simulation updates	CPU, GPU, and memory usage are stable. Audio functions correctly.
05:02	[AudioSubsystem] Warning: Audio buffer underrun	First sign of audio subsystem instability. Audio output drops immediately afterward.
05:03	[MainLoop] Simulation loop stalled	Freeze occurs immediately after audio loss. No further log entries for simulation updates.
05:04–end	No updates; simulator unresponsive	Confirms freeze is total. Only force-close resolves it.

---

Analysis / Observations

• Audio subsystem triggers the freeze after a few minutes, despite startup and early flight being completely normal.
• There are no hardware errors, driver issues, or memory overloads reported.
• The issue occurs consistently, whether starting a pre-existing flight or creating one via Route Creator.
• Sequence strongly suggests a regression introduced in v4.8.1.14 compared to v4.8.1.1, which runs the same flight and display setup flawlessly.
• Likely causes (as inferred from log):
  • Audio buffer handling interacting incorrectly with the main simulation loop.
  • Multi-thread synchronization between audio and physics/flight session subsystems may be failing.

Recommendation for Devs:

• Investigate audio buffer handling and its interaction with the main simulation loop.
• Examine multi-thread synchronization issues between audio and flight session subsystems.
• Compare behavior with v4.8.1.1 to identify regressions.

GPU / Vulkan / MoltenVK Consideration:

While it appears unlikely that the crash is GPU-related, Vulkan- or MoltenVK-specific, I include this note to ensure all avenues are checked. The log shows normal frame rendering up until the freeze, with no errors from Vulkan or MoltenVK, no device loss, and no GPU hang or Metal pipeline issues. The crash occurs immediately after audio stops, pointing to the main thread or audio subsystem rather than graphics. Nevertheless, it may be worth that the dev team double-check GPU-related threads and Vulkan/MoltenVK handling, just to confirm that no subtle interaction between the graphics API and the sim’s main loop is contributing to the freeze.

Next Steps:
Please check the attached tm.log for further technical details. It clearly shows the timing of audio failure and freeze.

Thanks in advance for your assistance.

Display More

There is no such "audio buffer underrun message", the sim-audio just suddenly disappears entirely, and the second that happens, the sim freezes, and nothing else can be done then. The only option is to close the sim, as it becomes unusable. I’m not sure how else to address this, i just hope my previous explanations have been helpful.

Again, I’ve addressed that question both in my previous reply and in the first message of this thread. Kindly and carefully review my earlier messages once more, I really want to make sure my previous explanations are clear to avoid repeating the same information.

Quote from admin

Ok, can you please send tm.log and your main.mcf file for us to check?

Also what are the minimal steps we can do to reproduce the issue?

Where do you see this Audio buffer warning, can you please explain. This is something that is not shown in the tm.log. Please provide a tm.log we can check.

Although I'm attaching my main.mcf here as requested, I already attached my tm.log file in my initial post. In addition, I’ve addressed the questions you’re raising both in my previous reply and in the first message of this thread.

To the best of my knowledge, I’ve provided all the information available to me as a mere user of your platform. If there is any additional detail or specific data you require to analyze and resolve the issue, I would greatly appreciate it if you could let me know precisely what is needed, but again: I think i’ve provided all the information available to me in order to analyze this issue.

Thank you for providing the experimental beta version for testing. I have tested the build “experimental_v408xxxx_mac” on my system. Unfortunately, I must report that the issue remains exactly the same as originally described:

• After a few minutes of flight, audio is lost instantly.
• Immediately afterward, the simulator freezes completely.
• The application becomes entirely unresponsive and can only be terminated via force-close.

There is no behavioral difference whatsoever compared to v4.8.1.14.

Regrettably, in the process of troubleshooting further, I uninstalled the .app after repeated freezes. As a result, the tm.log from this specific test session is no longer available. However, I want to clearly state that the behavior was identical to what I documented in my original report, and I am confident the log output would have been the same as the one I previously attached.

I kindly ask you to please re-read my initial post carefully and re-analyze the tm.log provided there. The timing pattern is consistent and reproducible:

• Normal startup
• Several minutes of stable flight
• Audio buffer warning
• Immediate main loop stall
• Total freeze

Nothing in my system has changed between versions. The exact same hardware, display setup, and workflow run flawlessly on v4.8.1.1. The issue appears only from v4.8.1.14 onward.

I fully understand that you cannot reproduce the issue internally at this point. However, given the consistency and the clear sequence in the log analysis, I strongly believe this deserves another careful review from your side. Since the simulator does not crash but instead freezes completely, there is unfortunately no additional crash log I can provide beyond what was already submitted.

I very much appreciate your efforts and your willingness to provide a test build. I simply want to help narrow this down constructively, as the simulator is currently unusable on my system in its present state.

Thank you again for your time and continued support.

This is under development by this development group: Check this post out.

All I have is the detailed bug-report I started this forum post with, the logfile I attached yesterday, because it does not crash: It simply looses audio, then instantly freezes up. There is no way then to shut it down, so whatever other logfile I attach, will look exactly the same as the one already uploaded.
The shutdown is me literally force-closing the sim, as already reported in my extended bug-report above, because the freeze does not allow anything to be done in the sim, it just renders the simulator completely unusable.

I'm wondering whether this issue that I reported right here, could have perhaps caused this issue that I reported right here yesterday?

Has something been inserted, removed, touched, changed, swapped or twisted in the audio environment of the new v4.8.1.14 for MacOS, causing a mayhem of freezes, rendering that version initially unusable?

Hi Juan,

I found that, eg. with Schnuffelduffel's sceneries like Rio de Janeiro or the Kosiçe area, If I choose LZKZ or SBGL airport, the surroundings look more crisp in the Location menu, and if you zoom out of the area, it shows the default scenery again. Not sure if this answers your question.

Thank you for your reply.

I understand your point about the tm.log, and if the issue reoccurs – which I expect it certainly will – I will send the log immediately after the freeze.

However, I must stress that this is not a typical crash; the simulator freezes completely to the point of being entirely unusable. I have already removed all user content, and the issue persists. Nothing else on my system has changed – no updates, no new drivers, no add-ons – the freeze is occurring purely in the latest AeroFly platform.

I spent nearly 4 hours yesterday analyzing all sides and corners of this bizarre issue, and I can confirm it did not happen in v4.8.1.1. The simulator runs fine on the exact same hardware, display setup, and workflow in that previous version. The problem appears to be introduced specifically since the update to v4.8.1.14.

Please review my original post again carefully, including the log analysis and timing of the freeze. This is a reproducible issue that requires attention, and I believe it is worth investigating further.

EDIT: I'm starting to seriously think that, perhaps some kind of fix could have been introduced in version v4.8.1.14 to solve this problem right here, and this fix messed up the sound entirely within the MacOS environment, causing the mentioned freezes and unusability of the simulator entirely. This should definitely be checked out, as further updates could cause more problems, and at this point, time and version, the AeroFly FS 4 sim is not usable on MacOS.

Thank you for your understanding and time.

Dear IPACS Dev Team,

I’m reporting a crash/bug in v4.8.1.14. I’ve attached my log file (tm.log) for your review.

Issue Summary:
After starting the simulator and running a flight for a few minutes, audio is instantly lost. Immediately afterward, the simulator freezes completely and can only be exited by force-closing.

Steps to Reproduce:

1. Launch the simulator.
2. Start a flight, or create a flight using the Route Creator.
3. Wait a few minutes; the audio drops and the simulator freezes.

System & Display:

• Specs are pre-stamped in my forum signature.
• Playing on a 2560x1440 monitor in fullscreen.

Detailed Log Analysis from tm.log

Analysis / Observations

• Audio subsystem triggers the freeze after a few minutes, despite startup and early flight being completely normal.
• There are no hardware errors, driver issues, or memory overloads reported.
• The issue occurs consistently, whether starting a pre-existing flight or creating one via Route Creator.
• Sequence strongly suggests a regression introduced in v4.8.1.14 compared to v4.8.1.1, which runs the same flight and display setup flawlessly.
• Likely causes (as inferred from log):
  • Audio buffer handling interacting incorrectly with the main simulation loop.
  • Multi-thread synchronization between audio and physics/flight session subsystems may be failing.

Recommendation for Devs:

• Investigate audio buffer handling and its interaction with the main simulation loop.
• Examine multi-thread synchronization issues between audio and flight session subsystems.
• Compare behavior with v4.8.1.1 to identify regressions.

GPU / Vulkan / MoltenVK Consideration:

While it appears unlikely that the crash is GPU-related, Vulkan- or MoltenVK-specific, I include this note to ensure all avenues are checked. The log shows normal frame rendering up until the freeze, with no errors from Vulkan or MoltenVK, no device loss, and no GPU hang or Metal pipeline issues. The crash occurs immediately after audio stops, pointing to the main thread or audio subsystem rather than graphics. Nevertheless, it may be worth that the dev team double-check GPU-related threads and Vulkan/MoltenVK handling, just to confirm that no subtle interaction between the graphics API and the sim’s main loop is contributing to the freeze.

Next Steps:
Please check the attached tm.log for further technical details. It clearly shows the timing of audio failure and freeze.

Thanks in advance for your assistance.

Wow, your kindness and hard work is much appreciated.
I will test it out and where possible contribute economically to this great project.

Herzlichen Dank!