Problems wirh FSUIPC ini-file

[quixote]

I have just reinstalled my FSX including FSUIPC. But I think something has gone wrong. FSUIPC do nor create an ini-file - and my backup ini-file (with all my yoke setups) does nog affect FSUIPC - nothing happens accodring to this ini-file. Furthermore I have huge problems getting my FS Commander to Work - it will not connect to FSX, and I suspect FSUIPC to be the 'sinner'.

 

Here is what files I have in the module-folder - also after trying to confugure som control-buttons:

 

FSUIPC4 for Advanced Users

FSUIPC4 History

FSUIPC4 User Guide

FSUIPC4.DLL

List of FSX controls

 

Mogens Gaardbo

Denmark

[Pete Dowson]

I have just reinstalled my FSX including FSUIPC. But I think something has gone wrong. FSUIPC do nor create an ini-file - and my backup ini-file (with all my yoke setups) does nog affect FSUIPC - nothing happens accodring to this ini-file. Furthermore I have huge problems getting my FS Commander to Work - it will not connect to FSX, and I suspect FSUIPC to be the 'sinner'.

 

If there is no INI file produced and also no LOG file then FSUIPC has not even run, so it cannot possibly "sin".

 

It looks exactly like you have not actually installed it at all (!), because if you had there would be an Install log and a subfolder called FSUIPC Documents with all the documentation and other add-ons (Lua mainly). Also, the documents you are listing are never installed in the Modules folder, only in the subfolder., so I'd guess that you cobbled the contents of that folder together yourself?

 

Just delete those files and run the latest Installer for FSUIPC4. See the Download Links subforum..

 

Pete

[quixote]

OK - but why did the installer work and told me, that the program was installed? - why did the program appear in the addon-meny' - and why was I able to configure buttons via FSUPPC (and they were still configured later in trhe same game - just not after a re-open of FSX)? How is that possible, when I obviously did not install the program at all?

[Andydigital]

Possibly because you have UAC switched on still and you also have FSX installed in the default location i.e. program files (x86) If that was the case then all file changes are thrown out at the end of your session and are not saved.

[Pete Dowson]

OK - but why did the installer work and told me, that the program was installed? - why did the program appear in the addon-meny' - and why was I able to configure buttons via FSUPPC (and they were still configured later in trhe same game - just not after a re-open of FSX)? How is that possible, when I obviously did not install the program at all?

 

If it appears in the Add-ons menu and you can use it, then there MUST be an INI file and a LOG file and an INstall log, and the problem is that you are simply looking in the wrong place!

 

It may be related to UAC and a default install location, as Andy suggests, but I don't think the files are "thrown out". The way Windows tries to "protect" you is by only showing you the originally installed version of the Folder, not the one actually in use -- and changes there don't affect the real copies. Try running Windows Explorer "as administrator" (a right-click option) to see if it shows you the correct folder then.

 

When the Installer runs it creates the Modules folder with full user access, so you should always be able to see it no matter what privileges you use. However, it is just possible that, if you did not run the Installer itself "as administrator", as instructed in the provided installation instructions, the folder still doesn't have full user rights.

 

If you have allowed FSX to install in the default Program Files folder then you will probably have problems with lots of add-on programs which need to access those folders. There are two ways around that. Either run FSX, and all add-on programs for it, "as administrator", or turn Windows UAC off.

 

Pete

[quixote]

Thanks for the answers. Yes - UAC was on, but the FSX is not in the default location, but on another HD. Now I reinstalled FSX (for the 3. time) and will try again without UAC and as 'administrator'.

[quixote]

Now UAC is not active - and I have reinstalled FSX on my D:\ drive, updated with SP1 and SP2. Then run the latest FSUIPC setup as administrator. STILL the same files as described in my first question - no log-file and no ini-file. After setup, I gat the message, that FSUIPC was correctly installed.

[quixote]

Now I got the FS Commander to connect with FSX, but f.i. the autoheading dosent Work. I can see the plane on FSC. And still no ini-file and no log-file.

[Pete Dowson]

Now I got the FS Commander to connect with FSX, but f.i. the autoheading dosent Work. I can see the plane on FSC. And still no ini-file and no log-file.

 

I've no idea what "autoheading" is, sorry.

 

There is really no way FSUIPC can ever run without producing both a Log and an INI file and no one has ever failed to find these before, not ever, in the 14 years of FSUIPC. I really have no idea where you are looking, but it really does have to be the wrong place. I think you need to do a search. Search for the Install log as well. The filenames to look for are:

 

FSUIPC4.log

FSUIPC4.ini

FSUIPC4 Install.log

 

An alternative is to re-run the Installer, and save the Install log via its menu entry before clicking the OK button when it confirms it has installed okay. The menu is in the log display, which will be behind the confirmation prompt. Click "Save As" and select a place and filename to save it where you can recoup it. Youwill need to move the log display afterwards in order to press 'OK'.

 

Then show me that log.

 

Regards

Pete

[Andydigital]

Maybe this is just something so simple as "hide extensions for known file types" being enabled so the user is not seeing the full names? I note that no extensions are listed in the opening post in this thread. Simply go into "Folder Options" by typing that into the windows start button search box and click on the link called Folder Options, then remove the tick from the box labelled "hide extensions for known file types". Now you should find the files in question.

[quixote]

YES - after another clean install of FSX, it works. The problem seem to be the DirectX (too high version for FSX) causing bad install of FSX. Found a solution for this at Microsoft, and now FSUIPC has installed with all the correct files and maps in FSX modules.

 

Thankyou for your patience. The technical side of computer-programs is not my core competention.

[Pete Dowson]

YES - after another clean install of FSX, it works. The problem seem to be the DirectX (too high version for FSX) causing bad install of FSX. Found a solution for this at Microsoft, and now FSUIPC has installed with all the correct files and maps in FSX modules.

 

Thankyou for your patience. The technical side of computer-programs is not my core competention.

 

Hmm. I too wouldn't understand why the version of DirectX causes such problems (each version is supposed to support all previous versions). But I'm glad you got it resolved in the end. Thanks for letting us know.

 

Regards

Pete

[quixote]

Yes, each version of DirectX should support previous versions - but FSX obviously don't like it :-) I got the error 'incompatible DirectX' and searched for that on the web. Found that Microsoft suggested to install 'DirectX 9.0c End-User Runtime' which updated the current DirectX version for high-end multimedia and games. The core version is - according to dxdiag - still version 11. Strange World :-)