Jump to content

Search the Community

Showing results for tags 'dx10'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • General Forum
    • FSL Control Center Discussion
  • Aircraft
    • Concorde-X
    • A3xx Master Series
    • Screenshots
  • Tools
    • FSL Hardware Interface
    • FSL Spotlights
  • Cockpit Building
    • Chat about cockpit building
  • easyJet Crew's easyForum
  • British Airways's The BA Club
  • Aegean Airlines's The Pub of Accord
  • Wizz Air's Topics
  • My little software corner's Developments


  • A319-X Liveries
    • PBR User Submitted Liveries
    • Older Non PBR Liveries
  • A320-X Liveries
    • Older non PBR Liveries
    • FSX & P3Dv3 Liveries
  • A321-X Liveries
    • User Submitted Liveries
  • A3XX Misc Files
    • Cabin Textures
    • EFB Backgrounds
    • A320-X - Unsupported Mods
    • Utilities
  • Concorde-X Files
  • FSL Aircraft Paint Kits
  • Spotlights
  • Hardware Interface for Prepar3D v4 & v5
  • Legacy Interfaces
  • Olympic Air Virtual's Files
  • Wizz Air's Files
  • Eurowings Crew's Configs / Textures / Sounds
  • Eurowings Crew's Operational Files
  • My little software corner's Downloads

Product Groups

