No I don’t believe this will be addressed in the hotfix as the test team is still working on this one and the hotfix build is already complete and going through final testing - progress is being made and it is high pri.
4 Likes
I can’t install this update. It was taking a long time to download. So I went to bed when it was on 6.5 GB completed. When I woke up it was still at the same point. still had movement. The counter and percentage were animated, indicating something was happening but it must have been stuck on the same file all night.
These constant enormous updates (22GB, are you for real?!) are getting ridiculous. Just let me fly the d*&%@#! thing already!
It would be bad enough if it weren’t for the fact that every update introduces new and more interesting bugs that I didn’t have to deal with before.
1 Like
Really hope the hotfix addresses the multiplayer bug that is causing major stutters all over the sim. It’s getting frustrating!
2 Likes
I have tried it again and got some more information. It is apparently getting stuck downloading pc-fs-base-bigfiles-0.1.129.fspatch. It keeps downloading this over and over continuously. It gets to just over 1 GiB and 20% then it resets to 0 and 0% but the file count still remains at [1/57].
Anybody know where I can get some help with this problem? It is so irritating, it was work normally until I started it last night and it forced the update that it can’t complete.
I feel like I should get a refund on the price of this software.
Still nothing about the stupid useless logbook popping up right in the middle of the shutdown ruining the experience. Such an easy fix and they still haven’t done a thing about it.
3 Likes
I thought that there was a beta testing group before the release. Have they tested anything?
Bonjour moi j’ai des problèmes pour réinstaller certain avions qui me fond planter le jeu des conseils a donner MERCI😎
SOLVED: This fixed it for me.
THE DOWNLOAD SEEMS STUCK ON “BIG FILES”
If the download is stuck on a package such as “pc-fs-base-bigfiles-0.1.59.fspackage”
A) Disable Window Auto-tuning
- In the Windows search bar, type Command and look for ‘Command Prompt’
- In the menu select “Run as administrator”
- Enter: netsh int tcp set global autotuninglevel=disabled
- Press enter
- Reboot your computer
1 Like
This may be a record breaker for the number of "■■■■■■■■"s, but nothing to be proud of 
Thanks for pointing this out and have no regards or help for frustrated guy venting his frustration.
Well hello Mr @HarryRaner. What an emotional outbreak. The point is: when you don’t study how the sim works and where the updates are you will have a hard time. The information that you seek is on this forum, Jayne posts this info every single time there is an update. This sim is under active development, with regular updates, and it is a very complex piece of software. It is not something that you just jump into and expect that you understand everything at once. So my advise would be: search this forum with the right keywords, tone down your emotions and everyone here will be glad to help you out. Chill?
4 Likes
They discussed this in the dev Q&A and some fixes will come in the next update
Planes from the marketplace or mods?
It would be nice to have a new/trending feedback snapshot, in addition to the overall feedback snapshot.
That way the Top 10 items with the most votes in the past week could be featured, without needing 400+ votes.
Any timeline as to when we’ll see replay mode built in?
Perhaps I can help you. Set in the fliht files (apron.flt,…) the avionics to “True”
[Avionics.0]
Comm1Active=124.850
Comm1Standby=124.850
.
.
.
AudioAdf2Listen=False
AvionicsSwitch=TRUE
Thanks for trying to help but all that does is make the default flight start with the avionics switch turned on.
Also on behalf of other scenery hobbyists, I’d like to thank Asobo for update 1.15.8.0
It has solved a very nasty SDK scenery editor bug. Community in-game developed freeware has survived
1 Like
I was having the same problem. I cleared the binding and then reapplied it and it is working again
You are fortunate, then.
I’ve tried clearing/rebinding for both the Ctrl-1 and the mouse right button - but to no avail, so think yourself lucky it works for you!
For me, I still have the problem with the Ctrl-# actions, despite having investigated it quite deeply. Only the right mouse panning is affected, not the panning lock (middle mouse button). Also, panning with the joystick hat works, but is too coarse to be usable. Pressing F to restore the forward view restores panning with the right-mouse button, but only till I press Cntrl-# again. If I set up a view with the Cnrl-Alt-# command, then enter the view with Alt-# the right mouse panning works, so this is a potential workaround, but it will need to be set up for each view for each plane (which would be a pain), and at the loss of my current settings which use Alt-# keys for various window views.
So I’m no nearer a satisfactory solution with this. I’ve submitted a Zendesk ticket, and as ever received a “Solved” rating which only means it’s been filed in their “backlog” section, never to be looked at again. It’s just so annoying - why would they change something like this, either accidentally or on purpose? Why aren’t simple things like this sorted straight away, rather than accepted as “that’s the way it works now”? It’s easier to fix a new bug immediately when you have it fresh in your mind what has been changed to cause it, but the way that Asobo thinks is beyond me.