489: B58 Baron Gauge Updated

Following the A36 Bonanza update, links for the Default B58 Baron Gauges update have been sent to all users earlier today.  Similarly, there are bug fixes, feature enhancements and code optimizations.   Should any user not receiving the update, feel free to contact me by email or via Comment of this post.

Updates for the Carenado B58 will be ready in the next few days.

Advertisements

488: A36 Bonanza Gauge Updated

Have been working hard on the updates for many of my earlier Gauges these few weeks.   The first one ready is the A36 Bonanza instrument, in which there are bug fixes, feature enhancements and code optimizations.

Download Links are being sent to all existing users by emails.   Should any one not receiving it by tomorrow, feel free to contact me.

Updates for the default B58, followed by the Carenado B58, will come next.

487: Gauge File Updating for SPAD.neXt


When my FIP gauges are having major updates, say from version R3 to R4, they will be installed onto a new folder ending with the new version in their names, e.g. A36_Bonanza_R4.   This is to prevent mixing the new files with the old files, and to avoid the possibility of overwriting user-customized files, just in case.

For those who are running the Saitek/Logitech Drivers, the gauge installer will create corresponding links for the update automatically.

But for those who are using SPAD.neXt, they will have to reinstall the gauges to the SPAD.neXt system again as the folder location has changed.   This is quite troublesome especially when one has configured the buttons and knobs on the FIP extensively.

Following is what I do and it is relatively simple and efficient. Continue reading

486: SL Migrator Lite Version

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.

 

485: SL Migrator v1.1 Update

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

484: FIP Customizer Logitech Version

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.

 

 

483: SL Migrator & FIP Driver Toggler

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

482: Logitech FIP Driver Migration

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 8.0.132.0. is fine, which I am currently using.

Followings are the steps I took for the migration: Continue reading