FSUIPC FS9 not responsing

[jorane]

Can anyone help me with this “FS9 not responding problem“.

My computer is a Dell Studio 1555 laptop running Window 7. I am running FSX with standalone vasFMC 2.09 and FSUIPC4 and do not see any problems. With the right settings a reasonable performance is obtained.

I was interested in the 2004 gauge version of vasFMC and because this only runs under previous versions of FS decided to reload my old version of FS9, A320 aircraft, FMC gauge and FSUIPC.

At first all was OK and I was getting quite expert at programming the vasFMC and using the advanced functions with an A320 aircraft. However I ran into the FS9 not responding condition described below.

The problem occurs when a new flight is being loaded . The load commences but when the loading scenery objects box stage appears FS9 freezes and the task manager indicates FS9 is not responding.

I have since de/re installed FS9 twice ( under C: Flight simulator 9 as suggested in the FSUIPC manual) with the corresponding A320 gauge version aircraft and FSUIPC and ensuring the FSUIPC ddl was positioned first in the modules list. On the first new flight all is ok however after this first new flight all following new flights the old problem of FS9 not responding reappears. So it seems to be a one shot problem which locks and cannot be reset.

If the FSUIPC.dll is deleted the new flight does loadsuccesfully with no freeze up but obviously the no connection on the gaugewaring is present, so one must deduce it is something to do with FSUIPC and interaction with FS9.

I have no Dr Watson on my compter.

Any suggestions would be appreciated

[Pete Dowson]

The problem occurs when a new flight is being loaded . The load commences but when the loading scenery objects box stage appears FS9 freezes and the task manager indicates FS9 is not responding.

I'd need more information: especially the version number of FSUIPC, and a sight of the FSUIPC log file from the Modules folder.

There is nothing FSUIPC is doing whilst FS9 is loading scenery. In fact it is not even able to get any time to run as FS keeps it all. What percentage does the progress bar get to? Does it say scenery, autogen, textures, traffic or what? Maybe it's actually got to 100% and would therefore be on the point of starting?

If the FSUIPC.dll is deleted the new flight does loadsuccesfully with no freeze up but obviously the no connection on the gaugewaring is present, so one must deduce it is something to do with FSUIPC and interaction with FS9.

The only interaction it might perform would be responding to requests from applications using it. Maybe one of those is instigating something which clashes with whatever is being loaded? Can you do a process of elimination, removing each possible FSUIPC client program or add-in? What additional DLLs apart from FSUIPC have you got installed in the Modules folder? Does it still hang without this "vasFMC" running? What is this "gaugewaring" thing you mention, and can you remove that to check?

I have no Dr Watson on my compter.

Dr. Watson? Does that still exist?

BTW if you are not using at least version 3.98 I don't want to know. Even if you are you might want to first try version 3.989w, from the Download Links subforum here. Then at least you'll be using the same version as me.

Regards

Pete

[jorane]

1) & 2) I am using FSUIPC version 3.9.8 and the log is shown below. I should have said when a flight is created the progress bar does not start progressing at all and stays on 0% and indicating “loading scenery objects”message . The only way to get out of this situation is to ctrl/alt/del and start the task manager to get out of the freeze condition.

3) When the FSUIPC dll is removed the aircraft loads normally with the Upper ECAM gauge showing a “NO FLTSIM CONNECT” message. Sorry about the “guagewaring” I meant the ECAM gauge.

I left the FSUIPC in the modules folder and de installed the vasFMC guage. Thisaction removes a vasfmc macro file from the Modules folder. Created new flight with the project airbus aircraft selected and the progress bar achieved 100% but the aircraft has a blank instrument panel. So I assume this macro file seems to load the gauges.

4) I only referred to Dr Watson as this is mentioned in your user manual regarding a tool for detecting problems.

5) Tried version 3,989with all the same checks but no change and FS still freezes.

I checked the files under the modules folder for viruses but none detected.

Install log details follow

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 (x86)\Microsoft Games\Flight Simulator 9"

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

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

... Version 3.980 found.

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

"Modules\FSUIPC Documents" folder already exists.

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 program ... no longer relevant

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

All installer tasks completed okay!

Registration for FSUIPC was cancelled or failed! (result code 40)

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

I also de/reinstalled FS9 in the c/program files (x86)/microsoft games/fs9 without success and no change to the tests carried out

I am well and truly stumped on this one

John

[Pete Dowson]

1) & 2) I am using FSUIPC version 3.9.8 and the log is shown below. I should have said when a flight is created the progress bar does not start progressing at all and stays on 0% and indicating “loading scenery objects”message . The only way to get out of this situation is to ctrl/alt/del and start the task manager to get out of the freeze condition.

3) When the FSUIPC dll is removed the aircraft loads normally with the Upper ECAM gauge showing a “NO FLTSIM CONNECT” message. Sorry about the “guagewaring” I meant the ECAM gauge.

Right. In that case it sounds like something that gauge is doing. Is that gauge running at the time you try to load another flight? If so I am guessing that the gauge is stuck in a loop and not allowing the new flight to be loaded.

I left the FSUIPC in the modules folder and de installed the vasFMC guage. Thisaction removes a vasfmc macro file from the Modules folder. Created new flight with the project airbus aircraft selected and the progress bar achieved 100% but the aircraft has a blank instrument panel. So I assume this macro file seems to load the gauges.

Is this "vasFMC gauge" the same one you mention above as the "upper ECAM gauge"? If so then this confirms that there is a problem with that gauge.

Install log details follow

The install log doesn't tell me anything about FSUIPC running. I needed to see the FSUIPC log file.

However, it sounds like that won't help much either.

Is this vasFMC / upper ECAM gauge payware? Do the authors offer support at all? You might need to ask them for help on this one. If it is a freeware package and I can download it someplace then I could try it here for you. But I cannot really support nor fix other folks software, so the most likely way to move on this would be for you to contact them and, if they need help resolving it, they could contact me to discuss what is happening.

Regards

Pete

[jorane]

Thank you Pete for your input, its nice to know that ther is someone out there who can share a problem.

I will go away for the time being and try out other possibilities but your comments have been useful.

If you are interested in this vasfmc freeware you can get the idea from www.vas-project.org/

best regards and thanks again

John

[jorane]

Hi Pete

After further checking with the vasFMC forum the problem I have is a known fault which is still to be resolved. This shows your deductions are correct. once again thank you for your efforts.

John

[Pete Dowson]

After further checking with the vasFMC forum the problem I have is a known fault which is still to be resolved. This shows your deductions are correct.

Okay. Thanks for letting me know. If they want any help from my end I suppose they'll be in touch with me?

Regards

Pete