|
Post by bob on Dec 18, 2017 10:17:41 GMT -5
Recently I have discovered that using a multi monitor setup does have drawbacks. Having FS9 running on one monitor and then FSNAV on another monitor with vastly different display resolutions results in random FS9 crash to desktop. This usually occurred when clicked in the ID box to search for ICAO. Clean re- installs ( numerous times) did not resolve the problem. The only way I seem to be able to resolve this problem is keeping fsnav and fs9 on same monitor. IF you know a soultion to this PLEASE by all means post it. I have exhausted all possibilities up to and including searching forums and trying their suggestions.
|
|
|
Post by steve on Dec 19, 2017 5:45:47 GMT -5
Im not sure on the dual monitor set up but all info that I can find states that fsNav must to be on the same system as fs9 in the moduals folder.I have been using fsNav since the very first version and in 95% of problems you can narrow it down to fsuipc.dll. Try a fresh and clean copy of the correct version of FSUIPC as it is known to stutter and even fail at times. The file may become corrupt after awhile. Check you current version. Only d/l from Pete's official sites as some have spread trojans into the file. Bastard hackers!Use the latest for your OS (XP,Win7,Win10) etc. Note that it has been reported unstable within Win10.Also you may try, if using Win7 + you should be using the latest WideServer because it supports dual monitors and is built into FSUIPC . Without knowing your OS, there is not much more I can say. fsNavigator is very stable. If all else fails - try a CLEAN install of fsNav - run the database program then install a clean FSUIPC I know it may not be much help but the above is the most common problem. If doing a clean install be sure to do so as admin and allow access to all users even if you are the only user. I hope this helps. Pls. keep us updated.
|
|