puukart14

For those interested, another Beta update (Update 3) was released today: https://ifly.flight1.net/forums/max-beta-update-3_topic21252.html Same as the last one, a .rar to download then copy/paste those files into the appropriate iFlyMax folder.

As another performance reference, I booted up 5.4 and loaded in to gate 534 at SimWings EGLL. With AIG Traffic at 50% (roughly 65 planes near me), no ASP3D, but with Chaseplane running, I was maintaining 30fps in the cockpit (I limit it to 30 in NCP). VRAM was around 6.5GB used out of 21.5GB, but more interestingly 37GB of system RAM was being used out of 64GB. This was also without the interior option selected and at a monitor resolution of 3440x1440. Never flew the original Concord module so I’m looking forward to learning how to operate this bird!

This is only one data point, but I've done about a dozen flights since I got it after the new year with no CTDs. Even did a real-time PHX-OGG flight yesterday with no issues to really test out the stability.

Well used reference from The Right Stuff 😉 Excellent aviation flick!

Correct, I meant G-sync. I limit the frame rate of P3D to 30 FPS inside of the Nvidia Control Panel (I also set the P3D target frame rate limiter to “Unlimited” inside P3D) and disable G-sync entirely. On my setup at least it provides a fairly fluid experience. I believe there is a “V-sync” setting in the program settings menu for P3D inside the Nvidia Control Panel, but I leave this at the default value. I would try the settings I mentioned above and see if that makes a difference.

Might be a long shot suggestion, but do you have G-sync enabled? I have a similar machine as yours and experienced almost constant stutters in the cockpit with G-sync enabled. I turned it off through the Nvidia Control Panel and the sim is more fluid for me. Hope this helps!

I'll preface this with I was only having the blinking UI issues with AIG Manager and AIG Traffic Controller. I recently decided to try and use Reshade, but it was being tricky and not actually opening up while in P3D. I stumbled across this thread where the topic author pointed to reinstalling the C++ 2015-2019 redistributables would solve the Reshade menu problem: https://www.reddit.com/r/ReShade/comments/mybh8o/fix_discovered_for_reshade_menututorial_not/ I've done what was suggested and Reshade now opens while in P3D and both AIG programs I mentioned above no longer have the blinking UI issues. Thought I'd share my findings.

I restored my original shaders in the sim and made this comparison with the brightness setting set to 0.1 (the default value in RDShade after the shader restore was 1.0). Pre-brightness tweak applied Cockpit brightness set to 0.1 in RDShade It might be a little hard to see in the shots above, but making that brightness change added a touch of a grey hue across the image (the runway markings actually show it somewhat). I also went back and checked the visuals at night, same results as before with not much overall sim brightness differentiation between the two settings. Think I'm going to go back to trying the remaining presets to see which one I like most.

Alright, I did a quick check and have a few more screenshots. As an FYI, I'm using a different preset now than I had during my earlier screenshot post (cockpit textures are brighter than vanilla P3D, but not as overdone looking to me). The cockpit brightness setting has an adjustable range of 0.1 to 1.9. The "before" screenshot below for the "ClearedTakeoff" preset has a value of 0.3 and gives the following cockpit brightness and external sim appearance at night. RDShade lighting panel example NGXu cockpit at "ClearedTakeoff" preset default settings External shot at "ClearedTakeoff" preset default settings NGXu cockpit with brightness value changed to maximum of 1.9 (all other preset settings untouched) External shot with cockpit brightness value changed to maximum of 1.9 (all other preset settings untouched) Once the shaders loaded in after making the change, I didn't notice much of if any difference at all subjectively in the overall sim brightness at night. I've not run shader programs like this before with P3D, so I'm still trying to take it all in. Hope this brief look helps!

Sure thing! I’m a little tied up at the moment, but I’ll try and report back when I get to flying.

Which preset did you install where this is happening? I just checked my cfg and the value I put in for that category is unchanged at 32000 (I have the “ClearedTakeoff” preset installed currently). Going to experiment more later today and I’ll double check if this is changing on my end.

For those screenshots I just selected that preset and hit apply, nothing else was done. I’m going through all the presets and trying them out before diving into the individual settings. There’s a lot to adjust, including one section dedicated to cockpit brightness.

Here are a couple more screenshot comparisons from the flightdeck for reference. Used the same planes, time of day and location for all shots while the preset I selected at random was the "Natural Preset" from their current collection or presets. I'm going to do more experimentation, but at least with this particular preset these are the differences on my machine. 747 before preset applied: 747 after preset applied: 737 before preset applied: 737 after preset applied: A32X before preset applied: A32X after preset applied:

I'm probably in the minority here, but after experiencing the intermittent pauses/wild GPU usage fluctuations with 5.3, I'm no longer getting them on 5.3 HF1.1. I know it's a small sample size, but during three of the first five flights I did on 5.3 the pauses appeared out of nowhere (either during climb out, just after TOC or in the descent). I've done six flights so far with 5.3 HF1.1 and they have not reappeared (running same hardware and software as I was previously). For reference, I got the pauses on 5.3 using different aircraft (FSL, NGXu, 777) all the while running ASP3D, ASCA, GSX, Chaseplane, Navigraph Simulink, Parallel 42 Immersion Manager, various large payware airports and all ORBX regions (except Vector). Maybe I haven't done enough flights to trigger it again, but I'm a bit lost for the sudden reversal in sim performance as others still seem to have the pauses occurring on 5.3 HF1.1. The only thing I did differently this time when installing 5.3 HF1.1 was deleting all of the various LM sub-folders located in the %/AppData/Local, %/AppData/Roaming and I believe a folder or two on the C:/ drive after completely uninstalling P3D. I left the root P3D and Add-Ons folder alone and then reinstalled 5.3 HF1.1. Maybe I got lucky this time, but I will keep doing more flights in different regions/aircraft to see if the pauses return.

I’m currently using the 254 setting with my 9700K and having pretty good performance. Then moving everything not P3D related to Core 0 has given me some nice headroom. I’ve seen points where Core 1 is fluctuating just below 100% with the sim running at full tilt, but not stuttering and staying smooth. Also using NCP to limit frames to 30 as an FYI.