When is this happening Ben - I have never seen it - what function are you running to generate this message?
It happens at startup. As the TBC loads up this pops up and stays up as a separate window and doesn’t go away until I shut down. After running TBC for a while there will be this as well. If I try to close the window it kills the program as well.
Alan, I replied to the email message that was generated. I was just wondering if you got it or if I need to reply in here instead.
The problem appears to be related to how the software sets up the Multithreading on your computer. There has been some reported issues with AMD Processors that apparently do not support the threading correctly for Windows OS and this may be what you are seeing since you are using an AMD Processor Ben.
I will push again today to get you a response on how to move forwards here.
In TBC 5.00 a component was added which makes use of Intel's internal threading API. This API is not supported on certain AMD Ryzen processors. The effect is that when you start the program, a text box is created that displays an error message similar to the following: “KMP_AFFINITY: affinity not supported, using “disabled””. If you close the text box, TBC will crash. We are working to get a computer to duplicate the error and so far have not been able to find the change that causes the problem.
I believe that you may be able to set an environment variable that will disable this, but without a computer I cannot verify it. Try setting KMP_AFFINITY=disabled and let us know if this corrects the problem.
Go to control panel>system>advanced systems settings>environment variables>
Create a new system variable
Name = KMP_AFFINITY
Variable value = disabled
Start TBC and see if the problem still persists.
I'm also getting this error on my new PC. I have an AMD 2950 with 16x cores. As already described, as long as you don't close the command window, TBC seems to work.
I'm now travelling and coming back to the office next Friday, so if you want to access to my machine via TeamViewer to test whatever needed, please let me know.
I'll be able to try it with the environment variable also next friday as I have the dongle with me, and I think the error doesn't come if you launch TBC in viewer mode without the dongle.
BTW, if you want to try sooner, one colleague can start the PC and give you access via TeamViewer so you can add a 30 days trial code so the error should also pop up if it's not reading the dongle but a current valid license instead.
Please let me know if I can help
I was finally able to try this and after creating the environment variable and setting it to "disabled", indeed I don´t get the error message any longer, so it seems to fix it.
Thanks for the workaround !
Awesome Fernando -Thanks for the update - Good to know that this works on at least your PC
Ben - Hopefully you have seen this and have tried it also - can you let us know if it also worked for you too
Retrieving data ...