Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

I agree and I am trying to find a way to do that, but it's more difficult than you would think. Blender's API doesn't lend itself to custom dialog boxes for some reason. If someone can find me a code snippet of a custom, MODAL, dialog box for Blender's python, I'm happy to give it another try. I already spent around two days with this with zero results. In the meantime, I'd suggest to open the system console to get some feedback on the export process.

Yep, that's already done! Thanks for the reminder!

May I know what is your suggestion please?Hello
Speaking of updates... don't forget the log file change I suggested earlier![]()

That's a good idea though. Thank you for the suggestionHello
Instead of a general log filename - when clicked would save with the model file, using the model name with date and time. For example, hangar_(date)_(time)_log.txt.


The new update is live!
Changelog (05.04.2020):
- changed the name of the logfile to include the name of the exported model
- add z-bias property back to specular material
- fixed an issue with virtual cockpit texture names
Let me know if you run into any issues and feel free to keep the suggestions coming!







@Robert Richardson that's strange. Could you tell me the name of the $ texture you use please? It might have to do with the way I replace the file extension, but I'd first like to reproduce the issue.
I hope you guys don't mind the frequent updates...

No extensionsI'm more interested in the file extension of the texture map you're putting into the shader. I.e. is it $pan1.dds, $pan2.dds and.... wait for it..... $pan3.dds?