Cura не запускается на windows 10 - Доктор Windows

this is from today’s load — no monitor plugged in:
2022-05-05 11:43:15,254 — INFO — [MainThread] UM.Qt.QtApplication.init [87]: Adding QT6 plugin path: C:Program FilesUltimaker Cura 5.0.0PyQt6plugins
2022-05-05 11:43:15,255 — INFO — [MainThread] UM.Qt.QtApplication.init [97]: Adding QT5 plugin path: C:Program FilesUltimaker Cura 5.0.0PyQt6plugins
2022-05-05 11:43:15,255 — DEBUG — [MainThread] UM.Application.initialize [161]: Initializing Ultimaker Cura
2022-05-05 11:43:15,255 — DEBUG — [MainThread] UM.Application.initialize [162]: App Version 5.0.0-beta+1
2022-05-05 11:43:15,255 — DEBUG — [MainThread] UM.Application.initialize [163]: Api Version 8.0.0
2022-05-05 11:43:15,255 — DEBUG — [MainThread] UM.Application.initialize [164]: Build type None
2022-05-05 11:43:15,255 — WARNING — [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:Program Filesliburanium must be a folder.
2022-05-05 11:43:15,255 — WARNING — [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:Program Fileslib64uranium must be a folder.
2022-05-05 11:43:15,255 — WARNING — [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:Program Fileslib32uranium must be a folder.
2022-05-05 11:43:15,256 — WARNING — [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:Program FilesUltimaker Cura 5.0.0plugins must be a folder.
2022-05-05 11:43:15,256 — WARNING — [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:Program FilesResourcesuraniumplugins must be a folder.
2022-05-05 11:43:15,256 — WARNING — [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:Program FilesResourcescuraplugins must be a folder.
2022-05-05 11:43:15,256 — DEBUG — [MainThread] UM.Resources.__initializeStoragePaths [447]: Initializing storage paths
2022-05-05 11:43:15,256 — DEBUG — [MainThread] UM.Resources.__initializeStoragePaths [457]: Config storage path is C:UsersdcoopAppDataRoamingcura5.0
2022-05-05 11:43:15,256 — DEBUG — [MainThread] UM.Resources.__initializeStoragePaths [465]: Data storage path is C:UsersdcoopAppDataRoamingcura5.0
2022-05-05 11:43:15,256 — DEBUG — [MainThread] UM.Resources.__initializeStoragePaths [477]: Cache storage path is C:UsersdcoopAppDataLocalcura5.0cache
2022-05-05 11:43:15,256 — INFO — [MainThread] UM.PackageManager.init [56]: Found bundled packages JSON file: C:Program FilesUltimaker Cura 5.0.0UM..shareuraniumresourcesbundled_packagesuranium.json
2022-05-05 11:43:15,256 — INFO — [MainThread] UM.PackageManager.init [56]: Found bundled packages JSON file: C:Program FilesUltimaker Cura 5.0.0sharecuraresourcesbundled_packagescura.json
2022-05-05 11:43:15,256 — INFO — [MainThread] UM.PackageManager.init [56]: Found bundled packages JSON file: C:Program FilesUltimaker Cura 5.0.0cura..sharecuraresourcesbundled_packagescura.json
2022-05-05 11:43:15,257 — INFO — [MainThread] UM.PackageManager.init [56]: Found bundled packages JSON file: C:Program FilesUltimaker Cura 5.0.0shareuraniumresourcesbundled_packagesuranium.json
2022-05-05 11:43:15,257 — DEBUG — [MainThread] UM.View.GL.OpenGLContext.detectBestOpenGLVersion [124]: Trying OpenGL context 4.1…
2022-05-05 11:43:15,257 — DEBUG — [MainThread] UM.View.GL.OpenGLContext.detectBestOpenGLVersion [132]: Yay, we got at least OpenGL 4.1 core: 4.1 Core profile
2022-05-05 11:43:15,257 — DEBUG — [MainThread] UM.Qt.QtApplication.initialize [180]: Detected most suitable OpenGL context version: 4.1 Core profile
2022-05-05 11:43:15,257 — INFO — [MainThread] UM.Qt.QtApplication.initialize [187]: Initializing job queue …
2022-05-05 11:43:15,257 — INFO — [MainThread] UM.Qt.QtApplication.initialize [191]: Initializing version upgrade manager …
2022-05-05 11:43:15,257 — INFO — [MainThread] UM.PackageManager._loadManagementData [174]: Loaded bundled packages data from C:Program FilesUltimaker Cura 5.0.0UM..shareuraniumresourcesbundled_packagesuranium.json
2022-05-05 11:43:15,257 — INFO — [MainThread] UM.PackageManager._loadManagementData [174]: Loaded bundled packages data from C:Program FilesUltimaker Cura 5.0.0sharecuraresourcesbundled_packagescura.json
2022-05-05 11:43:15,257 — INFO — [MainThread] UM.PackageManager._loadManagementData [174]: Loaded bundled packages data from C:Program FilesUltimaker Cura 5.0.0cura..sharecuraresourcesbundled_packagescura.json
2022-05-05 11:43:15,257 — INFO — [MainThread] UM.PackageManager._loadManagementData [174]: Loaded bundled packages data from C:Program FilesUltimaker Cura 5.0.0shareuraniumresourcesbundled_packagesuranium.json
2022-05-05 11:43:15,258 — INFO — [MainThread] UM.PackageManager._loadManagementData [201]: Loaded user packages management file from C:UsersdcoopAppDataRoamingcura5.0packages.json
2022-05-05 11:43:15,258 — INFO — [MainThread] UM.PackageManager._removeAllScheduledPackages [280]: Attempting to remove the following scheduled packages: —
2022-05-05 11:43:15,258 — INFO — [MainThread] UM.PluginRegistry.initializeBeforePluginsAreLoaded [121]: Loading plugin configuration file ‘C:UsersdcoopAppDataRoamingcura5.0plugins.json’
2022-05-05 11:43:15,258 — WARNING — [MainThread] UM.PluginRegistry.addPluginLocation [202]: Plugin location C:Program Fileslibcura must be a folder.
2022-05-05 11:43:15,259 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin FileLogger
2022-05-05 11:43:15,277 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin LocalContainerProvider
2022-05-05 11:43:15,298 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin LocalFileOutputDevice
2022-05-05 11:43:15,314 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin CameraTool
2022-05-05 11:43:15,333 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin MirrorTool
2022-05-05 11:43:15,354 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin RotateTool
2022-05-05 11:43:15,375 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin ScaleTool
2022-05-05 11:43:15,392 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin SelectionTool
2022-05-05 11:43:15,412 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin TranslateTool
2022-05-05 11:43:15,446 — INFO — [MainThread] UpdateChecker.UpdateChecker.checkNewVersion [68]: Checking for new version
2022-05-05 11:43:15,449 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin UpdateChecker
2022-05-05 11:43:15,563 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin SimpleView
2022-05-05 11:43:15,644 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin 3MFReader
2022-05-05 11:43:15,670 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin 3MFWriter
2022-05-05 11:43:16,304 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin AMFReader
2022-05-05 11:43:16,339 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin CuraDrive
2022-05-05 11:43:16,454 — INFO — [MainThread] CuraEngineBackend.CuraEngineBackend.init [96]: Found CuraEngine at: C:Program FilesUltimaker Cura 5.0.0CuraEngine.exe
2022-05-05 11:43:16,455 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin CuraEngineBackend
2022-05-05 11:43:16,473 — DEBUG — [MainThread] UM.Backend.Backend._logSocketState [188]: Socket state changed to Listening
2022-05-05 11:43:16,490 — INFO — [MainThread] UM.Backend.Backend.startEngine [91]: Started engine process: C:Program FilesUltimaker Cura 5.0.0CuraEngine.exe
2022-05-05 11:43:16,491 — DEBUG — [MainThread] UM.Backend.Backend._backendLog [111]: [Backend] Calling engine with: [‘C:Program FilesUltimaker Cura 5.0.0CuraEngine.exe’, ‘connect’, ‘127.0.0.1:49674’, »]
2022-05-05 11:43:16,508 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin CuraProfileReader
2022-05-05 11:43:16,528 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin CuraProfileWriter
2022-05-05 11:43:16,570 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend]
2022-05-05 11:43:16,571 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] Cura_SteamEngine version 5.0.0-beta+1
2022-05-05 11:43:16,572 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] Copyright (C) 2021 Ultimaker
2022-05-05 11:43:16,572 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend]
2022-05-05 11:43:16,572 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] This program is free software: you can redistribute it and/or modify
2022-05-05 11:43:16,573 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] it under the terms of the GNU Affero General Public License as published by
2022-05-05 11:43:16,573 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] the Free Software Foundation, either version 3 of the License, or
2022-05-05 11:43:16,573 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] (at your option) any later version.
2022-05-05 11:43:16,574 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend]
2022-05-05 11:43:16,574 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] This program is distributed in the hope that it will be useful,
2022-05-05 11:43:16,574 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] but WITHOUT ANY WARRANTY; without even the implied warranty of
2022-05-05 11:43:16,575 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2022-05-05 11:43:16,575 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] GNU Affero General Public License for more details.
2022-05-05 11:43:16,575 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend]
2022-05-05 11:43:16,576 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] You should have received a copy of the GNU Affero General Public License
2022-05-05 11:43:16,576 — DEBUG — [EngineErrorThread] UM.Backend.Backend._backendLog [111]: [Backend] along with this program. If not, see http://www.gnu.org/licenses/.
2022-05-05 11:43:16,664 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin DigitalLibrary
2022-05-05 11:43:16,664 — DEBUG — [MainThread] UM.Backend.Backend._logSocketState [192]: Socket state changed to Connected
2022-05-05 11:43:16,664 — DEBUG — [MainThread] UM.Backend.Backend._onSocketStateChanged [181]: Backend connected on port 49674
2022-05-05 11:43:16,692 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin FirmwareUpdateChecker
2022-05-05 11:43:16,707 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin FirmwareUpdater
2022-05-05 11:43:16,721 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin GCodeGzReader
2022-05-05 11:43:16,736 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin GCodeGzWriter
2022-05-05 11:43:16,750 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin GCodeProfileReader
2022-05-05 11:43:16,777 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin GCodeReader
2022-05-05 11:43:16,799 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin GCodeWriter
2022-05-05 11:43:16,819 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin ImageReader
2022-05-05 11:43:16,836 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin LegacyProfileReader
2022-05-05 11:43:16,850 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin MachineSettingsAction
2022-05-05 11:43:16,925 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin Marketplace
2022-05-05 11:43:16,942 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin ModelChecker
2022-05-05 11:43:16,957 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin MonitorStage
2022-05-05 11:43:16,979 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin PerObjectSettingsTool
2022-05-05 11:43:16,995 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin PostProcessingPlugin
2022-05-05 11:43:17,009 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin PrepareStage
2022-05-05 11:43:17,024 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin PreviewStage
2022-05-05 11:43:17,048 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin RemovableDriveOutputDevice
2022-05-05 11:43:17,080 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin SimulationView
2022-05-05 11:43:17,098 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin SliceInfoPlugin
2022-05-05 11:43:17,114 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin SolidView
2022-05-05 11:43:17,129 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin SupportEraser
2022-05-05 11:43:17,143 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin TrimeshReader
2022-05-05 11:43:17,159 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin UFPReader
2022-05-05 11:43:17,174 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin UFPWriter
2022-05-05 11:43:17,191 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin UltimakerMachineActions
2022-05-05 11:43:17,410 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [448]: Plugin [UM3NetworkPrinting] has been disabled. Skip loading it.
2022-05-05 11:43:17,455 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [448]: Plugin [USBPrinting] has been disabled. Skip loading it.
2022-05-05 11:43:17,483 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade21to22
2022-05-05 11:43:17,498 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade22to24
2022-05-05 11:43:17,515 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade25to26
2022-05-05 11:43:17,530 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade26to27
2022-05-05 11:43:17,545 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade27to30
2022-05-05 11:43:17,562 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade30to31
2022-05-05 11:43:17,577 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade32to33
2022-05-05 11:43:17,590 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade33to34
2022-05-05 11:43:17,605 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade34to35
2022-05-05 11:43:17,618 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade35to40
2022-05-05 11:43:17,631 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade40to41
2022-05-05 11:43:17,647 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade411to412
2022-05-05 11:43:17,661 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade413to50
2022-05-05 11:43:17,675 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade41to42
2022-05-05 11:43:17,689 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade42to43
2022-05-05 11:43:17,705 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade43to44
2022-05-05 11:43:17,719 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade44to45
2022-05-05 11:43:17,733 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade45to46
2022-05-05 11:43:17,749 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade460to462
2022-05-05 11:43:17,765 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade462to47
2022-05-05 11:43:17,779 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade47to48
2022-05-05 11:43:17,793 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade48to49
2022-05-05 11:43:17,808 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin VersionUpgrade49to410
2022-05-05 11:43:17,827 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin X3DReader
2022-05-05 11:43:17,855 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin XmlMaterialProfile
2022-05-05 11:43:17,869 — INFO — [MainThread] UM.PluginRegistry.loadPlugin [494]: Loaded plugin XRayView
2022-05-05 11:43:17,902 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Exception: Import error loading module CuraFreeCADPlugin
2022-05-05 11:43:17,903 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Traceback (most recent call last):
2022-05-05 11:43:17,904 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «UMPluginRegistry.py», line 727, in _findPlugin
2022-05-05 11:43:17,904 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: module = imp.load_module(plugin_id, file, path, desc) # type: ignore #MyPy gets the wrong output type from imp.find_module for some reason.
2022-05-05 11:43:17,904 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 245, in load_module
2022-05-05 11:43:17,904 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 217, in load_package
2022-05-05 11:43:17,904 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 719, in _load
2022-05-05 11:43:17,905 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 688, in _load_unlocked
2022-05-05 11:43:17,905 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 883, in exec_module
2022-05-05 11:43:17,905 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 241, in _call_with_frames_removed
2022-05-05 11:43:17,905 — ERROR — [MainThread] UM.PluginRegistry.findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsCuraFreeCADPluginCuraFreeCADPlugin_init.py», line 12, in
2022-05-05 11:43:17,906 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from . import FreeCADReader
2022-05-05 11:43:17,906 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsCuraFreeCADPluginCuraFreeCADPluginFreeCADReader.py», line 14, in
2022-05-05 11:43:17,907 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from .CadIntegrationUtils.CommonCLIReader import CommonCLIReader # @UnresolvedImport
2022-05-05 11:43:17,908 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsCuraFreeCADPluginCuraFreeCADPluginCadIntegrationUtilsCommonCLIReader.py», line 8, in
2022-05-05 11:43:17,908 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from .CommonReader import CommonReader # @UnresolvedImport
2022-05-05 11:43:17,908 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsCuraFreeCADPluginCuraFreeCADPluginCadIntegrationUtilsCommonReader.py», line 22, in
2022-05-05 11:43:17,909 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from .Extras.Preferences import PreferencesAdvanced
2022-05-05 11:43:17,909 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsCuraFreeCADPluginCuraFreeCADPluginCadIntegrationUtilsExtrasPreferences.py», line 2, in
2022-05-05 11:43:17,909 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from PyQt5.QtCore import pyqtSlot # @UnresolvedImport
2022-05-05 11:43:17,909 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: ModuleNotFoundError: No module named ‘PyQt5’
2022-05-05 11:43:17,910 — WARNING — [MainThread] UM.PluginRegistry._populateMetaData [821]: Could not find plugin CuraFreeCADPlugin
2022-05-05 11:43:17,914 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Exception: Import error loading module CuraFreeCADPlugin
2022-05-05 11:43:17,914 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Traceback (most recent call last):
2022-05-05 11:43:17,915 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «UMPluginRegistry.py», line 727, in _findPlugin
2022-05-05 11:43:17,915 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: module = imp.load_module(plugin_id, file, path, desc) # type: ignore #MyPy gets the wrong output type from imp.find_module for some reason.
2022-05-05 11:43:17,915 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 245, in load_module
2022-05-05 11:43:17,915 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 217, in load_package
2022-05-05 11:43:17,916 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 719, in _load
2022-05-05 11:43:17,916 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 688, in _load_unlocked
2022-05-05 11:43:17,916 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 883, in exec_module
2022-05-05 11:43:17,916 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 241, in _call_with_frames_removed
2022-05-05 11:43:17,917 — ERROR — [MainThread] UM.PluginRegistry.findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsCuraFreeCADPluginCuraFreeCADPlugin_init.py», line 12, in
2022-05-05 11:43:17,917 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from . import FreeCADReader
2022-05-05 11:43:17,917 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsCuraFreeCADPluginCuraFreeCADPluginFreeCADReader.py», line 14, in
2022-05-05 11:43:17,917 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from .CadIntegrationUtils.CommonCLIReader import CommonCLIReader # @UnresolvedImport
2022-05-05 11:43:17,918 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsCuraFreeCADPluginCuraFreeCADPluginCadIntegrationUtilsCommonCLIReader.py», line 8, in
2022-05-05 11:43:17,918 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from .CommonReader import CommonReader # @UnresolvedImport
2022-05-05 11:43:17,918 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsCuraFreeCADPluginCuraFreeCADPluginCadIntegrationUtilsCommonReader.py», line 22, in
2022-05-05 11:43:17,918 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from .Extras.Preferences import PreferencesAdvanced
2022-05-05 11:43:17,918 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsCuraFreeCADPluginCuraFreeCADPluginCadIntegrationUtilsExtrasPreferences.py», line 2, in
2022-05-05 11:43:17,919 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from PyQt5.QtCore import pyqtSlot # @UnresolvedImport
2022-05-05 11:43:17,919 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: ModuleNotFoundError: No module named ‘PyQt5’
2022-05-05 11:43:17,920 — ERROR — [MainThread] UM.PluginRegistry.removeCorruptedPluginMessage [527]: Exception: Error loading plugin CuraFreeCADPlugin:
2022-05-05 11:43:17,920 — ERROR — [MainThread] UM.PluginRegistry.removeCorruptedPluginMessage [527]: NoneType: None
2022-05-05 11:43:17,935 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Exception: Import error loading module MeshTools
2022-05-05 11:43:17,935 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Traceback (most recent call last):
2022-05-05 11:43:17,935 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «UMPluginRegistry.py», line 727, in _findPlugin
2022-05-05 11:43:17,936 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: module = imp.load_module(plugin_id, file, path, desc) # type: ignore #MyPy gets the wrong output type from imp.find_module for some reason.
2022-05-05 11:43:17,936 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 245, in load_module
2022-05-05 11:43:17,936 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 217, in load_package
2022-05-05 11:43:17,936 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 719, in _load
2022-05-05 11:43:17,937 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 688, in _load_unlocked
2022-05-05 11:43:17,937 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 883, in exec_module
2022-05-05 11:43:17,937 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 241, in _call_with_frames_removed
2022-05-05 11:43:17,938 — ERROR — [MainThread] UM.PluginRegistry.findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsMeshToolsMeshTools_init.py», line 4, in
2022-05-05 11:43:17,938 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from . import MeshTools
2022-05-05 11:43:17,938 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsMeshToolsMeshToolsMeshTools.py», line 4, in
2022-05-05 11:43:17,938 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from PyQt5.QtCore import pyqtSlot, QObject
2022-05-05 11:43:17,939 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: ModuleNotFoundError: No module named ‘PyQt5’
2022-05-05 11:43:17,939 — WARNING — [MainThread] UM.PluginRegistry._populateMetaData [821]: Could not find plugin MeshTools
2022-05-05 11:43:17,942 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Exception: Import error loading module MeshTools
2022-05-05 11:43:17,943 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Traceback (most recent call last):
2022-05-05 11:43:17,943 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «UMPluginRegistry.py», line 727, in _findPlugin
2022-05-05 11:43:17,943 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: module = imp.load_module(plugin_id, file, path, desc) # type: ignore #MyPy gets the wrong output type from imp.find_module for some reason.
2022-05-05 11:43:17,943 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 245, in load_module
2022-05-05 11:43:17,944 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 217, in load_package
2022-05-05 11:43:17,944 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 719, in _load
2022-05-05 11:43:17,944 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 688, in _load_unlocked
2022-05-05 11:43:17,944 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 883, in exec_module
2022-05-05 11:43:17,945 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 241, in _call_with_frames_removed
2022-05-05 11:43:17,945 — ERROR — [MainThread] UM.PluginRegistry.findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsMeshToolsMeshTools_init.py», line 4, in
2022-05-05 11:43:17,945 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from . import MeshTools
2022-05-05 11:43:17,945 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsMeshToolsMeshToolsMeshTools.py», line 4, in
2022-05-05 11:43:17,945 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from PyQt5.QtCore import pyqtSlot, QObject
2022-05-05 11:43:17,946 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: ModuleNotFoundError: No module named ‘PyQt5’
2022-05-05 11:43:17,946 — ERROR — [MainThread] UM.PluginRegistry.removeCorruptedPluginMessage [527]: Exception: Error loading plugin MeshTools:
2022-05-05 11:43:17,946 — ERROR — [MainThread] UM.PluginRegistry.removeCorruptedPluginMessage [527]: NoneType: None
2022-05-05 11:43:17,973 — WARNING — [MainThread] UM.PluginRegistry.loadPlugin [460]: Plugin [OrientationPlugin] with supported sdk versions [[‘5.0.0’, ‘6.0.0’, ‘7.0.0’, ‘5.0.0’]] is incompatible with the current sdk version [8.0.0].
2022-05-05 11:43:17,987 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Exception: Import error loading module SettingsGuide2
2022-05-05 11:43:17,987 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Traceback (most recent call last):
2022-05-05 11:43:17,988 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «UMPluginRegistry.py», line 727, in _findPlugin
2022-05-05 11:43:17,988 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: module = imp.load_module(plugin_id, file, path, desc) # type: ignore #MyPy gets the wrong output type from imp.find_module for some reason.
2022-05-05 11:43:17,988 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 245, in load_module
2022-05-05 11:43:17,988 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 217, in load_package
2022-05-05 11:43:17,989 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 719, in _load
2022-05-05 11:43:17,989 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 688, in _load_unlocked
2022-05-05 11:43:17,989 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 883, in exec_module
2022-05-05 11:43:17,989 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 241, in _call_with_frames_removed
2022-05-05 11:43:17,989 — ERROR — [MainThread] UM.PluginRegistry.findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsSettingsGuide2SettingsGuide2_init.py», line 7, in
2022-05-05 11:43:17,990 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from . import CuraSettingsGuide
2022-05-05 11:43:17,990 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsSettingsGuide2SettingsGuide2CuraSettingsGuide.py», line 9, in
2022-05-05 11:43:17,990 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from PyQt5.QtCore import pyqtSlot, pyqtProperty, pyqtSignal, QObject, QUrl # To expose data to the GUI and adjust the size of setting tooltips.
2022-05-05 11:43:17,990 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: ModuleNotFoundError: No module named ‘PyQt5’
2022-05-05 11:43:17,991 — WARNING — [MainThread] UM.PluginRegistry._populateMetaData [821]: Could not find plugin SettingsGuide2
2022-05-05 11:43:17,993 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Exception: Import error loading module SettingsGuide2
2022-05-05 11:43:17,994 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Traceback (most recent call last):
2022-05-05 11:43:17,994 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «UMPluginRegistry.py», line 727, in _findPlugin
2022-05-05 11:43:17,994 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: module = imp.load_module(plugin_id, file, path, desc) # type: ignore #MyPy gets the wrong output type from imp.find_module for some reason.
2022-05-05 11:43:17,994 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 245, in load_module
2022-05-05 11:43:17,995 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 217, in load_package
2022-05-05 11:43:17,995 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 719, in _load
2022-05-05 11:43:17,995 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 688, in _load_unlocked
2022-05-05 11:43:17,995 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 883, in exec_module
2022-05-05 11:43:17,995 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 241, in _call_with_frames_removed
2022-05-05 11:43:17,996 — ERROR — [MainThread] UM.PluginRegistry.findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsSettingsGuide2SettingsGuide2_init.py», line 7, in
2022-05-05 11:43:17,996 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from . import CuraSettingsGuide
2022-05-05 11:43:17,996 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsSettingsGuide2SettingsGuide2CuraSettingsGuide.py», line 9, in
2022-05-05 11:43:17,996 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from PyQt5.QtCore import pyqtSlot, pyqtProperty, pyqtSignal, QObject, QUrl # To expose data to the GUI and adjust the size of setting tooltips.
2022-05-05 11:43:17,997 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: ModuleNotFoundError: No module named ‘PyQt5’
2022-05-05 11:43:17,997 — ERROR — [MainThread] UM.PluginRegistry.removeCorruptedPluginMessage [527]: Exception: Error loading plugin SettingsGuide2:
2022-05-05 11:43:17,997 — ERROR — [MainThread] UM.PluginRegistry.removeCorruptedPluginMessage [527]: NoneType: None
2022-05-05 11:43:18,010 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Exception: Import error loading module StartOptimiser
2022-05-05 11:43:18,010 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Traceback (most recent call last):
2022-05-05 11:43:18,011 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «UMPluginRegistry.py», line 727, in _findPlugin
2022-05-05 11:43:18,011 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: module = imp.load_module(plugin_id, file, path, desc) # type: ignore #MyPy gets the wrong output type from imp.find_module for some reason.
2022-05-05 11:43:18,011 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 245, in load_module
2022-05-05 11:43:18,011 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 217, in load_package
2022-05-05 11:43:18,012 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 719, in _load
2022-05-05 11:43:18,012 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 688, in _load_unlocked
2022-05-05 11:43:18,012 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 883, in exec_module
2022-05-05 11:43:18,012 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 241, in _call_with_frames_removed
2022-05-05 11:43:18,012 — ERROR — [MainThread] UM.PluginRegistry.findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsStartOptimiserStartOptimiser_init.py», line 4, in
2022-05-05 11:43:18,013 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from . import StartOptimiser
2022-05-05 11:43:18,013 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsStartOptimiserStartOptimiserStartOptimiser.py», line 10, in
2022-05-05 11:43:18,013 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from PyQt5.QtCore import QObject
2022-05-05 11:43:18,013 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: ModuleNotFoundError: No module named ‘PyQt5’
2022-05-05 11:43:18,014 — WARNING — [MainThread] UM.PluginRegistry._populateMetaData [821]: Could not find plugin StartOptimiser
2022-05-05 11:43:18,016 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Exception: Import error loading module StartOptimiser
2022-05-05 11:43:18,016 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: Traceback (most recent call last):
2022-05-05 11:43:18,016 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «UMPluginRegistry.py», line 727, in _findPlugin
2022-05-05 11:43:18,017 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: module = imp.load_module(plugin_id, file, path, desc) # type: ignore #MyPy gets the wrong output type from imp.find_module for some reason.
2022-05-05 11:43:18,017 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 245, in load_module
2022-05-05 11:43:18,017 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «imp.py», line 217, in load_package
2022-05-05 11:43:18,017 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 719, in _load
2022-05-05 11:43:18,017 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 688, in _load_unlocked
2022-05-05 11:43:18,018 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 883, in exec_module
2022-05-05 11:43:18,018 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «», line 241, in _call_with_frames_removed
2022-05-05 11:43:18,018 — ERROR — [MainThread] UM.PluginRegistry.findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsStartOptimiserStartOptimiser_init.py», line 4, in
2022-05-05 11:43:18,018 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from . import StartOptimiser
2022-05-05 11:43:18,019 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: File «C:UsersdcoopAppDataRoamingcura5.0pluginsStartOptimiserStartOptimiserStartOptimiser.py», line 10, in
2022-05-05 11:43:18,019 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: from PyQt5.QtCore import QObject
2022-05-05 11:43:18,019 — ERROR — [MainThread] UM.PluginRegistry._findPlugin [729]: ModuleNotFoundError: No module named ‘PyQt5’
2022-05-05 11:43:18,020 — ERROR — [MainThread] UM.PluginRegistry.removeCorruptedPluginMessage [527]: Exception: Error loading plugin StartOptimiser:
2022-05-05 11:43:18,020 — ERROR — [MainThread] UM.PluginRegistry.removeCorruptedPluginMessage [527]: NoneType: None
2022-05-05 11:43:18,022 — DEBUG — [MainThread] UM.PluginRegistry.loadPlugins [417]: Loading all plugins took 2.9966700077056885 seconds
2022-05-05 11:43:18,033 — INFO — [MainThread] UM.VersionUpgradeManager.upgrade [163]: Looking for old configuration files to upgrade.
2022-05-05 11:43:18,087 — INFO — [MainThread] UM.VersionUpgradeManager.upgrade [177]: Checking and performing updates took 0.059400081634521484
2022-05-05 11:43:18,098 — INFO — [MainThread] UM.Qt.QtApplication.startSplashWindowPhase [254]: Completed loading preferences.
2022-05-05 11:43:18,123 — INFO — [MainThread] UM.Qt.QtApplication.startSplashWindowPhase [289]: Created system tray icon.
2022-05-05 11:43:21,938 — DEBUG — [MainThread] UM.Settings.ContainerRegistry.loadAllMetadata [534]: Loading metadata into container registry took 3.799590587615967 seconds
2022-05-05 11:43:21,951 — DEBUG — [MainThread] cura.Scene.CuraSceneController.setActiveBuildPlate [142]: Select build plate: 0
2022-05-05 11:43:21,958 — INFO — [MainThread] cura.CuraApplication.run [815]: Initializing machine error checker
2022-05-05 11:43:22,044 — WARNING — [MainThread] UM.Settings.DefinitionContainer._preprocessParsedJson [299]: Unable to override setting filter_out_tiny_gaps
2022-05-05 11:43:22,173 — WARNING — [MainThread] LocalContainerProvider.LocalContainerProvider._saveCachedDefinition [300]: The definition cache for definition creality_cr6se failed to pickle.
2022-05-05 11:43:22,183 — INFO — [MainThread] cura.UI.MachineActionManager.addDefaultMachineActions [74]: Default machine actions added for machine definition [creality_cr6se]
2022-05-05 11:43:22,202 — WARNING — [MainThread] UM.Settings.DefinitionContainer._preprocessParsedJson [299]: Unable to override setting filter_out_tiny_gaps
2022-05-05 11:43:22,324 — WARNING — [MainThread] LocalContainerProvider.LocalContainerProvider._saveCachedDefinition [300]: The definition cache for definition creality_base failed to pickle.
2022-05-05 11:43:22,440 — INFO — [MainThread] cura.Settings.GlobalStack.addExtruder [192]: Extruder[creality_base_extruder_0 #2] added to [Creality CR-6 SE] at position [0]
2022-05-05 11:43:22,483 — INFO — [MainThread] FirmwareUpdateChecker.FirmwareUpdateChecker.checkFirmwareVersion [79]: No machine with name Creality CR-6 SE in list of firmware to check.
2022-05-05 11:43:22,676 — DEBUG — [MainThread] cura.Machines.ContainerTree.getitem [120]: Adding container tree for creality_cr6se took 0.18052220344543457 seconds.
2022-05-05 11:43:22,691 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: ChangeAtZ
2022-05-05 11:43:22,695 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: ColorMix
2022-05-05 11:43:22,700 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: CreateThumbnail
2022-05-05 11:43:22,705 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: DisplayFilenameAndLayerOnLCD
2022-05-05 11:43:22,711 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: DisplayProgressOnLCD
2022-05-05 11:43:22,715 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: FilamentChange
2022-05-05 11:43:22,719 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: InsertAtLayerChange
2022-05-05 11:43:22,724 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: PauseAtHeight
2022-05-05 11:43:22,729 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: RetractContinue
2022-05-05 11:43:22,732 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: SearchAndReplace
2022-05-05 11:43:22,741 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: Stretch
2022-05-05 11:43:22,745 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: TimeLapse
2022-05-05 11:43:22,749 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [206]: Begin loading of script: UsePreviousProbeMeasurements
2022-05-05 11:43:22,791 — WARNING — [MainThread] UM.Settings.InstanceContainer.setProperty [377]: Tried to set value of the setting speed_equalize_flow_enabled, but it has no SettingInstance in this InstanceContainer CF PLA Fine Print #2 or its SettingDefinition Creality Base Printer
2022-05-05 11:43:22,928 — WARNING — [MainThread] LocalContainerProvider.LocalContainerProvider._saveCachedDefinition [300]: The definition cache for definition fdmprinter failed to pickle.
2022-05-05 11:43:22,950 — INFO — [MainThread] cura.CuraApplication.run [820]: Initializing machine manager
2022-05-05 11:43:22,952 — INFO — [MainThread] cura.CuraApplication.run [825]: Initializing container manager
2022-05-05 11:43:22,980 — DEBUG — [MainThread] cura.OAuth2.AuthorizationService.loadAuthDataFromPreferences [258]: Attempting to load the auth data from preferences.
2022-05-05 11:43:22,984 — WARNING — [MainThread] UM.OutputDevice.OutputDeviceManager.removeOutputDevice [235]: Could not find output device with id digital_factory to remove
2022-05-05 11:43:23,055 — DEBUG — [MainThread] UM.Scene.Camera._preferencesChanged [255]: Changing perspective mode to perspective.
2022-05-05 11:43:23,164 — DEBUG — [MainThread] cura.Machines.MachineErrorChecker._rescheduleCheck [156]: New error check scheduled.
2022-05-05 11:43:23,332 — INFO — [MainThread] cura.Machines.MachineErrorChecker._setResult [215]: Error check finished, result = False, time = 0.2s
2022-05-05 11:43:23,342 — DEBUG — [MainThread] UM.Qt.Bindings.Theme.load [176]: Loading theme file: C:Program FilesUltimaker Cura 5.0.0sharecuraresourcesthemescura-lighttheme.json
2022-05-05 11:43:23,519 — DEBUG — [MainThread] UM.Qt.Bindings.Theme.load [306]: Loaded theme C:Program FilesUltimaker Cura 5.0.0sharecuraresourcesthemescura-light
2022-05-05 11:43:23,519 — INFO — [MainThread] UM.Qt.Bindings.Theme.load [307]: System’s em size is 13px.
2022-05-05 11:43:24,489 — WARNING — [MainThread] UM.Qt.Bindings.MainWindow.init [82]: Could not restore to previous location on screen, since the sizes or number of monitors have changed since then
2022-05-05 11:43:24,491 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin._createView [344]: Creating post processing plugin view.
2022-05-05 11:43:24,634 — DEBUG — [MainThread] PostProcessingPlugin.PostProcessingPlugin._createView [354]: Post processing view created.
2022-05-05 11:43:24,752 — WARNING — [MainThread] UM.Qt.Bindings.Theme.getIcon [142]: The icon ‘search’ is deprecated. Please use icon ‘Magnifier’ instead.
2022-05-05 11:43:24,755 — WARNING — [MainThread] UM.Qt.QtApplication.__onQmlWarning [431]: file:///C:/Program Files/Ultimaker Cura 5.0.0/share/cura/resources/qml/Settings/SettingView.qml:40:9: QML TextField: Binding loop detected for property «implicitHeight»
2022-05-05 11:43:24,755 — WARNING — [MainThread] UM.Qt.QtApplication.__onQmlWarning [431]: file:///C:/Program Files/Ultimaker Cura 5.0.0/share/cura/resources/qml/Settings/SettingView.qml:40:9: QML TextField: Binding loop detected for property «implicitHeight»
2022-05-05 11:43:24,825 — WARNING — [MainThread] UM.Qt.QtApplication.__onQmlWarning [431]: file:///C:/Program Files/Ultimaker Cura 5.0.0/PyQt6/Qt6/qml/UM/MenuItem.qml:13:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 66. Use ‘sequences: [ ]’ to bind to all of them.
2022-05-05 11:43:24,831 — WARNING — [MainThread] UM.Qt.QtApplication.__onQmlWarning [431]: file:///C:/Program Files/Ultimaker Cura 5.0.0/PyQt6/Qt6/qml/UM/MenuItem.qml:13:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 12. Use ‘sequences: [ ]’ to bind to all of them.
2022-05-05 11:43:24,832 — WARNING — [MainThread] UM.Qt.QtApplication.__onQmlWarning [431]: file:///C:/Program Files/Ultimaker Cura 5.0.0/PyQt6/Qt6/qml/UM/MenuItem.qml:13:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 11. Use ‘sequences: [ ]’ to bind to all of them.
2022-05-05 11:43:25,012 — WARNING — [MainThread] UM.Qt.QtApplication.__onQmlWarning [431]: file:///C:/Program Files/Ultimaker Cura 5.0.0/share/cura/resources/qml/ObjectSelector.qml:28:9: QML Button: Binding loop detected for property «height»
2022-05-05 11:43:25,119 — DEBUG — [MainThread] cura.Machines.Models.NozzleModel._update [28]: Updating NozzleModel.
2022-05-05 11:43:25,426 — DEBUG — [MainThread] UM.Controller.setActiveStage [180]: Setting active stage to PrepareStage
2022-05-05 11:43:25,514 — DEBUG — [MainThread] cura.Machines.Models.NozzleModel._update [28]: Updating NozzleModel.
2022-05-05 11:43:25,790 — DEBUG — [MainThread] UM.Controller.setActiveView [108]: Setting active view to SolidView
2022-05-05 11:43:25,800 — DEBUG — [MainThread] ModelChecker.ModelChecker._createView [118]: Creating model checker view.
2022-05-05 11:43:25,807 — DEBUG — [MainThread] ModelChecker.ModelChecker._createView [127]: Model checker view created.
2022-05-05 11:43:25,808 — DEBUG — [MainThread] SliceInfoPlugin.SliceInfo._createDialog [76]: Creating dialog [MoreInfoWindow.qml]
2022-05-05 11:43:25,851 — DEBUG — [MainThread] cura.CuraApplication.run [866]: Booting Cura took 11.653780698776245 seconds
2022-05-05 11:43:25,851 — DEBUG — [JobQueueWorker [0]] cura.Machines.ContainerTree.run [174]: Started background loading of MachineNodes
2022-05-05 11:43:25,887 — DEBUG — [MainThread] cura.Machines.Models.CustomQualityProfilesDropDownMenuModel._update [33]: Updating CustomQualityProfilesDropDownMenuModel.
2022-05-05 11:43:25,898 — DEBUG — [MainThread] cura.Machines.Models.QualityProfilesDropDownMenuModel._update [58]: Updating QualityProfilesDropDownMenuModel.
2022-05-05 11:43:26,095 — DEBUG — [MainThread] cura.Machines.Models.QualityProfilesDropDownMenuModel._update [58]: Updating QualityProfilesDropDownMenuModel.
2022-05-05 11:43:26,097 — DEBUG — [MainThread] cura.Machines.Models.CustomQualityProfilesDropDownMenuModel._update [33]: Updating CustomQualityProfilesDropDownMenuModel.
2022-05-05 11:43:26,353 — DEBUG — [JobQueueWorker [0]] cura.Machines.ContainerTree.run [185]: All MachineNode loading completed
2022-05-05 11:43:26,787 — WARNING — [MainThread] UM.Qt.QtApplication.__onQmlWarning [431]: file:///C:/Program Files/Ultimaker Cura 5.0.0/share/cura/resources/qml/PrintSetupSelector/PrintSetupSelector.qml:28:17: QML PrintSetupSelectorHeader: Qt Quick Layouts: Polish loop detected. Aborting after two iterations.
2022-05-05 11:43:26,937 — DEBUG — [MainThread] UM.Qt.QtRenderer._initialize [211]: Support for Vertex Array Objects: True
2022-05-05 11:43:26,957 — DEBUG — [MainThread] UM.View.GL.OpenGL.init [115]: Initialized OpenGL subsystems.
2022-05-05 11:43:26,957 — DEBUG — [MainThread] UM.View.GL.OpenGL.init [116]: OpenGL Version: 4.1.0 NVIDIA 496.49
2022-05-05 11:43:26,957 — DEBUG — [MainThread] UM.View.GL.OpenGL.init [117]: OpenGL Vendor: NVIDIA Corporation
2022-05-05 11:43:26,958 — DEBUG — [MainThread] UM.View.GL.OpenGL.init [118]: OpenGL Renderer: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2
2022-05-05 11:43:26,958 — DEBUG — [MainThread] UM.View.GL.OpenGL.init [119]: GLSL Version: 4.0.0
2022-05-05 11:43:26,963 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0shareuraniumresourcesshadersdefault.shader]…
2022-05-05 11:43:26,969 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0shareuraniumresourcesshadersselection.shader]…
2022-05-05 11:43:26,973 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0shareuraniumresourcesshadersselect_face.shader]…
2022-05-05 11:43:26,976 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0shareuraniumresourcesshadersdefault.shader]…
2022-05-05 11:43:26,977 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0shareuraniumresourcesshaderscomposite.shader]…
2022-05-05 11:43:26,982 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0sharecuraresourcesshadersoverhang.shader]…
2022-05-05 11:43:26,987 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0sharecuraresourcesshadersstriped.shader]…
2022-05-05 11:43:26,992 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0sharecuraresourcesshaderstransparent_object.shader]…
2022-05-05 11:43:26,996 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0sharecuraresourcesshadersstriped.shader]…
2022-05-05 11:43:26,997 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0sharecuraresourcesshadersxray.shader]…
2022-05-05 11:43:27,001 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0sharecuraresourcesshadersxray_composite.shader]…
2022-05-05 11:43:27,005 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0shareuraniumresourcesshadersdefault.shader]…
2022-05-05 11:43:27,006 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0sharecuraresourcesshadersgrid.shader]…
2022-05-05 11:43:27,010 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0shareuraniumresourcesshadersplatform.shader]…
2022-05-05 11:43:27,022 — DEBUG — [MainThread] UM.View.GL.ShaderProgram.load [61]: Loading [C:Program FilesUltimaker Cura 5.0.0sharecuraresourcesshadersxray.shader]…
2022-05-05 11:43:37,874 — DEBUG — [MainThread] cura.AutoSave._onTimeout [64]: Autosaving preferences, instances and profiles took 0.012451171875 seconds

