There are some new features but not much has fundamentally changed that I can think of. It's more likely the AI did something wrong as it won't have any idea how Opus plugins work.
Maybe it would be worth to try other IAs and see if they can up with a better implementation of the 64bit version ?
Thanks for your work !
AIs can’t do this kind of work. They still can’t do any technical work reliably, especially not in more niche areas with less examples to copy from.
We also don’t allow AI generated content here on the forum (see the FAQ for more detail), which especially goes for any kind of code. Code needs to be written carefully and understood by the person who is responsible for it, not randomly generated and left for others to clean up whatever messes it makes.
Maybe it would be worth to try other IAs
AIs can’t do this kind of work. They still can’t do any technical work reliably, especially not in more niche areas with less examples to copy from.
Yes, I confirm this. AI doesn't know anything about the DOpus Plugin API, thus it just generates very convincingly looking nonsense that unfortunately also passes compilation.
However, AI is insanely useful. For example, I have never written a viewer plugin for DOpus, but if you attach the examples of Viewer plugins to the AI chat, it will understand them very well and explain what every line of the code does and why it is there. It is super useful because the viewer plugin is 95% C++ MFC, which AI knows very well.
But it will not generate the finished code for you.
Would you be willing to share the source code of your plugin?
AI is working on rewriting this plugin from scratch:
Already showing the list control. It will probably take another week or two for it to finish.
Ooooh, this is very good news and looking good already !!
Keep us updated please
What IA are you using ?
You are not going to believe it, but AI actually managed to write this plugin and even created a repo on GitHub:
DirectoryOpus-CSV-viewer-plugin
It works well. The code is very strange, but it is obviously because AI wrote it.
I will create a separate thread about this plugin.
How do you know it works properly if you don't even understand it?
How can anyone work on it to fix or improve it if issues arise?
Yes, fair enough. In my defence, AI (ChatGPT O3) actually generated probably 80% of this code, but only using very specific prompts and not from the first try.
But I still had to suffer through every line of code, because even generated code needs to be polished and integrated into the codebase so that the codebase looks cohesive and not like a bunch of random code lazily stitched together ![]()

