shamrockflyer

I am also experiencing this. With FTX Ireland from Orbx I use FTX Vector and global with the frozen water in winter option turned off. It is like bright large squares are appearing at night where there are no lakes or water. I thought it could be snow but the surrounding areas do not have any snow, but then again P3D can be funky like that in the winter. I only started to notice it since updating to 4.4, I am also wondering if it has to do with the new ambient moon lighting LM added into 4.4?..

I had the same problem when trying to install Doha and Hong Kong, however - a quick search of the internet came up with results which fixed the issue, yes it does involve adding an entry into the registry but if you're willing to get any scenery up and running then its worth it imo.

I think LM should just stick with 4.X until they build a new flight simulator on an up to date engine. Yes we would all have to purchase licenses again for all of our addons, but it would remove a lot of headaches and performance issues many are having. Its time LM moved on from the extremely outdated engine they currently use.

That is a fine idea! Thank you for the suggestion. Ciaran

To keep this post short. Is there anyway to make the Saitek throttle quadrant work without the saitek flight yoke? I have the old style throttle with the old connector and will be moving to the Yoko yoke in a couple of weeks, since Virtual Flys throttle is also very expensive, I would like to use the Saitek throttle with Yoko until I can scrape up enough funds to get the VF throttle.

I used Process Lasso too but also had bad results with it. Check out the link below, that is where I found the method which I still use... https://www.prepar3d.com/forum/viewtopic.php?t=129222

I use the manual AM method which goes by unselecting core 0 in task manager when P3D is open, closing the Set Affinity tab and then reopening and reselecting core 0. That method has always worked well for me on V4 and I do notice a big difference between with and without.

I hope Orbx adopt PBR in their sceneries soon. The current static ground reflections are very bad! Its the early days of P3D and PBR and it may look funky, but it will get better!

Now that we have PMDG and a number of other developers adding rain drops to our virtual windshields, I would like to know whether there is an option in AS that enables constant rain in a rain forecasted area? The reason being, when it rains in P3D, it starts and stops therefore leaving the rain/snow effect on the windows rather unrealistic with the constant popping in and out of rain texture.

I think this was what I thought was an issue, as it turns out it seems to just be normal behaviour of the aircraft. Descent into Sydney in the 400 went smoothly without a "hitch". I guess this thread was mainly created because of lack of patience in terms of waiting to see what the aircraft would do in the situation that occurred. This thread may be marked as solved, as stated above it was just a user "error" rather than software.

Yes I had as always. The same issue happened with two flights I had done in the past two days. I am now performing a flight of equal flight time to my previous flight and will report back with what the FMA says before and after TOD, hopefully the issue will repeat itself and I can get some information together.

Ok - after doing another test flight to see if the issue would arise and it didn't. Aircraft descends as per usual and there are no issues to report in regards to TOD. I know this doesn't fully answer any of your questions, but if I get a chance to reproduce the issue in the coming days then I will report back here with details. I may possibly be able to do a flight tomorrow, I will report back when I can.

Since updating to the latest update for the 400 I have noticed that setting my descent altitude on the MCP well before hitting T/D the aircraft doesn't start descent via the VNAV profile. I haven't changed the way I set up my flight planning and everything is correct. To initiate the descent I have to manually start descent via the VS dial, wait until the aircraft is about 500 feet below the T/D altitude and then hit VNAV, that is the only way I can get VNAV to activate and control the descent. The speed is decreasing and going below set speed but with no change in altitude. Has anyone else noticed this or is it just an issue on my side? VNAV works as it should during climb out and cruise, its just the initiation of the descent phase where it seems to be having difficulty. Just to note - I have only experienced this on the 400 as I haven't flown the -8 yet with the latest update.

Ok its worked now. What ever you did, thanks.

I thought it was best the take a screenshot of where it stops exactly.