Jump to content
The simFlight Network Forums

New Build


Recommended Posts

I am building a new machine and am hoping I can transfer my FSUIPC settings over to a new load of FSX.

If the older one was FSX too, then just save and copy the FSUIPC4.INI file from the Modules folder, plus of course any Lua and MCRO files you may have made or installed. Your registration is contained in the FSUIPC4.KEY file so don't lose that either. You'll need to run the Installer on the new PC, but do this after your first successful run of FSX, to ensure all of its files are properly readable.

Regards

Pete

Link to comment
Share on other sites

Thank You for the answer I hoped for.

Note that unless you used the Joystick Lettering facilities in your FSUIPC assignments, the numbering of the joystick devices on your new PC might not be the same as they were before, so there may be some editing of the INI file to do. If you've not yet taken down your old system, and are not yet using joystick lettering, it might be wise to do the lettering change first, on the old FSX system. Then there's no mess to fix.

Regards

Pete

Link to comment
Share on other sites

Note that unless you used the Joystick Lettering facilities in your FSUIPC assignments, the numbering of the joystick devices on your new PC might not be the same as they were before, so there may be some editing of the INI file to do. If you've not yet taken down your old system, and are not yet using joystick lettering, it might be wise to do the lettering change first, on the old FSX system. Then there's no mess to fix.

Regards

Pete

Great catch! I did look at lettering but not sure if I followed thru. I will have a look and implement lettering if not already.

Link to comment
Share on other sites

  • 2 weeks later...

I have built my new machine and moved the fsuipc.ini file from the existing machine to preserve my hardware configurations, keystroke mapping, etc.

According the the ASE installtion guide concerning simconnect, I am to reinstall FSUIPC after installing the simconnet ini and xml files.

If I reinstall FSUIPC according the the ASE document on the top of page 54, will I preserve the current fsuipc.ini file?

Thanks,

Link to comment
Share on other sites

According the the ASE installtion guide concerning simconnect, I am to reinstall FSUIPC after installing the simconnet ini and xml files.

Don't know why, as FSUIPC is not dependent on either of those two files, only the DLL.XML file. And ASE doesn't use FSUIPC4. But it doesn't matter re-running the Installer, it won't do any harm.

If I reinstall FSUIPC according the the ASE document on the top of page 54, will I preserve the current fsuipc.ini file?

The installer doesn't touch the INI file, and in fact it won't even replace the FSUIPC4.DLL unless the one you have installed already is older. you always need to run the Installer for major updates in any case, else you don't get up to date documentation. It wouldn't be nice of it to destroy your configuration now, would it? :-)

Regards

Pete

Link to comment
Share on other sites

Answer from an ASE developer.

It's been a long time but from my memory, FSUIPC configures these files on installation based on the existing configuration. Depending on the way you configure SimConnect, FSUIPC and other add-ons including ASE may fail to operate. Installing FSUIPC again would solve such issues and thus recommended to avoid connectivity problems.

It's entirely possible to set things up without re-installing FSUIPC, you just need to correctly configure the server xml file. As a suggestion, you could back up your FSUIPC files to replace after re-installing if it becomes necessary.

Link to comment
Share on other sites

It's been a long time but from my memory, FSUIPC configures these files on installation based on the existing configuration.

Not "these files", only the DLL.XML, the file responsible for telling SimConnect which DLLs to load. Does ASE use DLLs loaded into FSX? I didn't think so. I have none.

It's entirely possible to set things up without re-installing FSUIPC, you just need to correctly configure the server xml file. As a suggestion, you could back up your FSUIPC files to replace after re-installing if it becomes necessary.

FSUIPC isn't dependent upon the Simconnect.XML file and doesn't touch it. Since FSX SP1, or maybe SP2, even if local Simconnect support is omitted from that XML file FSX still supplies both TCP/IP and PIPE interfaces. It is possible to deliberately stop those by adding stuff to the XML to do so, but no installers I know would do such a daft thing.

Regards

Pete

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.