Art_P

Why should you have to use a 3rd party program to add functionality that any 7th grade programer could add in 5 minutes. That's pretty stupid. Everytime there's something wrong with this program, we're gonna need a 3rd party app to fix it?

 

I reported the problem to Zendesk and use the SimRateBandit to get by in the meantime. I don't think that is stupid.

Since people are saying that we are (involuntary) beta testers, I decided to troubleshoot my problems and seem to have discovered something (maybe). When I fly with AI traffic, I lose the autopilot at some point in the flight. When I fly without any AI traffic, everything works fine. I've tried it several times each way with the same result. Is this a known issue?

Do you have both the yoke and joystick attached at the same time? If so, try detaching one.

I have not had any of those problems??

 

Using yoke, throttle quadrant and rudder pedals only. I must admit that I had problems that I eventually found were caused by myself in using addons at the same time. But what I am now experiencing is with just the basic application.

I can't believe that I would get to this point, but I now agree with the negative posts. Since the last update, avionics come up blank at flight startup, or if they work at startup, they quit partway thru the flight. Or, the program just crashes to desktop with no error message. Rather than occasionally happening, it has got to the point of always happening.

 

Back to FSX at least until the next update.

Can you go as far away from the plane with that if you want?

 

No, the zoom is limited. Drone view would be needed to go farther. The outside view and controlling it works for me, and it doesn't for others. I shouldn't be in this discussion.

The problem with the normal external view is that when you move the plane, the camera lurches behind as if it's attached by a rope, whereas I sometimes want a view that where the camera remains in a fixed position relative to the aircraft. I can't remember what the view was called in FSX, it's not the locked spot (but it should be).

 

Okay. I really don't see a lot of movement when changing directions on the ground to the extent it's objectionable. In slew mode, the camera is totally locked in place.

I am using two monitor from different manufacturers, with different refresh rates and resolutions, and have never had any problems.

I must be missing something in this discussion. I just use the external view from the menu when flying and get what looks like the FSX locked spot view which can be moved with the POV hat switch on my controller and zoomed with the mouse wheel. Now if we are talking about a separate window, that's another matter.

There are commands that can be assigned in the sim, but downloading the FsSimRateBandit from the library is a better option.

Art, for normal or economy cruise, I would think 2300-2400 rpm is more used, 2500 for high speed cruise. The lower rpm will save a little fuel and lengthen time between overhauls.

 

I agree that there are economy settings, and I certainly like the sound better at lower power/RPM. The MSFS G36 modification I downloaded from the library gives a little too much airspeed at the settings I listed, so it may need a little more tweaking.

As I usually do, I Googled and read the many checklists, reference data narratives available online and then made my own checklist in a text file. There is also a good modification to the flight characteristics of the MSFS Bonanza in the library. It helped me with many of the faults I found in the default plane. Similar to the Baron, it flies with a MP of 25 (except full power above 6000') and RPM of 2500 for climb, cruise and approach based on what I found. Needs the power with flaps down and slows down quickly. Can drop the gear while at cruise speed, must manage fuel tank selection (no both). If you have managed the G1000, you are way ahead of me.

You install add-ons into the Community folder. If you've installed MSFS onto your C drive, it'll be here:

C:\Users\your name\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community

 

I found that path works no matter where your program files were installed, even if it's on another drive.

The Zendesk issues marked as solved would be better thought of as closed, with Asobo most likely moving the bugs to an internal bug tracker.

 

Yeah, I solve most of my problems by moving them to the bottom of the file tray.

If no one complains about something not working in MSFS (and some things do not work) the publisher will not fix it. It will only cause anger to some and relief to yourself to state the problem on the forum. If you find something wrong, research as best you can and report it to the publisher's Zendesk.

 

https://flightsimulator.zendesk.com/hc/en-us/requests/new

 

I'm sorry to say that I have reported some issues to Zendesk, received replies that they were "solved", and they continue to be issues following the latest update.

With FSX out of the box, everything was pure fantasy, improved with Ultimate Terrain for actual coastlines and roads or photo scenery with no autogen at additional cost. MSFS provides photo scenery with autogen, 3d lights at night, seasons and pretty good weather depiction. While not as good as expensive addon scenery, it gives more of a reality feeling than what I was using in FSX, and it utilizes computer hardware that 32 bit FSX couldn't, giving smooth FPS in dense scenery areas. Except in limited areas, sightseeing isn't all that great, but my concern is not with the scenery, but with the problems preventing errorless flying of an airplane from one point to another.

 

The altimeter doesn't work right with real weather, the autopilot doesn't work at all in some areas of the world for some strange reason, airport taxiways are given made-up designators rather than what is in the real world, and other issues reported by others. I can live with the scenery issues, but I cannot live with the functional issues, and am actually a bit angry about it.

Hi Art,

Anyway, I shall be reinstalling it all tomorrow, including Windows (new computer setup coming :) )

 

