• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Profile Information

  • Gender
  1. Thank you Lars for spending time reading my post. Of course it makes sense now. I 'll try to find your up to date topics. I am not visiting the forums a lot lately, and many interesting things are currently escaping my attention. Cheers Nikos
  2. Hi Lars (SAAB340), Congratulations on your tremendous work. I 've tried out AM=249 and it works great for me. Even better frames than my previous and more widely tested AM=84. I test my various settings in a very specific scenario and some really demanding "views" and "spots" of some missions that are mostly CPU hungry, so even the slightest differences can be measured. I was really surprized when I saw the results of your research on Hyper Threading and it's contribution to faster loading of terrain and textures. I always suspected that there must be something escaping most people's research on this. You proved that there is something missing, and it's a great thing to have facts that can't easily be disputed. Now, in the main subject. AM=249 makes use of cores 0, 3, 4, 5, 6 and 7, right? Core3 though is a logical-non physical core. How can someone put a load on a logical core without involving its physical part? Wouldn't be the same if we assigned an AM=245 instead? What is the difference? Sorry for my ignorance. And something else, please. What is the best FFTF setting for me when I am using these setting under [Display]: TEXTURE_BANDWIDTH_MULT=60 TextureMaxLoad=30 UPPER_FRAMERATE_LIMIT=30 Thanks in advance! Nikos (Greece)
  3. Very nice! I guess DX9 with EnbSeries? How do you make the slow motion thing?
  4. nikos

    New tweak?

    I don't know if anyone is still interested, but the last 2 days I've been experimenting with the settings I mentioned above, with the heaviest scenarios I could, (heavy in relation to my computer specs of course). Nothing too heavy though for the specs of other systems exposed here. I must admit that a target of 60 frames inside FSX was not the best for heavy situations. At a specific "hot" spot, with a specific view angle, seeing the whole airport in front of me and most of the add-on scenery from a height of 2000-2500 ft, the winner setting was unlimited with 28-29 fps. In all other angles and view spots 30 fps average was easily maintained with fps value varying from 27 to 35 but with no tearing and lag showing up. 30, 60 and 90 fps inside FSX were tested with the exact same settings and flight paths and gave similar results: 30 fps steadily, but when I reached the specific "hot" spot fps went down to 22-24 fps and stuttering became annoying. On the other hand, TFR set to 60fps was a better, less demanding choise in lighter situations. Fps were always close to 30 with a much smaller value breadth (~29-31 fps), whereas the breadth I observed with a TFR set to unlimited was significantly larger (~27-33, as above) while the Graphics Card auto-fan was making a greater noise trying to keep temps down. So, sorry for all the fuss. Nothing new and nothing special... I will post my Nvidia's and FSX's settings here, just in case someone wants to give them a try. I run FSX with DX10 Preview. VSync Tear control was set back to Standard for this test. The rest were taken from the well known NickN's and RotationX's settings. My fsx.cfg tweaks: [bUFFERPOOLS] UsePools=1 Poolsize=8388608 RejectThreshold=126976 [GRAPHICS] ForceFullScreenVSync=1 D3D10=1 TEXTURE_MAX_LOAD=2048 HIGHMEMFIX=1 MultiSamplesPerPixel=8 MultiSampleQuality=8 [Main] DisablePreload=1 FIBER_FRAME_TIME_FRACTION=0.25 [Display] TEXTURE_BANDWIDTH_MULT=80 TextureMaxLoad=30 UPPER_FRAMERATE_LIMIT=0 WideViewAspect=True [JOBSCHEDULER] AffinityMask=14 (quad core, no HT) [TERRAIN] LOD_RADIUS=6.500000 TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=800 TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=1000 [sCENERY] MAX_ASYNC_BATCHING_JOBS=3 SmallPartRejectRadius=3.0 Yesterday I tried this texture conversion too with remarkable results. Credits to NickN, RotationX, Steve and Word Not Allowed. That's all.
  5. nikos

    New tweak?

    I may not be the most appropriate one to explain, but the FSX's command is not a limiter. It's a target frame rate. You choose the frame rate you want FSX to achieve. You don't exactly limit its frames. By setting it to "unlimited" you force the system to run at its best all the time and you come afterwards to "cut" what is above a desired limit with an external limiter (ex. FPS Limiter), because if you don't, instability might occur. A widely accepted frame limit for smooth performance (fps is not the real issue) is 30. What I am saying here is that I don't think it's (always? we 'll see) necessary to ask FSX to constantly run with full power, especially with the light scenarios I use (small airports, prop engine planes etc.). Add-ons like REX and FTX don't kill fps in the way a huge airport does (I only have Fly Tampa Athenes and some Iceland's freeware sceneries and airports). In my case, 60 fps as a target inside FSX made my simulation softer (with unlimited frames my GPU temperature rises way above 70° C) and smoother (almost no tearing effect and no stuttering). I don't know what would happen with heavier stuff like the PNDG 737, big airports etc. In this case, target frame rate set to unlimited might work better.
  6. nikos

    New tweak?

    From here: "The profiles are stored in a binary file that's usually edited using the Nvidia Control Panel's "Manage 3D settings" page, Program Settings tab. That's all Inspector is, an alternate way of editing that file - it does not make the video card do things it and the driver are not already capable of doing." By selecting "Adaptive (half refresh rate)" in Nvidia's Control Panel you just make sure that 1/2 rr is going to be applied. It's not "Setting Vsync in three different places". There is only one place basically. GC's Driver. You all have a point though. Maybe unlimited frames inside FSX work better with heavy add-ons and full traffic. I never use them. My system is not as good as the ones mentioned above (i7 OC etc.) and I try to stay away from trouble. I will try a demanding scenario soon and I will post my conclusions. Thanks anyway. Nick
  7. nikos

    New tweak?

    Thanks for the answers. I forgot to mention (or emphasize) a few things. 1. Inside nvidiaInspector, in Vertical Sync Tear Control I chose "adaptive" and not "standard" . Inside Nvidia's Control Panel make sure that "Adaptive (1/2 refresh rate)" is checked. Inspector is an external tool that does not always communicate perfectly with the Graphics Card Driver. Nvidia's Control Panel gives the final commands, not the Inspector. 2. I run FSX in DX10 Preview, not DX9. I basically use the Inspector settings shown here Everything except the "standard" Vsync Tear Control (I use "adaptive"). In Texture filtering I switch between "High Performance" and "High Quality". Depends on the scenery I intend to load. These settings are widely tested and known to give a 6-10% increase in fps. 3. Don't try only 58 fps in TFR. Try also 59 and 60. Might make the difference. 4. All the above work with WideViewAspect=True and ForceVsync...=1 4. This thread is not exactly about fps. It's about smoothness, tearing and stuttering. When I use no limiters I also get 50-60 fps in many cases. That's not the issue here. I couldn't get rid of tearing and stutters even with an average of over 50 fps. Anyways, thanks again for trying this out. I might upload my exact settings in the near future. Cheers, Nick
  8. nikos

    New tweak?

    Hi everyone! I am new here in the forums and new in the FSX thing. I’ve been "flying" with FSX for about 2 months now. From the day I started, I’ve tried to read some basic things about FSX. The most difficult part for me was to achieve smooth performance (everyone wants that). I must mention here that I have a mid-end computer (i5 @ 3.2-3.6GHz, and a GTX660 OC) and tweaking was inevitable in order to gain some performance, especially with some heavy add-ons like REX and FTX Global. So, I started watching videos and tutorials in YouTube and learned a lot (not everything, of course, the basic stuff). I 've used J. Bojote's optimizing tool, I 've read the biggest part of NickN's "Bible" which helped me setting up my system, I 've watched RotationX's tweaking series (very informative and easy to use), some Frooglesim's videos, read Nikos's answers, used Steve's DX10 fixing tools and many, many more... My respect to all these guys. They really helped me immensely in understanding all these new things. There are, as I can see now, 2 accepted ways of locking frames in a simulator like this: 1. Internally, with FSX's settings (NickN suggests a target frame rate of 30fps with no external locking) 2. Externally, either with the FPS Limiter (when DX9 is used), or with the NVidia's Inspector Frame Limiter command (when DX10 is used). In this case, people sets the internal TFR to Unlimited and externally force it down to 30 fps. When Vsync is used, they just select a 1/2 refresh rate in nvidiaInspector, which locks frames to 30 fps (60Hz/2). My basic problem with the solutions above was that I kept having the image tearing effect, even with Vsync on, and when the desired frame rate was finally accomplished, another problem kept breaking my nerves... Stuttering. Then suddenly, eureka! Inside the Inspector's Frame Limiter I read this: "58 (might improve inputlag on vsync 60Hz)" I don't know if anyone has already tried this out, but by setting the TFR (Target Frame Rate) of FSX to 58-60 internally and applying 1/2 refresh rate inside the Inspector one gets impressive results (in my system, the best so far), compared to all the other combinations (and believe me, I've tryed a tone of them). No more tearing, no more stuttering. A perfectly smooth simulation! I am not a computer genius, but I sense that by setting the TFR to 58-60 inside FSX, you guide the application to synchronize with the screen's refresh rate. Then, the NVidia's 1/2 refresh rate setting really makes an easy job producing 29-30 fps from a stabilized system. (Make sure to check the Vsync 1/2 refresh rate option inside the NVidia's Control Panel too. The Inspector does not always communicate well with it). Try this out if you want, and see what happens. I would like to read your opinions. Nick PS NVidia's ShadowPlay is a great invention!!