Источник

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Closed

reibuehl opened this issue

Apr 4, 2019

· 59 comments

Comments

Application Version
3.6 and 4.0

Platform
Windows 10 Professional 64-bit, Version 1809

Printer
Ultimaker 2

Steps to Reproduce
After installing Windows 10 Version 1809, start Cura

Actual Results
Cura doesn’t start even if the same Cura installation has started on the same PC before. After setting «Windows 8» compatibility on the Cura.exe, Cura starts fine again.

Expected results
Cura should start without the need for the Windows 8 compatibility beeing set manually.

Additional Information
See https://community.ultimaker.com/topic/27056-cura-36-and-40-dont-start/ for more reports of the same issue.

Maybe do you have a log file of Cura starting unsuccessfully (without the compatibility mode set)?

Copy link

Contributor

Author

The files %AppData%curastderr.log and %AppData%curastdout.log are created when I try to start cura without the compatibility flag but they stay empty. The file %AppData%cura4.0cura.log is not created. The process is visible in task manager but no UI components are shown — not even the splash screen.

Very weird! Then maybe running this via the command line would give a bit more output to debug what’s going on. Here’s some instructions, though you seem to know your salt but just in case:

Press Win+R.
Type cmd and press enter.
In the command window, type C:Program FilesUltimaker Cura 4.0Cura.exe (or wherever you installed it).

