Rogen

Hi, Been experimenting this this and have found the following. 1), yes locking the frame rate in P3D typically doesn't actually get you the frame rate you've set. That said I experimented with increasing the value of [Display] TEXTURE_BANDWIDTH_MULT= The P3D default is 30, FSX-SE is 160, so I went to 160 and then incremented by 100 till I saw no appreciable changes, 760 was the result and now when I set 30 fps in the P3D slider. 30 fps is what I get. Would proably depend on an individual machine and the silicon lottery but worth a go and it's easy to experiment with. The advantage I see of it all is the frame rate is much more stable, and doesn't jump all over the place so much as when v-sync and unlimited frames is on. 2), To get the NVidia half refresh rate working I needed to disable Aero (I run Windows7) for which I wrote a small toggle script, so the 1/2 refresh tweak does work, although 30 Hz and v-sync is better but if I didn't have a 30 Hz monitor myself I'd use the 1/2 refresh tweak. 3), Even with 30 Hz, v-sync and unlimited framerate set a lot of spare overhead is needed as if the framerate drops under 30 v-sync drops off and a sudden and distacting "frame rate jump" occurs. (this is where the frame rate slider in P3D can help). For those interested a 1080p monitor that can support a custom 30Hz value is the Dell MultiSync MHL IPS monitor (U2417H - can sync down to 23 Hz) . Cheers

Hi jcmygod, Well, there are M2s that are the same speed as SSD and then there are M2 that run at PCI speeds. The one I run is @ PCI speeds and it is very fast, much faster than my SSD drives (and I run 2 x 1Tb drives as a striped raid array for speed). While I haven't actually timed load speeds, my anecdotal observation is that it feels much faster and I do load ~345 GB of data plus another ~153 GB of Orbx data off the M2. I do have P3D v3 installed on the SSD drives, I'll see how long it takes to load up an Orbx location compared to P3D v4 which is located on the M2 and post back. Cheers

