TexasGary

Hey Jude, I would also appreciate it if you could provide some details on how to go about doing this. Thanks.

This is one of the bugs listed on the official forums. https://forums.flightsimulator.com/t/mixed-textures-in-ground-at-default-airport-dx12-beta/534963 If you haven't already, please vote to have it addressed.

I just had these at KPHL. Wish there was a permanent fix. You can fix it temporarily in your flight by going into Developer Mode and cycling an airport debug mode on then off.

I'm currently on the latest driver (536.67) and have not had any issues.

Thanks. You're probably right. I will just have to hope it happens in the new sim next year. When I used to live in Mt. Pleasant (KOSA) years ago they also did a major expansion project that included a new longer runway and terminal building. It didn't get updated in P3D or FSX, but when MSFS came out it had the new runway and terminal building. So one can hope .........

My local airport is doing a major expansion project that includes a new longer runway and terminal building. The old runway was 3586 feet, and it didn't have any IAPs. The new runway is 5201 feet, and it has two published IAPs. Will this new runway and terminal building be updated in the sim by ASOBO at some point? Or is that just left up to someone out there to hopefully do a mod for it?

Thanks Umberto. Was going to post about the sale here, but you beat me to it.

Just released. Here are the release notes: Game Ready for RTX 4060 Ti This new Game Ready Driver provides the best gaming experience for the latest new games featuring DLSS 3 technology including The Lord of the Rings: Gollum. Additionally, this Game Ready Driver introduces significant performance optimizations to deliver up to 2x inference performance on popular AI models and applications such as Stable Diffusion. Gaming Technology Introduces support for the GeForce RTX 4060 Ti (8GB) Fixed Bugs [Age of Wonders 4] Application stability issues [4101637] [Bus Simulator 31] Ansel & Freestyle not working [4090979]

For all of you using Defender, do you pause it during your flights or do you just leave it running all the time?

I use ESET NOD32. I pause it when I am making a flight. Works well, no issues with MSFS.

I am also having this issue. I put in a support ticket.

Hey jlohrenz, good point. The 1000W PSU is "Gold" rated, and the 1500W PSU is "Platinum" rated. I did some reading on it and you're right, the Platinum rating means less energy use and less heat. So based on that I am definitely going with the1500W PSU. Appreciate all of your responses. Great info. Thanks.

odourboy, thanks. Yea, I would prob go with a 1200W PSU if that was an option. But the only options that Jetline has right now are 1000W and 1500W. So, I will prob go with the 1500W PSU. Besides the extra cost, are there any other downsides to a 1500W PSU? Do they put out more heat or noise than a smaller PSU?

stans, thanks. That's what I'm thinking, larger is better when it comes to PSUs. Just want to make sure I understand all the advantages/disadvantages of having a larger PSU before I order the system.

I am looking at getting the following system: Corsair 4000X Mid Tower Gigabyte Z790 Aorus Master Core i9 13900KF (5.8GHz Boost Clock) RTX 4090 64GB DDR5 SDRAM 5600MHz 2TB Samsung 980 PRO Gen 4 NVMe SSD Corsair H100i Elite 240mm Liquid Cooling The power supply options are either 1000W or 1500W. Which one do you guys think I should go with? Thanks.

SOLVED!!! I followed your suggestion and renamed my AppConfig and then ran P2ATC. It created a new AppConfig file. I then went to the buttons menu and hit "Set" for the PTT Joystick button, and this time I got the drop down menu to select my joystick. I selected my Alpha, hit my preferred button, and it saved it. I am a happy P2ATC user again 😀 Again, thanks for your help with this issue Dave. It was driving me nuts, and I was pulling out what little hair I have left 🤪

Dave, thanks. Really appreciate your help with this issue. OK, I ran the software for the Alpha from Honeycomb's site. That didn't fix it. Then I went to Control Panel->Devices and Printers, and I DO see my Honeycomb Alpha listed correctly and the properties says it is working properly. Can I perhaps send you my P2A AppConfig, Settings, and most recent log file? They have entries for the PTT joystick, but I am not knowledgeable enough to know what they mean. Thanks Gary

Hey Dave, thanks. I rebooted, but that didn't help. OK, I assume by "list provided by Windows of attached Joysticks" you mean the list in Device Manager. I went there, and I have 6 USB devices listed as "Unknown USB Device." So I guess that one of these is my yoke. Interestingly, 4 of these say "Device Descriptor Request Failed." The other 2 say "Port Reset Failed" and "Set Address Failed." Could that be why P2ATC is not seeing my yoke? Would it help if I sent you my .LDF files? Appreciate the help. Gary

I'm on 2.6.4.1. I had assigned my PTT and Say It Joystick buttons on my Honeycomb Alpha with a previous version and they worked fine. Today I deleted my PTT and Say It Joystick button assignments and then tried to reassign them. But now I dont have a dropdown to select my joystick, it just says "PTT Joystick." And if I try to assign a button to my joystick by pressing "Set" nothing happens and I cant assign anything. I tried reinstalling 2.6.4.1 and unplugging and re-plugging in my joystick, but that didn't help. Anybody have any ideas what could be causing this? Thanks.

P2ATC also has an active discord channel.

I'm currently at 95%. And so far I have seen large updates for airports VHHX, EDLO, LILC, CAA8, LFPI, SCVH, TNCM, EDGD, LEMD, HEGH, EGAO, FAWC, KORD, SMDH, EDDF, KJRB, KCGX, KDEN, FYVF, LFNC, and RJTI.

I got the update from the MS Store at 1001. Maybe try restarting your PC.

Downloading now. Currently 90 MB/S.

I have also had this problem, but only at one very specific location in Texas. Whenever I get within 2 miles of KETN for landing on runway 17 my frames always drop significantly. If I approach from the south and land on runway 35 I dont lose any frames, smooth as silk. I tried clearing the community folder, changing graphic settings, and caching the area around KETN. The only thing I found that helped was lowering Texture Synthesis to Medium from High. On Medium I dont experience the frame drops. I am going to put in a ticket and cross my fingers that they can fix it in a future update.

Just tried my first flight with V1.2. In V1.1b, I needed a little bit of power to start taxing. Now with V1.2 as soon as I release the brakes it starts moving on its own and continues accelerating until I hit the brakes. This is with PLs at ground idle, props full forward, and CLs at low idle. The V1.2 release notes say that "Idle thrust on the ground is more subdued." But to me it seems just the opposite. Seems like idle thrust is alot higher.