I’d expect it to produce something in STDCOUT then… 🤔

Copy link

Contributor

Author

Unfortunately no output at all (see attached screenshot). The command prompt comes back very fast. Process Explorer shows that the process is running but no output on the command line.

Run eventvwr.msc and check Windows LogsApplication for any Cura-related entries.

fwiw I’m running Cura 3.6 and 4.0 under Windows 10 64-bit edition (17763) without any such issues.

Copy link

Contributor

Author

I checked the Application event log but no entries there either.

We’re also getting this bug report via the support channel of Ultimaker (who gets it via resellers who gets it from customers).

If it helps, my issue was actually caused by the fact my laptop has multiple graphics chipsets. My laptop has both Intel Graphics on board but also a dedicated Nvidia 1060 as well. If I configured the app to always start using the Intel Chipset it opens fine, it only has an issue with the Nvidia chipset.

It just seems to be this shared setup that is the issue as my desktop PC only has an Nvidia Card and that opens fine.

Thanks
Jamie.

It also happens on my notebook with Intel Core i7-8550u and just Intel UHD graphics 620.

This bug happened to me in 3.5, 3.6 and 4.0 (and it also takes an eternity to open :/ )

Thanks in advance.

It also happens on my notebook with Intel Core i7-8550u and just Intel UHD graphics 620.