It looks like all you need is a new motherboard and CPU.

Steve ...

 

Windows is ALWAYS the C: drive. Thats they way it installs.

 

Art...

 

Check your C:\Users\{your name}\App Data\Local\Packages... You'll find the "MicrosoftFlightSimulator_8weky3d8bbwe" folder... in there, under "LocalCache\Packages" you'll find the Community folder. You can install add-ons there and it moves/copies it to your installation drive.

 

If you activate the developers mode, one of the options is to view the install path. Even tho you installed it on a non-C: drive...it will have the path to the Community folder on the C: drive. Much easier to get to.

 

I realize there is a path to the community folder thru C: drive, but the actual folder is on D: drive. Either path is a lot more complicated than G:\MSFS\Community. Developers Mode only shows the C: path on my computer.

Doesn't the folder symbol mean that the folder is actually on another drive?

I have observed the imperfections and accepted that improvements will come until I noticed today why I can't find my way around airports in MSFS vs FSX. Using an airport diagram for MSFS is useless because some dumbnuts assigned taxiways whatever letter of the alphabet he chose rather than consult the airport diagrams for the real world airports. There's a lot of work ahead to make this "sim" anywhere near useful to a real world pilot. Of course you could just fly to/from the few enhanced airports which were done correctly.

Like most people, Windows is on my C: drive

When I installed MSFS, I used my G: drive (it’s an M.2+SSD)

I’m only using it for the new sim. Nothing else.

 

The installation created a handful of folders.. including my community folder. It put it on the same drive.

G:\MSFS\Community - that’s it. It’s so easy to find.

The official folder is G:\MSFS\Official - again very easy to find.

 

Regards

Steve

 

My installation from the Microsoft Store was directed by me to Drive D: and installed in a folder named WpSystem. The path to Community is D:\WpSystem\S-1-5-21-163.......\AppData\Local\Packages\Microsoft\.FlightSimulator_wekybdbbwe\Packages\Community. Not so easy to find.

The online weather data globally is only updated every 4 hours which. probably wouldn't be noticeable in Nevada, but would be very noticeable in the Rocky Mountains for example.

 

Sent from my KFDOWI using Tapatalk

 

And in Florida, they would have to update it every 15 minutes. The METARs even can't be accurate with hourly updates. Four hour updates would certainly explain the problem.

 

Is anyone else having the altimeter problems?

I am considering a new computer to run MSFS 2020. Here's listing of the features of one I'm looking at.

 

Windows 10 Home 64

 

9th Generation Intel® Core™ i7-9700 Processor with vPro™ (3.0 GHz, up to 4.70 GHz with Turbo Boost, 8 Cores, 8 Threads, 12 MB Cache)

 

16 GB DDR4 2666MHz

 

512 GB PCIe SSD

 

NVIDIA® GeForce® GTX 1660 6GB

 

I would like to know if anyone feels this is adequate to to the job or should I invest in something better.

 

Thanks to you all.

 

Don

 

If you are trying to keep cost to a minimum, you are on the right track. With this in mind, I would tweak two things you have listed.

 

1. The memory should be at least 3000Mhz, and that speed should be enabled in Bios.

 

2. The video card should be upgraded to GTX 1660 Ti or at least Super at little extra cost.

Yeah, there is no question that I am in real weather mode. What I am seeing in the sky is apparently from a METAR that is over an hour old. MSFS eventually gets it right. MSFS gives you weather over an hour old and photo scenery over 10 years old.

 

The altimeter and airport beacons are other problems.

I never had good luck with FSX weather, even using AS Next, so maybe I shouldn't be so disappointed. But, I just started a flight with real weather after checking the current METAR as well as looking out the window. The current conditions were reported as scattered clouds at a little over 2000 ft, broken at a little over 3000 ft, a high overcast, and 2 miles visibility making it IFR. When I started the flight, there was blue sky, scattered clouds and plenty of visibility. It was daytime and the airport beacon was on (indicating IFR?).

 

While I like the clouded sky depictions in MSFS, real weather doesn't seem to work, and the airport beacons are on all the time. Am I correct?

 

Also, the altimeter doesn't display the correct altitude under real weather. It was showing 120 feet above sea level instead of the actual 32 feet. Pressing the keyboard selection to set altimeter results in 1800 feet below sea level. If I manually set the altitude on the altimeter, the autopilot doesn't level off at the correct indicated altitude. Is this just my problem?

 

This was the situation before as well as after the second MSFS update 1.8.3.0. I submitted the altimeter issue to the Zendesk and was informed that it was solved well before the update came out.

Well, finished the update and started the sim to check the items I submitted to Zendesk. They had sent me an email saying issues were solved. I can report that NONE of them were fixed. So far I have seen nothing different.