MartinP

I guess we were typing at about the same time! In respect of going back could I suggest that you leave FG in as in latest test version. As long as it isn't focused it works perfectly. People using FG accepting that you cannot really use the UI on the fly..

Just carried out a test and can confirm that frame generation ceases when any application is running and is selected to take the focus away from MSFS A selected focused Dynamic LOD window is actually recognising the reduction in frame rates as frame generation ceases and the latest test app doubles that rate. My version is MS Store. Hope this helps.

To clarify on my setup if I have msfs running in window on say half the screen and run Dynamic LOD on the half of the screen. If I set the window focus to MSFS your latest version displays the correct fps (new version doubles the ffps). Now switch the focus from MSFS to Dynamic LOD window, the display for fps doubles. The situation is the same if MSFS occupies the whole screen, bringing the app orward and visible results in the doubling. For further inormation I am using the AMD mod for frame generation.

Installed latest test version - confirm PCMode & FG active plus Compatible MSFS version detected (in green). When the app window is activated to be visible on the desktop the fps displayed doubles from that on the non visible window.

Also confirm with 0.37 test - PC Mode and FG active MSFS 1.36.20 However what I have noted is that fps in both 0.36 and 0.37 when app is focused on screen are showing correct fps with frame generation - but when not focused off screen are indicating half the fps. Don't know if this is an issue? Just to say extremely impressed with the way this app works and my thanks to Reset XPDR for all the work he has done.

Rod Thank you, very much. I have started the process, hopefully back flying in a couple of days. Martin

I have just updated (clean install) to Window 10, downloading FSX SE as I type. My question is this: Should I completely setup FSX, install scenery and aircraft etc, then apply Steve's DX10 fix. Or should I apply the fix on completing the download of fsx and then install the scenery etc. Thanks for any advice. Martin

Simply a typo, yes manufacturer was OCZ. It doesn't appear that anyone has a solution so I will go to plan B. I will use a PCI e x 16 extension cable from its current location and relocate the SSD card. Might also, with another cable, have to slightly re-locate the new graphics card. Not a perfect solution but should work. Martin

I would like to upgrade my GPU from a GTX580 to 780 Ti. On checking I have found that the width of the card is greater than the current one and the only wat to fit a 780 is to move a SSD card to a different slot. The problem is that having moved it, Windows no longer recognises it and the drive is gone. Moving it back the drive is also back. My motherboard is Asus Maximus iv extreme, there are two OCD RevoDrive3 SSD's 240GB. One has the O/S W7 Home Premium - the other FSX. Both drives currently are in PCIe 2.0 x 16 slots. In order to make room for a new GPU, the one and only remaining slot is a PCIe 2.0 x 8 slot. According to OCZ the SSD remains compatible at x 8. All the PCI switches on the motherboard are on. However as stated above the drive disapears following relocation to the x 8 slot. The drive does not appear when opening Disk management. Can anyone help, please. Martin

Michael That's no problem as the FFTF does not automatically appear in the fsx cfg. The default fsx value is 0.33. The tweak to improve frame rates is to set a lower number. However depending upon the system and scenery too low s fraction produces blurries. On the subject of scenery I notice in your profile that you have your home made scenery - these could potentially not be compatible with Fiber Accelerator - hence maybe the decrease in fps when you have tried the product? Martin

Initially I agreed with those posters that found Fiber accelerator to be of little or no use. I too came close to removing it from my system. However thinking about it I wondered if there was a clue in FIBER as part of the name. A tweak than many use is Fiber_Frame_Time _Fraction=*.* Could setting this aggressively to improve fps prevent FA from operating correctly? So I removed the entry from the fsx.cfg, fired up FSX and FA and following the instruction manual FA performed on my system as the developers claimed. And textures were sharper than ever before. I have set 30fps in fsx, 24fps lower rate in FA with 30fps as the middle rate. The AGL is set at 10,000 ft and 40000 ft. The latter figure to ensure that FA is always operating. Important for me as Active Sky Next often throws storms at altitude or overcasts and FA does the job of keeping up the frame rates. Could I suggest that those people who cannot get it to work and have the FFT Fraction tweak in their cfg - try it without. You never know it may work for you too. Martin

Please make sure that you unzipped the WHOLE package into its own folder and not simply the nvidiainspector.exe file. Martin

JohnI suspect that there in actual fact nothing wrong with your FSX or simconnect setup. What OS are you using? I found exactly what you found when FSRealwx tried to set the wx using simconnect on a W7 64 networked PC. However when I set it up using a networked XP PC then it works and sets the wx well.If your setup is W7 and you have access to a XP system then try setting it up with that.A lot of other people are having problems with simconnect and FSRealwx. I hope a solution is found soon as it is a great prog!Martin

The comments above relating to restoring the default fsx haze are interesting. The suggestion is that the original cirrus overcast 3 file should be pasted back into fsx texture folder. However I have installed the beta update. One of the issues was with the said cirrus overcast file. On checking I find that the original file is still in my folder! No matter how many changes you made to the graphics this file stubbonly remained.To see if this was related to the beta update, I performed a comple reinstall of AS2012, back to the original. Now I was back to a replacement cirrus overcast 3 file and no matter how many changes and flightplans made, no sight of the original.However after reinstalling the 'beta', following a flightplan graphics change, back to the original default. Again no matter how many changes to graphics the file remains as earlier found, unchangeable.My question is, has this happened to everyone who uses the 'beta'? If so is this reversion of the cirrus overcast 3 file intentional? And does it on its own re-instate the fsx haze layer?For information I'm using standard mode.Martin