reball

I forgot to add the final bit above. After, ...and fps remained "crippled.", I should have also added that, with the King Air, I changed the shadows back to "overlay" and fps increased to 22, then when I checked the HDR box and closed the rendering menu, the XP program promptly crashed!! Shortly after that, within a second or two, I got a high CPU usage window open up, and under details, the indication that at least one of the cores was at 100%. Now, is that of any diagnostic help???

Sundowner Exonerated!! The story gets more interesting. Yesterday I wondered if the Sundowner update somehow crippled XP performance--now I'm pretty sure it did not, but something else is. I booted XP today after disabling all of Symantec Security Suite and also canceling any Mcafee scans. The last plane that was opened yesterday was the default C172, so that's what came up at my local airport (KBAF) with a fps rate of 39 plus -- all fine. I had a short flight and observed fps of between 30-42 with my usual settings. Then, during flight, I added first more shadow detail (overlay to global low) and fps was about the same, then added HDR and maybe a slight drop of 2-3 fps, but nothing unusual---this is what I had been accustomed to. Then landed, did not shut down XP but opened the Sundowner, and lo and behold, fps remained high at 38-40 fps on the apron, with the enhanced shadow and HDR setting. So the Sundowner is not the problem. But here's the rest--I shut down XP, then restarted it, and the Sundowner came up with fps now of just 13-14 fps, same display rendering settings as previously had given more than double that value. Then , without shutting down XP, I changed to two default planes, the C172 and then the King Air, and fps remained "crippled." So, I'm sorry, Cameron, for hastily suspecting the Sundowner, when I now suspect there is some kind of either RAM leakage or maybe a video memory issue, and possibly in my hardware and not in XP. I would love to hear if someone has encountered this kind of behavior, and if so, what might be the solution.

I will try to track this down--the timing of these performance problems and the Sundowner update may have been just coincidental. Tomorrow I will see how some of the default planes react to those rendering settings changes. My X-plane is pretty much free of addons, except for Urban Maxx. On the positive side, I did notice an improvement in the Sundowner's flight model. Previously, flaring at touchdown was tough, not easy to touch down on the main gear. Now, flaring seems more realistic. Thanks, Cameron for your fast reply.

Am I the only one to have this problem. After installing the Sundowner update last week, I noticed abyssmal frame rates, between 0.9 and 2 fps after opening the plane. Oddly, when that happened, I then opened the default C171, and still crippled performance. I did get the C23 into the air and went to the settings menu and clicked the "set for maximum framerat" button, and upon resuming the program, beautiful performance of 59-62 fps, but of course, blurry, featureless surroundings. One by one, I restored settings, and found two killer changes---going from, under shadows, any setting above "3D on aircraft", including any of the global settings, set framerate right down to single digits. Similarlly, engaging HDR rendering again killed framerates. Critically, I was able to use those high settings with no trouble before updating the Sundowner. Is it possibole that there's a glitch in the update that, when initiated, even affects the default aircraft. By the way, I had on a previous day gone into the system config menu of Windows and disabled all services, but running the Sundowner was still crippled, so I'm pretty sure the computer was not busy doing other tasks. At one occasion when Sundowner is so misbehaving, I found the CPU usage was only 25%, so again, I think the problem is within XD-Plane and not Windows. Any thoughts?? Thanks!

Thanks! I can't believe I missed that fast update. Just installed 1.51 and did a quick test and now all seems OK. Now must get back to mastering the FMS and autopilot.

I hope someone can help--if I start XP and then the CRJ (1.5 downloaded yesterday), inevitably when starting cold and dark, after the master switch is on, center displays on, HYD 3A on, ext GPU on and in use, IRS both to NAV, all procedures normal, then on FMS display, hitting POS INIT always leads to a drop to desktop after the message XP is shutting down. But it gets odder--if I follow the advise on original thread and load a default plane first, exit XP, restart and back to default plane, then change to CRJ, then I can set the INIT POS, however, also reproducibly, the two displays (pilot and copilot sets) are black. If I hover mouse over the DISPL switch on left side panel, I get large arrows suggesting the switch can be changed from its OFF position, but I can't switch it on. I had none of these issues with version 1.4. Finally, under settings and warnings (XP 10.10r3), if I set to start with engines runniing, then reload the CRJ, the engines are running but again, those PD screens are black and can't be switched on. Any ideas anyone, or is there an elusive bug? Thanks in advance.

Thanks ntr09 and Kaphias. I did some stall speed checking and found out I was contacting the water way too fast, around 60 mph, whereas the plane seems to stall with full flaps more like 45-48 mph, so I lowered the speed and can now do a reasonably good water landing even with wave height increased to 0.4 feet. In retrospect, J Rollon did a masterful job of programming this very light and buffetable plane. I now really love it. Appreciation for the good pointers. Dick

Thanks, Kaphias, I will try this right now. It's easy to forget that hitting a wave at 60 knots must give the hull a huge whallop! Dick

Thanks, ntr09. I found the wave height setting and lowered it to 0.2 ft, then managed a few landings. Still some porpoising, but a lot better. Looks as though the SeaMax is quite sensitive to wave quality. Thanks again. Dick

Just to apologize for bad typing--should have said a bump on water touchdown, and should have said, of course, landing gear was raised, so a clean hull was making contact. I saw many beautiful water landings on Youtube, but these were with XP 9, so I'm wondering if my problem is XP 10.10r3. Can anyone shed any light on this? Thanks again. Dick

If anyone could help, would most appreciate it. Just installed the SeaMax, and have had no problems other that touching down on water. No matter what speed, angle of attack or flap settings, touching down results in an uncontrolled bumb upwards. I am using XP 10.10r3. I tried some landings on land with gear down, and can do very smooth landings--it is only the water that's the problem, and that's my main reason for wanting this plane. Can anyone advise? It makes no difference whether the water rudders is down or up. Thanks! Dick