patrice_bambou

After installing W10, I checked on the MB manufacturer web site, for the latest drivers related to the MB and W10 and installed them (SATA, USB, ME, even the BIOS etc.), but this is not mandatory. For example, If you install a NVME SSD from Samsung, it is better to install the Samsung drivers, as W10 will install some drivers (that run OK), but not the optimal ones.

Hi, I personally made the transition from W7 to W10 in January 2018 and I am very happy. W10 rocks and I made it look like W7 using some customization tools from StarDock. I made a new fresh install and reinstalled all my programs afterwards (Finally it is not so difficult, just to make this carefully and provided you have all your software install files with keys ready to be installed). Doing that, I installed a NVME SSD for the system and it was very simple with W10. So, I suggest making a fresh install instead of an update. You will have all things properly installed with no problems and all programs will also be in a very good state. And if you are not sure, you can make a backup of your existing W7 system (using free Macrium Reflect backup software for instance) Regarding drivers, W10 installation normally makes all things automatically, but if you want the latest drivers, you can make updates after that (specially the display driver) About performance, I did not see any difference with w7. Patrice.

So, FSL put some files inside Windows directory. And what? Is it forbidden? I don't think so. Does my system crash? no. Does P3D crash? no. Do they spy me? no. A storm in a glass of water. I surely will buy the A319 when it comes on the market. FSL rocks. Patrice.

Don't use high priority, it will stuck your system (all system services behavior will be problematic) . Let P3D at normal priority and even low priority, and things will go better, far better. Patrice.

Disable hyper threading. It is useless with this number of cores and you can go higher in overclocking with moderate temps. And also, don't think that more threads means better performance in such a case. Affinity mask may be useful to reserve one core for the system and services.

Hi Filou, Nice shot, as usual. For your next shots, could you indicate where the shot was taken? Patrice.

Hi Holdit, You say :(Update: Forgot to add a link: http://www.fsd-international.com/Hangar/GLV2000/ ) Does this tool (GLV2000) work on P3D V4? They say P3D, but V4? Yes or No? Patrice.

Ok, thanks for your answers. I asked this because today I had a FTXCentral crash on startup and could not make it working preperly. So, I deleted the above folder and recreated it via a reinstallation of FTXCentral and all is returned back to normal. Patrice.

The topic is in the title: FTX Central V3 does not appear in Windows programs, so, how to uninstall it? Thanks. Patrice.

Where do you check the file version (what is the file name?)? I have installed ORBX on P3DV4 and not on P3DV3. I do not see any update via FTX Central.

To disable Orbx Trees simply uninstall them from FTX Central.

Yes, North owners should get a discount buying South...

Problem solved: bad folder for P3DV3 in ChasePlane

Hi, This morning I wanted to make a flight with P3DV3. Being on the runway, no view control works with my joystick (ThrustMaster T-flight Hotas X). It appears that ChasePlane is not connected to the simulator (Red color in ChasePlane). I have the ChasePlane activation in my exe.xml file, as below: <Launch.Addon> <Name>ChasePlane</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\OldProp Solutions Inc\ChasePlane\ChasePlane.exe</Path> <CommandLine>P3Dv3</CommandLine> </Launch.Addon> I tried normal or experimental releases of ChasePlane : same behavior: Panning is not working and all my views buttons also. I have no problem with P3D V4 ChasePlane version: 0.3.144 beta exp. If someone can help me on this... Thanks. Patrice.

Hi Maarten, I made some complementary tests. So, the problem occurs when we exit SLX when a Mapbox map is displayed. When displaying a non Mapbox map (terrain for instance), it does not occur. I tried with the version 2 step ago (SimLauncherX_5.9.6445.2969) and same problem. Regards. Patrice.