So, unfortunately, there are no errors in the log. The only hint of what might be an issue (but in theory should only affect saving files, not opening them) is that Civ is installed under C:\Program Files (x86)\. Windows Vista and later tend to protect access to that folder, which has been the root cause of many mysterious "I made updates to my BIQ and re-saved it, but when I re-opened the BIQ, the changes weren't there" type bugs over the years, including with the Firaxis editor. This can apply to Civ saves as well; back in 2007 when Vista was new and I had Civ installed to C:\Program Files\, my saves would mysteriously disappear.
I should really add a warning message about potential issues when those install directories are detected. It's common since it's it was and still is the default, but any of us old-timers who lived through Windows Vista + Civ3 likely learned the hard way to avoid it.
There's a 10-50% chance this is causing what you are seeing; the only way that comes to mind to test it is to copy the whole Civ structure to somewhere outside of Program Files (and Program Files (x86)), change the editor's "Civ Install Directory" in Editor Settings (Ctrl+P) to point to that folder, and try again.
But read on...
I'm having a similar problem... I can open the Editor and get the same screen as B-29_Bomber. But it has almost no functionality. I cannot open any BIQs or saves, only change the Editor Settings and use one or two options in the Help menu.
However, I'm not entirely convinced I am opening the ConquestsEditor in the correct way. I started it by double-clicking the "Conquests Editor.jar" within the main folder, which seemed the only logical choice. But the original post of this discussion mentions a "launcher.jar" file which is supposed to start the Editor, and a download link for a "start.bat" file that also references "launcher.jar". Same in the HTML documents. I'm pretty sure that no such file exists within the current v1.44 download.
I'm on Windows 10 and installed the Liberica full JRE 8 as recommended. The Civ install path (a non-system folder) was auto-detected correctly according to the Settings tab.
This seems to be happening significantly more this year, and alas, never on my machine so figuring out why is quite difficult.
But I would suggest trying
this "Windows XP build" and seeing if it works as expected. It included a bundled build of Java, includes a XP_launcher.vbs script to start it, and should work just as well on 10 as on XP. Originally the bundling of Java was only necessary on XP, but it seems to be an increasingly good idea on all versions of Windows nowadays.
launcher.jar was required in the early days as back then Java would restrict itself to low amounts of memory by default - I think 64 MB - and the launcher would tell the editor it could use more memory, which was necessary for map graphics. Over the years, Java became more willing to use more memory by default, so launcher.jar was eventually retired. start.bat was used to launch the launcher on systems that didn't have Java installed at all.
This year, I've seen reports of Java restricting itself to 256 MB again, which on larger maps with graphics enabled is not enough. So launcher.jar may be coming back.
You do get brownie points for checking the HTML documents. I'm glad someone has looked at them!
Let me know if the "XP build" works. If it does I'll probably switch that to the default for 1.45, on Windows anyway. It's more work to build and upload it (while still having the traditional build for Linux/Intel Mac), but if it is solving the "2022 Java issues", that work will be saved in terms of support.