- Official Post
Japan airports update
-
admin -
October 13, 2023 at 3:51 PM -
Thread is marked as Resolved.
-
-
Will there be an update of the terrain images? The images are horrible and lacking in definition.
-
Could you please tell us the exact steps to reproduce the issue? What aircraft and how do you create the flight plan?
- Select the A320 livery All Nippon Airlines,
- Create a flight plan with the navigation menu (see attachment RJTT > RJBB),
- Set RWY 34R as spawn ready to take off (or a Cold & Dark place),
- Take off,
- Rotate,
- It becomes laggy here (almost frozen).
The same without flight plan runs seamlessly.
MacBook Pro (restarted) M1 Pro / 16 GB RAM / macOS Sonoma 14.0. Graphic quality set to HIGH instead of the usual ULTRA.
You can feel lags with a flight plan at New York JFK, and no lags with no flight plan (even with streaming OFF)
-
- Official Post
Thank you for those steps, it doesn't show up on our side. It must be something else causing this. We will further investigate it.
-
Dear admin
Finally I found a way to reproduce it.
- You have a flight plan you will encounter lags
- You don't have one it will run seamlessly
With Streaming, I tried New York (DLC loaded) and Tokyo. Both taking off toward the town. With a flight plan Tokyo is almost jammed, New York is laggy. The both towns run seamlessly with no flight plan.
4.03.01.22 (20231012).
Attachments: 4 TM.LOG files with or without flight plans + the flight plan.
A320.
ANA livery but it is the same with another.
No controller / no other Thrustmaster devices.
MacBook Pro / M1 Pro 16 GB RAM.
The MacBook Pro M1 Max 32 GB RAM of ApfelFlieger passes Tokyo because it is over powerful whereas mine is just powerful enough to feel New York laggy under a flight plan.
There's a différence with or without flight plan from Tokyo and probably all other towns.
Best regards
[EDIT] One more thing: it is the same with Streaming OFF, New York with a flight plan is laggy, without works seamlessly!
I have that problem too: with a flight plan, my Mac begins to lag. No flight plan and everything is fine
-
Thank you for those steps, it doesn't show up on our side. It must be something else causing this. We will further investigate it.
I have already reported that problem to support.
-
- Official Post
-
Take off from Tokyo RWY 34R (and spawn here ready for takeoff).
F-PLN: RJTT 34R ISOGO1 CANDYC ILS24LY 24L RJBB (no points between SID and STAR).
A320.
No controller.
Aerofly is closed between 2 tests. And launch out of Steam.
Test with: RJTT 34R ISOGO1 CANDYC ILS24LY 24L RJBB
9 GB RAM and almost frozen.
I use ESC to quit the flight session, I reset route, 9 GB RAM and fluid.
Test with no F-PLN
9 GB and fluid.
Test with no SID no STAR: RJTT RJBB
9 GB fluid!!
Test with SID only RJTT 34R ISOGO1 RJBB
9 GB frozen (almost).
Test with STAR only and no approach RJTT 34R CANDYC RJBB
9GB fluid.
Test with STAR and approach RJTT 34R CANDYC ILS24LY 24L RJBB
9GB fluid
In my case, the STAR is a problem.
Hope it's gonna help.
PS: I think this problem exists since ever. Because at New York I always remarked lags. I said it’s New York! But without flight plan, New York feels totally fluid.
-
- Official Post
Take off from Tokyo RWY 34R (and spawn here ready for takeoff).
F-PLN: RJTT 34R ISOGO1 CANDYC ILS24LY 24L RJBB (no points between SID and STAR).
A320.
No controller.
Aerofly is closed between 2 tests. And launch out of Steam.
Test with: RJTT 34R ISOGO1 CANDYC ILS24LY 24L RJBB
9 GB RAM and almost frozen.
I use ESC to quit the flight session, I reset route, 9 GB RAM and fluid.
Test with no F-PLN
9 GB and fluid.
Test with no SID no STAR: RJTT RJBB
9 GB fluid!!
Test with SID only RJTT 34R ISOGO1 RJBB
9 GB frozen (almost).
Test with STAR only and no approach RJTT 34R CANDYC RJBB
9GB fluid.
Test with STAR and approach RJTT 34R CANDYC ILS24LY 24L RJBB
9GB fluid
In my case, the STAR is a problem.
Hope it's gonna help.
PS: I think this problem exists since ever. Because at New York I always remarked lags. I said it’s New York! But without flight plan, New York feels totally fluid.
Do you experience the same lag with more basic aircraft, e.g. the Sopwith Camel?
-
A320
RJTT 34R ISOGO1 (no next, no end)
Almost frozen after takeoff (as previously).
Sopwith Camel
RJTT 34R ISOGO1 (no next, no end)
Fluid, I think it's OK (controlling this bird, takeoff right ahead is complicated for me)
-
B777 / B737 / B787 / A380
RJTT 34R ISOGO1 (no next, no end)
Almost frozen after takeoff when the town in front is revealed (as previously).
-
I told about STAR but it is the SID. If there’s a SID the problem occurs
-
In my case, I tried this
B787 (Singapore)
KLAS-RKSI
Flight plan : KLAS takeoff runway 25R, then SHEAD7. I15L, landing runway 15L RKSI
Take-off runway 25R with flight plan:
begins to lag just after take-off (6.5 GB)
Then quit flight session, reset route:
perfectly fluid
Takeoff runway 25R without flight plan:
perfectly fluid
Then I Tried an approach with flight plan:
KLAS 25L with I25 : perfectly fluid
I put my tm.log file if you want to see it
-
-
ThomyW You are using a beta, aren't you? Under the previous macOS.
I think the problem is here whenever you use a SID and since a long time. In most case we didn't notice because of power. For exemple, I can notice a difference at New York with out without SID. Tokyo must be too much to stand. However, it is fluid without SID and almost frozen with.
-
ThomyW You are using a beta, aren't you? Under the previous macOS.
I think the problem is here whenever you use a SID and since a long time. In most case we didn't notice because of power. For exemple, I can notice a difference at New York with out without SID. Tokyo must be too much to stand. However, it is fluid without SID and almost frozen with.
No I use the normal version. And yes I 'm still on macOS Ventura, but I don't thing it is problematic.
And what do you mean by "SID" ?
-
No I use the normal version. And yes I 'm still on macOS Ventura, but I don't thing it is problematic.
And what do you mean by "SID" ?
SID stands for Standard Instrument Departure. It is the path that an aircraft flying IFR has to use to depart from an airport to an airway.
If there's a SID in the flight plan I encounter lags in New York and froze in Tokyo. Without everything is fluid.
Flight Plan : Origine > Runway > SID > Airways/waypoints > STAR > Approach > Runway > Destination
-
SID stands for Standard Instrument Departure. It is the path that an aircraft flying IFR has to use to depart from an airport to an airway.
If there's a SID in the flight plan I encounter lags in New York and froze in Tokyo. Without everything is fluid.
Okay I understand,
yes it always lags with SID
-
Okay I understand,
yes it always lags with SID
I'm not alone...
-
Dear admin
I did a few tests with the freshly Aerofly FS 4 Version 4.03.01.24 (20231017). It's always the same but here is my reasoning.
I noticed that when it lags or almost freezes, I'm still able to use the Mac normally, I'm able to edit a heavy picture with Affinity Photo or edit a video with LumaFusion. So, as the entire computer is not jammed, I told myself that it is a "choice" of Aerofly to limit frame rate for some reasons (when there'e a SID in the flight plan).
So I tried :
- Limit frame rate to 60 fps instead of VSYNC,
- Set LOW in graphics quality instead of ULTRA or HIGH,
- After one of my test, after quitting normally Aerofly, I had an Apple crash report (see the attachment).
What ever I did, it is still almost frozen after takeoff (RJTT 34R ISOGO1).
Regards
-