In response to some friends requests, a simplified version of the SL_Migrator is created to help other non-FSX Times Gauges users to convert their “exe.xml” files after the Logitech Drivers migration. Similarly, it is good for FSX, FSX-SE, P3Dv3 and P3Dv4 and can handle more than one simulators simultaneously if exists.
The utility is called SL_Migrator_Lite and it can be downloaded from the Freeware section in my Store.
The SL_Migrator has just been updated to version 1.1, which helps further speeding up and simplying the Saitek-to-Logitech migration.
Besides the FIP Gauges copying process, the new utility can now automatically modify ALL the “exe.xml” files found in the computer’s simulator cfg folders for the necessary Logitech conversion, including FSX, FSX-SE, P3Dv3 and P3Dv4.
In other words, Continue reading
Alexey has added a new version of his FIP Customizer for the Logitech FIP drivers. To refresh what the utility does, read my Post 264 here.
Note that this new version is good for the Logitech FIP drivers only. Anyone interested could click on the image to download it.
Link for the FIP Customizer for the Saitek FIP version is still valid in Post 264.
In the last Post about migration from Saitek to Logitech FIP drivers, I put a divider right after Step 9 in the article. It is because the succeeding process mainly is the copying of previous FIP gauges to the new locations.
Here’s the new utility SL_Migrator (Saitek-to-Logitech Migrator) I just wrote to help do the job efficiently. Especially, it will copy and convert the original SaiFlightSimX.xml and SaiFlightFip.xml to the appropriate Logitech version if they are found, so that users can quickly restore the gauges they were running before the migration. Continue reading
Some friends email me saying that they are interested to know how I upgraded (“migrate” I think is more accurate) my Saitek drivers to the Logitech version. Again, as mentioned a few times, such a migration is not necessary if the Saitek drivers are working fine.
Anyway, it does no harm if anyone want to keep up with the Logitech version. But ensure to AVOID using version 0.8.144.0 as it has error. Version 184.108.40.206. is fine, which I am currently using.
Followings are the steps I took for the migration: Continue reading
Last month, I bought a GoFlight GF-TPM because the Saitek TPM I’ve been using for years is too big for the new cockpit I am building.
Frankly, the GoFlight TPM wasn’t my preferred choice in the beginning due to its relatively high price ($169) and lack of extra features compared to the Saitek one.
However, there aren’t much choice on the market. And most importantly, its size does fit nicely to my layout requirements. So I ordered one.
The following is a review after using it for a few weeks. Continue reading
A friend, Christian, recently told me that he was confused by the movement of the attitude indicator arc and triangle above it on the Generic G5 PFD. He asked if it is possible to modify the attitude indicator like the real Garmin G5 does as shown in the image on the right below, so that the arc and the triangle above it move with the horizon and have the lower triangle stay in relation to the plane.
I fully understand his frustration as I sometimes got confused as well.
Actually when I developed the instrument, I did aim to implement the attitude indicator as the Garmin G5 does. However, Continue reading
FSX Times in January was a bit quiet after the Christmas and New Year holidays because there were many things happening to my flightsim system. For one, I have “upgraded” the FIP driver from Saitek to Logitech version.
Truly, back in last August, I mentioned in my Post 447 that the “new” Logitech drivers are in general the same as the “old” Saitek drivers. “Upgrade” is not necessary and it is still valid.
However, as my new X-Plane gauges were developed under the Logitech plugins; and the number of my FIP gauge users running the Logitech version are steadily growing, the switch, to me based on my own situation, is inevitable.
This also means that all my existing installers and utilities have to be upgraded accordingly — so that they will not only fit for the previous Saitek and SPAD.neXt installation, but also good for the new Logitech setup.
I am glad that all works are completed after weeks of intensive programming.
It’s time to move on.