This bug happened to me in 3.5, 3.6 and 4.0 (and it also takes an eternity to open :/ )

Thanks in advance.

yes. me too on my microsoft surface 2017 model (windows 10)

If it helps, my issue was actually caused by the fact my laptop has multiple graphics chipsets. My laptop has both Intel Graphics on board but also a dedicated Nvidia 1060 as well. If I configured the app to always start using the Intel Chipset it opens fine, it only has an issue with the Nvidia chipset. It just seems to be this shared setup that is the issue as my desktop PC only has an Nvidia Card and that opens fine. Thanks Jamie.

I think I have this problem, too. How do you make it use Intel rather than Nvidia?

I disabled Intel UHD 620 in the control panel and Cura 4.0 now runs. #5699

Copy link

Contributor

Author

I have the problem on a Desktop PC with only one display adapter according to device manager. It is an Intel HD Graphics 630.

Same here. (MS Surface Pro 4; Intel HD Graphic with dual screen setup)
Only extra Plugin is OctoPrint.

same here (i3-6100 with integrated Intel GPU), Windows 10 x64.
Tested with Cura 3.6 and 4.1

Any luck with this? interestingly i also have intel UHD620 as graphic card (notebook), so this issue might be related to it

No luck for me. I still have to disable UHD 620 when I want to use Cura.

