Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Ive upgraded to an MCP PRO by goflight from an MCP COMBO by vri. Now I get this message "mcp combo is enabled but not found on com 3 ".

 

Harmless but annoying. Where is the entry for this so I can remove it does anyone know please. I Guess in FSUIPC.ini somewhere ?

 

Graham

Posted

Ive upgraded to an MCP PRO by goflight from an MCP COMBO by vri. Now I get this message "mcp combo is enabled but not found on com 3 ".

 

Harmless but annoying. Where is the entry for this so I can remove it does anyone know please. I Guess in FSUIPC.ini somewhere ?

 

Graham

 

Just remove whatever you added to make the VRi COMBO work. I don't recall any of the VRi stuff myself (not been involved with it for years), and I'm away from the PC containing the documentation. Can you look it up? It's be an appendix to either the User Guide or the Advanced Users guide, or maybe even a separate document.

 

All the documentation for all things to do with FSUIPC is found in the FSUIPC Documents folder, within your FS Modules folder.

 

Pete

Posted

Thanks Pete,

I'm going to have to have a dig around.. I can't uninstall the vrinsight software as I still use their cdu. I wondered if the message could have arrived onscreen via fsuipc or some other fsx config file.

I'll have a look deeper if no-one else here is familiar.

Thanks

Graham

Posted

I'm going to have to have a dig around.. I can't uninstall the vrinsight software as I still use their cdu. I wondered if the message could have arrived onscreen via fsuipc or some other fsx config file.

 

If it is on-screen then it isn't FSUIPC. I thought you meant in the Log file -- FSUIPC only deals with VRi devices if there's a VRinsight section in the INI file. e.g. something like

 

[VRInsight]
1=COM3
 

but if the device isn't there there would simply be an entry in the Log file -- same as if it was there in fact but with a "not" or similar.

 

Try the VRinsight support forum. It probably just needs something disabling in the VRi control program. I think it is all new since I last got involved.

 

Pete

Posted

Thank Peter

I'll head over to vrinsight now.. I'll post back here when I get a result incase other's who visit here find themselves likewise

Graham

Posted

This will be a LINDA popup printed by their LUA's and nothing to do with FSUIPC or VRInsight. By the way I answered you already over on the VRi forum and the fix is the same as Pete posted above in post 4 i.e. remove the VRinsight section from the FSUIPC.ini, you should also disable the MCP Combo in Linda too.

Posted

Thanks Andy I'll take as look at the ini file. I don't use Linda anymore though just the original vrinsight program. This runs for the cduii.. Is there anything in that?? I seem to remember it being modular and perhaps has an mcp module running in it that I should remove or disable

Graham

Posted

You may not be using Linda but it's LUA's are obviously still installed as that is where that error is coming from, it's nothing to do with FSUIPC or VRInsight as I said above.

Posted

Avsim forums are down it seems as I was at first going to uninstall LINDA taking advice from there.

 

I first took the tick out of Enable mcp combo in Linda ( even though it wasn't running ) and this changed the message to linda is loaded and ready.

 

So there is "a way back " if I need to, Ive just renamed the linda.lua file in the modules folder to Linda.bak preventing whatever was loading it from doing so. Its done the trick it would seem

 

Graham

  • 1 year later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.