Commercial Member
  • Content count

  • Joined

  • Last visited

Community Reputation

344 Excellent


About SteveW

  • Rank

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Profile Information

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

About Me

  • About Me
    Writing Ideal Flight - website

Recent Profile Visitors

4,296 profile views
  1. SteveW

    Locking Frame Rate

    You can try that. It's actually a frame-limiter rather than a frame-lock so can work with VSync=On. With locking on the slider you don't see frames exceed the limit but also it introduces look ahead so that each frame is made for a particular period. Otherwise each next frame is timed for the average of the last few frames, so with VSync=On you see frames wobble above the limit, therefor the external limit can work.
  2. SteveW

    P3D 4.1 CTD near Labrador

    If the sim itself CTDs then it is being taken down by an attached DLL or Gauge because I've been back and forth throughout the region with no worries. That attached DLL or Gauge may be reading faulty data at a particular area - faulty data installed into the stock sim navdata. It's possible it could be stock navdata but then that's to be proved by getting a CTD from the stock sim with a non-complex plane and scenery. So remove dll and gauge addons, fly the stock navdata and see if it CTDs then. Another idea is that an addon airport in that area may have a stationary plane model or similar with perhaps a bad cfg. A minor fault in an addon cfg can crash the sim with a CTD and look like another app or condition causes the crash.
  3. SteveW

    Congratulations to Rob Ainscough!

    Nice one Rob! Keep up the good work Jim!
  4. SteveW

    Locking Frame Rate

    Locked frame rate creates a look-ahead buffer, so in effect your system is making two frames where it only makes one in Unlimited. Start a setup with all sliders and functionality reduced. Creep up those sliders and traffic settings until you start to see performance drop. Go back a notch from there and get on with flying!
  5. No I wouldn't bother to do it that way: Instead I use IFPro to ensure I get the exact same repeat of what are otherwise variables in the sim What I do is set a flight onto AP with IFPro and save the flight just before a turn. Making sure the flight can start un-paused and then it is paused after a couple of minutes and a graph produced - then repeated exactly the same each time. Another good test of the setup is simply to measure the sim with the plane parked at the gate for a few minutes and don't touch any controls. Adjust a single item and repeat to see the exact influence. Without proper tools it's all just guessing, but with IFP used as a repeatable test harness is great, there's nothing else to match it.
  6. Instead of looking at fps (frames per second) we can study the time it takes to load the sim and load a scenario. We can use a stopwatch. Might seem a bit over simplified but in fact the rapidity with which the sim can load is a major factor on how quickly new resources can be utilised by the sim and hence affects the performance directly across the board. It's interesting to note that we can add cores and see the load time reduce up to a point whereby obviously there's nothing more to gain. What we can watch is, that adding ever more cores uses up more shared cache in the CPU reducing the performance without gain to the loading time.
  7. I use IFPro to ensure the flight is repeated exactly the same each time with AI traffic weather and so on. Using real time weather is no good it's got to be the same each time. I save a flight on AP about to make a turn onto final, something like that. I can make a config change and run the flight again and again. I run two to four minutes of flight and make graphs related to performance, fps and other data (30+ P3D items) recorded with IFPro during the flight. I usually make sure to repeat the same test three times each.
  8. He's not saying that is he, although he might think that. I would assume from what he says he simply wanted to compare fps when he makes changes to GPU and other settings to see what they do. But you're correct, simple fps comparison is not an indication of performance
  9. SteveW

    Flight Sim Expo in Vegas

    Good luck S!
  10. SteveW

    Couatl crashes

    The Prepar3D software Development Kit (PDK) incorporates access to some simulation objects through the IUnknown service interface. These are dll only as they don't do networking like the network pipes of SimConnect. However, it is the dll that is the cause of performance problems and of crashes and instability issues which are infrequently SimConnect borne, if ever. However it's good to know that it is understood that the overkill of SimConnect can be avoided where possible.
  11. Yes, should be OK with what you have.
  12. A study sim with FMS and navigation techniques does not need 60 when 24 will do so long as it is consistent that's key. If we want to run a glider or a fast jet up the fps then. Those guys on about how we must have massive fps - agreed. But it's a moot point if we can't have it. If they can get it they will use it quite obviously.
  13. I'm seeing 200fps+ with bald landscape adding in stuff reduces that so it's rather up to the user what they can get out of their PC and stick to what you can do.
  14. ...That's P3D 4.2. Other sims can do lots of fps with small areas to fly in that's fine and dandy too.
  15. I doubt it. It is a moot point you speak of. If they want to run 200 fps they can't so it's irrelevant.. I run 60fps with lowered settings 24 with advanced graphics.