@Donner-Party you have another graphic card right? i dont think thats a option for me, i made it work with win7 compatibility, but its kinda slow

Yes. My laptop has dual graphics processors.

This thread on the Ultimaker forums seems to be confirming an issue with Intel GPUs. https://community.ultimaker.com/topic/29138-cura-421-does-not-start-and-makes-41-dead-as-well/?tab=comments#comment-245633

I have a SurfaceBook v2. This has an Nvidia GTX 1060 in the detachable keyboard and an Intel UHD 620 in the screen. When the screen is detached (Intel GPU only) Cura will not start. When connected to the keyboard it starts fine.

I did have an issue where the Nvidia adapter would stop responding. When this happened, again with only Intel GPU available, Cura would not start.

When Cura fails to start like this, there is no log information written.

In my case, I have 100% repro for having it start or fail under these conditions.

Yup, same here on a Surface Pro 2017
Cura starts up and runs a process in the background but never creates a window

TaskManager Process view

Same issue on Windows 10/64 laptop with just the Intel HD Graphics 520 GPU. I’ve only been able to get Cura to open a couple times, but some article I’d seen had mentioned trying over and over — so I’ve been attempting to open it about a dozen times both as administrator and not, before wiping them out in Task Manager and starting over. It has worked a couple times but the method may have nothing to do with it.

Today, I succeeded by running in Win8 compatibility mode and hitting Test the program 3-times (without killing the failed processes). Finally got the Cura splash screen to load on the third try and the program to open. I’ll try to come back and edit this comment if I reboot and succeed with same method a few times.

This issue still exists in 4.3!
Is this ever going to be addressed?

I have to revert to 4.1 (again!!!) in order to have Cura running on my MS Surface Pro 2017

We’re trying to fix this. Since 4.3 it also started reproducing on our test printers. We still have no idea what’s causing it though and it hasn’t happened yet on any computer with the debugging tools to fix it. And it’s a bit of a phantom bug, too, as is evident by you reporting that it works in 4.1 but not in 4.3 while the original issue was reported for 3.6 and 4.0.

This is happening with me on my fully updated Surface Book 2 (Core i5 with integrated Intel graphics only) with Windows 10 and Cura 4.1. If I start Cura, the Cura process appears in task manager, but never opens a window. If I start another Cura instance, it does the same thing. Restarting Windows or power-cycling the machine don’t fix the issue. I’ll see if reinstalling Cura does.

Update: Uninstalling Cura (full uninstall, including configuration files), restarting Windows, and reinstalling Cura doesn’t fix the issue for me. However, reinstalling, then setting Windows 8 compatibility mode did: https://community.ultimaker.com/topic/27056-cura-36-and-40-dont-start/?do=findComment&comment=236568

Hi @Adminius , thanks for the report. Please report again if you have any further problems related to this.

Copy link

Contributor

Author

Hi @reibuehl , thanks for the report, sorry it didn’t help you.

Could you also try to run cura but then via commandline? Some things are logged before the logging plugins are loaded (so they don’t get written to the semi permanent logs).

Copy link

Contributor

Author

Hi @nallath , if I try that, the command prompt returns immediately. No logging there. The Cura.exe seems to just run the python stuff that then shows the splash screen and everything after. Should I create a short video of the behavior?

Hi, I had a similar problem with another slicer.
You have to go to the system registry, delete the records and leave that window open.
Open Cura, go to the registration window and update data, if there is an error it will appear there.

Similar issue here. Cura 4.4.1 installed fine on Win 8.1 64bit. Upon execution, it hangs during interface load, then shuts down. Log file attached. Thanks in advance for any advise.
cura.log

Try running curaengine.exe and then cura.exe … it happened to me in the latest version and I only did it once, then I charge well.

Cesar,

Thank you very much for the quick reply and advise. Unfortunately, it did not fix my problem:

Do you know anything else I might try?

Best Regards,

Bob

have you tried this? it was the best result for me

Hi Cesar,

I was using those settings but they did not get the program to start.

I found my solution. I had to turn on the high performance settings on my NVIDEA graphics processor. Once I did that, it started up properly.

Maybe this info will be helpful to others. Thanks for your help.

Bob

Copy link

Contributor

Author

I tried setting my INTEL HD graphics to high performance but Cura still doesn’t start. All versions from 3.x to 4.4.1. Cura 15.04 runs fine without issues.

reibuehl

changed the title
[3.6 and 4.0] Cura doesn’t start on Windows 10 Pro 64bit unless Windows 8 Compatibility is selected

[3.6 to 4.4.1] Cura doesn’t start on Windows 10 Pro 64bit unless Windows 8 Compatibility is selected

Feb 6, 2020

For me clicking like 20 times on the program eventually opens it, tho honestly i gave up on cura (at least on my personal laptop).

Probably a compatibility issue with the INTEL HD driver. That failed on my LT as well. I also have an INVIDEA GeForce card installed. Enabling 3D acceleration on the GeForce fixed my issue.

Glad you can run with 15.4

