SteveW

Commercial Member
  • Content count

    4,578
  • Joined

  • Last visited

  • Days Won

    1

SteveW last won the day on November 2 2012

SteveW had the most liked content!

Community Reputation

263 Excellent

2 Followers

About SteveW

  • Rank
    Developer

Flight Sim Profile

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

Profile Information

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

About Me

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

Recent Profile Visitors

3,087 profile views
  1. ...take a four core no HT, you got just four cores - runs the sim pretty well with no AM, what else would you do - but add HT and with no AM you still got only four cores but you got two processes ganging up on the first core that would otherwise occupy two cores so with HT enabled we usually use the "01" on the right the least significant part or core 0. But with four cores and P3D v4 the second process is small less affecting those setups no AM or "11" on the right than with v3 and FSX.
  2. ...any long string of ones, there's a physical limit to what the hardware can do so after a while those ones do nothing other than slow down the sim and heat up the CPU.
  3. ...either one of the logical processors (LPs) of a core active means that the entire core is active, there's no real two cores on a core. So to have "11" on the main core the process stops for the other. Instead the AM "01" moves that other work onto the next physical core along. If you think any old little app using only a little tiny 6% of the CPU is not disturbing the sim think again.
  4. You got it. The "0,1" restricts the monolithic main process to one LP of one core. The way P3D is written is to take out of that first process some work which would go onto the same core with "11" defeating the object. However, we can use "11" for the background tasks but we are going to get hotter. So Yes you're correct.
  5. That's it, pretty much in a nutshell. Problems faced are with only four cores and shoe horning in a sim that makes use of more than six where the old FSX/P3Dv3 made use of four. Even though P3D v4 really does use the CPU to better intent, in the end we have to be keeping things right with respect to HT enabled or having many cores, meaning adding a custom AM is mandatory.
  6. ...this comes back to what I was saying earlier which you missed - wind back the GPU function to set up the CPU and the addons, only after that increase the use of the GPU functions, finally adding AA.
  7. CPU and GPU both play a big part. A GPU must display lots of things at once and a CPU must do lots of things. The use of AMs is to organise multiple executables and so your idea that they are not important is a myth, there's no such thing as no AM.
  8. The AM can only restrict the sim from using all the cores, it cannot improve performance. Also we are talking about AMs in relation to *sharing* the CPU with addons that otherwise take performance from the sim. Your system is set up incorrectly since P3D settings can crush any system your exhibits the behaviour of being set up to do more than your system can manage.
  9. With higher frequency monitors the next frame is displayed sooner after the buffer is complete since there's less time between. With 30Hz and below that's getting too slow for using a mouse comfortably as it will drag but still be quite a fast fps for the type of sim that P3D is. With 144Hz that's too much to expect for P3D to keep up with so a division of that can be used effectively, With latest PCs we should be able to use fixed fps on the slider for 20-30 fps. With 144Hz monitor we would select 144/5=28.8 so 28fps on the slider might work well or set a limit in NPI at 28.5. With higher fps there's less time between frames, this makes it appear more fluid because the time between frames appears to be more consistent to us. If we use 30fps or less it becomes much more important to keep the time between frames consistent or we see it, which the fixed fps on the slider can do. Only way to find out is experiment because systems are so vastly different no one can say set this or that is going to be better until it's tried out. Don't make settings set too high, they might appear fluid but then slow down as the scenery complexity changes because there's no overhead capacity in the system. Then making changes to AMs and other things doesn't work because the sim is flat-lined somewhere.
  10. Why not try, I'm thinking there will be little or no difference, comes down to the weight of numbers anyway. Backing off is the only way.
  11. Yes, please refer back to my post regarding sequence of setup, go through those steps and get a feel of what's going on there.
  12. You might be using NPI to alter AA strength or do a few things, but those NPI VSync adjustments don't help since it's all under control of the system. So we set everything we have available in the P3D settings page. Only if it's not available in P3D do we need to bring out NPI.
  13. Why? The 30Hz monitor and VSync=On and Unlimited fps on the slider provides a pretty good setup. However, it's not a limiter and the output wavers. You might see 25-35fps or maybe 27-33fps depending on performance and settings. Going into NPI and setting the fps limiter to just below the 30Hz of the monitor provides more throughput to the system and improves frame coincidence. Check out the graph earlier. Not much in it, it's an option we can try. Another is setting 30 on the slider, that's smoother still but uses more system throughput.
  14. Don't use any of that, leave it up to P3D Display Settings. Default/Apply the profile in NVidia Control Panel.
  15. Sorry but unfortunately I cannot go over all the nomenclature and descriptions of technical matters every time I make a post, or indeed post in several languages. Some legwork by yourself will be required to understand the technical matters about which I'm posting.