by Oleg » Thu Oct 19, 2017 10:45 am
does placing "ZModeler3_profile.xml" file from original package into pre-installed folder solves the problem too? I clarify: Windows could apply some settings/compatibility options to an application. placing XML file from original package into a folder with problematic (fail to start) ZModeler will force ZModeler to start with no 3D configuration (an options dialog will appear), but it will start with windows-defined compatibility options on executable file (zmodeler3.exe).
If ZMod still crashes at startup even after being feed with non-configured original XML file, the problem might be in compatibility options windows apply to an executable file.
will try to inspect this more closely as I see a report "windows has configured compatibility options for this application" from time to time. Don't know what windows does there and what exactly gets changed, need it explore this.
does placing "ZModeler3_profile.xml" file from original package into pre-installed folder solves the problem too? I clarify: Windows could apply some settings/compatibility options to an application. placing XML file from original package into a folder with problematic (fail to start) ZModeler will force ZModeler to start with no 3D configuration (an options dialog will appear), but it will start with windows-defined compatibility options on executable file (zmodeler3.exe).
If ZMod still crashes at startup even after being feed with non-configured original XML file, the problem might be in compatibility options windows apply to an executable file.
will try to inspect this more closely as I see a report "windows has configured compatibility options for this application" from time to time. Don't know what windows does there and what exactly gets changed, need it explore this.