Hi, Crytek.
I am receiving this error after a level ended and the next one is initialized.
Have you seen this before? Do you know why this error appears?
I am using Wwise.
Screenshot attached.
https://imgur.com/PvHW2Si
Please help.

Hi leozin,
Yes that error is known to us. Fortunately it got fixed quite a while ago which is around last quarter of 2016.
Which engine build version are you seeing this in?

Hi, cry-thomas,
thanks for answering.
The Cryengine version I am using is 3.6.17.
Do you think it is better to upgrade to Cryengine 3.8.6 or Cryengine 5.0 or 5.1?
Which one is more compatible with it(3.6.17)?
I really appreciate your help.
Best Regards,
Leozin

Hi leozin,
Yes that error is known to us. Fortunately it got fixed quite a while ago which is around last quarter of 2016.
Which engine build version are you seeing this in?

Ok that engine build is older than life itself. It's time to step into CRYENGINE 5.4.

Thanks for answering.
I agree it´s time to change.
But 5.4 has significant changes in code/Flowgraph/tools and etc.
I am using GameSDK as base.
In your experience, do you think 3.6.17 is more compatible with 3.8.6 or 5.1.1?

Ok that engine build is older than life itself. It's time to step into CRYENGINE 5.4.

I wouldn't use any of them. Get your project over to 5.4 which lays the foundation of CRYENGINE's future.

Hi leozin,
In order to receive the fix for the issue that you reported you'd have to upgrade to at least 5.3.

So you have basically two options.
1)
Stay on the version that you're on now. Meaning no worries with moving your project over to the new CRYENGINE but the issue stays unfixed.
Basically things stay as they're now.

2)
Upgrade to latest CRYENGINE (currently 5.4 stable). Meaning a lot of work moving your project over to the new CRYENGINE but the issue gets fixed.
Welcome to the now!

Your call

Hi, cry-thomas,
thanks for answering.
I am using some custom plugins that are not compatible with 5.4 yet.
I will try to make them compatible.
But thanks again for guiding me on the correct choice(5.4).
Thank you very much
Best Regards,
Leozin

Hi leozin,
In order to receive the fix for the issue that you reported you'd have to upgrade to at least 5.3.

So you have basically two options.
1)
Stay on the version that you're on now. Meaning no worries with moving your project over to the new CRYENGINE but the issue stays unfixed.
Basically things stay as they're now.

2)
Upgrade to latest CRYENGINE (currently 5.4 stable). Meaning a lot of work moving your project over to the new CRYENGINE but the issue gets fixed.
Welcome to the now!

Your call