Jump to content

SteveW

Commercial Member
  • Content Count

    7,464
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

1,709 Excellent

About SteveW

  • Rank
    Developer

Profile Information

  • Gender
    Male
  • Location
    UK
  • Interests
    Writing Ideal Flight and other FS related material

Flight Sim Profile

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

About Me

  • About Me
    Writing Ideal Flight - website www.codelegend.com

Recent Profile Visitors

8,925 profile views
  1. When we first run P3D, or after removing the cfg file, the sim generates the file fresh. The fresh file contains settings pertaining to the system installed on, but some values are not yet included because they equate to default values. The sim reads the file and if a value isn't in there it assumes the default value, that value will appear in the file when the user changes the setting from default, hence the file grows a little by two or three KBytes. Even so, this file is read in once at the startup of the sim and amounts to the same amount of work. There is no change to how the sim performs unless settings were made that require more work, adding traffic or increasing shadows for example. So the only reason that a new cfg might improve performance is because the defaults are back. Remember that (with all versions of P3D and FSX) when we have Hyperthreading or SMT enabled in the CPU we need to apply an optimised affinity mask to guard against the sim putting scenery loading or other threads on the main thread core since performance is lost that way because the main core is doing more work unnecessarily.
  2. ..that is because I believe the Ryzen tool counts from 1..12 but the P3D AM thread locations are counting from 0..11, and count only the ones in the AM so thread 8 would be core 9 when using 4095=111111111111
  3. Sorry, brain still in numbering from1..12 mode - I should have said 8,9,10: AffinityMask=4095 P3DCoreAffinityMask=4095 MainThreadScheduler=8 RenderThreadScheduler=9 FrameWorkerThreadScheduler=10 since numbering is from 0..11 Certain out of order patterns can cause CTD's.
  4. I'm guessing you have a 12 core SMT disabled. Your AM setup puts the main thread on core 11 (counting from 1 to 12) and also there are problems with P3D when not keeping the three main tasks in order. With 12 core CPU with SMT (or HT) disabled and core 9 being the "best" you need to put the main task on core 9 and keep the order of the other two like this: AffinityMask=4095 P3DCoreAffinityMask=4095 MainThreadScheduler=9 RenderThreadScheduler=10 FrameWorkerThreadScheduler=11 However, that's not going to cure the fps drop but it will keep things running better.
  5. Make sure that the NVidia Global profile and P3D profile (3D settings Restore/Apply) are both defaulted to factory settings before testing and making settings. When making changes there only set the P3D profile. The few options are: Setting the TV to 25 or 30Hz refresh and setting VSync=on, in the P3D display settings set unlocked on the slider and TP=off. NVidia profiles at factory settings. Setting the TV to highest refresh frequency it can do and setting NVidia Control panel P3D profile to limit fps with P3D set to VSync=off, unlocked, TP=off. Setting the sim to output at 1920x1080 and when in full screen it will be upscaled to fit. By he way, with SMT enabled and a custom AM you can't improve frame rate but it will improve the rate at which the scenery and objects are collected and processed which might help improve some graphics features, would need testing.
  6. Yes it is 8 core and 16 LPs with SMT enabled and should work just as well as the 8 core Intel CPUs with HT enabled.
  7. Yes, the AM structure I posted for 8/16 keeps the three main threads (foreground) to a physical core each by only allowing one LP on each of the first three cores 0,1,2. The remaining cores 3,4,5,6,7 can run background threads and are great to be paired two per core. Add-on exe apps can be corralled across those background cores, allow at least two LPs per add-on exe. Main threads running up to 100% - utilisation can be reduced by using a limiting technique - VSYNC or Nvidia Control Panel fps limit - which will prevent the sim making lost frames. Also try the AM I posted just now for 8 core 16 logical processor to increase background thread performance which reduces the time it takes to process scenery and objects and loading the GPU.
  8. HT Enabled 8 core 16 LP 07,06,05,04,03,02,01,00=core number 11,11,11,11,11,01,01,01=AffinityMask = 65493 11,11,11,11,11,01,01,01=P3DCoreAffinityMask = 65493 00,00,00,00,00,00,00,01=MainThreadScheduler = 0 00,00,00,00,00,00,01,00=RenderThreadScheduler = 1 00,00,00,00,00,01,00,00=FrameWorkerThreadScheduler = 2 [JobScheduler] AffinityMask=65493 P3DCoreAffinityMask=65493 MainThreadScheduler=0 RenderThreadScheduler=1 FrameWorkerThreadScheduler=2
  9. Actually I would just leave SMT on and apply the affinity settings I showed anyway because ultimately that gives the best overall performance. But as I said, you can prove if this is an issue by testing with SMT off to see if fps improves, then you can turn it back on and use the affinity setup to equal that fps performance. SMT off saves problems from poor affinity settings and gives good fps but with reduced scenery loading performance, SMT enabled gives better scenery loading but it must have the correct affinity setup to maintain fps.
  10. If you run Task Manager and choose the Performance tab you will see cores: 12 and Logical Processors: 24. That will mean SMT is enabled. You enable/disable SMT in the motherboard settings (usually press F2 key during system boot to enter the settings).
  11. Is that the 12 core? If you have SMT enabled you have 24 threads (virtual cores) and the P3D v5 Affinity mask settings defaults unfortunately allows main threads to share cores with scenery loading threads which reduces fps sometimes as much as 30%. You can check if there is a slowdown from SMT by turning off SMT and running P3D from there. If you see a higher fps then at least you know core sharing is not helping. However, with SMT off you lose a lot of performance from scenery gathering (and basically hurts all file loading and networking) which reduces the performance especially when you fly along over new terrain - you can see the sim takes longer to load with SMT disabled by several seconds showing that the file loading and scenery/object creation processes are slower with SMT disabled. If that is so, re-enable SMT and apply the proper Affinity settings to get full fps with SMT enabled. In Prepar3D.cfg: [JobScheduler] AffinityMask=16777173 P3DCoreAffinityMask=16777173 MainThreadScheduler=0 RenderThreadScheduler=1 FrameWorkerThreadScheduler=2 This setup gives you good and sometimes slightly better fps with SMT enabled than when disabled, so I would always use that first of all and then concentrate on checking other settings from there.
  12. The motherboard is PCIe 3 so doesn't take such great advantage of the PCIe 4 GPUs and soon PCIe 5. Maybe wait for new hardware to emerge opting for a complete well balanced system in the future since I don't think you will see big gains over what you have for the money just yet.
  13. Nvidia recommends a minimum of 750W PSU for a 3090, but you may need more depending on the other hardware in the system. You may be OK with 850W. The i9 9900k is 8 core 16 thread with HT enabled. Please also refer to my previous posts in this discussion for 8/16 CPUs: HT Enabled 8 core 16 LP 07,06,05,04,03,02,01,00=core number 11,11,11,11,11,01,01,01=AffinityMask = 65493 11,11,11,11,11,01,01,01=P3DCoreAffinityMask = 65493 00,00,00,00,00,00,00,01=MainThreadScheduler = 0 00,00,00,00,00,00,01,00=RenderThreadScheduler = 1 00,00,00,00,00,01,00,00=FrameWorkerThreadScheduler = 2 [JobScheduler] AffinityMask=65493 P3DCoreAffinityMask=65493 MainThreadScheduler=0 RenderThreadScheduler=1 FrameWorkerThreadScheduler=2
  14. The fps slider (frame lock) is not a cap because as soon as it finishes one frame it begins another to fill the look ahead buffer so that it has frames in hand to keep outputting on precise intervals. This shows as a very flat line in a frame time delta graph and should be very smooth but keeps the system running hard. The fps limit in NCP holds back the frame rendering when it produces frames faster than the period between frames allows, reducing the load on the system.
  15. That might be helpful given you are using three monitors. However these new cards are more suited to motherboards with PCIe 4 which provides more bandwidth to the GPU than PCIe 3. Also these GPUs require more power from the PSU. So consider the motherboard and the power supply are adequate before purchase. Also you may want to wait for prices to drop or maybe even wait for the 40 series GPUs apparently shipping near the end of this year.
×
×
  • Create New...