PMSounds

[Sil3ntLoneWolf3]

Hello all, any input or assistance would be lovely!

So, first off, i'm running FS9 on a toshiba laptop, Windows Vista 32bit, latest version of FSUIPC and PMsounds.

Now, beforehand, when i was using FSX (switched due to performance issues), PMsounds worked perfectly, a few sounds didn't play (airbus callouts, minimums, etc..) but it worked nonetheless. Now that i use FS9, PMsounds no longer works at all. When i start it up, then FS9, it says "ReadData Fails". I've uninstalled it and reinstalled it, but not FSUIPC. So, anybody know what's going on here? Any suggestions? Am i perhaps needing another file to use it? This is all being run on one PC. Many thanks in advance!

[Pete Dowson]

So, first off, i'm running FS9 on a toshiba laptop, Windows Vista 32bit, latest version of FSUIPC and PMsounds.

"latest version" is meaningless I'm afraid. I need to know actual version numbers.

Now, beforehand, when i was using FSX (switched due to performance issues), PMsounds worked perfectly, a few sounds didn't play (airbus callouts, minimums, etc..) but it worked nonetheless. Now that i use FS9, PMsounds no longer works at all. When i start it up, then FS9, it says "ReadData Fails". I've uninstalled it and reinstalled it, but not FSUIPC. So, anybody know what's going on here? Any suggestions? Am i perhaps needing another file to use it?

pmSounds uses a parameter file to define the sounds. If you are using the exact same folder containing pmSounds that you were using with FSX, there's no difference whatsoever.

Tell me the version number of FSUIPC. Show me the FSUIPC.LOG file (from the FS Modules folder).

Pete

[Sil3ntLoneWolf3]

I had to reset my laptop to factory settings a while ago so there's no FSX installation on here whatsoever. The version i have is the current 3.98. Both FSUIPC and PMSounds were installed for FS9 on this computer, as i said before all trace of FSX was erased when i did the factory reset. As for the FSUIPC.LOG, i don't seem to be finding any file with that exact name in my modules folder, there is however a readable text file which i think might be what you're asking for, but it's like a mile long worth of text...

[Pete Dowson]

I had to reset my laptop to factory settings a while ago so there's no FSX installation on here whatsoever.

It wasn't the FSX installation I was asking about, only pmSounds.

The version i have is the current 3.98. Both FSUIPC and PMSounds were installed for FS9 on this computer, as i said before all trace of FSX was erased when i did the factory reset. As for the FSUIPC.LOG, i don't seem to be finding any file with that exact name in my modules folder, there is however a readable text file which i think might be what you're asking for, but it's like a mile long worth of text...

It sounds like you have Windows set to hide filetypes from you. Best to switch that option off -- it disguises the names of all sorts of files.

Anyway, if it is a Text file called FSUIPC it will likely be the Log. It should not be very many lines long unless you have enabled lots of logging options, or something is drastically wrong. In FS9 go into the FSUIPC options and uncheck any logging you've enabled, then close FS9, restart it, close it again. then show me what should now be a short log!

Regards

Pete

[Sil3ntLoneWolf3]

Ok sorry i was looking at a different file there, with a similar name, here's the log for FSUIPC:

Installer for FSUIPC.DLL version 3.98a

Looking in registry for FS9.1 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1

Parameter"EXE Path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1

Parameter"EXE Path"

... NOT found! ...

Looking in registry for FS9 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0

Parameter"EXE Path"

... >>> OK! FOUND FS9! <<< ...

Looking in registry for FS8 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\8.0

Parameter"EXE Path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\8.0

Parameter"EXE Path"

... NOT found! ...

Looking in registry for FS7 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\7.0

Parameter"path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\7.0

Parameter"path"

... NOT found! ...

Looking in registry for FS6.1 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\6.1

Parameter"InstallDir"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\6.1

Parameter"InstallDir"

... NOT found! ...

Looking in registry for CFS2 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\2.0

Parameter"EXE Path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\2.0

Parameter"EXE Path"

... NOT found! ...

Looking in registry for CFS1 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\1.0

Parameter"EXE Path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\1.0

Parameter"EXE Path"

... NOT found! ...

===========================================================

INSTALLATION FOR FS9:

EXE Path="C:\Program Files\Microsoft Games\Flight Simulator 9"

Checking if there's already a version of FSUIPC installed in:

C:\Program Files\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL

... No previous valid version found.

Okay -- installed FSUIPC into "C:\Program Files\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL"

"Modules\FSUIPC Documents" folder created okay!

Now installing additional files into the "Modules\FSUIPC Documents" folder:

Installed "FSUIPC User Guide.pdf" okay

Installed "FSUIPC for Advanced Users.pdf" okay

Installed "FSUIPC History.pdf" okay

Installed "List of FS2004 controls.pdf" okay

Installed "GlobalSign Root.exe" okay

Installed "FSUIPC Lua Library.pdf" okay

Installed "FSUIPC Lua Plug-Ins.pdf" okay

Installed "Lua License.pdf" okay

Installed "Lua Plugins for VRInsight Devices.pdf" okay

Installed "Example LUA plugins.zip" okay

Installed "SIMSAMURAI+FSUIPC+TUTORIAL.pdf" okay

FSUIPC.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix programno longer relevant

===========================================================

All installer tasks completed okay!

Registration offers were declined

*************** End of Install Log ***************

[JSkorna]

Hi,

That is the install log. There is another long produced when FS is run with FSUIPC.

FS and all FS add-ons should be installed outside of the Program Files folder.

[Sil3ntLoneWolf3]

Oh...well where in the heck would I find that little file?

[Pete Dowson]

Oh...well where in the heck would I find that little file?

The FSUIPC.LOG file is in the same folder as the Installer log file, which you already found. In other words, in

C:\Program Files\Microsoft Games\Flight Simulator 9\Modules

If there is no such file, then FS has never been run with FSUIPC.

Additionally, I notice that, according to the Installer log:

Looking in registry for FS9 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0

Parameter"EXE Path"

... >>> OK! FOUND FS9! <<< ...

you are running the original version of FS2004 (i.e. FS9.0), not the fixed updated version 9.1. I would advise you to apply the update as it fixes a lot of FS9 problems.

Regards

Pete

[Sil3ntLoneWolf3]

Oh i had no idea there was an update. And i may have not run FS9 with FSUIPC? How would that be possible...i can see it in the toolbar at the top of my FS window, says FSUIPC. Unless i did something wrong...

[Pete Dowson]

And i may have not run FS9 with FSUIPC? How would that be possible...i can see it in the toolbar at the top of my FS window, says FSUIPC.

If the FSUIPC menu entry is present, then there absolutely MUST be an FSUIPC log file! I suggest you look again. If FSUIPC is running it ALWAYS creates a log file!

Pete