As far as we know, this issue is fixed in the 4.5 version. We’ll release a beta today, so feel free to give that a try. It’s a complicated issue since a lot of people are reporting different things under the same denominator.

Copy link

Contributor

Author

I just installed 4.5 beta and it still fails to start on my HP Laptop. Should I try any special settings or is there anything I can do to help you fix this issue?

Hi Reiner,

I’m not affiliated with Cura; just another user like you. I also happened to have the same issue on my HP Envy LT (for any version up to 4.4.1; haven’t loaded 4.5 beta as yet). What worked for me was to go into the NVidea control panel; Manage 3D Settings and select High-performance NVIDIA processor as the preferred graphics processor on the Global Setting tab. Auto-select will default to integrated graphics and GUI load will fail. Apparently the imbedded graphics processor is not up to the task.

Hope this helps!

Good luck,

Bob

Copy link

Contributor

Author

@BobBuenzow I have INtel HD graphics, no NVidia. I tried what seemed to be the equivalent in the Intel driver of what you suggested already earlier. My last comment was meant for @Ghostkeeper who seems to be one of the developers. I tried 4.5beta and was wondering if I can create some logs that help him and the other developers to identify the root cause of why it does crash with the Intel HD graphics on the HP Elitebook.

@riebuehl there are two things I’d like to ask you to try:

Update your Intel graphics drivers. I think we’ve probably asked you this before, but a few weeks ago Intel came with an update to their graphics drivers that specifically fixed one of our issues that had this symptom.
If Cura still doesn’t start after that, kill the process from the task manager and please find the file C:Users<riebuehl>AppDataRoamingcura4.5cura.cfg and open that with a text editor. Under the header [view], add the following line:
```
opengl_version_detect = force_modern
```
Save that file and try starting Cura again. Does it start then?

Copy link

Contributor

Author

@Ghostkeeper I did already have the latest drivers from the laptop vendor but did now manually install the newer generic graphics drivers from Intel. Version 10.18.10.5100 was the latest Intel had for the Intel Graphics HD 4000. With this driver version, Cura 4.4.1 and 4.5beta both start.
I will verify if this also solves the issue on my other system that has a different configuration on Saturday and close the issue then if successful.

@Ghostkeeper Cura 4.5 states something was fixed with Intel GFX drivers.
Is this about this issue? And what is the related commit?

Copy link

Contributor

Author

Installing the latest (as of February 2020) graphics card drivers from Intel fixed the issue for me on both systems where I had the issue. One had the Intel Graphics HD 4000 and the other the Intel Graphics HD 630.

Cura 4.5 states something was fixed with Intel GFX drivers.
Is this about this issue? And what is the related commit?

We’ve fixed multiple things in 4.5 that are related to Cura not starting. One of them is the workaround I posted above with force_modern. Related commits are here: Ultimaker/Uranium#565

Hi all,

Cura 4.6.2 on Windows 7 on an HP G72 laptop w/ szitchable GPUs :

Intel GMA HD (PCIVEN_8086&DEV_0046&SUBSYS_143A103C&REV_02)
AMD-ATI Radeon HD 5470 (PCIVEN_1002&DEV_68E0&SUBSYS_143A103C&REV_00).

Cura wouldn’t even start w/ AMD : process visible a few seconds, then disappears with no log anywhere,

With Intel, it starts but at first click, it hangs w/ standard Windows popup «recherche une solution» («looking for a solution») then «fermer l’application» («close application»).

So for me this software is just useless…

Did you try Windows 8 Compatibility? Or the workaround I mentioned above?

Thanks Ghostkeeper for your answer !

I’ve left the issue for now, got another machine on which Cura works OK and no time to test. This machine is usually on Linux and rarely booted on Windows ^-^ But this week-end I’ll probably have enough time to test both workarounds. I don’t know if there is a W8 compat setting on W7, but I’ll look… but the force_modern workaround seems best bet…

Источник

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Closed

reibuehl opened this issue

Apr 4, 2019

· 59 comments

Comments

Application Version
3.6 and 4.0

Platform
Windows 10 Professional 64-bit, Version 1809

Printer
Ultimaker 2

Steps to Reproduce
After installing Windows 10 Version 1809, start Cura

Actual Results
Cura doesn’t start even if the same Cura installation has started on the same PC before. After setting «Windows 8» compatibility on the Cura.exe, Cura starts fine again.

Expected results
Cura should start without the need for the Windows 8 compatibility beeing set manually.

Additional Information
See https://community.ultimaker.com/topic/27056-cura-36-and-40-dont-start/ for more reports of the same issue.

Maybe do you have a log file of Cura starting unsuccessfully (without the compatibility mode set)?

Copy link

Contributor

Author

Very weird! Then maybe running this via the command line would give a bit more output to debug what’s going on. Here’s some instructions, though you seem to know your salt but just in case:

Press Win+R.
Type cmd and press enter.
In the command window, type C:Program FilesUltimaker Cura 4.0Cura.exe (or wherever you installed it).

I’d expect it to produce something in STDCOUT then… 🤔

Copy link

Contributor

Author

Unfortunately no output at all (see attached screenshot). The command prompt comes back very fast. Process Explorer shows that the process is running but no output on the command line.

Run eventvwr.msc and check Windows LogsApplication for any Cura-related entries.

fwiw I’m running Cura 3.6 and 4.0 under Windows 10 64-bit edition (17763) without any such issues.

Copy link

Contributor

Author

I checked the Application event log but no entries there either.

We’re also getting this bug report via the support channel of Ultimaker (who gets it via resellers who gets it from customers).

It just seems to be this shared setup that is the issue as my desktop PC only has an Nvidia Card and that opens fine.

Thanks
Jamie.

It also happens on my notebook with Intel Core i7-8550u and just Intel UHD graphics 620.

This bug happened to me in 3.5, 3.6 and 4.0 (and it also takes an eternity to open :/ )

Thanks in advance.

It also happens on my notebook with Intel Core i7-8550u and just Intel UHD graphics 620.

This bug happened to me in 3.5, 3.6 and 4.0 (and it also takes an eternity to open :/ )

Thanks in advance.

yes. me too on my microsoft surface 2017 model (windows 10)

If it helps, my issue was actually caused by the fact my laptop has multiple graphics chipsets. My laptop has both Intel Graphics on board but also a dedicated Nvidia 1060 as well. If I configured the app to always start using the Intel Chipset it opens fine, it only has an issue with the Nvidia chipset. It just seems to be this shared setup that is the issue as my desktop PC only has an Nvidia Card and that opens fine. Thanks Jamie.

I think I have this problem, too. How do you make it use Intel rather than Nvidia?

I disabled Intel UHD 620 in the control panel and Cura 4.0 now runs. #5699

Copy link

Contributor

Author

I have the problem on a Desktop PC with only one display adapter according to device manager. It is an Intel HD Graphics 630.

Same here. (MS Surface Pro 4; Intel HD Graphic with dual screen setup)
Only extra Plugin is OctoPrint.

same here (i3-6100 with integrated Intel GPU), Windows 10 x64.
Tested with Cura 3.6 and 4.1

Any luck with this? interestingly i also have intel UHD620 as graphic card (notebook), so this issue might be related to it

No luck for me. I still have to disable UHD 620 when I want to use Cura.

@Donner-Party you have another graphic card right? i dont think thats a option for me, i made it work with win7 compatibility, but its kinda slow

Yes. My laptop has dual graphics processors.

I did have an issue where the Nvidia adapter would stop responding. When this happened, again with only Intel GPU available, Cura would not start.

When Cura fails to start like this, there is no log information written.

In my case, I have 100% repro for having it start or fail under these conditions.

Yup, same here on a Surface Pro 2017
Cura starts up and runs a process in the background but never creates a window

TaskManager Process view

This issue still exists in 4.3!
Is this ever going to be addressed?

I have to revert to 4.1 (again!!!) in order to have Cura running on my MS Surface Pro 2017

Hi @Adminius , thanks for the report. Please report again if you have any further problems related to this.

Copy link

Contributor

Author

Hi @reibuehl , thanks for the report, sorry it didn’t help you.

Could you also try to run cura but then via commandline? Some things are logged before the logging plugins are loaded (so they don’t get written to the semi permanent logs).

Copy link

Contributor

Author

Similar issue here. Cura 4.4.1 installed fine on Win 8.1 64bit. Upon execution, it hangs during interface load, then shuts down. Log file attached. Thanks in advance for any advise.
cura.log

Try running curaengine.exe and then cura.exe … it happened to me in the latest version and I only did it once, then I charge well.

Cesar,

Thank you very much for the quick reply and advise. Unfortunately, it did not fix my problem:

Do you know anything else I might try?

Best Regards,

Bob

have you tried this? it was the best result for me

Hi Cesar,

I was using those settings but they did not get the program to start.

I found my solution. I had to turn on the high performance settings on my NVIDEA graphics processor. Once I did that, it started up properly.

Maybe this info will be helpful to others. Thanks for your help.

Bob

Copy link

Contributor

Author

I tried setting my INTEL HD graphics to high performance but Cura still doesn’t start. All versions from 3.x to 4.4.1. Cura 15.04 runs fine without issues.

reibuehl

changed the title
[3.6 and 4.0] Cura doesn’t start on Windows 10 Pro 64bit unless Windows 8 Compatibility is selected

[3.6 to 4.4.1] Cura doesn’t start on Windows 10 Pro 64bit unless Windows 8 Compatibility is selected

Feb 6, 2020

For me clicking like 20 times on the program eventually opens it, tho honestly i gave up on cura (at least on my personal laptop).

Probably a compatibility issue with the INTEL HD driver. That failed on my LT as well. I also have an INVIDEA GeForce card installed. Enabling 3D acceleration on the GeForce fixed my issue.

Glad you can run with 15.4

Copy link

Contributor

Author

I just installed 4.5 beta and it still fails to start on my HP Laptop. Should I try any special settings or is there anything I can do to help you fix this issue?

Hi Reiner,

Hope this helps!

Good luck,

Bob

Copy link

Contributor

Author

@riebuehl there are two things I’d like to ask you to try:

Update your Intel graphics drivers. I think we’ve probably asked you this before, but a few weeks ago Intel came with an update to their graphics drivers that specifically fixed one of our issues that had this symptom.
If Cura still doesn’t start after that, kill the process from the task manager and please find the file C:Users<riebuehl>AppDataRoamingcura4.5cura.cfg and open that with a text editor. Under the header [view], add the following line:
```
opengl_version_detect = force_modern
```
Save that file and try starting Cura again. Does it start then?

