Art_P

ambitiouspilots-shiftzstats

Sometimes the same jetway has all it's parts and then parts disappear as you move across the apron.  This was something that used to happen with fences in FSX.  In the fence case, it depended on the view angle.  In this jetway case, it appears to be something else.

After reading this topic, I installed FSLTL.  I'm noticing a considerable increase in load times after this installation.  Is this also true using FS Traffic by Just Flight?

The simple answer: The update reset all of the options on the assistance menu to on, so we had to reset them to our preferences. There are plenty of other things from the update that required workarounds more difficult than this one.

Enough of my bad-mouthing MSFS and myself. It seems every time they do an update, I have to learn things over again. I reinstalled the NXi G1000 display and it is working beautifully, just like the real thing according to the instruction manual. I set up a flight plan in the World Map with departure and arrival airports and waypoints. Even though it didn't appear correctly on the World Map, it did appear correctly when the flight was started with no input needed on the G1000, and the autopilot hit all the waypoints with no hint of the TIME legs. I am now a happy camper until the next update, but it would be nice if they could make the World Map work better.

In most cases, the only way I can produce a VFR navigable route in the World Map useable by the autopilot is enter the arrival as a waypoint short of the runway rather than the airport itself, even if the waypoint is custom. I see from other threads that using the NXi version of the G1000 requires entering the flight plan in the device rather than using the World Map.

All of my real flying experience was before GPS and glass cockpits, so I had issues with the glass cockpit aircraft in MSFS. After some time, I adapted to modern cockpits and was having a pleasant relationship with MSFS, including setting up GPS flightplans. This included the defining of departure points, in-route waypoints and destination for VFR flights. After recent MSFS updates, I can no longer set up a VFR flightplan on the World Map. Instead of a straight GPS path from the departure airport to the arrival airport when they are defined, there is a timed path from the runway and on approach and often a kink in the path between these:

 

 

A waypoint can be added beyond the runway takeoff as before:

 

 

An attempt to add a waypoint for approach to the runway results in a path from the timed approach away from the runway:

 

 

When the flight is started, the VFR map seems to show a proper path although the waypoints are not defined:

 

 

However, the autopilot follows the path shown on the World Map instead of what is shown on the VFR map. KPBI-TIME-CAFE-TIME-CD06-MYGF. There appears to be no way to define a flightplan path KPBI-CAFE-CD06-MYGF except for an IFR flightplan. I tried setting the IFR flight plan on the World Map with all appearing okay, then canceling the plan before takeoff. The waypoint before approach to the destination runway was eliminated.

 

I wasn't able to accomplish any navigation using the G1000 add-on and went back to the original, so all that is now happening is with the original G1000. Am I too stupid to use these instruments, or is MSFS broken?

I've not tried to save during a long flight and therefore haven't had a CTD trying to save. However at least for me, the AP doesn't work in a reloaded saved flight anyway, so it's of no use.

One of the hardest things to do in MSFS is find your parking spot location at a large airport unless you use the obnoxious looking visual guidance offered by the game, which I find a non-starter. Taxiways are poorly marked, and ATC ground is useless. Someone in a forum explained that they just let the AI control (co-pilot) take over after landing, so I gave it a try. It works fine, although a bit slow. I thought I could just increase the sim rate, but found that it has no effect on AI control, so I turn the AI control on and off with a key assignment as seems advantageous.

 

Anyway my reason for posting this is to share that I found the AI control setting does not change when you exit the game. If you quit with it active, it will still be active the next time you fly. After I gave the parking method a try, I couldn't understand why I couldn't control the aircraft when I started another flight the next day.

Started the download, ate lunch, took a nap, trimmed two palm trees and download completed without issue. Checked content manager and found everything up to date. Tried USA eastern tour and was directed to download new content. Went to content manager and found download items now appear. Began download and it froze without completing. Tried again and got a CTD before completing. Tried again and it stopped with 16 EiB remaining (=16 billion gigabytes). What?

Just look at other web sights to see what I mean.

 

???

I never flew a real airplane with all the expensive avionics included in FSX and MSFS aircraft let alone an AP. I assumed that FSX accurately depicted the AP functions until I started using MSFS. In order to use the G1000 in MSFS, I had to download the actual manual from Garmin. However, if real aircraft react to the AP like they sometimes do in MSFS, I don't know why more pilots are not being killed these days.

Not thing that does puzzle me about the Baron is what prop speed I should be setting it to at certain levels. I’ve tried looking online but almost every checklist I find has a different setting.

 

I've always understood it to be MP 25" and prop 2500 rpm for climb, and MP 23" and prop 2300 rpm for cruise. Pretty simple.

With the new curves (?) there is no correct setting. You can make the near-center segment less sensitive, but when your controller hits the dogleg you get a sudden overcontrol. Therefore, it is best not to set the sensitivity too low (-50). I'm finding between -30 to -40 is safer. The curve needs to be smoother as it was earlier but is not currently achievable.

I actually tried the numeric method on the ATC window first (it was the method I used most frequently in FSX), and couldn't activate a message that way, either.

 

Must be setup in keyboard control assignments first.

I can't seem to be able to get off the runway in any decent way. I don't appear to have the ability to steer the aircraft once I've landed. Any advice, please?

 

If you don't have rudder pedals or a twist grip joystick, you can enable a setting to provide assistance on takeoffs, but I don't know what to do about landings and taxiing. FSX had an auto-rudder setting, but I don't see it in MSFS.

The first thing I did after loading MSFS to my computer was go to Options>Controls and remap all commands to my yoke, rudder pedals and keyboard. All of the commands used most from the keyboard were assigned to keys without the need to hold down Ctrl, Shift, etc. Since I already did this for FSX, I used the same key assignments where possible. For FSX, I had purchased a cheap miniature USB keyboard and applied labels to the keys rather than using a list to remember them. The parking brake toggle is the space bar.

I have no problem with the Caravan throttle from a cold dark start. Only when it's a saved flight. Like you say, when it happens, the throttle moves but there is no torque increase.

The new update changed the way control sensitivities are adjusted, so I had to redo my setups as shown below:

 

 

This is working for me. If someone thinks otherwise, I would like to see their solution.

After the new update, I tried saving a flight and loading it. Could not move throttle in Caravan, one of the many problems with trying to restart a saved flight.

One hour to install. One visual hiccup during first startup, but no CTD. Everything looking okay.

Don't use either, so I have no opinion

Is that response any better?

 

+1

I had that happen on one day but can't remember what cured it, and it hasn't happened since. Just try exiting and reentering the program, turn on/off weather, AI traffic, etc. Saved flights definitely don't work right. I should keep a list of odd happenings and cures since they are so numerous with this program.

I have a similar dual monitor setup - ac/panel on left display, on the right I typically have the ATC window, FlightShare and FSTramp. The instant that my mouse cursor crosses over to the right hand monitor, my joystick freezes and is unresponsive. A real pain when taxiing. Simple moving the cursor back to the left hand monitor returns everything to normal.

 

I've used this setup for years on FSX without any problems whatsoever. Something has indeed changed in the way MSFS handles display focus.

 

Mine is similar with the main monitor full screen and TrackIR. I like that when you move the VFR map to the second monitor it stays there for future flights. In FSX, you had to move windows to the second monitor every flight, even saved flights. In MSFS, I find it best to leave the ATC window on the main monitor so that you don't lose control by moving to another screen and since you need to continue flying the plane while communicating.

Do you mean ships in the Bing satellite imagery or AI ship traffic? The water texture semi-covers up the imagery of boats, docks, etc., and I have yet to see any ship and ferry traffic with the setting at 100%.