I keep getting stuck in the fly by view. Until Microsoft fixes this bug, is there a file that can be changed to remedy this?

The rather rough method can be found here: http://forum.avsim.net/tutorials/article/30-stuck-in-fly-by-view-simple-solution/but there also is a more gentle solution where you only have to edit one file with Notepad and set a certain setting from True to False. However, the Search option of the forum doesn't work right now due to the System Update.... So maybe it's better to wait a while until Search works again or until someone can post exactly which file and which line to edit.

MS really needs to fix this bug soon...The easiest fix:Navigate to you CurrentSituation.FLT file. You will find it under appdata-local-microsoft-flight-players - your user folder<sequence numbers/letters> - career-current situation.Open the file with notepad.You will see several camera sections, lke camera 1.1, 1.2, 1.3, ect.Each section has a " Locked=" line. They should say " Locked=False".When you get stuck in one of these views, one of those lines has gotten changed to " Locked=True". This is the bug.Change the true back to false , and save. You should be good to go.Hope this helps,MS really needs to fix this bug soon...The easiest fix:Navigate to you CurrentSituation.FLT file. You will find it under appdata-local-microsoft-flight-players - your user folder<sequence numbers/letters> - career-current situation.Open the file with notepad.You will see several camera sections, lke camera 1.1, 1.2, 1.3, ect.Each section has a " Locked=" line. They should say " Locked=False".When you get stuck in one of these views, one of those lines has gotten changed to " Locked=True". This is the bug.Change the true back to false , and save. You should be good to go.Hope this helps,

Thanks, dburne! Now that I know the "formula", that all lines should say Locked=False, I can figure it out on the fly without having to deal with step-by-step instructions.Hook

Thanks for your quick response dburne and J van E. However, I could not find the files mentioned. Would they change if I am a Windows Vista user? Are these files in the MS Flight folder? Where would I find the appdata file?

You are most welcome!It is pretty easy to glance through those lines and spot the one that got changed to true, kind of stands out ya know.So far < knocking on wood> I have only gotten stuck in exterior view one time.I don't know what happens to trigger this though, from what I have seen, seems to be some random occurences to me.

The AppData folder in Windows Vista is equal to the Documents and Settings folder in Windows XP. The AppData folder is also hidden in Vista.To unhide this folder (and others), open the Folder Options in the Vista Control Panel, and on the “View” tab, change the option to “show hidden files and folders”, and click ok.Vista has a new Users Folder which replaces XP’s Documents and Settings. The most important new subfolder is AppData.

Thanks for your quick response dburne and J van E. However, I could not find the files mentioned. Would they change if I am a Windows Vista user? Are these files in the MS Flight folder? Where would I find the appdata file?

Gerry: If you are using Windows Vista, be aware that you might also run into some CTD's (app. crashes), but I hope you haven't.From a developer a couple days ago, regarding CTD's

I just wanted to mention that we did find a bug that is affecting Vista only. It was in code that changed between beta and RTW, so it seems likely that it might have been what was causing your issues. We will have a fix for it in a future update,

Seriously guys, Windows 7 - especially 64 bit, is sooo much better than Vista. Vista was ok, but bloated and a hog - Win 7 much leaner and meaner, does a fantastic job with memory management, and 64 bit kicks some serious butt! And if I am not mistaken, Win 7 does not require any more in the hardware department that Vista did.I previously ran Vista 64 bit, and am much happier with Win 7 64.So any Vista users out there - I know it is a pitb to make an OS change, but if you can swing it give some serious thought to moving to Windows 7 64 bit...

Using Vista64 here,To unstick the stuck in flyby mode press the "R" keyLately I have been getting the "stuck in flyby mode" and found that hitting the r key resets the camera controls.I think "R" stands for remote camera.

To unstick the stuck in flyby mode press the "R" keyLately I have been getting the "stuck in flyby mode" and found that hitting the r key resets the camera controls.

Your are correct, but it has been documented that sometimes the only way to reset the view is to edit the file.

I'm going to guess that people who say that editing the file is the only way to fix it didn't think to try the R key. I wouldn't have thought of it. At least do that first, and if it doesn't work, then mess with editing files. Thanks for the info, bloefield.Hook

I'm going to guess that people who say that editing the file is the only way to fix it didn't think to try the R key. I wouldn't have thought of it. At least do that first, and if it doesn't work, then mess with editing files. Thanks for the info, bloefield.Hook

Agreed,So far in over 30 hours of flight time this has only happened to me once, and I fixed it by editing the file as I posted above. I am sure I did not try the R key, first I have heard of that. If it happens again I will certainly try that first as then I do not have to exit the game.Hopefully though MS will push out a fix for this relatively soon - imagine the folks with Flight that do not go to forums such as this and that happens...

I'm going to guess that people who say that editing the file is the only way to fix it didn't think to try the R key. I wouldn't have thought of it. At least do that first, and if it doesn't work, then mess with editing files. Thanks for the info, bloefield.Hook

That makes sense if people have not tried the "R" key.But sometimes the view gets stuck, no matter what you press, it is a bug and the devs are aware of it.Quote from a developer:

Yeah, the information to delete the current situation should be up on the FAQ or going up soon.We will have a fix for the actual bug in a future update.