Copy link

Contributor

Author

@Ghostkeeper Cura 4.5 states something was fixed with Intel GFX drivers.
Is this about this issue? And what is the related commit?

Copy link

Contributor

Author

Cura 4.5 states something was fixed with Intel GFX drivers.
Is this about this issue? And what is the related commit?

We’ve fixed multiple things in 4.5 that are related to Cura not starting. One of them is the workaround I posted above with force_modern. Related commits are here: Ultimaker/Uranium#565

Hi all,

Cura 4.6.2 on Windows 7 on an HP G72 laptop w/ szitchable GPUs :

Intel GMA HD (PCIVEN_8086&DEV_0046&SUBSYS_143A103C&REV_02)
AMD-ATI Radeon HD 5470 (PCIVEN_1002&DEV_68E0&SUBSYS_143A103C&REV_00).

Cura wouldn’t even start w/ AMD : process visible a few seconds, then disappears with no log anywhere,

With Intel, it starts but at first click, it hangs w/ standard Windows popup «recherche une solution» («looking for a solution») then «fermer l’application» («close application»).

So for me this software is just useless…

Did you try Windows 8 Compatibility? Or the workaround I mentioned above?

Thanks Ghostkeeper for your answer !

Источник

UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.

SmileyNeil

ksihota

Link to post

Share on other sites

TrollingFlies

Link to post

Share on other sites

dwardio

Link to post

Share on other sites

TrollingFlies

Link to post

Share on other sites

ksihota

dwardio

Link to post

Share on other sites

D1lazarus

Link to post

Share on other sites

elirebelband

Link to post

Share on other sites

Ilanh

Link to post

Share on other sites

dwardio

Link to post

Share on other sites

Travis7s

Link to post

Share on other sites

D1lazarus

Link to post

Share on other sites

haddad

trg

Link to post

Share on other sites

eilerle1

Link to post

Share on other sites

MB3Y

Link to post

Share on other sites

Stef1885

Link to post

Share on other sites

eilerle1

Link to post

Share on other sites

MB3Y

Link to post

Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Sign in

Already have an account? Sign in here.

Источник

Может быть, у вас есть файл журнала, в котором Cura запускается неудачно (без установленного режима совместимости)?

Файлы% AppData% curastderr.log и% AppData% cura stdout.log создаются, когда я пытаюсь запустить cura без флага совместимости, но они остаются пустыми. Файл% AppData% cura 4.0 cura.log не создается. Процесс виден в диспетчере задач, но компоненты пользовательского интерфейса не отображаются — даже экран-заставка.

Очень странно! Тогда, возможно, запуск этого через командную строку даст немного больше информации для отладки того, что происходит. Вот несколько инструкций, хотя вы, кажется, знаете свою соль, но на всякий случай:

Нажмите Win + R.
Введите cmd и нажмите Enter.
В командном окне введите C:Program FilesUltimaker Cura 4.0Cura.exe (или там, где вы его установили).

Я бы ожидал, что это что-то произведет в STDCOUT …

К сожалению, вывода вообще нет (см. Приложенный снимок экрана). Командная строка возвращается очень быстро. Обозреватель процессов показывает, что процесс запущен, но в командной строке нет вывода.

Запустите eventvwr.msc и проверьте Windows LogsApplication наличие записей, связанных с Cura.

fwiw Я использую Cura 3.6 и 4.0 под 64-разрядной версией Windows 10 (17763) без каких-либо подобных проблем.

Я проверил журнал событий приложения, но там тоже нет записей.

Мы также получаем этот отчет об ошибке через канал поддержки Ultimaker (который получает его через посредников, а тот получает его от клиентов).

Если это поможет, моя проблема на самом деле была вызвана тем, что в моем ноутбуке несколько графических чипсетов. В моем ноутбуке есть как Intel Graphics, так и выделенная Nvidia 1060. Если я настроил приложение, чтобы оно всегда начинало использовать набор микросхем Intel, оно открывается нормально, проблема связана только с набором микросхем Nvidia.

Кажется, проблема заключается в общей настройке, поскольку на моем настольном ПК есть только карта Nvidia, и она открывается нормально.

благодаря
Джейми.

Это также происходит на моем ноутбуке с Intel Core i7-8550u и только с графикой Intel UHD 620.

Эта ошибка случилась со мной в 3.5, 3.6 и 4.0 (и на открытие тоже уходит целая вечность: /)

Заранее спасибо.

Это также происходит на моем ноутбуке с Intel Core i7-8550u и только с графикой Intel UHD 620.

Эта ошибка случилась со мной в 3.5, 3.6 и 4.0 (и на открытие тоже уходит целая вечность: /)

Заранее спасибо.

да. я тоже на моей модели Microsoft Surface 2017 (windows 10)

Если это поможет, моя проблема на самом деле была вызвана тем, что в моем ноутбуке несколько графических чипсетов. В моем ноутбуке есть как Intel Graphics, так и выделенная Nvidia 1060. Если я настроил приложение, чтобы оно всегда начинало использовать набор микросхем Intel, оно открывается нормально, проблема связана только с набором микросхем Nvidia. Кажется, проблема заключается в общей настройке, поскольку на моем настольном ПК есть только карта Nvidia, и она открывается нормально. Спасибо, Джейми.

Думаю, у меня тоже есть эта проблема. Как заставить его использовать Intel, а не Nvidia?

Я отключил Intel UHD 620 на панели управления, и теперь работает Cura 4.0. # 5699

У меня проблема на настольном ПК только с одним адаптером дисплея согласно диспетчеру устройств. Это Intel HD Graphics 630.

Тоже самое. (MS Surface Pro 4; Intel HD Graphic с настройкой двух экранов)
Единственный дополнительный плагин — OctoPrint.

То же самое здесь (i3-6100 со встроенным графическим процессором Intel), Windows 10 x64.
Протестировано с Cura 3.6 и 4.1

Удачи с этим? Интересно, что у меня также есть Intel UHD620 в качестве графической карты (ноутбука), поэтому эта проблема может быть связана с ней

Мне не повезло. Мне все равно нужно отключить UHD 620, когда я хочу использовать Cura.

@ Donner-Party, у вас ведь есть еще одна видеокарта? Я не думаю, что это вариант для меня, я заставил его работать с совместимостью с win7, но это довольно медленно

Да. У моего ноутбука два графических процессора.

Эта ветка на форумах Ultimaker, похоже, подтверждает проблему с графическими процессорами Intel. https://community.ultimaker.com/topic/29138-cura-421-does-not-start-and-makes-41-dead-as-well/?tab=comments#comment -245633

У меня SurfaceBook v2. У этого есть Nvidia GTX 1060 на съемной клавиатуре и Intel UHD 620 на экране. Когда экран отсоединен (только Intel GPU) Cura не запускается. При подключении к клавиатуре запускается нормально.

У меня была проблема, из-за которой адаптер Nvidia перестал отвечать. Когда это произошло, опять же при наличии только графического процессора Intel, Cura не запускалась.

Когда Cura не запускается таким образом, информация в журнал не записывается.

В моем случае у меня есть 100% репро для запуска или отказа в этих условиях.

Да, то же самое здесь, на Surface Pro 2017
Cura запускается и запускает процесс в фоновом режиме, но никогда не создает окно

Представление процесса TaskManager

Та же проблема на ноутбуке с Windows 10/64 только с графическим процессором Intel HD Graphics 520. Мне удалось заставить Cura открыться только пару раз, но в какой-то статье, которую я видел, упоминалось о попытках снова и снова — поэтому я пытался открыть ее около десятка раз как администратор, так и нет, прежде чем стереть их в диспетчере задач и начать заново. Пару раз это срабатывало, но, возможно, метод не имеет к этому никакого отношения.

Сегодня мне это удалось, запустив в режиме совместимости с Win8 и трижды нажав кнопку «Проверить программу» (без остановки сбойных процессов). Наконец-то получил заставку Cura для загрузки с третьей попытки и программу для открытия. Я постараюсь вернуться и отредактировать этот комментарий, если я перезагружусь и получу тот же метод несколько раз.

Эта проблема все еще существует в версии 4.3!
Будет ли это когда-нибудь решено?

Мне нужно вернуться на 4.1 (снова !!!), чтобы Cura работала на моем MS Surface Pro 2017

Мы пытаемся это исправить. Начиная с версии 4.3 он также начал воспроизводиться на наших тестовых принтерах. Мы до сих пор не знаем, чем это вызвано, и этого еще не произошло ни на одном компьютере с инструментами отладки, чтобы исправить это. И это тоже немного фантомная ошибка, как видно из того, что вы сообщили, что она работает в 4.1, но не в 4.3, в то время как исходная проблема была обнаружена для 3.6 и 4.0.

Это происходит со мной на моем полностью обновленном Surface Book 2 (только Core i5 со встроенной графикой Intel) с Windows 10 и Cura 4.1. Если я запускаю Cura, процесс Cura появляется в диспетчере задач, но никогда не открывает окно. Если я запускаю другой экземпляр Cura, он делает то же самое. Перезапуск Windows или выключение и включение и выключение компьютера не решают проблему. Я посмотрю, поможет ли переустановка Cura.

Обновление: удаление Cura (полное удаление, включая файлы конфигурации), перезапуск Windows и повторная установка Cura не решают проблему для меня. Однако переустановка, а затем установка режима совместимости с Windows 8 сделали: https://community.ultimaker.com/topic/27056-cura-36-and-40-dont-start/?do=findComment&comment=236568

то же самое здесь, на моем HP EliteBook 840 G5
работает в режиме совместимости с windows 8

Привет, установка в режиме совместимости

ps: если он перестал работать, запустите совместимость

Я пробовал точно такие же настройки, но даже с установленными настройками совместимости он не запускается на моем HP Elitebook 8470p со встроенной графикой Intel. Он показывает экран-заставку с начальным пользовательским интерфейсом, затем открывает большое, полностью белое окно и затем вылетает.

В моем случае это UHD 600 Intel N4000, надеюсь продолжит работать.

С включенным Intel UHD 620 следующие программы не будут работать должным образом на моем ноутбуке:

Autodesk Fusion 360
Autodesk DWG Trueview 2019
Ultimaker Cura 3.x и 4.x