There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 10 results

  1. Gerald Krutsch

    My FSX:SE tweak experience

    Ok guys, here are some of mine findings regarding FSX:SE tweaks. -FOREWORD- Now and then comes the time when your SIM gets realy laggy and you can't seem to figure it out what's exactly causing the issue. Is it your drivers, your SIM settings, a particular addon or is just because you overloaded your SIM? -HOUSEKEEPING STEPS- This just happened to me and I decided to start again from 0. For housekeeping stuff I went ahead and uninstalled all my Addons in an order that I thought would make the best sense: 1. External services like: weather (AS16), GSX services, traffic; 2. Internal "stand alone" addons like liveries, ACFTS; 3. ARPT sceneries; 4. Enhancements (that modify STD FSX files like textures...): REX, GEX, UTX,... You get the point right? Finaly I uninstalled FSX:SE, restarted my PC, cleaned up the registry and tried to delete everything FSX related from all known locations (Program Files, AppData...). I basically opened all locations where I knew FSX or addons are installing stuff and deleted those. Final step was to defragment the drive where all of the main files were installed. Not to forget: I reverted all nVidia inspector settings to default! -FRESH INSTALL- I then installed FSX:SE fresh and the first thing I did was to start FSX and move all scenery setting sliders to the max (even the water reflections). Further I turned Anisotropic ON, AA ON, Lens flare and advanced animations ON, frames to unlimited, all traffic OFF, all shadows OFF...and then closed FSX:SE. This step was necessary to get the first fsx.cfg created. The next step was to open fsx.cfg and change only the Wide aspect from false to true. Saved fsx.cfg and copied it as "vanilla_FSX.cfg" for later comparison (pretty smart ). *PART I in DX9* -TESTING PREREQUISITES- Testing begins here with the same prerequisites always: default blue A321, EDDM Gate 104, daytime summer, fair weather, FRAPS to show my FPS and Task manager to see CPU loading. A sidenote to CPU cores: I talk in CORE numbers. 4 CORES are referred by me as CORE 1, 2, 3 and 4 (not CORE 0, 1, 2 and 3). -FIRST RESULTS- FPS: In the VC the FPS quite stable between 72...76, outside even greater. CPU: CORE 1 no load, CORE 2 100% (all the time), now and then CORE 3 and 4 get 100% load (for short periods of time). -FINDING 1- Switching from VC to outside and back (Key "S" 1 time -> look around -> Key "F9") leads to: CORE 1 getting 100% load instantly and a framedrop to 30FPS CORE 3 and 4 kicking in after ~5s with 100% load FPS raise again to ~70 CORE 1, 3, 4 revert to almost 0% load -> SIM stable above 73FPS I thought to myself: FSX:SE runs "out of the box" on all 4 physical cores with the main load on core 2 (I have never seen CORE 1 getting 100% of the load before). Time for the first tweak: remove CORE 1 loading with AFFINITYMASK=84 -> FSX should now use only CORES 2, 3 and 4 (NO HT). I did expect a change in Core loading but got the same results again! I will spare you from explaining each other test I made and get to the result: FRAPS was causing the CORE 1 "overload". Closing FRAPS and activating the FPS counter within GeForce Experience did fix CORE 1 beeing loaded and the massive FPS drop. CORE 3 and 4 still kick in after ~5s with 100% load and revert to normal after a short period of time. -AFFINITYMASK TWEAK- Having dealed with the unusual CPU load and the FPS drop it was time to test different AFF MSK values. 1. 252 (CORE 1 and it's HT OFF, all other CORES with theyre HT ON) FSX loads a lot quicker FPS seems improved a bit but negligible CPU load clearly shows that the new setting has an effect. You can see this with the switch from VC to outside and back as usual (I WILL CALL THIS PROCEDURE AS "THE VIEW SWITCH"). FINDING: While FSX loads quicker, performing "the view switch", I observed a higher FPS variation (65..72) and the SIM stuttered a bit. 2. I then played around with AFF MSK 84 (CORE 2,3,4 active / no HT) and even AFF MSK 20 (CORE 2 and 3 active / no HT). FINDING 1: It turned out that more cores with ht enabled will deffinately LOAD FSX quicker but "the view switch" performes worse (FPS variation and stutter). FINDING 2: My personal best setting was AFF MSK 20. While FSX did take longer to load, doing "the view switch" lead to constant high FPS ~77 even though CORE 2 and 3 were 100% loaded (short time after doing "the view switch"). FINDING 3 (probably the most important finding ever): If you set a tweak (here was AFF MSK) and comment it out afterwards in your fsx.cfg, IT WILL STAY THE WAY YOU TWEAKED IT BEFORE! To be clearer: lets say you set "AFFINITYMASK=252" and afterwards comment it out "//AFFINITYMASK=252". Your FSX will NOT return to the default settings but remain in AFF MSK 252 setting. I'm not a programmer but this is how my system performed. There are so many known "tweaks" and I tried all of them and always thought that if a "so called tweak" does not work, I'll comment it out and have my genuine FSX setting back so I could try another tweak. This beeing the case you have a plethora of tweak combinations and might be the reason some of you can't get the system "finetuned" or some tweaks work more or less better on a end-user machine. -BUFFERPOOLS- 1. Having settled for AFFINITYMASK=20 (remember it's a vanilla FSX:SE install so far and I didn't move the ACFT from EDDM Gate 104), I went for the USEPOOLS=0 tweak. This supposedly moves some of the CPU load to the GPU. -FINDING (or behavior in this case)- FPS improved and steady at ~82FPS (79..84FPS) CPU CORE 1 shows a constant load at about 30% with a 10-15% increase after performing "the view switch". This is odd. Why do I use more CPU power (but also get higher FPS) when Usepools=0 should have moved the load to the GPU??? 2. Usepools=1 (no size or rejected treshhold). -FINDING- Same as Usepools=0 but with CORE 1 beeing loaded ~10% more then with Usepools=0 (instead of constant 30% it's now ~40% with 50..55% after performing "the switch"). For consistency check I tried to comment the Usepools=1 out to have CORE 1 without any load. I failed at the beginning and then tried to play again with AFFINITYMASK to try to get FSX to "reset" itself. I think I got it solved switching AFF MSK to 252 - start FSX - reboot PC - set AFF MSK back to 20 (I realy can't recall how it got fixed but it did) and got my wellknown 77FPS back. So again: I think the tweak sequence does make a difference... After this part it seemed that restarting the PC after each FSX.cfg change would be whise (but realy timeconsuming so I didn't do it). I also did not try the combo Usepools=1 with Poolsize and Rejected...since it seemed I will not be able to get more and steadyer FPS above ~77. I even let the FIBER FRAME TIME FRACTION.... out and finaly decided to fly. I took the Sitka Approach mission for further testing. It was perfect with 75+FPS (outside views even >100FPS). So let's load some stuff up :). If you recall my upper uninstall procedure, but inverted. 1. GEX install + configure 2. UTX + UT lights install + configure Flew Sitka with almost the same high FPS (maybe but just maybe 3-4 FPS less). Time for nVidia inspector... My profile is tweaked for performace PC mainly following the AVSIM guide. Sitka: Nice graphics (now that AA and the other good stuff get's applied) with again mostly the same FPS. *PART II the switch to DX10* I recently purchased the FIXER and the cloud shadows. This is also the reason why I started all this since I thought I have lost FPS after applying DX10 + Fixer + clouds. 1. Reverted inspector to default (since it had the DX9 profile loaded). 2. fsx.cfg backup (just a precaution and a quick switch back if possible). 3. DX10 Preview + ACFT casts shadow on itself ticked (all other settings remained maxed out). At EDDM Gate 104 a 10 to 12 gain in FPS (from ~76 to +87) wow. Sitka: same +10FPS but no ACFT lights (Fixer not applied yet) and no (or no noticeable) shadows in the cockpit (you fly towards the sun). 4. Installed DX10 fixer using Steve's profile with HD shadows. I changed nothing (AA listed as 4x). Interesting thing here: if you go to the FSX.CFG from the fixer GUI, it reads out some of the settings from the file (you can apply tweaks from the GUI itself). If you remember further up, I commented the Usepools tweak out and got CORE 1 unloaded. The fixer yet still displayed Usepools=1 entry (blank poolsize and treshhold). Checking fsx.cfg I found no active Usepools entry (mine was commented out and no new one has been created). Maybe a slight bug with the Fixer GUI. Shadows work, lights work but unfortunately I lost the gained FPS and I'm back to ~76 but have shadows now :). 4.1. Installed new DX10 inspector profile with no change in FPS. I can't tell if the graphics looked better since I forgot to take screenshots for comparison (it looked good, trust me). 5. Installed Steves Cloud Shadows. I encountered a problem while updating the libraries, something related to DLL.XML. Since I didn't install any Addons that needed to be triggered with FSX, the file was simply missing. I didn't want to create one by myself and decided to (see point 6). 6. Installed FSUIPC (latest version, unregistered). DLL.XML created, cloud libraries installed. Slight decrease in FPS (now at ~73) at EDDM, almost the same but some variations with Sitka, some increased CPU CORE 3 usage. 7. Aerosoft Mega ARPT Munich + service pack installed (it comes with VISTAMARE which does not work with FSX:SE, also the static ACFT installed). ~36FPS at EDDM Gate104 (~30FPS frame loss). ***************************** Here ends my first testing sequence (~6hours). In my further steps I will install REX Ess w/OD, precipitFX,..so all my visual enhancements, followed by Traffic, GSX, AS16...and follow how the system behaves. I think that at some point I will get my CORE 3 fully loaded and will have to either try BUFFERPOOLS again (CORE 1 load) or AFFINITYMASK=84 to load CORE 4.
  2. Tamer Khayyat

    DX 10 FIXER

    Hello, i would like to know the recommended anti aliasing value to be inserted in DX10 fixer. Is it 2x or 4x or 8xCSAA as in the nvidia inspector profile? i have all FSX settings recommended by FSlabs. thank you.
  3. Matthias Hanel

    Request for a dummy effect

    For the upcoming update it would be great if you could consider to add a dummy effect that is always on. The problem I have under DX10 (using the fixer) is that older sceneries, most importantly the Aerosoft German Airports and Mega Airports sceneries, can have severe lighting issues under DX10 on some systems. For all other planes it is possible to just add another light effect in the [LIGHTS] section of the aircraft.cfg, defined as a navigation light for example; the called effect file would be a so called lightshield effect provided by Steve, which is an invisible light in front of the windshield which in turn brings all the airport lighting back to life. However, due to the custom lighting on the A320X, this is not possible. I experimented changing an engine heat effect in the smoke section to the lightshield, which works standing at the gate, but not in the air it seems. So if you could add a dummy effect that is always active (but empty) no user would have any restrictions, but the users requiring the lightshield fix would have the option to replace the dummy by the lightshield, position it properly and finally can enjoy working PAPIs, runway- and taxi lights on these sceneries again.
  4. As the title says, I am looking for a way to implement the lightshield fix for use with the DX10 fixer. Some older Aerosoft airports won't show taxiway lighting for example if it's not installed.. on other aircraft I could just add it defined as a navigation light, and then position it accordingliy in front of the windshield. However it seems that all lights on the FSL bus are done internally.. does anyone have a solution for this problem? Regards, Matthias
  5. Hi all, I am very happy about the A320! A superb machine. I also like the route uplink which loads your flightplan instantly when IFR flight plan is loaded in MSFSX. I also noticed that I "lose" the navigation lights as soon as I take off (LG no ground contact anymore). Strobes and other white lights stay on, as does the red beacon of course. Is it normal during daytime that NAV lights switch of on the A320 as it takes off?? I should do a flight at nighttime next time. I this bus that smart?? Then I am stunned!! Of course it could also be a bug. But the fact that the nav lights worked on the tarmac eliminates this hypothesis. Enlighten me? I always thought it was commonplace to leave navlights ON, whether night or day? In either case. I do not have the option to turn them on again during flight. Nav lights switch OFF/1/2 give nothing at all. btw: I am doing a flight now from LEBL to EHEH at 6.00 UTC. Regards, Peter
  6. Terblanche

    DX9 versus DX10

    I've tried DX10 previously after the DX10 Fixer was released but switched back to DX9 because of 'bad' performance (i.e. FPS impact). Now I'm back at DX10 because it was well advised by FSLabs for the A320X. Although there is an improvement in VAS usage, it comes at the expense of FPS - on my rig anyway. I've imported the DX10 and Nvidia Inspector settings as prescribed on the forum ... NI = 8xCSAA and 4xSGS while DX10 is on 4x AA and Trilinear & AA is set in FSX A new fsx.cfg was written when I installed the A320 and only [Bufferpool] PS=0, [Jobschedular] AF=14, and Highmemfix were added My rig setup is: Win7x64 i7 4790 3.60 quad + 16GB RAM + GTX750 + HT=OFF Previously with DX9 and fsx.cfg well tweaked with FPS locked at 30 it was possible to maintain a high 20s at most of the airports with PMDG B738 except for EDDFv2, EGLL-Xstreme, and LSZHv2 where it will come down to 18-22 FPS - and obviously none of the sliders inside FSX are full and just about balanced between performance and quality. Strangely I get better FPS in window mode with DX10 while there was a ±10 FPS gain in FULL screen mode in DX9 ... maybe you could share your experience with DX10 and what your settings are to maintain good FPS with the A320X ... after two weeks of DX10 and the constant fight to squeeze the last bite from 32-bit and spending hours to try different combinations between NI, DX10 Fixer and fsx.cfg just to get better performance, Maybe we can all learn something from what your experience and setting are. Attached are my NI settings and fsx.cfg fsx_14Sep2016.CFG
  7. Remy Sarkis

    NAV Lights Not Working

    Hello Guys, The Nav lights are not working they just illuminate the logo and nothing else [ no NAV Lights Illuminated] . anyone facing this problem ?
  8. G1880

    DX10 Problem in FSX

    I've installed the DX10 fixer and loaded the profile from here. I've pretty much followed the manuals and advice for NVI settings and .cfg settings. I've updated to the latest NVidia Driver and I am running a GTX970 3GB. In windowed mode - there is a drop in performance but sharp and fluid graphics. In full screen I am getting 'dragging' of images as seen in the attached video... Has anyone seen this before or can offer a solution ? Thanks IMG_2547.mov
  9. Aidan Hutchison

    DX10 crash on startup

    I went ahead and bought the dx10 fixer by Steve to compliment the wonderful a320x after experiencing low frame rates (as was expected). However, when the dx 10 preview is enabled my fsx crashes on startup. I'm running an fx 8350 @ 4.1ghz and an r9 270x card. I realize that fsx does much better with intel/nvidia (rip me) but i was happy with my system's performance in fsx before the a320x, hence why i invested in the dx10 fixer. Included is my cfg file, a screenshot, and the dx10 scenery fixer profile provided by Matt Davies that i tried to use. I cant remember how to find the offending file in the crash, otherwise I would have included that too. Thanks everyone, and the fslabs team for an amazing feat of software engineering! fsx.cfg dx10 scenery fixer.dfp
  10. Konstantin Didushok

    Video about VAS Consumption in FSX:SE and P3D

    Hello Concorde-Fans, To those of you who want to see how the VAS behaves in FSX:SE and Prepar3D in combination with Concorde-X, I have a video for you. In it, I have measured the VAS consumption in identical flight situations under comparable settings in FSX:SE and P3D v3.2. To make things more interesting, I have actually run the test in three modes - FSX:SE DX9, DX10 and Prepar3D v3.2 (since it is known that DX10 can provide a sizeable VAS relief over DX9). In the tests, I flew Concorde-X from KIAD to KJFK, similarly to what I did in the tests that I conducted over a year ago (which is still archived somewhere in this forum). Back then, I ran the test on FSX only using the old Concorde version 1.2. This time I, used the new, optimized Concorde version (1.32), and the test comes in a video form where I added Prepar3D v3.2 to the "race". So, if you are interested in knowing how much VAS is consumed by different sims when flying Concorde-X, I'm sure you will find this video useful.
  • Create New...