Jump to content

Mischung

Members
  • Content Count

    116
  • Donations

    $25.00 
  • Joined

  • Last visited

Community Reputation

48 Neutral

About Mischung

  • Rank
    Member
  • Birthday 07/08/1979

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

1,327 profile views
  1. The database in P3D 5.1 is dated around 2017 (no exact date known) I don't know if 5.2 has further updates, but I would guess no. So, the data you get is already kind of outdated. The only option is to send a request to Herve (aero.sors) to get access to his updated airport files for P3D V5. This will only update stock airports of course. Cheers...
  2. Hi... That should be no problem. In that case you can use the advanced driver search: https://www.nvidia.com/Download/Find.aspx Just download an older version and reinstall 😉
  3. Sorry, forgot to mention that... I'm using a RTX2080 Super...
  4. Updated to the new driver yesterday, but had a lot of microstutters in the sim after that. Going back to 457.30 solved this for me, so will stay there until I really have a reason to update 😉
  5. Yeah, I think that's it...unfortunately 😕 Aivlasoft's algorithm is not able to handle the way FSAerodata is updating the airport database (especially the ILS updates). The only option you have, is to use Herve Sors (aero.sors.fr) updates and he cannot provide any updates for P3DV5 right now due to copyright reasons. It would be an option to use the AIE (Airport Inspector and Editor) from his site to search for discrepancies and fix them one by on with AIE (which is some work to do I guess). Also third-party airports have to be updated manually, because Herve's data only updates the stock files. Hope this helps...
  6. Version X.1 release always was about 3-5 months later. So just keep in mind we had two hotfixes already, but I would still guess it will be released this month 😎🤞 Marc
  7. Hi, we had a topic on this some time ago and I did a comparison, maybe worth a look 😉 How are you limiting you frame rate I would definitely recommend RTSS, but in the meantime I bought a new monitor capable of 30 Hz and this is the best option IMO. Marc
  8. I'm pretty sure it should be "Voice Cockpit Services" 😉 With a nice German-English-Slang... I would guess this can be used to control aircraft systems and ATC via voice-control, which would be a nice feature.
  9. I really hope that Vector for V5 does not add any airports via BGL-files, but only updates streets, shorelines e.g. Anyone can confirm that the Vector data does not include airport BGLs at all? Thanks! Marc
  10. My own test applies to V5 only, but in my opinion the results should be transferable to V4 too... It's worth a try 😉
  11. Hi Bert, that's what I thought at first too, but there seems to be an easy explanation 😉 Using the NVCP limiter wll show your "real" CPU usage/load, so you can use it to check your settings. In my case the CPU was between 40-60%, so this should be fine. But the results with RTSS are much better regarding fluctuations and all methods have the same loading stutters at the same position in flight. So even the CPU usage goes up to 100% it does not harm at all and here is why: RTSS is limiting the frame rate by introducing wait cycles to the rendering task (usually core 0). These wait cycles will be shown in task-manager as CPU-load, but it is not real (also worth reading Link). I would assume it will also not change CPU-temperatures etc, but I will check that again in the sim 🤓 This method seems to be the best way to realize a very stable frame limiting, but one cannot see the "real" CPU-usage now. I would use the NVCP-limiter to find out the best P3D-settings not overloading your CPU and afterwards use RTSS for daily use 🙂
  12. Hi! It took some time, but because I started this poll I wanted to come back on this topic now 🙂 First off all, thank you very much for voting and the great discussion! (until now 196 members took part!) 👍 I know that this poll was not as complete as many suggested, but I think it revealed the most basic settings we're using in our sim right now. I'm aware this all depends on the P3D-version you are using and your monitor refresh rate and so forth...but I did not want to bloat up this poll. I've seen a lot of different settings people are using and of course every system is different, with various addons and hardware, but I think I identified four major configurations which are used very often. They can be split into two groups: 1) Monitor refresh rate < 60Hz (or monitors with any other sync-feature) If you're lucky and your monitor supports it, you can set the refresh rate to 30Hz or even lower and then use VSYNC to match the fps to the monitor's refresh rate. 2) Monitor refresh rate >= 60Hz I would guess the majority does not have the ability to set their refresh rate to 30Hz or below, so in that case there are three major configuration I've seen: a) Use the P3D internal-frame-limiter A lot of people are using the internal limiter (~31%). Also a lot of other people said it's rubbish and did not understand why it is used at all. So I must admit I've used the internal limiter for quite a long time too, until it did not satisfy me anymore. b) Use the NVidia-frame-limiter Another 25% are using the NVidia Limiter. Wether via NV Control panel or via NV Inspector. I have not used it yet, but planned to try it, but more on that later. c) Use RTSS with the scanline x/2 option This tool seems to be a bit undervalued, because at the moment only <5% are using it to limit their frames. I've been using this tool for some time now. For me the option "scanline sync x/2 = -1" was performing quite well. I'm sorry, but this is going to be a bit longer 😂 🙈 With these options in mind I wanted to do a comparison to find out, which configuration works best. For a real comparison however, you need a measured value to be able to quantify the differences. For that purpose I used a tool called "CapFrameX", which is absolutely great for measuring frame times. So this was my test setup: System-specs: Intel i7-9700K @4.9GHz NVIDIA RTX 2080 8GB (Palit Super Jetstream) 32GB RAM @3200MHz 2x M.2 SSD Samsung EVO 970 (OS + Sim) Three Full-HD monitors using Nvidia-Surround @60Hz (only 60Hz available) OS and NVidia-driver - NVIDIA driver 446.14 - Windows 10 - 64Bit - 1909 - Build 18363.836 P3DV5 - HF1 (with only selected addons) - ORBX Global Base/OpenLC NA/Building/TerraFlora2 - FS Global Mesh 2010 - ChasePlane - ENVTEX/ENVSOUND/ENVSHADE - FSUIPC I also tried with all addons disabled, but the results differ not that much. P3D-Settings - no AM in use (using all 8 cores - 8 full cores, no HT for the 9700K) - my settings are very reasonable and not every slider right (maybe I add them later, but I recognized they did not play a major role regarding fps - as long the system is not overloaded of course) - No cfg-tweaks in place - Absolutely no traffic - Weather: only Clear Skies - Using a Standard Aircraft - Mooney Acclaim I recorded a flight in P3D, so I could load this recording and use the exact same flight for all captures. Taking off @KFUL, flying some circles and then landing @KLAX (around 13min flight time) As I only have monitors with 60Hz, I had to focus on the second group 2) with config a), b) and c) mentioned above. I tried a lot of different settings and variations, so I will pick the most representative for evaluation. Here are some basic findings: - There are always some little stutters, which I could not get rid of. Even with disabled addons and all sliders left they are still there, no matter which configuration I tried. It's not happening every second, but appr. 6-7 times during the 13min flight. (remember it was LA I was flying over) - CPU (Core0) load varies depending on the configuration (RTSS is always @100%, where an external limit with NVCP was around 50-60%) I've read about the behavior using RTSS (using up the idle cycles) and it does not seem to harm, so I accepted this behavior as is. - I also tried the AM-trick (removing core 0 and then set it again using task-manager) -> it seems to spread the load better, but regarding frame times it made absolutely no difference at all (snake oil...ha ha) - VSYNC and Triple Buffer on or off also makes not much of a difference for my setup, but I guess, that's because of the 60Hz refresh rate. And here is the table for 5 different configurations - using the standard deviation for comparison: So when looking at the standard deviation of the FPS, the configurations using RTSS are definitely recommended. I tried different combinations with unlimited internal, using the P3D limiter@33 and the combined option with the RTSS limiter @24fps (no big difference). Interesting is, that the NVCP-limiter is even worse compared to the internal limiter. And here come the diagrams (showing FPS during the 13min test flight): Here we can see, that the NVCP-limiter has much more fluctuations compared to the internal limiter. Also visible are the occuring stutters, because they are always at the exact same position (causing long frames with 6-15fps) I would guess, this is some kind of loading issue during the flight (maybe an airport coming into range). Looking at these results I would definitely recommend using RTSS with the "scanline sync x/2 = -1" option for users with a 60Hz monitor (limiting internally or not has to be tested, but it's no a big difference...maybe autogen is loading better with limiting in sim). The NVCP-Limiter is not doing a great job, so I would rather stick with the internal limiter in this case 😜 Cheers! Marc
  13. Hi! I'm really interested in how you guys are handling your frame-rate-limit? 🤓 Unfortunately I'm not able to run my monitors on 30Hz and just use VSYNC, as I would guess this is the best option to handle the frame-rate-limit. So I've been using the internal limiter on 30fps for quite a long time and it was kind of ok. Then I switched to RTSS with the scanline sync option and internally unlimited, which felt a bit better. But it would be nice to see what works for most of you 😎 Cheers, Marc
  14. It's not Freemesh, but I did a comparison using my good old FS Global 2010 and the P3DV5 default mesh (Comparison) I found out, that the default mesh is pretty good already, but in the meantime I enabled the "old" FS Global mesh anyway because I have seen some issues with the low-res-default-mesh when you're in mountainous terrain from a certain distance...when coming closer, the next LOD level takes over and everything is ok, but sometimes there are some walls in narrow valleys from a distance. So the FS Global version has a better base (low-res) mesh compared to P3DV5...but maybe this will be improved too over time 😉 Marc
×
×
  • Create New...