Bug reports:
Sometime I jump on an enemy, the Ero jeet in one direction xD
Sometime the game crashed. It happand in 1h 2 times. Don't really get why. Both time an enemy was near by and I change the direction while do an action. Maybe because of something of this or it was a coincidence, don't know. :/
Sometime I jump on an enemy, the Ero jeet in one direction xD
omg that's funny! do you have video capture of this bug? I would like to see it, it would help me to identify the cause of the problem!
Oh no crashing is bad! But you can help me to fix it, go to this path on your system:
C:\USERS\YOURUSERNAME\AppData\LocalLow\Mega Blue Ball\Mystic Knight Maya\Crashes
If you can upload the folder "Crashes" and its contents, inside are text logs of the errors that might caused the crash. I can take a look and try to fix it.
If there is no Crashes folder, then are there at least log files in the MKM folder? There should be some "Player.log" that could help us out. You can open these in any text editor to see its contents.
If you'd like you can make a copy of it, open and edit it to redact your windows username or the GPU that you use (the only user identifiable info in this log), then send me this copy so that I can analyse it and find the crash report.
Lol the username seems to be ignored in the logs and and I don't see any GPU line. Maybe the logs don't show it itself? xD
Theres two logs. player-prev.log and player.log
It's a little weird. Last time I searched a save date for a game and it should have an equal path, but there was no one. Have you an crash.log there or is something on my pc weird?
------------------------------------------------------------------------
player.log:
Mono path[0] = 'C:/DataG/G1/Mystic Knight Maya/alpha 0.7.5 (bugfix1)/Mystic Knight Maya_Data/Managed'
Mono config path = 'C:/DataG/G1/Mystic Knight Maya/alpha 0.7.5 (bugfix1)/MonoBleedingEdge/etc'
Initialize engine version: 2019.2.6f1 (fe82a0e88406)
[XR] Discovering subsystems at path C:/DataG/G1/Mystic Knight Maya/alpha 0.7.5 (bugfix1)/Mystic Knight Maya_Data/UnitySubsystems
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: NVIDIA GeForce GTX 1660 Ti (ID=0x2191)
Vendor:
VRAM: 5966 MB
Driver: 32.0.15.6603
Begin MonoManager ReloadAssembly
- Completed reload, in 0.077 seconds
<RI> Initializing input.
<RI> Input initialized.
<RI> Initialized touch support.
UnloadTime: 1.655200 ms
Unloading 5 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 2.294300 ms
Unloading 15 unused Assets to reduce memory usage. Loaded Objects now: 30001.
Total: 11.330300 ms (FindLiveObjects: 1.726400 ms CreateObjectMapping: 2.248500 ms MarkObjects: 7.304700 ms DeleteObjects: 0.050200 ms)
Unloading 12 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 3.265900 ms
Unloading 1 unused Assets to reduce memory usage. Loaded Objects now: 37797.
Total: 15.585100 ms (FindLiveObjects: 1.172100 ms CreateObjectMapping: 1.741900 ms MarkObjects: 12.629800 ms DeleteObjects: 0.040600 ms)
Setting up 6 worker threads for Enlighten.
Thread -> id: 37f4 -> priority: 1
Thread -> id: 4bc8 -> priority: 1
Thread -> id: 1fa0 -> priority: 1
Thread -> id: 2e7c -> priority: 1
Thread -> id: 3978 -> priority: 1
Thread -> id: 4404 -> priority: 1
------------------------------------------------------------------------
Player-prev.log:
Mono path[0] = 'C:/DataG/G1/Mystic Knight Maya/alpha 0.7.5 (bugfix1)/Mystic Knight Maya_Data/Managed'
Mono config path = 'C:/DataG/G1/Mystic Knight Maya/alpha 0.7.5 (bugfix1)/MonoBleedingEdge/etc'
Initialize engine version: 2019.2.6f1 (fe82a0e88406)
[XR] Discovering subsystems at path C:/DataG/G1/Mystic Knight Maya/alpha 0.7.5 (bugfix1)/Mystic Knight Maya_Data/UnitySubsystems
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: NVIDIA GeForce GTX 1660 Ti (ID=0x2191)
Vendor:
VRAM: 5966 MB
Driver: 32.0.15.6603
Begin MonoManager ReloadAssembly
- Completed reload, in 0.364 seconds
<RI> Initializing input.
<RI> Input initialized.
<RI> Initialized touch support.
UnloadTime: 0.929600 ms
Unloading 5 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 2.661600 ms
Unloading 15 unused Assets to reduce memory usage. Loaded Objects now: 30001.
Total: 11.468200 ms (FindLiveObjects: 1.322900 ms CreateObjectMapping: 2.340300 ms MarkObjects: 7.735900 ms DeleteObjects: 0.068800 ms)
Unloading 11 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 3.344700 ms
Unloading 1 unused Assets to reduce memory usage. Loaded Objects now: 34419.
Total: 12.979700 ms (FindLiveObjects: 1.538400 ms CreateObjectMapping: 1.568800 ms MarkObjects: 9.832500 ms DeleteObjects: 0.039600 ms)
Unloading 7 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 6.548200 ms
Unloading 109 unused Assets to reduce memory usage. Loaded Objects now: 34359.
Total: 11.963700 ms (FindLiveObjects: 1.099900 ms CreateObjectMapping: 1.569600 ms MarkObjects: 9.121200 ms DeleteObjects: 0.172800 ms)
Unloading 11 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 4.964300 ms
Unloading 181 unused Assets to reduce memory usage. Loaded Objects now: 34275.
Total: 14.278200 ms (FindLiveObjects: 1.188300 ms CreateObjectMapping: 1.763700 ms MarkObjects: 11.099500 ms DeleteObjects: 0.226300 ms)
Unloading 11 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 5.015900 ms
Unloading 226 unused Assets to reduce memory usage. Loaded Objects now: 34420.
Total: 14.201400 ms (FindLiveObjects: 1.586200 ms CreateObjectMapping: 1.686300 ms MarkObjects: 10.677500 ms DeleteObjects: 0.250900 ms)
Unloading 12 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 7.270500 ms
Unloading 280 unused Assets to reduce memory usage. Loaded Objects now: 32000.
Total: 13.217300 ms (FindLiveObjects: 1.086900 ms CreateObjectMapping: 1.605400 ms MarkObjects: 10.175600 ms DeleteObjects: 0.349000 ms)
Unloading 12 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 2.435000 ms
Unloading 59 unused Assets to reduce memory usage. Loaded Objects now: 37798.
Total: 16.318500 ms (FindLiveObjects: 1.298800 ms CreateObjectMapping: 1.686200 ms MarkObjects: 13.162700 ms DeleteObjects: 0.170500 ms)
Unloading 10 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 5.468300 ms
Unloading 224 unused Assets to reduce memory usage. Loaded Objects now: 37308.
Total: 16.478500 ms (FindLiveObjects: 2.188300 ms CreateObjectMapping: 1.689900 ms MarkObjects: 12.262100 ms DeleteObjects: 0.337800 ms)
Unloading 10 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 5.551800 ms
Unloading 306 unused Assets to reduce memory usage. Loaded Objects now: 32224.
Total: 16.338500 ms (FindLiveObjects: 2.544000 ms CreateObjectMapping: 1.923700 ms MarkObjects: 11.163200 ms DeleteObjects: 0.707200 ms)
Unloading 10 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 2.979800 ms
Unloading 74 unused Assets to reduce memory usage. Loaded Objects now: 37308.
Total: 15.071800 ms (FindLiveObjects: 1.603900 ms CreateObjectMapping: 1.592700 ms MarkObjects: 11.711900 ms DeleteObjects: 0.162800 ms)
Unloading 11 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 8.251600 ms
Unloading 157 unused Assets to reduce memory usage. Loaded Objects now: 34275.
Total: 14.430700 ms (FindLiveObjects: 1.400800 ms CreateObjectMapping: 1.655200 ms MarkObjects: 11.168500 ms DeleteObjects: 0.205800 ms)
Unloading 12 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 4.536800 ms
Unloading 239 unused Assets to reduce memory usage. Loaded Objects now: 37798.
Total: 15.869400 ms (FindLiveObjects: 1.459400 ms CreateObjectMapping: 1.761800 ms MarkObjects: 12.406500 ms DeleteObjects: 0.241400 ms)
Setting up 6 worker threads for Enlighten.
Thread -> id: 4330 -> priority: 1
Thread -> id: 4c24 -> priority: 1
Thread -> id: 4a9c -> priority: 1
Thread -> id: 51f0 -> priority: 1
Thread -> id: 3e4c -> priority: 1
Thread -> id: 11c0 -> priority: 1
The ero-jeet-bug didn't happend again. A little weird, before I end the game for the first time it happend more frequently. Maybe it needs a special condition. So I have no record for you sorry. :o
But I give you a description, maybe you can don't know. The jeet-direction was the direction from the jump. The ero stays on the ground and climb for 1 block high, and if it don't manage it, it jeet trough. After the ero the enemy is in the new location and Maya stays where the ero has started. The jeet-speed shuold be movement-speed, but not sure.
