Meeko

Thank you "AS" for your import. Hope this will be of interest to Aniiran as well. I have already rolled back to previous video drivers with no luck and reinstalled the latest version. Cache directories have already been cleaned with the exception of the scenery cache within MSFS. I'm not able to get into MSFS to do that. The resetting of the page file is a bit daunting, so I don't have the confidence to go there. Lastly, reinstalling MSFS doesn't appear to make any difference. MSFS forum indicates here's a huge number of MSFS pilots who have the same problem. A lot of these pilots have reinstalled MSFS but it doesn't fix the problem. I think I'm doomed to wait another week or so for SU11 and hope that's going to be the magic cure. In the meantime, it's back to YouTube videos. Regards.

Yes, I have my fingers crossed for this update.

Aniiran, you should consider yourself lucky. At least you can take off and have some sort of flight. I can't do anything. Prior to SU10 I had that message two or three times. When you consider how often I flew in MSFS (most days) it was a very low percentage of flights. Back in Sept, I downloaded SU10, opened the flight sim and all was good. However, the next day when I opened the sim I got that message and have ever since. I get it every time, either during the loading stages, or on the opening screen. I haven't flown in MSFS since I downloaded and installed SU10. I'm certainly going through withdrawals. I'm living in hope that SU11, which is due in a week or so, will fix this problem. Yes, my computer is all up to date and I've done all the checks with the community folder and other addons, but none appear to cause this message. Bruce R i9-9900K @ 3.6GHz, 32 RAM, GeForce RTX 2028Ti

Just to update this... I received a reply back from Honeycomb the other day regarding the ticket I submitted. I was advised to return the Bravo to the supplier for a replacement. Bruce Ross

Hello Grant. I submitted a ticket back on 7 March (7383) and have heard nothing. I also Started a topic on 13 March in the Bravo Throttle Quadrant Support entitled "Y Axis on Bravo Throttle Quadrant Not Working" and haven't heard back. Are you able to help me with my query? Regards Bruce Ross

I have W10 and P3D V4.5 installed. I purchased the Alpha and Bravo last year. At the end of the year I ran into trouble with the Bravo. Two Boeing reversers for a twin jet on the Rz and Ry axis's (slots 3 and 4 from the left) stopped working. They worked on one flight, and the next, failed to work. The supplier here in New Zealand arranged for a replacement Bravo. The new one arrived early March. As much as I've tried, I can not get the Y axis (first on the left side) to work. I assign this axis for spoilers for the jets, and engine one throttle for twin turbo prop aircraft. When that axis is assigned I only have to move it 2 or 3 millimeters and it will go from off to fully on, and vise versa. There's nothing in between. It won't return until it's fully back in the buffer. It seems to be working like a switch - either on or off. I did not have this problem with the other Bravo. I've hunted for any double assignments and have ruled that possibility out. I do have FSUIPC, but since using both the Alpha and Bravo I have not used it. All my assignments are now done within P3D and there's nothing in FSUIPC. This is a brand new Bravo. Do you have any ideas how this can be fixed? I have submitted a ticket (#7383), but after a week have heard nothing. I would appreciate any advice given. Regards Bruce Ross NZ

The latest from TFDI regarding their B717 crashes. Push back from that hanger and get ready. https://forums.tfdidesign.com/index.php?/topic/4018-ctd-via-changing-views/page/4/#comments Bruce R

Yes I’ve been getting a strange page as well. If I scroll down to a small ‘sign in’ I can get in but then have to click on ‘forums’. Bruce R

This is excellent news. The cause has finally been solved, and those who swore and coursed at TFDI should perhaps take out their frustrations elsewhere. "As of 12/12, Lockheed Martin have confirmed that this is indeed a bug in Prepar3D. They are now working on a fix and a workaround in the interim. Please keep an eye on this thread, and we will continue to update you here." https://forums.tfdidesign.com/index.php?/topic/3754-view-switch-crash/ Bruce R

For those interested, QualityWings have have released their Service Pack 2, Version 1.2.0. This of course includes the 787-10. Bruce R

1. Are you using Orbx Central? 2. Are use using the latest Orbx Libraries? 3. Why don't you go over to the Orbx Forums. They are the experts and I'm sure they can solve your problem. Bruce R

It seems TFDI are onto the cause of these crashes. This is good news. https://forums.tfdidesign.com/index.php?/topic/4018-ctd-via-changing-views/page/2/#comments Bruce R

Presumable you're flying in RNV/Map mode. In that case, just before GS/Localiser capture press the V/L button (next to the RNV button). You should then capture the GS and Localiser. Bruce R

Hello Allan. I read your reply with interest. I had a look at my settings and they were already at "Very High". I still got the flickering at that setting. What I suggested above has fixed it for me. Cheers

Hello Pat. Welcome to Dunedin. I live only 10 minutes from NZDN, so of course, I have Godzone Dunedin. In my previous life I did a lot of flying from NZTI which is included in the Godzone package. If you're not from these parts "Taieri" is a Maori name. The common pronunciation is "Tie ree". it's a great little aeroclub airfield on the outskirts of the town of Mosgiel and directly under the flight-path of runway 21 into NZDN. Anyway back to your problem .... I had the same frustration as you have. I have ORBX SI installed and when on the NZDN tarmac and runway I had flashes of the default (or probably ORBX) textures. I've done a couple of things, and I suggest you do the same; 1. Go into your main flightsim folder (in my case P3D) and click on ORBX. Then FTX_NZ and FTX_NZSI_05_Scenery. Make sure you don't open the "NZNI" file by mistake. Click on scenery and then scroll down to these files; ADE_FTX_NZSI_NZDN.BGL ......NZDN_CVX.bgl .....NZDN_objects.bgl Turn these files off by renaming them by putting .OFF after them. 2. I have also done this ... and I have no idea if it's necessary or not, but it probably doesn't do any harm. Go to your main flightsim folder and scroll down to Scenery / World / scenery and find ADE_FTX_NZSI_NZDN_elevation_adjustment.BGL Turn this off. And while you're there find the NZTI file and turn that off as well or you may find ditches on the Taieri airfield runways. Let us know how you get on. Bruce R