До апреля 2019 года это не было проблемой. Думаю, мое горе вызвало обновление Windows.

Я думаю, нам нужно жаловаться в Intel или Microsoft, а не в Autodesk или Ultimaker / Cura. Я не нашел форума поддержки Intel, который мог бы предложить что-то лучшее, кроме обновления драйверов и перезагрузки. Когда я пытаюсь установить более старый драйвер с веб-сайта HP, он не распознается как правильный драйвер для моего ноутбука.

@smartavionics
Спасибо! у меня теперь работает (i3-6100 с 530 GPU)

Привет, @Adminius , спасибо за отчет. Сообщите еще раз, если у вас возникнут дополнительные проблемы, связанные с этим.

Привет, @reibuehl , спасибо за отчет, извините, он вам не помог.

Не могли бы вы также попробовать запустить cura, но затем через командную строку? Некоторые вещи регистрируются до загрузки плагинов ведения журнала (поэтому они не записываются в полупостоянные журналы).

Привет, @nallath , если я попробую, командная

Привет, у меня была аналогичная проблема с другим слайсером.
Вам нужно перейти в системный реестр, удалить записи и оставить это окно открытым.
Откройте Cura, перейдите в окно регистрации и обновите данные, в случае ошибки она появится там.

Аналогичная проблема здесь. Cura 4.4.1 установил нормально на Win 8.1 64bit. При выполнении зависает при загрузке интерфейса, затем отключается. Файл журнала прикреплен. Заранее благодарим за любой совет.
cura.log

Попробуйте запустить curaengine.exe, а затем cura.exe … это случилось со мной в последней версии, и я сделал это только один раз, потом заряжаюсь хорошо.

Сезар,

Большое спасибо за быстрый ответ и совет. К сожалению, мою проблему это не решило:

Вы знаете что-нибудь еще, что я могу попробовать?

С уважением,

Боб

ты пробовал это? это был лучший результат для меня

Привет Сезар,

Я использовал эти настройки, но они не запускали программу.

Я нашел свое решение. Мне пришлось включить настройки высокой производительности на моем графическом процессоре NVIDEA. Как только я это сделал, все заработало.

Возможно, эта информация будет полезна другим. Спасибо за вашу помощь.

Боб

Я попытался настроить графику INTEL HD на высокую производительность, но Cura все еще не запускается. Все версии от 3.x до 4.4.1. Cura 15.04 работает нормально без проблем.

Для меня, щелкнув примерно 20 раз на программе, в конечном итоге она открывается, хотя, честно говоря, я отказался от cura (по крайней мере, на моем личном ноутбуке).

Вероятно проблема совместимости с драйвером INTEL HD. Это не удалось и на моем LT. У меня также установлена карта INVIDEA GeForce. Включение 3D-ускорения на GeForce решило мою проблему.

Рад, что вы можете бегать с 15.4

Насколько нам известно, эта проблема исправлена в версии 4.5. Сегодня мы выпустим бета-версию, так что вы можете попробовать. Это сложный вопрос, поскольку многие люди сообщают о разных вещах под одним и тем же знаменателем.

Я только что установил бета-версию 4.5, но она все еще не запускается на моем ноутбуке HP. Стоит ли мне попробовать какие-либо специальные настройки или могу ли я что-нибудь сделать, чтобы помочь вам решить эту проблему?

Привет Райнер,

Я не связан с Cura; просто еще один пользователь вроде вас. У меня также была такая же проблема на моем HP Envy LT (для любой версии до 4.4.1; еще не загрузил бета-версию 4.5). Что сработало для меня, так это войти в панель управления NVidea; Управляйте настройками 3D и выберите Высокопроизводительный процессор NVIDIA в качестве предпочтительного графического процессора на вкладке Глобальные настройки. При автоматическом выборе по умолчанию используется встроенная графика, и загрузка графического интерфейса завершится ошибкой. Видимо встроенный графический процессор не справляется с этой задачей.

Надеюсь это поможет!

Удачи,

Боб

@BobBuenzow У меня есть графика INtel HD, нет NVidia. Я попробовал то, что в драйвере Intel казалось эквивалентом того, что вы уже предлагали ранее. Мой последний комментарий был адресован @Ghostkeeper, который, похоже, является одним из разработчиков. Я попробовал 4.5beta, и мне было интересно, могу ли я создать журналы, которые помогут ему и другим разработчикам определить основную причину, по которой происходит сбой с графикой Intel HD на HP Elitebook.

@riebuehl , я хочу попросить вас попробовать две вещи:

Обновите графические драйверы Intel. Я думаю, мы, вероятно, спрашивали вас об этом раньше, но несколько недель назад Intel представила обновление для своих графических драйверов, которое специально исправило одну из наших проблем, у которых был этот симптом.
Если после этого Cura все еще не запускается, завершите процесс из диспетчера задач, найдите файл C:Users<riebuehl>AppDataRoamingcura4.5cura.cfg и откройте его в текстовом редакторе. Под заголовком [view] добавьте следующую строку:

  opengl_version_detect = force_modern

Сохраните этот файл и попробуйте снова запустить Cura. Тогда оно начинается?

@Ghostkeeper У меня уже были последние версии драйверов от производителя ноутбука, но теперь я вручную установил новые общие графические драйверы от Intel. Версия 10.18.10.5100 была последней версией Intel для Intel Graphics HD 4000. С этой версией драйвера запускаются обе версии Cura 4.4.1 и 4.5beta.
Я проверю, решит ли это проблему и в другой моей системе, имеющей другую конфигурацию, в субботу, и в случае успеха закрою проблему.

@Ghostkeeper Cura 4.5 утверждает, что что-то было исправлено с драйверами Intel GFX.
Это об этой проблеме? И что это за коммит?

Установка последних (по состоянию на февраль 2020 года) драйверов видеокарты от Intel устранила проблему для меня в обеих системах, где у меня возникла проблема. У одного была Intel Graphics HD 4000, а у другого — Intel Graphics HD 630.

В Cura 4.5 говорится, что что-то было исправлено с драйверами Intel GFX.
Это об этой проблеме? И что это за коммит?

В 4.5 мы исправили несколько вещей, связанных с тем, что Cura не запускается. Один из них — это обходной путь, который я опубликовал выше с помощью force_modern . Связанные коммиты находятся здесь: https://github.com/Ultimaker/Uranium/pull/565

Привет всем,

Cura 4.6.2 в Windows 7 на ноутбуке HP G72 с переключаемыми графическими процессорами:

Intel GMA HD (PCI VEN_8086 & DEV_0046 & SUBSYS_143A103C & REV_02)
AMD-ATI Radeon HD 5470 (PCI VEN_1002 & DEV_68E0 & SUBSYS_143A103C & REV_00).

Cura даже не запускается с AMD: процесс отображается несколько секунд, затем исчезает без журнала,

У Intel он запускается, но при первом нажатии, он зависает со стандартным всплывающим окном Windows «recherche une solution» («ищу решение»), затем «fermer l’application» («закрыть приложение»).

Так что для меня эта программа просто бесполезна …

Вы пробовали совместимость с Windows 8? Или обходной путь, о котором я упоминал выше?

Спасибо Ghostkeeper за ваш ответ!

Я оставил проблему на данный момент, у меня есть другая машина, на которой Cura работает нормально, и нет времени на тестирование. Эта машина обычно работает под управлением Linux и редко загружается под Windows ^ — ^ Но в эти выходные у меня, вероятно, будет достаточно времени, чтобы протестировать оба обходных пути. Я не знаю, есть ли на W7 настройка совместимости с W8, но я посмотрю … но обходной путь force_modern кажется лучшим выбором …

Была ли эта страница полезной?

0 / 5 — 0 рейтинги

Источник

Решил обновить Cura. Удалил старую версию. Удалил папки cura из appdata/roaming и appdata/local. Установил свежую 4.2.1. После запуска появляется окошко загрузки, и через пару секунд пропадает. И всё… Система Win 10 64.

Есть ли ещё какие-то необходимые манипуляции, помимо удаления папок cura? Других советов сам здесь не нашёл…

Ответы на вопросы

ЧПУ токарный станок на платах 3д принтера

Андрей64

Загрузка

13.01.2023

858

Прошу подсказать, возможно ли изготовить токарный чпу станок на платах 3д принтеров?

Насколько понимаю, платы для токарных чпу не явл…

Деформация стола 3Д принтера

Добрый день. Столкнулся я с такой проблемой. Нужно было напечатать партию плоских деталек с большим (по моим собственным убежд…

Волнистые стенки.

Tortik

Загрузка

24.12.2018

22672

С того момента как я собрал принтер Ultimaker уважаемого Plastmaski, не могу избавиться от одной проблемы. Уже почти 2 кг пластика перевел на тесты. М…

Читайте в блогах

Источник

Hi Folks,

I have stumbled onto a fix for my Cura issues and wanted to share this in case it solves this for others too.

I have an Ender 3 Pro — Purchased new at beginning of December 2020 – Not sure of board version, it does not appear to have the quiet stepper motors.

My computer is a Dell M4660 laptop with a Quadro 2000M graphics card, my operating system is a clean install of Windows 10 Pro.

Neither Cura 4.8 OR the Creality would work both would hang on the empty screen, although on some occasions the Cura software would get to the third page for ‘getting started’ before terminating.

The Creality fix — Navigate to folder with Creality slicer software. Right Click on the Creality icon and select Properties, Run with graphics processor, select Integrated Graphics.

This has worked consistently for all modes of the software.

Cura Fix – Having unsuccessfully tried lots of solutions posted online, I installed the Prontaface/Slic3r combination ( I had previously used this to great success with my Reprap Huxley and was pretty impressed by how flexible this build is 18Nov2017. Today I accidently loaded the Cura software and found that it loaded ‘flawlessly’. I have tried many options in the software (version 4.8.0) and simply put it works.

To test this theory, I shut down the PC rebooted and loaded Cura, as before it works. This is the only change to my system and having checked I cannot see any Windows updates in the last 24 hours so am discounting that as the cure.

Hope this helps.

Tropical T

Источник

Comments

Comments

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Create an account or sign in to comment

Sign in

Популярные вопросы

ЧПУ токарный станок на платах 3д принтера

Деформация стола 3Д принтера

Волнистые стенки.

Читайте в блогах