I don't care about ATC at all.
Ben
Yep, don’t really care for ATC either. At the moment AI traffic is what I want the most. And after that... a lot of things.
I don't care about ATC at all.
Ben
Yep, don’t really care for ATC either. At the moment AI traffic is what I want the most. And after that... a lot of things.
I’ve been using this since your tip. Got all my old sounds that I used in fsx now (flaps, gear, spoiler, even cabincrew)
It’s great, thanks!
Display MoreExactly, you have to choose between 60 FPS (vsync on) and image tearing (vsync off).
I'm using a Track IR and must say 60 FPS with vsync in AFS2 results in chopped image movements when turning head (this isn't the case in other simulators where 40 FPS can be very smooth).
I ended up preferring the slight image tearing but smooth, natural movements using vsync off.
I found the chopped image with vsync on much more "immersion killing" than image tearing, but it's eventually a question of taste...
Cheers
Antoine
Using an external framelimeter, like rivatuner, at 60 fps solved choppy images for me.
I also externally let my graphic card driver do the vsync, but probably using the ingames vsync with an external framelimiter will allready solve the choppyness for you.
(Vsync and framelimit may seem like double measures, but it defenitly worked for me)
Maybe you can give that a try.
Again, A320 autoland works perfect! Unfortunately I can't replicate your problems.
If you can land the A320 manually at 145kts there's no reason why the AP shouldn't be able to do it.
Well, I reported the same problem a week ago. Happens to me every time. (Normal speed and flaps)
Hmm, well I had it at different airports. I remember trying Zurich and San Francisco.
I don't have that much knowledge, but I use a procedure that worked for me before. I create a flightplan, fly nav mode, press ils during flight. After I've started the descent and the localizer is set up, I press approach. It starts descending by itself (goes well in the path) and A/T manages the speed. I'm using flaps etc. The display does show g/s and loc on it. Everything seems to work and goes according to plan, and then... AP disengages, throttle increases (now that I think of it) and the rolling thing happens. It seems to come out of nowhere.
If you need more info, I'll have to try again and come back to you.
Thx!
Noticed this too.
Also, since the last update, the AP and A/T suddenly disengage during an autoland. It happens at about 100/200 ft above ground without a clear reason (no over- or underspeed etc). I follow the same procedures and never had this before, now it happens every time.
Can anyone confirm this?