I'm like yourself, cannot afford the huge prices of a 2080Ti series GPU which in Aust are ~$1850-$2600. I opted for a 1070Ti (while they were still available) and although, yes more power is always desirable (or maybe 2 x GPU in SLI?), I am happy with the 1070Ti but if you could pick up a 1080Ti I'd go for that over the 1070Ti, however the 2070 and 2080 would also be good options if they came at the right price (not in Aust though I'm afraid). One thing I found that complemented the 1070Ti was a monitor that could sync to 30 Hz and I chose the Dell MultiSync MHL IPS monitor (U2417H - can sync down to 23 Hz) as it's a very nice monitor with a stand that's a cut above other monitor stands, and although not 4K I find it fantastic for P3D flying with vsync smoothness. I also run a Ryzen 1700 overclocked with SMT off and the below vid shows the sort of perfomance I get with the monitor running @ 30 Hz. Cheers https://orbxsystems.com/forum/topic/168487-prepar3d-v44-tour-around-l35-big-bear-airport-in-the-ant-trojan-t28d/

While no doubt many people will find a mittigating reason for the issue in their particular case, the actual 6% loading delay issue is due to a flaw in the code that has always existed from back in the FSX codebase What apparently happens @ the 6% mark is P3D will begin checking scenery components against library objects and it will check all components against all libraries. So for example if you have Orbx scenery you'll also have the quite large Orbx library and the checks P3D performs (performed whether needed or not) will result in hundreds of thousands of code calls dramatically slowing down the loading. You can test this in action by unselecting all library objects in the scenery config where with no libraries to check against, the loading will be much faster (but of course things will be missing due to no library objects). Note this applies to all scenery and all libraries and is nothing in particular to do with Orbx and has mostly come about due to the highly detailed sceneries being produced using custom library objects. Essentually as P3D and it's capabilites have evolved, so to have the addins we run with the result being previously minor annoyances have evolved to needing resolution. The good thing is we have Orbx to thank for getting onto LM, who have advised they will be including a fix for the issue in P3D version 4.5. So moving forward everyone wins, and the 6% loading wait point prob is resolved. In the meatime I can recommend an M2 drive (such as this one https://www.samsung.com/us/computing/memory-storage/solid-state-drives/ssd-970-pro-nvme-m2-1tb-mz-v7p1t0bw/ ) as their perfomance it truely a sixer with the loading speed improvements they provide. And it you want to read more about the issue jump on over to the the Orbx forum, login and there are various threads discussing such in the P3D support areas. Cheers

Yes you won't, A2A take the position of FSX and P3D are two diferent platforms, and they also have separate purchases for Academic and Pro versions of P3D with some eyewatering price differences. But all said and done they make good planes in a class of their own and in the schema of first world problems they are worth a bit spending dosh. If you recently purchased the FSX C172 from their own shop you should have acumulated some purchase points you can offset against new purchases. I too had a few A2A planes in FSX that I'm slowing repurchasing for P3D, also if you've not come across Ant's aeroplanes before, they make a few planes of a similar type of quality to A2A for a fraction of the price, even has some demo releases. https://www.antsairplanes.com/ Cheers

Really all three monitors will have to be able to output @ 30 Hz. I've given it a go myself and having 2 monitors @ 60 Hz is not going to achieve great results, but you can certainly trial it out and see what sort of results you can achieve. Personally I'd say to give just the primary monitor @ 30 Hz a trial (as in use just the one screen), and it you like it get a couple more. I also have multiple P3D GFX profiles, each tuned with specific levels of detail pertaining to the type of scenery/aircraft catagory, e.g Photoreal is for when flying in Photoreal scenery and has most sliders to the max and low detail is the opposite. Cheers

kityatyi posted Friday at 09:51 PM "Since dusk and dawn often caught me over the Atlantic where there isn't any vegetation" =============================================================================== Well the case... another item that sucks out GPU power is dynamic lighting, which is handled fairly well, unless it's dusk/dawn where GPU will max out and start dropping off frames. I use a tool to monitor GPU/CPU usage and temps etc. so I can see the affects of changes that I make on the GPU directly in an easy to understand way. HWMONITOR https://www.cpuid.com/softwares.html Cheers

Yes you can do that, although generally a better result is to re-install windows to remove the extra baggage. I've actaully updated my hardware three times (complete new motherboard, CPU, GPU etc.) for this single install of Windows7 that I have. Can be a little complex though, have to be ready with drivers and then there is the enevitable cleanup via Device Manager (in show disconnected hardware mode) of old hardware related to the old motherboard and drivers etc. If you know what you're doing it is a perfectly viable way to do it, but a little time consuming and can be prone to requiring a degree of troubleshooting. Windows even has a sysprep tool for preparing an image based install that will basically install itself on hardware of choice and some backup applications also feature the ablity to automate the process of moving a backup image to new hardware. Cheers

I also noticed such issues and traced to vegetation shadows. Where the low sun of dusk/dawn was producing long complex shadows and of course there were hundreds of trees and thusly maxing out my GPU (1070Ti) to the point where it couldn't handle it any further (not to say there are not other reasons, just in my case this is what I found during monitoriing of the CPU and GPU sessions in my close to the ground GA style of flying). So now I don't bother so much with vegetation shadows for dusk/dawn and have separate tuned config profiles to change on the fly. I discovered that with vsync on and a monitor Hz rate of 30 I would get a very smooth 30 FPS and would also greatly reduce the GPU load (as compared to a monitor Hz rate of 60 which with vsync on would be a max of 60 FPS), meaning the GPU would only have to work half as hard for the same output and I could successfully ramp up the P3D details settings without overloading the GPU and killing off the frames. So now I have a selection of tuned profiles that mean I can chose a profile for the type of flying I'm intending to do. Do need a monitor capable of 30 Hz though, or alterantively a CPU/GPU that is capable of exceeding 60 fps in even the harshest of CPU/GPU driving. I chose the monitor route as it was the least expensive option and best bang for the buck when it came to smoothness and great detail levels. Cheers

Perchance are alternate configs being loaded i.e. Profiles in P3D's Display Global settings? Profiles do store traffic config info ([TrafficManager]) which can be different between profiles. Cheers

Mate, if you were a DOS guru then this stuff will be managable and it's GUI driven. In Prepar3D vsync is a On/Off dropdown and a checkbox, you'll find it located as per the following in P4D v4.4. Prepar3D open Menu/Options/Graphics/Display/Frame Rate Controls To see the Hz capabilites of the monitor, check with either windows itself or the Nvida Control Panel, note Windows(10) is a somewhat convoluted process compared to the NVidia control panel. Windows (10): Right click on the desktop and choose Display Settings When the Display Settings window opens, locate and click the Advanced Display Settings link When the Advanced Display Settings windows opens, locate and the click the Display Adaptor Properties link Another Windows will open, choose the Monitor Tab The available Refresh Rate Hz will show in a drop down Unfortunately Microsoft appears to be practicing delibrate obfusication/dumbing down with each new so called "better" version of Windows10 so things might be a little different the above, plus the "windows" (in Windows10) typically do not have the option to search the window contents like their previous releases did. And they also remove abilities and obfusicate for what was previously simple functions such as file associations and choosing a default program, but anyway, MS are clearly on an Emperors New Clothes type of path and that's that, and enough Windows ranting, I really hope Lockheed Martin have a plan in place to move off windows, even it it takes a number of years, maybe with a Vulcan engine perhaps ??? I think when I'm forced to move from Windows 7, I'll choose a LTSB edition of Windows10 (which has a locked feature set i.e. no massive twice yearly potentially breaking feature updates bringing more problems and less desirable so called features). NVidia Control Panel: Open the NVidia Control Panel In the Left Hand Pane, navigate to Display/Change Resolution and select The available Refresh Rate Hz will show in a drop down to the right of the Resolution picker For an average monitor the refresh rates will be 50/60 Hz with 60 the default, if you are luckly you'll have lower rates showing, which would typically mean you could probably configure a 30 Hz rate (see my previous posts in the thread) in the NVidia Control Panel for example. As a test you might want to try setting the Monitor refresh rate to 50 Hz and enabling vsync/unlimited frames in P3D. Such a setting means the frame rate will be locked at 50 fps (MAX) and while I've often found while 60 fps maybe unreachable, 10 fps less might be more achieveable, especially if flying photo real sceneries such as BlueSky/Mega Cheers

In my experience the use of vsync is as a frame rate limiter, that also provides an incredible level of smoothness when both the output frame rate and monitor hz are in sync. If your monitor refresh rate is @ 60hz and vsync/unlimited frames are on then P3D will try and maintain a fps rate of 60, which in general can be difficult to maintain and tends to use a lot of resources. However if your monitor refresh rate is 30hz then P3D will try and maintain a frame rate of 30 fps, and most machines can keep up with 30 fps and have a degree of overhead for those areas where there would be heavy frame rate drops. With vsync on and unlimited frames you've set P3D to run as fast as it can but at the same time to keep the frame rate matching the monitor hz value i.e. 30 hz equals 30 frames per second. So ideally a reasonably powerful computer and GFX card, (e.g I have a Ryzen 1700 O/C to 4.1 Ghz and a GTX1070Ti) will be able to maintain a 30+ fps frame rate and a monitor that can sync to 30hz will provide an excellent enviroment for syncing the frame rate to the refresh rate for silky smooth performance. Occasionaly I jump into FSX-SE and I'm amazed at what I used to think was smooth is actually full of jumps, stutters, and is not smooth at all, as compared to P3D with vsync on, unlimited frames and a monitor refresh rate set to 30 hz. Of course if a machine can actually maintain 60 fps, then a 60 hz refresh rate and vsync on will provide an even smoother level of performance, maybe in a few years I'll be able to afford such a machine, or maybe P3D performance will jump expotentially, who knows... Here's a thread that discusses it a little further. Cheers

Hi Mike, By RD ini I mean the RD preset available from the RD website (the presets are .ini files) But anyway I've put my config in the Spoiler below. Just highlight all the text, copy and past in a .txt doc. Then rename the .txt doc to, TBM v1.9.5 Tomato Shade - no advanced relections.ini And you'll have what I've configured and am using. Cheers

Sorry man, like I said I've many different sets of settings based on the time of day, high/low detail, photoreal scenery etc. plus I have a lot of addins that suck the frame rate down, hence the custom profiles and GPU tuning and what suits my custom rig/style won't necessarily suit others. The best advice I can give is to follow my previous advice and set the monitor refresh rate to 30 hz, leave vsync off initially (for fps testing) and start ramping up values making sure you're going to be geting around 33~36 fps and not max your GPU to 100%. At that point turn on vsync and P3D should be able to manage controlling its fps to the 30 fps required for vsync to work with @ a monitor refresh rate of 30 hz. Additionally I have quite a few custom config settings in the p3d.cfg file, mostly based off Rob Ainscough's custom config settings for P3D v4.4 If you want to run your monitor @ 60 hz for general use and have P3D automatically change it to 30 hz (and back to 60 hz on P3D exit) you'll find this thread of use. I also run a custom written startup script to call various addons, set priority and run them if they are not already running. So... many settings built to suit my rig and style and mostly built by following the 30 hz vsync rule and keeping the GPU just under 100% I think half the fun is the discovery and getting there with a build to suit your own rig and flying style. :-) Cheers

Happy you enjoyed. There are some minor stutters in it which are related to the video capture software, otherwise it's actually pretyy much as smooth a silk while flying. Note you see the occasional sudden momentary frame drop which will coincide with a drop in the framerate counter at the LH bottom, and at those points I was hitting 100% GPU usage and it momentarily would drop off from being in vsync. Yes I am using Tomato shade (also a few reshade shaders) and the PTA ini is a self-tuned combo from the examples at the below two links. Essentually it's mostly the RD ini without using Dynamic Aircraft Reflections and Aircraft Image Based Lighting and othewise tuned based on review of Adam's ini. https://www.rdpresets.com/rd-tomatoshade-preset.html https://www.nzfsim.org/index.php?dsp=TS So coodo's to those people who created them originally, there are certainly some talented people out there. Cheers