Continual rapid image movement [u]after engine start[/u
Re: Continual rapid image movement [u]after engine start[/u
Correct, or at least try running with out it.
Re: Continual rapid image movement [u]after engine start[/u
I removed the FSUIPC.dll from the FS2004 modules folder, started Flight simulator, verified that the .dll was, indeed, removed as "modules" no longer showed on the menu bar and then I selected, first, the default flight (Cessna at SEA) and then the Alphasim Prowler. The result was exactly the same as before and the same as when FSUIPC was installed.
I'm not sure if I mentioned this before but the problem only occurs in the VC cockpit and then only when TrackIR is activated.
The VC works perfectly when TrackIR is off.
Vincent, you've got the patience of a Saint!
Any ideas where we can go from here?
Frederick
I'm not sure if I mentioned this before but the problem only occurs in the VC cockpit and then only when TrackIR is activated.
The VC works perfectly when TrackIR is off.
Vincent, you've got the patience of a Saint!
Any ideas where we can go from here?
Frederick
Re: Continual rapid image movement [u]after engine start[/u
using the standard language.dll file for 2004?
Nothing like FSInn installed?
If you have room, you could try using both the 4.1.037, and the beta software, as well as try a clean install of the FS9 software, in a seperate install location, so you don't loose what you have currently installed.
Nothing like FSInn installed?
If you have room, you could try using both the 4.1.037, and the beta software, as well as try a clean install of the FS9 software, in a seperate install location, so you don't loose what you have currently installed.
Re: Continual rapid image movement [u]after engine start[/u
Vincent,
I'll be out of town for two days but I'll do all you suggested when I return on Monday.
I'll reinstall a virgin copy of the language .dll from the FS2004 disc and remove the one presently there.
I do have FSInn installed and when I install another copy of FS2004 on another partition I'll leave the FSInn out of the new installation and let you know how it goes.
Good ideas!
Thanks, Frederick
I'll be out of town for two days but I'll do all you suggested when I return on Monday.
I'll reinstall a virgin copy of the language .dll from the FS2004 disc and remove the one presently there.
I do have FSInn installed and when I install another copy of FS2004 on another partition I'll leave the FSInn out of the new installation and let you know how it goes.
Good ideas!
Thanks, Frederick