Содержание
- Minecraft Forums
- MCEdit crashes whenever loading a world
- Как исправить ошибку Unhandled Exception в Windows 10
- 6 решений для исправления необработанных исключительных ошибок
- Действия по исправлению ошибок необработанных исключений в Windows 10
- Решение 1. Выполните чистую загрузку
- Решение 2. Выполните сканирование SFC
- Решение 3. Запустите средство устранения неполадок оборудования
- Решение 4. Выполните проверку на вирусы
- Решение 5. Удалите и переустановите .NET Framework
- Решение 6. Запустите средство очистки .NET Framework.
- Minecraft Forums
- Can’t Open World in MCEdit 2
- MCEdit 2.0.0 and 0.1.7.1 crashes when opening worlds opened by 1.13.2 #961
- Comments
- Description of Issue: Unhandled exception when opening worlds opened with 1.13.2.
- MCEdit Version: 2.0.0-beta6 and 0.1.7.1 (most used)
- Minecraft Version the world was last opened in: 1.13.2
- Operating System: Windows 10 Professional
Minecraft Forums
This thread was marked as Locked by user-6840779 .
MCEdit crashes whenever loading a world
- li» data-page-inline=»False» data-scroll-inline=»False»>
- Out of the Water
- Join Date: 12/23/2019
- Posts: 8
- Member Details
I just downloaded MCEdit, yet whenever I tried to a world, It crashes. Does anyone knows how to fix it?
Here is the error details:
- Enderdragon Slayer
- Join Date: 10/6/2013
- Posts: 12,499
- Minecraft: TheMasterCaver
- Member Details
MCEdit is not compatible with worlds loaded in 1.13+ due to changes to the save format (it can’t find the block data because it is completely different), and will never be updated or fixed; the site hasn’t even updated their news for nearly 4 years with the last release 2 years ago (there is a successor in the works, called «Amulet», but it isn’t finished. Otherwise, I suggest using the «original» version of MCEdit, not the forever-in-beta MCEdit 2, either way, neither should be expected to ever be updated).
TheMasterCaver’s First World — possibly the most caved-out world in Minecraft history — includes world download.
TheMasterCaver’s World — my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
Источник
Как исправить ошибку Unhandled Exception в Windows 10
6 решений для исправления необработанных исключительных ошибок
- Выполнить чистую загрузку
- Выполнить сканирование SFC
- Запустите средство устранения неполадок оборудования .
- Выполнить проверку на вирусы
- Удаление и повторная установка .NET Framework
- Запустите инструмент очистки .NET Framework
Исключения можно рассматривать как известную форму ошибки, с которой операционная система запрограммирована для устранения. Другими словами, ОС – в данном случае Windows – знает об этой проблеме и уже знает, как с ней справиться.
К сожалению, также может быть какое-то исключение, которое выходит за рамки Windows. Именно эти сценарии стали известны как ошибки необработанных исключений . Это потому, что Windows не знает, как обрабатывать исключения. Тем не менее, эти ошибки также могут быть легко исправлены, хотя единственный улов здесь заключается в том, что может потребоваться некоторое время, прежде чем вы вернетесь в нужное русло.
Действия по исправлению ошибок необработанных исключений в Windows 10
Решение 1. Выполните чистую загрузку
Это позволит компьютеру запускать только минимальный набор драйверов и программ. Таким образом, вы будете знать, какая сторонняя программа, если таковая имеется, приводит к ошибке. Вот как это делается.
- Запустите msconfig. Это можно сделать, просто набрав msconfig в окне поиска Cortana и выберите Конфигурация системы в результаты поиска показаны. Либо нажмите клавишу Windows + R , чтобы запустить Выполнить , введите msconfig и нажмите ОК .
Ваш компьютер теперь будет загружаться в так называемой среде чистой загрузки, где все сторонние программы отключены. По этой причине ПК может не иметь всех функциональных возможностей, хотя, к сожалению, нет, они будут восстановлены на следующем этапе.
- СВЯЗАННЫЕ: Полное исправление: ошибка ОСНОВНОГО РЕЖИМА КЕРНЕЛА НЕ ОБРАБОТАНА в Windows 10
Между тем, вот как узнать, какая программа может играть в шалости.
- Запустите msconfig еще раз, выполнив шаги, упомянутые выше.
- В диалоговом окне Конфигурация системы выберите Службы .
- Затем установите флажок Скрыть все службы Microsoft .
- Выберите, чтобы включить половину из автозагрузки программ в Службах .
- Нажмите ОК , а затем Перезагрузите .
- Если проблема не возникает, все выбранные вами программы прошли тестирование.
- Повторите процесс со следующей половиной.
- Если проблема возникает, запустите msconfig >Службы .
- Выберите половину из программ, которые вы выбрали во время первого запуска, и Перезапустите .
- Повторите этот процесс с половиной программ каждый раз, пока не найдете проблемную программу.
Как только вы нашли программу, вызывающую ошибку, посмотрите, есть ли обновленная версия для этой же версии. Или удалите переустановку так же, чтобы увидеть, если проблема решена. Вы также можете связаться с производителем, чтобы узнать, могут ли они помочь решить проблему.
- СВЯЗАННО: ИСКЛЮЧЕНИЕ ПРЕРЫВАНИЯ ПОЛНОЙ ФИКСИРОВКИ НЕ РАБОТАЕТ в Windows 10
Решение 2. Выполните сканирование SFC
Эта операция выполняет сканирование всех системных файлов и вносит необходимые изменения по мере необходимости. Это делает его чрезвычайно пригодным для работы с ошибками необработанных исключений. Вот как выполнить sfc scan .
- Запустите командную строку , введя cmd в поле поиска Cortana .В показанном результате поиска щелкните правой кнопкой мыши Командная строка и выберите Запуск от имени администратора . Кроме того, вы также можете открыть окно Выполнить , удерживая клавишу Windows + R , введите cmd и нажмите Enter.
- В окне командной строки введите sfc/scannow и нажмите Enter .
- Для завершения сканирования может потребоваться несколько секунд. Терпеливо ждать, пока его показы 100% сканирования завершены.
Решение 3. Запустите средство устранения неполадок оборудования
Любые проблемы с оборудованием также могут быть причиной появления ошибки. Это делает крайне необходимым выполнять сканирование оборудования и устройств, чтобы исключить вероятность того, что аппаратное обеспечение или устройство где-то сыграют свою роль.
- Чтобы определить такое оборудование, введите следующую команду в окнах Выполнить и нажмите Enter или нажмите кнопку ОК : % systemroot% system32 msdt.exe -id DeviceDiagnostic
- Следуйте инструкциям на экране, чтобы определить, есть ли какое-либо оборудование.
- Откройте диалоговое окно Выполнить , используя шаги, упомянутые в предыдущем разделе.
Вы также можете запустить средство устранения неполадок оборудования на странице настроек, как показано на снимке экрана ниже.
- СВЯЗАННЫЕ: полное исправление: «Исключение режима ядра не обработано M» в Windows 10
Решение 4. Выполните проверку на вирусы
Есть также вероятность того, что вирусная атака является причиной таких ошибок. Поэтому настоятельно рекомендуется выполнить полное и тщательное сканирование вашей системы, чтобы убедиться, что на вашем компьютере нет вирусов, или справиться с ситуацией, когда на вашем компьютере есть вирусная атака.
Также убедитесь, что ваши файлы определений вирусов обновлены и ваш компьютер постоянно защищен. Откройте Центр безопасности Защитника Windows , чтобы выполнить аудит безопасности вашего компьютера. Нажмите на маленький значок стрелки в левом нижнем углу панели задач, чтобы открыть Центр безопасности Защитника Windows . Или вы также можете ввести то же самое в поле поиска Cortana .
Кроме того, лучше всего позволить защитнику Microsoft выполнять эту работу, а не какое-либо стороннее антивирусное программное обеспечение.
Решение 5. Удалите и переустановите .NET Framework
Это также еще один способ справиться с необработанной ошибкой исключения. Вот шаги:
- Запустите Панель управления , нажав Пуск >Система Windows >Панель управления . Кроме того, вы можете просто ввести Панель управления в окне поиска Cortana и выбрать из отображаемых результатов поиска.
- Выберите Программы >Программы и функции . Найдите Microsoft .NET Framework .
- Нажмите правой кнопкой мыши и выберите Удалить .
- После завершения удаления установите обновление Windows .
- Для этого перейдите в раздел Пуск >Настройки >Обновление и безопасность .
.NET Framework будет установлен автоматически. Кроме того, вы также можете загрузить его вручную с официального сайта Microsoft – dotnet.microsoft.com .
Решение 6. Запустите средство очистки .NET Framework.
Также рекомендуется убедиться, что у вас нет проблем с .NET Framework , установленным на вашем ПК. У вас будет вся информация и процедуры, перечисленные здесь для запуска инструмента.
Между тем, вот несколько других ресурсов, которые могут вас заинтересовать:
- Исправлено: SYSTEM_SERVICE_EXCEPTION ошибка в Windows 10
- Исправлено: ошибка MACHINE_CHECK_EXCEPTION в Windows 10
- Исправлено: SYSTEM_SERVICE_EXCEPTION ошибка в Windows 10
Источник
Minecraft Forums
Can’t Open World in MCEdit 2
When I try to open a Minecraft 1.16.2 world in MCEdit 2 I get the error below, but if I try opening a Minecraft 1.12.2 world it opens just fine. I have the current of my graphics drivers installed as well as the latest version of Java. Any help is appreciated!
Windows Version: Windows 10 Pro 21H1 (OS Build: 19043.1110
AMD Software Version: 21.5.2
AMD Driver Version: 27.20.20903.8001
GPU: AMD Radeon (TM) R5 Graphics
CPU: AMD A9-9425 Radeon R5, 5 COMPUTE CORES 2C+3G (2 Cores)
MC Launcher Version: 2.2.3555
Java Version: Version 8 Update 291 (build 1.8.0_291-b10)
MC Edit 2 Version: MCEdit 2.0.0 Beta 14
Error I’m getting:
An error has occurred: Unhandled Exception
It is recommended to ‘undo’ the last command, save your work and restart MCEdit.
Error Details:
MCEdit version: 2.0.0-beta14
Python version: 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:30:26) [MSC v.1500 64 bit (AMD64)]
Platform: win64
System version: Windows-10-10.0.19041
Processor: AMD64 Family 21 Model 112 Stepping 0, AuthenticAMD
Obtained a GL context with this format:
Valid: True
Version: 4.6
Hardware Accelerated: True
Depth buffer: True, 24
Double buffer: True
Rendering profile: PySide.QtOpenGL.QGLFormat.OpenGLContextProfile.CompatibilityProfile
Driver info:
GL_VERSION: 4.6.14831 Compatibility Profile Context 21.5.2 27.20.20903.8001 (4, 6)
GL_VENDOR: ‘ATI Technologies Inc.’
GL_RENDERER: ‘AMD Radeon(TM) R5 Graphics’
—-
Traceback (most recent call last):
File «mcedit2editorsession.py», line 1643, in viewOffsetChanged (self is a EditorTab)
File «mcedit2worldviewminimap.py», line 187, in currentViewMatrixChanged (self is a MinimapWorldView)
File «mcedit2utilraycast.py», line 30, in rayCastInBounds
File «mcedit2utilprofiler.py», line 73, in _wrapper (self is a Profiler)
File «mcedit2utilraycast.py», line 77, in rayCast
File «mcedit2utilraycast.py», line 215, in advanceToChunk
File «mceditlibworldeditor.py», line 831, in getChunk (self is a WorldEditorDimension)
File «mceditlibworldeditor.py», line 499, in getChunk (self is a WorldEditor)
File «mceditlibcachefunc.py», line 77, in __call__
File «mceditlibworldeditor.py», line 477, in _getChunkDataRaw (self is a WorldEditor)
File «mceditlibanviladapter.py», line 922, in readChunk (self is a AnvilWorldAdapter)
AnvilChunkFormatError: [Errno Error loading chunk: KeyError(‘Key Blocks not found.’,)] None:
Here is what is being displayed in the command line window:
Источник
MCEdit 2.0.0 and 0.1.7.1 crashes when opening worlds opened by 1.13.2 #961
MCEdit Unified bug report template. For MCEdit 2.0 bugs see here : https://github.com/mcedit/mcedit2
Description of Issue: Unhandled exception when opening worlds opened with 1.13.2.
MCEdit Version: 2.0.0-beta6 and 0.1.7.1 (most used)
Minecraft Version the world was last opened in: 1.13.2
Operating System: Windows 10 Professional
How the error started:
= Launch the 1.13.2.
= Open the world that is previously opened in 1.12.2 or lower.
= Things in the world went all right until. Opening the world in question using MCEdit.
Alternative:
= Try opening the old world affected by the 1.13.2 update using the old Minecraft version (1.12.2 and below)
= And then the world is, boom, blank.
MCEdit version: 2.0.0-beta6
Python version: 2.7.12 (v2.7.12:d33e0cf91556, Jun 27 2016, 15:24:40) [MSC v.1500 64 bit (AMD64)]
Platform: win32
System version: Windows-10-10.0.17134
Processor: Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
Obtained a GL context with this format:
Valid: True
Version: 4.6
Hardware Accelerated: True
Depth buffer: True, 24
Double buffer: True
Rendering profile: PySide.QtOpenGL.QGLFormat.OpenGLContextProfile.CompatibilityProfile
Driver info:
GL_VERSION: 4.6.0 NVIDIA 388.57 (4, 6)
GL_VENDOR: ‘NVIDIA Corporation’
GL_RENDERER: ‘GeForce 610M/PCIe/SSE2’
Traceback (most recent call last):
File «mcedit2utilprofiler.py», line 73, in _wrapper (self is a Profiler)
File «mcedit2worldlist.py», line 476, in loadTimerFired (self is a WorldListWidget)
File «mcedit2renderingchunkloader.py», line 205, in next (self is a ChunkLoader)
File «mcedit2renderingchunkloader.py», line 244, in _loadChunks (self is a ChunkLoader)
File «mcedit2renderingchunkloader.py», line 275, in _loadChunk (self is a ChunkLoader)
File «mceditlibworldeditor.py», line 807, in getChunk (self is a WorldEditorDimension)
File «mceditlibworldeditor.py», line 495, in getChunk (self is a WorldEditor)
File «mceditlibcachefunc.py», line 77, in call
File «mceditlibworldeditor.py», line 473, in _getChunkDataRaw (self is a WorldEditor)
File «mceditlibanviladapter.py», line 892, in readChunk (self is a AnvilWorldAdapter)
File «srcmceditlibnbt.pyx», line 569, in mceditlib.nbt.load (src/mceditlib/nbt.c:12098)
File «srcmceditlibnbt.pyx», line 662, in mceditlib.nbt.load_compound (src/mceditlib/nbt.c:12976)
File «srcmceditlibnbt.pyx», line 669, in mceditlib.nbt.load_named (src/mceditlib/nbt.c:13053)
File «srcmceditlibnbt.pyx», line 786, in mceditlib.nbt.load_tag (src/mceditlib/nbt.c:14277)
File «srcmceditlibnbt.pyx», line 662, in mceditlib.nbt.load_compound (src/mceditlib/nbt.c:12976)
File «srcmceditlibnbt.pyx», line 669, in mceditlib.nbt.load_named (src/mceditlib/nbt.c:13053)
File «srcmceditlibnbt.pyx», line 786, in mceditlib.nbt.load_tag (src/mceditlib/nbt.c:14277)
File «srcmceditlibnbt.pyx», line 662, in mceditlib.nbt.load_compound (src/mceditlib/nbt.c:12976)
File «srcmceditlibnbt.pyx», line 668, in mceditlib.nbt.load_named (src/mceditlib/nbt.c:13041)
File «srcmceditlibnbt.pyx», line 709, in mceditlib.nbt.load_name (src/mceditlib/nbt.c:13470)
UnicodeDecodeError: ‘utf8’ codec can’t decode byte 0x80 in position 6: invalid start byte
The text was updated successfully, but these errors were encountered:
Источник
I just downloaded MCEdit, yet whenever I tried to a world, It crashes. Does anyone knows how to fix it?
Here is the error details:
MCEdit version: 2.0.0-beta14 Python version: 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:30:26) [MSC v.1500 64 bit (AMD64)] Platform: win32 System version: Windows-10-10.0.18362 Processor: Intel64 Family 6 Model 158 Stepping 10, GenuineIntel Obtained a GL context with this format: Valid: True Version: 4.6 Hardware Accelerated: True Depth buffer: True, 24 Double buffer: True Rendering profile: PySide.QtOpenGL.QGLFormat.OpenGLContextProfile.CompatibilityProfile Driver info: GL_VERSION: 4.6.0 NVIDIA 441.45 (4, 6) GL_VENDOR: 'NVIDIA Corporation' GL_RENDERER: 'GeForce GTX 1650/PCIe/SSE2' ------ Unhandled Exception Traceback (most recent call last): File "mcedit2editorsession.py", line 1643, in viewOffsetChanged (self is a EditorTab) File "mcedit2worldviewminimap.py", line 187, in currentViewMatrixChanged (self is a MinimapWorldView) File "mcedit2utilraycast.py", line 30, in rayCastInBounds File "mcedit2utilprofiler.py", line 73, in _wrapper (self is a Profiler) File "mcedit2utilraycast.py", line 77, in rayCast File "mcedit2utilraycast.py", line 215, in advanceToChunk File "mceditlibworldeditor.py", line 831, in getChunk (self is a WorldEditorDimension) File "mceditlibworldeditor.py", line 499, in getChunk (self is a WorldEditor) File "mceditlibcachefunc.py", line 77, in __call__ File "mceditlibworldeditor.py", line 477, in _getChunkDataRaw (self is a WorldEditor) File "mceditlibanviladapter.py", line 922, in readChunk (self is a AnvilWorldAdapter) AnvilChunkFormatError: [Errno Error loading chunk: KeyError('Key Blocks not found.',)] None: <traceback object at 0x000002833D94BB48>
I just downloaded MCEdit, yet whenever I tried to a world, It crashes. Does anyone knows how to fix it?
Here is the error details:
MCEdit version: 2.0.0-beta14 Python version: 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:30:26) [MSC v.1500 64 bit (AMD64)] Platform: win32 System version: Windows-10-10.0.18362 Processor: Intel64 Family 6 Model 158 Stepping 10, GenuineIntel Obtained a GL context with this format: Valid: True Version: 4.6 Hardware Accelerated: True Depth buffer: True, 24 Double buffer: True Rendering profile: PySide.QtOpenGL.QGLFormat.OpenGLContextProfile.CompatibilityProfile Driver info: GL_VERSION: 4.6.0 NVIDIA 441.45 (4, 6) GL_VENDOR: 'NVIDIA Corporation' GL_RENDERER: 'GeForce GTX 1650/PCIe/SSE2' ------ Unhandled Exception Traceback (most recent call last): File "mcedit2editorsession.py", line 1643, in viewOffsetChanged (self is a EditorTab) File "mcedit2worldviewminimap.py", line 187, in currentViewMatrixChanged (self is a MinimapWorldView) File "mcedit2utilraycast.py", line 30, in rayCastInBounds File "mcedit2utilprofiler.py", line 73, in _wrapper (self is a Profiler) File "mcedit2utilraycast.py", line 77, in rayCast File "mcedit2utilraycast.py", line 215, in advanceToChunk File "mceditlibworldeditor.py", line 831, in getChunk (self is a WorldEditorDimension) File "mceditlibworldeditor.py", line 499, in getChunk (self is a WorldEditor) File "mceditlibcachefunc.py", line 77, in __call__ File "mceditlibworldeditor.py", line 477, in _getChunkDataRaw (self is a WorldEditor) File "mceditlibanviladapter.py", line 922, in readChunk (self is a AnvilWorldAdapter) AnvilChunkFormatError: [Errno Error loading chunk: KeyError('Key Blocks not found.',)] None: <traceback object at 0x000002833D94BB48>
Hi, I am 34486 not a buddy of mine 34486SCI heh.
I have noticed this with 2 worlds and get the exact same error EACH TIME! Its getting annoying.
An error occurred while opening D:/Servers/HHSDepleted/world/level.dat
‘utf8’ codec can’t decode byte 0xc0 in position 0: invalid start byte
Traceback (most recent call last):
File «mcedit2editorapp.py», line 781, in loadFile (self is a MCEditApp)
File «mcedit2editorsession.py», line 186, in __init__ (self is a EditorSession)
File «mceditlibworldeditor.py», line 233, in __init__ (self is a WorldEditor)
File «mceditlibfindadapter.py», line 62, in findAdapter
File «mceditlibanviladapter.py», line 463, in __init__ (self is a AnvilWorldAdapter)
File «mceditlibanviladapter.py», line 530, in loadMetadata (self is a AnvilWorldAdapter)
File «srcmceditlibnbt.pyx», line 590, in mceditlib.nbt.load
File «srcmceditlibnbt.pyx», line 683, in mceditlib.nbt.load_compound
File «srcmceditlibnbt.pyx», line 690, in mceditlib.nbt.load_named
File «srcmceditlibnbt.pyx», line 807, in mceditlib.nbt.load_tag
File «srcmceditlibnbt.pyx», line 683, in mceditlib.nbt.load_compound
File «srcmceditlibnbt.pyx», line 690, in mceditlib.nbt.load_named
File «srcmceditlibnbt.pyx», line 807, in mceditlib.nbt.load_tag
File «srcmceditlibnbt.pyx», line 683, in mceditlib.nbt.load_compound
File «srcmceditlibnbt.pyx», line 689, in mceditlib.nbt.load_named
File «srcmceditlibnbt.pyx», line 733, in mceditlib.nbt.load_name
UnicodeDecodeError: ‘utf8’ codec can’t decode byte 0xc0 in position 0: invalid start byte
64bit Mcedit2 2.0.0-beta7 I have tried another version, I forget which one and gave me the same error! What could this be from? I was able to load a factions world, but not my vanilla or depleted world? Whats the deal with this? I hope I get emails about this because I might forget of my issue…
Thanks!
Click here follow the steps to fix Mcedit Error During Function Confirm At and related errors.
Instructions
|
|
To Fix (Mcedit Error During Function Confirm At) error you need to |
|
Step 1: |
|
---|---|
Download (Mcedit Error During Function Confirm At) Repair Tool |
|
Step 2: |
|
Click the «Scan» button | |
Step 3: |
|
Click ‘Fix All‘ and you’re done! | |
Compatibility:
Limitations: |
Mcedit Error During Function Confirm At Error Codes are caused in one way or another by misconfigured system files
in your windows operating system.
If you have Mcedit Error During Function Confirm At errors then we strongly recommend that you
Download (Mcedit Error During Function Confirm At) Repair Tool.
This article contains information that shows you how to fix
Mcedit Error During Function Confirm At
both
(manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages related to Mcedit Error During Function Confirm At error code that you may receive.
Note:
This article was updated on 2023-01-24 and previously published under WIKI_Q210794
Contents
- 1. What is Mcedit Error During Function Confirm At error?
- 2. What causes Mcedit Error During Function Confirm At error?
- 3. How to easily fix Mcedit Error During Function Confirm At errors
What is Mcedit Error During Function Confirm At error?
The Mcedit Error During Function Confirm At error is the Hexadecimal format of the error caused. This is common error code format used by windows and other windows compatible software and driver vendors.
This code is used by the vendor to identify the error caused. This Mcedit Error During Function Confirm At error code has a numeric error number and a technical description. In some cases the error may have more parameters in Mcedit Error During Function Confirm At format .This additional hexadecimal code are the address of the memory locations where the instruction(s) was loaded at the time of the error.
What causes Mcedit Error During Function Confirm At error?
The Mcedit Error During Function Confirm At error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer.
There can be many events which may have resulted in the system files errors. An incomplete installation, an incomplete uninstall, improper deletion of applications or hardware. It can also be caused if your computer is recovered from a virus or adware/spyware
attack or by an improper shutdown of the computer. All the above actives
may result in the deletion or corruption of the entries in the windows
system files. This corrupted system file will lead to the missing and wrongly
linked information and files needed for the proper working of the
application.
How to easily fix Mcedit Error During Function Confirm At error?
There are two (2) ways to fix Mcedit Error During Function Confirm At Error:
Advanced Computer User Solution (manual update):
1) Start your computer and log on as an administrator.
2) Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.
3) In the new window, select «Restore my computer to an earlier time» option and then click Next.
4) Select the most recent system restore point from the «On this list, click a restore point» list, and then click Next.
5) Click Next on the confirmation window.
6) Restarts the computer when the restoration is finished.
Novice Computer User Solution (completely automated):
1) Download (Mcedit Error During Function Confirm At) repair utility.
2) Install program and click Scan button.
3) Click the Fix Errors button when scan is completed.
4) Restart your computer.
How does it work?
This tool will scan and diagnose, then repairs, your PC with patent
pending technology that fix your windows operating system registry
structure.
basic features: (repairs system freezing and rebooting issues , start-up customization , browser helper object management , program removal management , live updates , windows structure repair.)
-
Search
-
Search all Forums
-
Search this Forum
-
Search this Thread
-
-
Tools
-
Jump to Forum
-
-
#1
Jul 21, 2021
When I try to open a Minecraft 1.16.2 world in MCEdit 2 I get the error below, but if I try opening a Minecraft 1.12.2 world it opens just fine. I have the current of my graphics drivers installed as well as the latest version of Java. Any help is appreciated!
System Info:
Windows Version: Windows 10 Pro 21H1 (OS Build: 19043.1110
AMD Software Version: 21.5.2
AMD Driver Version: 27.20.20903.8001
GPU: AMD Radeon (TM) R5 Graphics
CPU: AMD A9-9425 Radeon R5, 5 COMPUTE CORES 2C+3G (2 Cores)MC Launcher Version: 2.2.3555
Java Version: Version 8 Update 291 (build 1.8.0_291-b10)
MC Edit 2 Version: MCEdit 2.0.0 Beta 14
Error I’m getting:
An error has occurred: Unhandled Exception
It is recommended to ‘undo’ the last command, save your work and restart MCEdit.Error Details:
MCEdit version: 2.0.0-beta14
Python version: 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:30:26) [MSC v.1500 64 bit (AMD64)]
Platform: win64
System version: Windows-10-10.0.19041
Processor: AMD64 Family 21 Model 112 Stepping 0, AuthenticAMDObtained a GL context with this format:
Valid: True
Version: 4.6
Hardware Accelerated: True
Depth buffer: True, 24
Double buffer: True
Rendering profile: PySide.QtOpenGL.QGLFormat.OpenGLContextProfile.CompatibilityProfileDriver info:
GL_VERSION: 4.6.14831 Compatibility Profile Context 21.5.2 27.20.20903.8001 (4, 6)
GL_VENDOR: ‘ATI Technologies Inc.’
GL_RENDERER: ‘AMD Radeon(TM) R5 Graphics’
—-Unhandled Exception
Traceback (most recent call last):
File «mcedit2editorsession.py», line 1643, in viewOffsetChanged (self is a EditorTab)
File «mcedit2worldviewminimap.py», line 187, in currentViewMatrixChanged (self is a MinimapWorldView)
File «mcedit2utilraycast.py», line 30, in rayCastInBounds
File «mcedit2utilprofiler.py», line 73, in _wrapper (self is a Profiler)
File «mcedit2utilraycast.py», line 77, in rayCast
File «mcedit2utilraycast.py», line 215, in advanceToChunk
File «mceditlibworldeditor.py», line 831, in getChunk (self is a WorldEditorDimension)
File «mceditlibworldeditor.py», line 499, in getChunk (self is a WorldEditor)
File «mceditlibcachefunc.py», line 77, in __call__
File «mceditlibworldeditor.py», line 477, in _getChunkDataRaw (self is a WorldEditor)
File «mceditlibanviladapter.py», line 922, in readChunk (self is a AnvilWorldAdapter)
AnvilChunkFormatError: [Errno Error loading chunk: KeyError(‘Key Blocks not found.’,)] None:Here is what is being displayed in the command line window:
[11560] PyInstaller Bootloader 3.x
[11560] LOADER: executable is C:UserscaseyDesktopMCEdit 2.0.0mcedit2.exe
[11560] LOADER: homepath is C:UserscaseyDesktopMCEdit 2.0.0
[11560] LOADER: _MEIPASS2 is NULL
[11560] LOADER: archivename is C:UserscaseyDesktopMCEdit 2.0.0mcedit2.exe
[11560] LOADER: Extracting binaries
[11560] LOADER: Executing self as child
[11560] LOADER: set _MEIPASS2 to C:UserscaseyAppDataLocalTemp_MEI115602
[11560] LOADER: Setting up to run child
[11560] LOADER: Creating child process
[11560] LOADER: Waiting for child process to finish…
[6692] PyInstaller Bootloader 3.x
[6692] LOADER: executable is C:UserscaseyDesktopMCEdit 2.0.0mcedit2.exe
[6692] LOADER: homepath is C:UserscaseyDesktopMCEdit 2.0.0
[6692] LOADER: _MEIPASS2 is C:UserscaseyAppDataLocalTemp_MEI115602
[6692] LOADER: archivename is C:UserscaseyDesktopMCEdit 2.0.0mcedit2.exe
[6692] LOADER: SetDllDirectory(C:UserscaseyAppDataLocalTemp_MEI115602)
[6692] LOADER: Already in the child — running user’s code.
[6692] LOADER: manifestpath: C:UserscaseyAppDataLocalTemp_MEI115602mcedit2.exe.manifest
[6692] LOADER: Activation context created
[6692] LOADER: Activation context activated
[6692] LOADER: Python library: C:UserscaseyAppDataLocalTemp_MEI115602python27.dll
[6692] LOADER: Loaded functions from Python library.
[6692] LOADER: Manipulating environment (sys.path, sys.prefix)
[6692] LOADER: sys.prefix is C:UserscaseyAppDataLocalTemp_MEI115602
[6692] LOADER: Setting runtime options
[6692] LOADER: Bootloader option: pyi-windows-manifest-filename mcedit2.exe.manifest
[6692] LOADER: Initializing python
[6692] LOADER: Overriding Python’s sys.path
[6692] LOADER: Post-init sys.path is C:UserscaseyAppDataLocalTemp_MEI115602
[6692] LOADER: Setting sys.argv
[6692] LOADER: setting sys._MEIPASS
[6692] LOADER: importing modules from CArchive
[6692] LOADER: extracted struct
[6692] LOADER: callfunction returned…
[6692] LOADER: extracted pyimod01_os_path
[6692] LOADER: callfunction returned…
[6692] LOADER: extracted pyimod02_archive
[6692] LOADER: callfunction returned…
[6692] LOADER: extracted pyimod03_importers
[6692] LOADER: callfunction returned…
[6692] LOADER: Installing PYZ archive with Python modules.
[6692] LOADER: PYZ archive: out00-PYZ.pyz
[6692] LOADER: Running pyiboot01_bootstrap.py
[6692] LOADER: Running pyi_rth_win32comgenpy.py
[6692] LOADER: Running pyi_rth_pkgres.py
[6692] LOADER: Running pyi_rth_multiprocessing.py
[6692] LOADER: Running pyi_rth_traitlets.py
[6692] LOADER: Running pyi_rth_qt4plugins.py
[6692] LOADER: Running main.py
Logging level set
sys.frozen is set
Logging to C:UserscaseyDesktopMCEdit 2.0.0MCEdit 2 Filesmcedit2.log
Setting up console handler
[WARNING][editorapp.py:95]:UserFilesDirectory: C:UserscaseyDesktopMCEdit 2.0.0MCEdit 2 Files
[WARNING][configure_blocks.py:121]:Failed to read definitions file defined_blocks.json
QSslSocket: cannot call unresolved function SSLv23_client_method
QSslSocket: cannot call unresolved function SSL_CTX_new
QSslSocket: cannot call unresolved function SSL_library_init
QSslSocket: cannot call unresolved function ERR_get_error
QSslSocket: cannot call unresolved function SSLv23_client_method
QSslSocket: cannot call unresolved function SSL_CTX_new
QSslSocket: cannot call unresolved function SSL_library_init
QSslSocket: cannot call unresolved function ERR_get_error
QSslSocket: cannot call unresolved function SSLv23_client_method
QSslSocket: cannot call unresolved function SSL_CTX_new
QSslSocket: cannot call unresolved function SSL_library_init
QSslSocket: cannot call unresolved function ERR_get_error
[ERROR][player_server.py:85]:Error reading JSON from session server.
Traceback (most recent call last):
File «mcedit2utilplayer_server.py», line 83, in _queryFinished (self is a PlayerDataCache)
File «json__init__.py», line 339, in loads
File «jsondecoder.py», line 364, in decode (self is a JSONDecoder)
File «jsondecoder.py», line 382, in raw_decode (self is a JSONDecoder)
ValueError: No JSON object could be decoded
[ERROR][player_server.py:85]:Error reading JSON from session server.
Traceback (most recent call last):
File «mcedit2utilplayer_server.py», line 83, in _queryFinished (self is a PlayerDataCache)
File «json__init__.py», line 339, in loads
File «jsondecoder.py», line 364, in decode (self is a JSONDecoder)
File «jsondecoder.py», line 382, in raw_decode (self is a JSONDecoder)
ValueError: No JSON object could be decoded
Exception AttributeError: «‘RevisionHistory’ object has no attribute ‘nodes’» in ignored
QSslSocket: cannot call unresolved function SSLv23_client_method
QSslSocket: cannot call unresolved function SSL_CTX_new
QSslSocket: cannot call unresolved function SSL_library_init
QSslSocket: cannot call unresolved function ERR_get_error
QSslSocket: cannot call unresolved function SSLv23_client_method
QSslSocket: cannot call unresolved function SSL_CTX_new
QSslSocket: cannot call unresolved function SSL_library_init
QSslSocket: cannot call unresolved function ERR_get_error
[ERROR][player_server.py:85]:Error reading JSON from session server.
Traceback (most recent call last):
File «mcedit2utilplayer_server.py», line 83, in _queryFinished (self is a PlayerDataCache)
File «json__init__.py», line 339, in loads
File «jsondecoder.py», line 364, in decode (self is a JSONDecoder)
File «jsondecoder.py», line 382, in raw_decode (self is a JSONDecoder)
ValueError: No JSON object could be decoded
[ERROR][player_server.py:85]:Error reading JSON from session server.
Traceback (most recent call last):
File «mcedit2utilplayer_server.py», line 83, in _queryFinished (self is a PlayerDataCache)
File «json__init__.py», line 339, in loads
File «jsondecoder.py», line 364, in decode (self is a JSONDecoder)
File «jsondecoder.py», line 382, in raw_decode (self is a JSONDecoder)
ValueError: No JSON object could be decoded
Could not parse stylesheet of widget 0x1d26eae4220
Could not parse stylesheet of widget 0x1d26eae6410
Could not parse stylesheet of widget 0x1d26eae82a0
Could not parse stylesheet of widget 0x1d26df06350
Could not parse stylesheet of widget 0x1d26df07ac0
Could not parse stylesheet of widget 0x1d26df084e0
Could not parse stylesheet of widget 0x1d26df096e0
Could not parse stylesheet of widget 0x1d26df0a130
Could not parse stylesheet of widget 0x1d26df0b9f0
Could not parse stylesheet of widget 0x1d26df0c650
Could not parse stylesheet of widget 0x1d26df0d4f0
[ERROR][main.py:203]:Unhandled Exception:
[Errno Error loading chunk: KeyError(‘Key Blocks not found.’,)] None:
Traceback (most recent call last):
File «mcedit2editorsession.py», line 1643, in viewOffsetChanged (self is a EditorTab)
File «mcedit2worldviewminimap.py», line 187, in currentViewMatrixChanged (self is a MinimapWorldView)
File «mcedit2utilraycast.py», line 30, in rayCastInBounds
File «mcedit2utilprofiler.py», line 73, in _wrapper (self is a Profiler)
File «mcedit2utilraycast.py», line 77, in rayCast
File «mcedit2utilraycast.py», line 215, in advanceToChunk
File «mceditlibworldeditor.py», line 831, in getChunk (self is a WorldEditorDimension)
File «mceditlibworldeditor.py», line 499, in getChunk (self is a WorldEditor)
File «mceditlibcachefunc.py», line 77, in __call__
File «mceditlibworldeditor.py», line 477, in _getChunkDataRaw (self is a WorldEditor)
File «mceditlibanviladapter.py», line 922, in readChunk (self is a AnvilWorldAdapter)
AnvilChunkFormatError: [Errno Error loading chunk: KeyError(‘Key Blocks not found.’,)] None: -
#3
Jul 22, 2021
I’m trying to edit a 1.16.2 world, so it should work. I have tried Amulet and didn’t really like it.
-
#5
Jul 22, 2021
1.16.2 is newer than 1.12.2
McEdit can’t open 1.13 or newer worlds
I guess I have no choice but to use Amulet them.
- To post a comment, please login.
Posts Quoted:
Reply
Clear All Quotes
Here you will find some information for troubleshooting information. These examples were mostly taken form the issue tracker.
There is not much here yet, but feel free to expand it!
Crashes
First, you should try development builds. Those are less stable, but they sometimes fix known crash errors. This was the case in Issue #193 and #198
Mac OSX
Missing X server
MCEdit is an X application. As such it needs an X server to function properly. Apple has its own version called XQuartz (AKA X11.app). This one is taken form Issue #192.
Other (running from source, typically Linux)
Missing pymclevel
When you run MCEdit from the source, you must get pymclevel too (in the git, it is a submodule). If you were following the instructions in README.md, you should not have this problem. However, if you have blindly cloned the repository, then you will have to run
git submodule init
git submodule update
This was the case in Issue 167
Wrong python version
MCEdit only works with Python 2.7. If you have any other version, it will fail. You should probably get Python 2.7 and run MCEdit as python2.7 mcedit.py
This was the case in Issue #168
Glitches
Windows, panels, interface items not showing up
This is a known issue. The interfaces are still usable, and this is a purely graphical glitch. Updating your graphics driver may (Issue #169), or may not (#191) solve your problem.
Common pitfalls
Clone, Fill & Replace and Filter buttons disabled
You have probably not selected an area, or maybe you have used the chunk tool instead of the select tool. If you want to operate on whole chunks, use the select chunks button in the panel of the select tool.
This was the case in Issue #196
Reporting an issue
If you haven’t found the solution for your problem here, you should report an issue. Before doing so, please read the related article (Reporting Issues) and search in the issue tracker to make sure not to make a duplicate. Thank you!
Today i downloaded MCEdit 2 Win64x 2.0.0 Beta14.When i opened it and selected my world to test editing after short time an error message appears:An error has occurred unhandled exception,and below:It is recommended to undo the last command,save your work and restart mceditor.
Notes:
— I have win 7 64x
— tryed running as administrator
— tryed installing a new version of mcedit
— i carefully checked mc version of the world and the selected version selected in mcedit
I soposse you need an whole log of the error so…….
MCEdit version: 2.0.0-beta12
Python version: 2.7.14 (v2.7.14:84471935ed, Sep 16 2017, 20:25:58) [MSC v.1500 64 bit (AMD64)]
Platform: win32
System version: Windows-7-6.1.7601-SP1
Processor: Intel64 Family 6 Model 42 Stepping 7, GenuineIntel
Obtained a GL context with this format:
Valid: True
Version: 3.1
Hardware Accelerated: True
Depth buffer: True, 24
Double buffer: True
Rendering profile: PySide.QtOpenGL.QGLFormat.OpenGLContextProfile.NoProfile
Driver info:
GL_VERSION: 3.1.0 — Build 9.17.10.3347 (3, 1)
GL_VENDOR: ‘Intel’
GL_RENDERER: ‘Intel(R) HD Graphics 3000’
——
Unhandled Exception
Traceback (most recent call last):
File «mcedit2editorsession.py», line 1643, in viewOffsetChanged (self is a EditorTab)
File «mcedit2worldviewminimap.py», line 187, in currentViewMatrixChanged (self is a MinimapWorldView)
File «mcedit2utilraycast.py», line 30, in rayCastInBounds
File «mcedit2utilprofiler.py», line 73, in _wrapper (self is a Profiler)
File «mcedit2utilraycast.py», line 77, in rayCast
File «mcedit2utilraycast.py», line 215, in advanceToChunk
File «mceditlibworldeditor.py», line 831, in getChunk (self is a WorldEditorDimension)
File «mceditlibworldeditor.py», line 499, in getChunk (self is a WorldEditor)
File «mceditlibcachefunc.py», line 77, in __call__
File «mceditlibworldeditor.py», line 477, in _getChunkDataRaw (self is a WorldEditor)
File «mceditlibanviladapter.py», line 922, in readChunk (self is a AnvilWorldAdapter)
AnvilChunkFormatError: [Errno Error loading chunk: KeyError(‘Key Blocks not found.’,)] None: <traceback object at 0x0000000018C77E88>
Click here follow the steps to fix Mcedit Error During Function Confirm At and related errors.
|
|
To Fix (Mcedit Error During Function Confirm At) error you need to |
|
Step 1: |
|
---|---|
Download (Mcedit Error During Function Confirm At) Repair Tool |
|
Step 2: |
|
Click the «Scan» button | |
Step 3: |
|
Click ‘Fix All‘ and you’re done! | |
Compatibility:
Limitations: |
Mcedit Error During Function Confirm At Error Codes are caused in one way or another by misconfigured system files
in your windows operating system.
If you have Mcedit Error During Function Confirm At errors then we strongly recommend that you
Download (Mcedit Error During Function Confirm At) Repair Tool.
This article contains information that shows you how to fix
Mcedit Error During Function Confirm At
both
(manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages related to Mcedit Error During Function Confirm At error code that you may receive.
Note:
This article was updated on 2023-02-03 and previously published under WIKI_Q210794
Contents
- 1. What is Mcedit Error During Function Confirm At error?
- 2. What causes Mcedit Error During Function Confirm At error?
- 3. How to easily fix Mcedit Error During Function Confirm At errors
What is Mcedit Error During Function Confirm At error?
The Mcedit Error During Function Confirm At error is the Hexadecimal format of the error caused. This is common error code format used by windows and other windows compatible software and driver vendors.
This code is used by the vendor to identify the error caused. This Mcedit Error During Function Confirm At error code has a numeric error number and a technical description. In some cases the error may have more parameters in Mcedit Error During Function Confirm At format .This additional hexadecimal code are the address of the memory locations where the instruction(s) was loaded at the time of the error.
What causes Mcedit Error During Function Confirm At error?
The Mcedit Error During Function Confirm At error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer.
There can be many events which may have resulted in the system files errors. An incomplete installation, an incomplete uninstall, improper deletion of applications or hardware. It can also be caused if your computer is recovered from a virus or adware/spyware
attack or by an improper shutdown of the computer. All the above actives
may result in the deletion or corruption of the entries in the windows
system files. This corrupted system file will lead to the missing and wrongly
linked information and files needed for the proper working of the
application.
How to easily fix Mcedit Error During Function Confirm At error?
There are two (2) ways to fix Mcedit Error During Function Confirm At Error:
Advanced Computer User Solution (manual update):
1) Start your computer and log on as an administrator.
2) Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.
3) In the new window, select «Restore my computer to an earlier time» option and then click Next.
4) Select the most recent system restore point from the «On this list, click a restore point» list, and then click Next.
5) Click Next on the confirmation window.
6) Restarts the computer when the restoration is finished.
Novice Computer User Solution (completely automated):
1) Download (Mcedit Error During Function Confirm At) repair utility.
2) Install program and click Scan button.
3) Click the Fix Errors button when scan is completed.
4) Restart your computer.
How does it work?
This tool will scan and diagnose, then repairs, your PC with patent
pending technology that fix your windows operating system registry
structure.
basic features: (repairs system freezing and rebooting issues , start-up customization , browser helper object management , program removal management , live updates , windows structure repair.)