Lots of UNRECOGNIZED_ID entries in my Couatl.log

[furger]

Hi

I am constantly ending up in lots of UNRECOGNIZED_ID entries like the following ones in my Couatl.log (see attached file)
Error: exception UNRECOGNIZED_ID in call SetInputGroupState param #3 '88202976'
Error: exception UNRECOGNIZED_ID in call RequestDataOnSimObject param #3 '5'
Error: exception UNRECOGNIZED_ID in call RequestSystemState param #3 '69'

A clean reinstal of GSX did unfortunately not resolve the problem.

Any idea what I can try?

Thank you for your support.

Andreas Furger

[virtuali]

I'm sorry but, while we were in Beta (which lasted 6 months) we had some users reporting this, but we never be able to understand the reason of the problem, which looks as if Simconnect was just acting up. We offered several times the chance to those affected to have a Teamviewer session, but nobody has ever replied to it, and we haven't heard of that error again after we released the final version.

Try a complete GSX uninstall/reinstall:

- Uninstall GSX from the Control Panel

- Be sure you reply YES to the question "Do you want to remove the Couatl scripting engine ?"

- If you still have a folder named fsdreateam\Couatl in the FSX main folder, remove it.

- Download and install the current version of the GSX Full installer

[furger]

Hi Virtuali

I already did so
- uninstalled GSX from the Control Panel and thereby replyed YES to both arising pairs of questions "Do you want to remove . . ."
- deleted both %APPDATA%\Virtuali\GSX and %ProgramData%\Virtuali\Couatl folders
- downloaded GSX Full installer and
- installed GSX again

but unfortunately with no success. Any other tip?

For your information:
I did not touch any other FSDT software during the above mentioned removal/reinstall process
I do have VRS Products installed (I think somebody else [with the same error message?] was mentioning that too).

Thanks

Andreas

[virtuali]

I do have VRS Products installed (I think somebody else [with the same error message?] was mentioning that too).

This would have been the next thing that I would say to check, in case reinstalling won't work.

Yes, we suspected this could be an issue, and while we were in Beta, we also had some contacts with VRS, so they sent me their software to try (only the TacPack base module, I don't have any planes that use it), but I couldn't find any problems on my system.

You can try disabling the VRS modules in the DLL.XML and EXE.XML files, by setting the Disabled line as follows:

<Disabled>True</Disabled>

You can try this with another 3rd party modules, to understand if one of them is causing problems to Simconnect data being corrupted somehow, because this is what it seems looking at that error.

[furger]

Hi Virtuali

I now have modified DLL.XML to have VRS_TacPack.dll loaded on request, i.e.

  <Launch.Addon>
    <Name>VRS_TacPack</Name>
    <Disabled>False</Disabled>
    <ManualLoad>True</ManualLoad>
    <Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path>
  </Launch.Addon>

When not loading VRS_TacPack.dll then Couatl.log is free from the mentioned error lines (see attachement). I hope that helps for isolating the root of the error messages. Please ask if you should need further information.

Regards

Andreas

[virtuali]

When not loading VRS_TacPack.dll then Couatl.log is free from the mentioned error lines (see attachement). I hope that helps for isolating the root of the error messages. Please ask if you should need further information.

Yes, this helps, but it seems we'll have to discuss it with VRS.

[furger]

Hi Virtuali

Thank you for the reply and for taking care of resolving the (cause of the) error. However I have to admit that I very seldomly use GSX when flying the VRS Superbug and also do have no use for VRS Tacpac when flying e.g. PMFG's 777 . Therefore the mentioned loading on request of VRS_TacPack.dll is quite fine for me. Nevertheless it looks like there is some incompatibility. And I have no idea what else could also have the same or similar pattern.

Regards

Andreas

[furger]

Any news on a possible resolution of this matter? Incompatibilty seems still to be existing.

I am working with:
Prepar3D 3.2.3
TacPack 1.4.2.8
Couatl v3.0 (build 3187)

Regards

Andreas

[virtuali]

Any news on a possible resolution of this matter? Incompatibilty seems still to be existing.

What happens if you disable the TacPack ?

[furger]

Then I do not have any such problem (see also Reply #4 in this thread).

But that's of course not what I am looking for. It would certainly be great to have FSDT sceneries working together with VRS software.

So any support would be highly appreciated.

[furger]

Hi

From the VRS team I received the feedback that they would be "happy to work with the Couatl authors" if you contact them.

So please let me know when you should need anything which I could provide to resolve that matter.

Regards

Andreas

[virtuali]

From the VRS team I received the feedback that they would be "happy to work with the Couatl authors" if you contact them.

We did this a long time ago. They sent me a copy of their product, and neither I nor them were ever able to replicate the problem. However, there has been many different new releases of the sim (P3D) in the meantime, and we tested in FSX. I think it's just something that happens in P3D for some reason, but I still never able to replicate it.

There's a known P3D bug that seems to be related to opening a Multiplayer session and this will cause such errors. Maybe the VRS is doing something similar or related to MP ?

[furger]

Umberto

That might be a reason why you haven't been able to reproduce the error. I would say that the problem came up with P3D V3.2. But I can't confirm for sure.

Somebody else in the forum who can confirm?

Regards

Andreas

[adiemus]

Umberto, it's Chris from VRS.  I've contacted you via e-mail regarding what we know of this problem.  It is known to be specific to P3D.

[furger]

Any news on that?

Problem still exists

Currently working with:
P3D 3.2.3.16769
Couatl v3.1 (build 3536)
PMDG 777-300
on FSDT airport LSZH

respective logfiled with and wothout having VRS_TacPack.dll enabled are enclosed