TexasGary

I have the full version. I launched P2ATC today, and I got an error message that says "Unable to initiate session with License Server. Please check your internet connection and security settings to be sure P2ATC has access to the web." I have internet access, and I haven't changed any of my security settings. I have never seen this in almost a year of using P2ATC.

I tried launching P2ATC/MSFS again and then validating and filing a flight plan without actually starting the flight. I then went into the P2ATC COM1 and COM2 control panels, and I was able to raise the green bar with the Up and Dn buttons.

I am running public beta 1a. My ATC voices were not very loud, so I went into the P2A config menu and changed them all from 75% (default) to 100%. This helped, but the ATC voices were still not as loud as the pilot voices. I went into the P2A COM Frequency menu, and there is a menu for setting volume via mute, up, or down buttons with a green bar at the bottom. The green bar was at about 75%. I clicked the volume up and down buttons, but the green bar never moves. If it matters, I did all of this during a flight with an active flight plan.

Thanks Vin.

Whenever I go into General Options > Misc > Pilot Avatar and hover my mouse over one of the options (Default, Pilot 1, Pilot 2, etc.) I used to get a preview on the right side under "Description" of what that avatar looks like. But now when I hover over an option nothing happens. This also applies to other options. It used to give me a description of the option when I hovered over it, but now I don't see that. This started after SU7, but it may not be a bug. It could just be something I inadvertently changed in my settings. Is anybody else seeing this? Thanks.

Just Flight just released updates for their Arrow, Turbo Arrow, and Warrior II. Kinda odd to me that they released these the day before SU7, but glad to see them nonetheless.

OK, I think I got it sorted. During one of my test flights I noticed that if I turned the control yoke while taxiing the aircraft turned. Then I remembered that I had takeoff auto rudder on as an option. I turned that off, and recalibrated my alerion axis. And that fixed it. Did a few more test flights with PBE and no more pulling to the left. Just wanted to post a follow up and let everyone know that the issue was on my end, no issues at all with PBE. Bryan, thanks again for making this awesome pushback program for MSFS. Gary

Did another flight with the C208B and had the same problem. When it was pulling to the left, I stopped and went to external view and looked at the rudder and nosewheel. The rudder was absolutely straight, but the nosewheel was turned slightly to the left. Ill do some more testing and report back.

Bryan, nice job on this program!! Got it today and after reading the Voice Control manual I was able to complete a voice command pushback with the C208B with no problems. Bui after I disconnected and started to taxi, the plane pulled a lot to the left. So I went back and calibrated my MFG Crosswind rudder pedals and checked the Control Options in MSFS to see if anything was off with my Sensitivity settings or if I had a brake engaged. Everything looked good there, so I tried another pushback and flight. But I got the same result (pull to the left during taxi). So then I tried the same flight without using Pushback Express, and my rudder pedal function was back to straight and normal. Any ideas on what may be causing this? If it matters, I am using dgtlanlg's Cessna 208B Grand Caravan EX Improvement Mod and I don't have any other mods in my Community Folder except the FS2crew cmd center and data proc mods. Thanks. Gary

I used the WT CJ4 mod and the WT G3000 mod with the Longitude a lot with no issues prior to WU6 (thanks WT team!!). After making several flights with these mods after WU6, I think I have identified a couple of issues. On the WT CJ4 mod, the autopilot will not always capture the preset altitude on a climb or descent. And after I do finally manage to get it level, the autopilot will not always maintain the set altitude. Sometimes it will very slowly drift higher or lower until I manually correct it. And on ILS approaches, even though I have an ILS set up and the APPR mode armed, the autopilot will not capture the GS like it used to before WU6. The white "GS" annunciates and it changes to green when the glideslope is captured, but with the autopilot on it now continues flying level right thru the glideslope. With the WT G3000 mod and the Longitude, before WU6 the Garmin MFD and PFD screens always initialized when the standby power switch was flipped on. But after WU6 when I flip the standby power switch and batteries ON the Garmin MFD and PFD screens stay dark. I'm not complaining, just wanted to make sure the WT team was aware of these issues. Thanks.

Here is what I have tried so far in WU6: WT CJ4 Mod - No issues WT G3000 Mod - So far only tested in the Longitude. The screens remain dark after standby and battery power are applied. That's as far as I got with it in the Longitude. PMS50 GNS530 Mod - So far only tested in the Just Flight Turbo Arrow. No issues. Just Flight Turbo Arrow - No new issues. ambitiouspilots-toolbar-pushback - No issues.

There's a post on the official forum that says 1030 CT.

Ditto. I am also getting better performance with Hags Off and Game Mode On with the latest win 10 update.

I'm also having this problem with the Turbo Arrow.

I am running with both off and having pretty good performance with SU5.

Just did a flight at FL320 in the WT CJ4 and I can confirm that the temp/wind issue appears to be resolved. Thanks to whoever was involved in fixing this.

I emailed Dave and he fixed this for me. Great support, thanks Dave!!

Hey Dave, I am also having this issue. I emailed you my log files. Thanks.

I second this. I am currently on my 2nd system built by them and they have both been excellent. My current system is getting a little long in the tooth, so I am starting to think about ordering another system from them. Will prob wait until Intel the 12th generation Alder CPUs come out later this year.

I am really loving the Arrow so far. One minor gripe I do have is that, with the throttle at idle, as soon as I release the parking brake the plane starts moving and just continues to pick up speed. To any of you with time in the real Arrow, is this normal? Thanks.

This problem was occurring before yesterday's update. It started happening to me after the UK world update.

I have both manual and rolling cache turned off, and I still have this problem. The only thing that fixes it for me is turning Online Functionality off.

I have had this happen on my last few flights. Disabled Online Functionality and fps returned to normal. I submitted a Zendesk ticket on it.

Bobcat, are you running your monitor at 60 Hz with vsync set to 30? If you are I may try that and see if its any better than 30 Hz with vsync set to 60. And I took your advice and turned off sharpness in the config file and set it to .50 in NCP. Definitely looks better, thanks. Reaper, your right. I am like one of those suckers in America back in the 1800s that would buy the snake oil from the guy when he rode into town. I definitely need to put the snake oil down and do more flying and less tweaking. Anyway, thanks for taking the time to respond guys. Appreciate it.

I have a 4K monitor, and I was running MSFS with my monitor at its native resolution (3840 X 2160) at 30 Hz and scaling the resolution to 70 (2688 X 1512) in MSFS. I have Vsync on, frames locked at 60 fps, running in fullscreen in MSFS. This looked pretty good and maintained a solid 30 fps for the most part. Then I started reading about others saying that setting a custom resolution with the Nvidia Control Panel and then running that resolution at 100 render scaling in MSFS was less blurry and the instruments on the panel were a little easier to read. Others said this is the way to go because the NCP does a better job of scaling than Windows or MSFS does. So I set a custom resolution of 2688 X 1512 with the NCP and then set that as my desktop resolution with render scaling set to 100 in MSFS. But after a couple of flights I cant really see any difference. For others that have done this, am I missing something here? It doesn't seem worth the pain of having to switch my desktop resolution back and forth between native and custom just to run MSFS like this. Thanks