PurdueKev

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

10 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

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

Recent Profile Visitors

214 profile views
  1. PurdueKev

    Which is better? V4 or V3

    With all due respect, Youtube videos are not an effective way to compare software performance. I have used all of the P3D versions from V2 through V4, and by far V4 is the most stable and polished of any of the ESP-based simulators. It is the first version of P3D that frankly feels "finished" in the sense that there are few, if any, remaining significant (meaning sim- or immersion-breaking) bugs, despite being only at 4.2. CTD's are an exceedingly rare occurrence (gosh, I remember having to limit view changes in previous versions because too much switching would inevitably lead to a CTD, or worrying that clicking on the menus too much would do the same), assuming one is disciplined in using add-ons that are specifically compatible with v4. Many users who complain that they don't get the "same performance" in v4 as in v3 are trying to run autogen settings that far exceed what was even possible in v3. The update mechanism, although the process could still be improved, is far easier than the mess that was v3. To be honest, I felt that v3 was never "finished" in that there were still features that did not function completely when the transition was made to the next full version... Yes, if backwards compatibility of third-party software is an important consideration, or if one is running hardware with limited performance headroom, then v3 may be something to consider. But frankly, for 90% of users I can't see how v3 makes any sense at all. I ran v3 and v4 side-by-side for some time when v4 first came out, and I can attest that the performance and stability difference was stark.
  2. PurdueKev

    A10 Warthog - Is There a Working Model for P3DV4?

    With respect, I do not believe this is a fair characterization of DCS. Yes, there are certainly gaming components to the experience - the developers just choose to focus the simulation elements in specific areas; for example, systems and flight model of certain aircraft, rather than faithful recreation of scenery for most of the world. IMHO, the DCS A-10C in particular is one of the most faithful study-level simulations of one aircraft type ever created for a desktop computer platform. For the record, I own P3D, X-Plane and DCS, and I use and enjoy them all - each has its place and purpose, and strengths and weaknesses. But DCS is no more or less a simulation than the others.
  3. PurdueKev

    Saitek Switch Panel - strange ALT behavior

    Thanks so much! I was pulling my hair out wondering what I was doing wrong! I will try out those edits in the LINDA editor as you described - I very much appreciate you checking into the code! Cheers!
  4. Hello: I recently installed LINDA in order to control my Saitek Switch and Radio Panels in P3Dv4. I have copied and pasted the appropriate profile text from the config-HID-saitek file into config-HID to control the "Default FSX" assignments with the Switch Panel, and all assignments show up properly in the LINDA GUI. However, for some reason when turning on the ALT switch with the BATTERY switch already on, the BATTERY switch turns off on its own. This occurs for every aircraft I have tried it with. Any idea what is occurring? I have tried several times to assign and re-assign the BAT and ALT switches, and I am sure that I have only the action for the Alternator to turn on when the ALT button is activated, but I can confirm this is happening repeatedly. I do not have the Saitek/Logitech plug-ins activated (so only LINDA is controlling the panels), and I have the latest version of FSUIPC v5 installed. Have you seen this behavior before? Thanks!
  5. PurdueKev

    Hyper Threading & P3D V4?

    Actually, my Skylake 6700k (4 cores, HT on, OC 4.5 Ghz) runs best (meaning, no noticeable stutters or long frames) with Affinity Mask=245 or 85; by contrast, with default setting (i.e. no affinity mask in cfg) I experienced fairly significant stutters. This is quite reproducible on my system. Whether or not one needs to use the affinity mask setting is highly dependent on one's specific hardware and software environment. On my system, allowing P3D to run with two threads simultaneously on cores 0 and 1 while also hyper-threading does not work well, and the observations are consistent with what was discussed in the reference thread posted by Alan. I choose to keep hyper-threading on because my sim computer is also used for other applications where HT is a clear benefit.
  6. PurdueKev

    AffinityMask - Why?

    I switched from 85 to 245, and set up TrackIR to run on the last two cores only, and... WOW. 85 was running nicely but 245 is even smoother now when panning in the VC. Thank you!
  7. PurdueKev

    P3D V4 - Can't get rid of microstuttering

    Hi Anders: If you go to the Windows Start Menu, under the Lockheed Martin group click "Learning Center." Go to Prepar3D + Getting Help + Advanced Configuration, and various additional tuning options are described. What we are discussing is under the [JobScheduler] heading (scroll down in the Help file to see the description); it does not normally exist in the Prepar3D.cfg file, and thus the default value when it is not present is 14 (use all available cores). If you wish to set specific cores for P3D to run on in a multi-threaded system, you can add a [JobScheduler] section to the cfg file and add the AffinityMask entry with the value you desire; Steve described various options depending on which cores you want to run on, whether you have HT enabled, etc. On my 6700k OC system, I added: [JOBSCHEDULER] AffinityMask=85 to the end of my Prepar3D.cfg file for best performance. This limits P3D to run threads on the 4 physical cores of the 6700k only, and not to run any threads on the virtual cores. I found this worked best for my system rather than letting the Windows job scheduler free reign to use all cores for P3D. I could go further to specify affinity masks also for my add-ons so they do not conflict with the main P3D thread, but I haven't found the need at this point on my system. If you are happy with the way P3D is running on your system, this is not necessary. But it may be helpful depending on what add-ons you have and what microprocessor you are running. YMMV.
  8. PurdueKev

    P3D V4 - Can't get rid of microstuttering

    Respectfully, that may certainly be true for your specific hardware set-up or combination of add-ons, but I have set up controlled testing on my system (overclocked 6700k, with Trackir, Active Sky and Spad.Next running) with and without various AM settings and there is very stark difference. The behavior is in-line with what Steve described. With AM=85, there is zero stuttering; without it (default), there are very pronounced stutters every second or two. The Affinity Mask setting is an LM-supported advanced option in the config file that is described in their Help documentation.
  9. PurdueKev

    P3D V4 - Can't get rid of microstuttering

    That is great! I am not an expert on how CPU threading works - my knowledge is just from reading posts by some of the smart folks around here like Rob - but that sounds about right. My understanding is that there is likely going to to be one main thread maxed out, and 2 or 3 others running at a lower utilization. Cores 0, 2, 4, and 6 are your physical cores, and 1, 3, 5 and 7 are the virtual ones you get from hyperthreading. This is all very hardware specific, but since we both have 6700k CPU's I thought perhaps you would be helped as I was. AM=85 is the exact same setting I had for v3 on this same computer, so at least for me it works much better to have P3D only running on the physical cores, and let Windows manage the other add-ons. When I say "much better" for me it is not just a matter of degrees - with AM=85 there is essentially zero stuttering and almost DCS-type smoothness, whereas without it I would see stutters every second or two especially when panning with Trackir. As Rob said, this is probably something with the specific add-ons I am running that P3D just works best only on the physical cores. I don't turn HT off because I don't have a flight-sim-dedicated rig, and I want the extra multi-threaded performance for other stuff. Note I am OC'd at 4.5 Hz - I don't know if you are as well. I definitely do not max all my settings - my 980 Ti is not strong enough for that (can you believe we are saying that?). But I don't feel I have to make undesirable compromises in the settings in V4 like I did in v3. And v4 is definitely WAY smoother. I would say if you are happy with the performance now, leave everything alone and go fly! EDIT: I just noticed you also talk about seeing blurries - I increased TextureMaxLoad to 30 and have FFTF at 0.10, just like I did in V3. That fixes blurries and slow texture loading for me. Essentially my only config tweaks are the same ones I had in v3 - Affinity Mask, TextureMaxLoad and FFTF. I could probably be fine without FFTF but I like the extra frames I get with it. The Help documentation supplied by Lockheed Martin describes where those entries go, as does Rob's excellent P3D guide (much of which still applies).
  10. PurdueKev

    P3D V4 - Can't get rid of microstuttering

    Boeing: I would definitely suggest following Rob's process, but FYI as another possibility I have found that my 6700k (same chip as yours... HT on) still responds to an affinity mask setting of 85 (i.e. running P3D only on the physical cores, not the virtual ones) to eliminate stuttering. It is very reproducible - with anything other than 85 (including default), I get stuttering; when I change the AM in the config to 85, stutters gone. The stutters I saw were big ones though, every second or two. I suspect this is because I am also running Trackir, Spad.next and Active Sky and there is a conflict there between one or more of those add-ons and the P3D threads (had this same problem in v3), but I have not gone through a controlled process to test with and without to find the true culprit. Since for me the sim is extremely smooth and fast with that AM=85 setting, I would rather fly than tweak at the moment. If you still see stutters after running through the process above, you may want to try it. Also, I have a G sync monitor and I run unlimited frames and vsync/triple buffering off both in the sim and in Nvidia Control Panel.
  11. PurdueKev

    Add-ons at risk

    Hello Keith: I tried the LM method using an add-on file to my current location for the Scout in P3Dv3 (same as I did successfully with the Turbine Duke and Lancair), but it did not work. I had no VC and no aircraft model, so I assumed the files were just not compatible. May I ask how you were able to get it to work? This is my all-time favorite aircraft in any sim... Thanks! Kevin EDIT: I figured it out - there are two gauge files associated with the Scout that must be installed in the Prepar3D v4 Gauges folder for the aircraft to work. Once I added those in, everything worked perfectly! Also, I don't think there is a custom sound gauge with the Scout like with the later RealAir aircraft - the flaps sounds worked fine and everything else could be heard as normal. Very pleased, as I love this old aircraft and would always find myself gravitating back to it. If anyone wants to install this via the LM-standard manner (using an add-ons file in your v4 Add-ons folder to point to where you have the Scout installed), the two gauge files that you must manually copy into the Gauges folder in P3D are RASScout07 and RASScout07_Radios. Without those in the proper location, I had no VC or external model.
  12. PurdueKev

    Is there any microstutters in V4?

    I concur with the other responders, V4 is vastly improved over v3 if you have your v-sync set up correctly for your hardware. Panning is very noticeably smoother with Trackir. For my G Sync monitor, with G Sync set to on (very desirable) I ensure V sync is off both in the sim and in the Nvidia Control Panel, and unlimited frames in the sim. G Sync does seem to work very well with this set up. My fps can even dip down into the 30's and still look quite smooth. I never could get the most out of G Sync with v3. (I also have Affinity Mask set to 85 in the cfg file like I did in v3, as I feel like my Skylake is handling simultaneous running add-ons - Trackir, AS16/ASCA, spad.next - better with P3D running only on the physical cores. But I have not measured anything in a controlled manner, it is just a qualitative observation at this point.)
  13. PurdueKev

    v4 same tweaks as v3?

    There is no reason to tweak at this point. Out of curiosity I did test the same affinity mask and FFTF tweaks that I have in v3, and they either did not make a noticeable improvement or actually (in the case of affinity mask) made things worse. IMO the in-sim sliders are all most users should need.
  14. PurdueKev

    Jumpy FPS in V4

    The Speedtrees are huge performance drags, and IMO frankly not very attractive either. I had low fps and stuttering on one flight, and I hadn't realized that the settings profile that I had loaded still had the dynamic tress to ON - as soon as I turned them off everything smoothed out. If you don't like the 2xSSAA alone, you can also try setting FXAA to ON for additional AA smoothing - does not appear to have a performance hit. Having said all that, I can still get occasional stutters here and there - but light-years better than v3. I should also say I have a 144Hz G-Sync monitor, which I am sure affects what is going on for me.
  15. PurdueKev

    Jumpy FPS in V4

    What anti-aliasing are you running? I had to drop down to 2xSSAA on my 980 Ti... 4x or 8x was too much - that level of SSAA cut fps almost in half and led to stutters. V4 is very demanding on the GPU and especially video memory. The good news is that even 2xSSAA plus FXAA ON looks much better than the highest anti-aliasing settings on v3. Also, Speedtrees and terrain and vegetation shadows are big performance drags as well. And I tested other affinity mask settings and they are not necessary - the default seems much more effective in managing threads on a multi-core system.