Does _BugReport.txt helps
On 16/02/2018 at 17:02, xxxxxxxx wrote:
I have a plugin that I created sometime ago.
It works great in R14, R15, R16, R17 and R18.
But, in R19, it hangs Cinema4D and informs me that further information could be found in the _BugReport.txt file.
Well, that file does have a lot of information there, but I can't seem to make anything out of it that would help me to find the problem with my plugin in R19.
How can I try to find the problem?
On 19/02/2018 at 09:13, xxxxxxxx wrote:
_BugReport.txt probably has it's main use for us internally as we are able to decode the call stacks. It may also be of value to C++ plugin developers, who might be able to locate calls into their plugin on the callstack. For Python developers it's currently of little use.
How to locate the problem is a difficult question, especially without knowing any details. Can you maybe isolate at least the situation, when it is happening? Does it happen directly on plugin load? Or only when the command is called or an object is generated? Then one could get at least an idea, which functions of the plugin are involved in this situation. And from there one could maybe further break it down, by disabling parts of the code.
By the way, which version of R19 is this exactly?
On 20/02/2018 at 06:45, xxxxxxxx wrote:
It is R19.014
And here is a video showing the error:
On 21/02/2018 at 05:33, xxxxxxxx wrote:
Looking at your video, the issue always happens after clicking the cogwheel button, right?
So, I'd take this and started checking the code involved in this situation, maybe first disabling all of it and then step by step re-activating it, to see what causes the issue.
Please don't get me wrong, I'm not denying a possible issue in R19, which needs fixing on our end. But without locating the issue on your end, we can not do much here.
Also there are quite a bunch of fixes in R19 SP1 and SP2, may I ask you to check, if the issue is still existing in these versions?