QUESTION Is there a definitive "crash checklist" for KSeditor? Having issues, FBX linked below

[TommyDean03]

So although I primarily use RTB, I do have limited knowledge of Blender as well. I have successfully made a few tracks, but this year I went the extra mile to make an aesthetically pleasing recreation of my previous track. I originally had issues with KSeditor crashing due to too many vertices on my string objects (checked them with Blender) but even when there were less than 65k vertices, I STILL couldnt load string objects into KSeditor. When removed, I did get the map to load, however trying to replace those objects with something to fill the voids, I have ran into an unloadable map again -_-.

I would love to see whats causing the crashes, as the log file isn't helping me at all in this situation.

QueryPerformanceFrequency: 10000.000000
Installing CrashGuard Fault Handler
[DX11] MAXIMUM_FRAME_LATENCY: 0.000000
[DX11] MIP_LOD_BIAS: 0.000000
Display mode 0: 640x480 @ 60.00 [60/1]
Display mode 1: 640x480 @ 75.00 [75/1]
Display mode 2: 640x480 @ 59.94 [60000/1001]
Display mode 3: 720x400 @ 60.00 [60/1]
Display mode 4: 720x400 @ 60.00 [60/1]
Display mode 5: 720x400 @ 70.00 [70/1]
Display mode 6: 720x480 @ 60.00 [60/1]
Display mode 7: 720x480 @ 59.94 [60000/1001]
Display mode 8: 720x576 @ 60.00 [60/1]
Display mode 9: 720x576 @ 60.00 [60/1]
Display mode 10: 720x576 @ 72.00 [72/1]
Display mode 11: 720x576 @ 72.00 [72/1]
Display mode 12: 720x576 @ 75.00 [75/1]
Display mode 13: 720x576 @ 75.00 [75/1]
Display mode 14: 800x480 @ 60.00 [60/1]
Display mode 15: 800x480 @ 60.00 [60/1]
Display mode 16: 800x480 @ 72.00 [72/1]
Display mode 17: 800x480 @ 72.00 [72/1]
Display mode 18: 800x480 @ 75.00 [75/1]
Display mode 19: 800x480 @ 75.00 [75/1]
Display mode 20: 800x600 @ 60.00 [60/1]
Display mode 21: 800x600 @ 72.00 [72/1]
Display mode 22: 800x600 @ 75.00 [75/1]
Display mode 23: 1024x600 @ 60.00 [60/1]
Display mode 24: 1024x600 @ 60.00 [60/1]
Display mode 25: 1024x600 @ 70.00 [70/1]
Display mode 26: 1024x600 @ 70.00 [70/1]
Display mode 27: 1024x600 @ 75.00 [75/1]
Display mode 28: 1024x600 @ 75.00 [75/1]
Display mode 29: 1024x768 @ 60.00 [60/1]
Display mode 30: 1024x768 @ 70.00 [70/1]
Display mode 31: 1024x768 @ 75.00 [75/1]
Display mode 32: 1280x720 @ 60.00 [60/1]
Display mode 33: 1280x720 @ 59.94 [60000/1001]
Display mode 34: 1280x768 @ 60.00 [60/1]
Display mode 35: 1280x768 @ 60.00 [60/1]
Display mode 36: 1280x1024 @ 24.00 [24/1]
Display mode 37: 1280x1024 @ 24.00 [24/1]
Display mode 38: 1280x1024 @ 60.00 [60/1]
Display mode 39: 1280x1024 @ 60.00 [60/1]
Display mode 40: 1280x1024 @ 23.98 [24000/1001]
Display mode 41: 1280x1024 @ 23.98 [24000/1001]
Display mode 42: 1280x1024 @ 59.94 [60000/1001]
Display mode 43: 1280x1024 @ 59.94 [60000/1001]
Display mode 44: 1360x768 @ 60.00 [60/1]
Display mode 45: 1400x1050 @ 24.00 [24/1]
Display mode 46: 1400x1050 @ 24.00 [24/1]
Display mode 47: 1400x1050 @ 60.00 [60/1]
Display mode 48: 1400x1050 @ 60.00 [60/1]
Display mode 49: 1400x1050 @ 23.98 [24000/1001]
Display mode 50: 1400x1050 @ 23.98 [24000/1001]
Display mode 51: 1400x1050 @ 59.94 [60000/1001]
Display mode 52: 1400x1050 @ 59.94 [60000/1001]
Display mode 53: 1600x900 @ 24.00 [24/1]
Display mode 54: 1600x900 @ 24.00 [24/1]
Display mode 55: 1600x900 @ 60.00 [60/1]
Display mode 56: 1600x900 @ 60.00 [60/1]
Display mode 57: 1600x900 @ 23.98 [24000/1001]
Display mode 58: 1600x900 @ 23.98 [24000/1001]
Display mode 59: 1600x900 @ 59.94 [60000/1001]
Display mode 60: 1600x900 @ 59.94 [60000/1001]
Display mode 61: 1680x1050 @ 24.00 [24/1]
Display mode 62: 1680x1050 @ 24.00 [24/1]
Display mode 63: 1680x1050 @ 60.00 [60/1]
Display mode 64: 1680x1050 @ 60.00 [60/1]
Display mode 65: 1680x1050 @ 23.98 [24000/1001]
Display mode 66: 1680x1050 @ 23.98 [24000/1001]
Display mode 67: 1680x1050 @ 59.94 [60000/1001]
Display mode 68: 1680x1050 @ 59.94 [60000/1001]
Display mode 69: 1920x1080 @ 24.00 [24/1]
Display mode 70: 1920x1080 @ 60.00 [60/1]
Display mode 71: 1920x1080 @ 23.98 [24000/1001]
Display mode 72: 1920x1080 @ 59.94 [60000/1001]
WARNING: Suitable video mode not found, but windowed mode requested.. continuing
ADAPTER DESCRIPTION
DESCRIPTION: Radeon RX 580 Series
VIDEO MEM: 3072
REVISION: 231
ERROR: Shader ksFXAA_0 NOT FOUND, RETURNING NULL
ERROR: Shader ksFXAA_1 NOT FOUND, RETURNING NULL
ERROR: Shader ksFXAA_2 NOT FOUND, RETURNING NULL
ERROR: Shader ksFXAA_3 NOT FOUND, RETURNING NULL
ERROR: Shader ksFXAA_4 NOT FOUND, RETURNING NULL
ERROR: Shader ksFXAA_5 NOT FOUND, RETURNING NULL
ERROR: Shader ksOculusVR NOT FOUND, RETURNING NULL
ERROR: Shader ksOculusVR2 NOT FOUND, RETURNING NULL
ERROR: Shader ksPerPixelMultiMap_damage_dirt_sunspot NOT FOUND, RETURNING NULL
ERROR: Shader newStefano_ksTyres NOT FOUND, RETURNING NULL
KGL CREATE FONT Segoe UI
LOADING PP SET:default
Loading PP set from: system/cfg/ppfilters/default.ini
Creating render target 612 424
Creating render target 612 424
Creating render target 612 424
RE-INSTANTIATE g_pPfxContext 00000000
LOADING MODEL content/objects3D/axis.kn5
VERSION=4
Loading 1 textures
LOADING PP SET:b&w
Loading PP set from: system/cfg/ppfilters/b&w.ini

Am I looking at the right log? Nothing else shows anything of value. I would appreciate any help you guys can offer me, I am stumped!


https://drive.google.com/open?id=18u88UwAufbZIBVCafF3cVTstac3jfcQf

This is the track I am working on, maybe someone could try loading it into KSeditor and seeing if it works? It may be a case of too many objects but I am not sure.

 

[Johnr777]

So although I primarily use RTB, I do have limited knowledge of Blender as well. I have successfully made a few tracks, but this year I went the extra mile to make an aesthetically pleasing recreation of my previous track. I originally had issues with KSeditor crashing due to too many vertices on my string objects (checked them with Blender) but even when there were less than 65k vertices, I STILL couldnt load string objects into KSeditor. When removed, I did get the map to load, however trying to replace those objects with something to fill the voids, I have ran into an unloadable map again -_-.

I would love to see whats causing the crashes, as the log file isn't helping me at all in this situation.

QueryPerformanceFrequency: 10000.000000
Installing CrashGuard Fault Handler
[DX11] MAXIMUM_FRAME_LATENCY: 0.000000
[DX11] MIP_LOD_BIAS: 0.000000
Display mode 0: 640x480 @ 60.00 [60/1]
Display mode 1: 640x480 @ 75.00 [75/1]
Display mode 2: 640x480 @ 59.94 [60000/1001]
Display mode 3: 720x400 @ 60.00 [60/1]
Display mode 4: 720x400 @ 60.00 [60/1]
Display mode 5: 720x400 @ 70.00 [70/1]
Display mode 6: 720x480 @ 60.00 [60/1]
Display mode 7: 720x480 @ 59.94 [60000/1001]
Display mode 8: 720x576 @ 60.00 [60/1]
Display mode 9: 720x576 @ 60.00 [60/1]
Display mode 10: 720x576 @ 72.00 [72/1]
Display mode 11: 720x576 @ 72.00 [72/1]
Display mode 12: 720x576 @ 75.00 [75/1]
Display mode 13: 720x576 @ 75.00 [75/1]
Display mode 14: 800x480 @ 60.00 [60/1]
Display mode 15: 800x480 @ 60.00 [60/1]
Display mode 16: 800x480 @ 72.00 [72/1]
Display mode 17: 800x480 @ 72.00 [72/1]
Display mode 18: 800x480 @ 75.00 [75/1]
Display mode 19: 800x480 @ 75.00 [75/1]
Display mode 20: 800x600 @ 60.00 [60/1]
Display mode 21: 800x600 @ 72.00 [72/1]
Display mode 22: 800x600 @ 75.00 [75/1]
Display mode 23: 1024x600 @ 60.00 [60/1]
Display mode 24: 1024x600 @ 60.00 [60/1]
Display mode 25: 1024x600 @ 70.00 [70/1]
Display mode 26: 1024x600 @ 70.00 [70/1]
Display mode 27: 1024x600 @ 75.00 [75/1]
Display mode 28: 1024x600 @ 75.00 [75/1]
Display mode 29: 1024x768 @ 60.00 [60/1]
Display mode 30: 1024x768 @ 70.00 [70/1]
Display mode 31: 1024x768 @ 75.00 [75/1]
Display mode 32: 1280x720 @ 60.00 [60/1]
Display mode 33: 1280x720 @ 59.94 [60000/1001]
Display mode 34: 1280x768 @ 60.00 [60/1]
Display mode 35: 1280x768 @ 60.00 [60/1]
Display mode 36: 1280x1024 @ 24.00 [24/1]
Display mode 37: 1280x1024 @ 24.00 [24/1]
Display mode 38: 1280x1024 @ 60.00 [60/1]
Display mode 39: 1280x1024 @ 60.00 [60/1]
Display mode 40: 1280x1024 @ 23.98 [24000/1001]
Display mode 41: 1280x1024 @ 23.98 [24000/1001]
Display mode 42: 1280x1024 @ 59.94 [60000/1001]
Display mode 43: 1280x1024 @ 59.94 [60000/1001]
Display mode 44: 1360x768 @ 60.00 [60/1]
Display mode 45: 1400x1050 @ 24.00 [24/1]
Display mode 46: 1400x1050 @ 24.00 [24/1]
Display mode 47: 1400x1050 @ 60.00 [60/1]
Display mode 48: 1400x1050 @ 60.00 [60/1]
Display mode 49: 1400x1050 @ 23.98 [24000/1001]
Display mode 50: 1400x1050 @ 23.98 [24000/1001]
Display mode 51: 1400x1050 @ 59.94 [60000/1001]
Display mode 52: 1400x1050 @ 59.94 [60000/1001]
Display mode 53: 1600x900 @ 24.00 [24/1]
Display mode 54: 1600x900 @ 24.00 [24/1]
Display mode 55: 1600x900 @ 60.00 [60/1]
Display mode 56: 1600x900 @ 60.00 [60/1]
Display mode 57: 1600x900 @ 23.98 [24000/1001]
Display mode 58: 1600x900 @ 23.98 [24000/1001]
Display mode 59: 1600x900 @ 59.94 [60000/1001]
Display mode 60: 1600x900 @ 59.94 [60000/1001]
Display mode 61: 1680x1050 @ 24.00 [24/1]
Display mode 62: 1680x1050 @ 24.00 [24/1]
Display mode 63: 1680x1050 @ 60.00 [60/1]
Display mode 64: 1680x1050 @ 60.00 [60/1]
Display mode 65: 1680x1050 @ 23.98 [24000/1001]
Display mode 66: 1680x1050 @ 23.98 [24000/1001]
Display mode 67: 1680x1050 @ 59.94 [60000/1001]
Display mode 68: 1680x1050 @ 59.94 [60000/1001]
Display mode 69: 1920x1080 @ 24.00 [24/1]
Display mode 70: 1920x1080 @ 60.00 [60/1]
Display mode 71: 1920x1080 @ 23.98 [24000/1001]
Display mode 72: 1920x1080 @ 59.94 [60000/1001]
WARNING: Suitable video mode not found, but windowed mode requested.. continuing
ADAPTER DESCRIPTION
DESCRIPTION: Radeon RX 580 Series
VIDEO MEM: 3072
REVISION: 231
ERROR: Shader ksFXAA_0 NOT FOUND, RETURNING NULL
ERROR: Shader ksFXAA_1 NOT FOUND, RETURNING NULL
ERROR: Shader ksFXAA_2 NOT FOUND, RETURNING NULL
ERROR: Shader ksFXAA_3 NOT FOUND, RETURNING NULL
ERROR: Shader ksFXAA_4 NOT FOUND, RETURNING NULL
ERROR: Shader ksFXAA_5 NOT FOUND, RETURNING NULL
ERROR: Shader ksOculusVR NOT FOUND, RETURNING NULL
ERROR: Shader ksOculusVR2 NOT FOUND, RETURNING NULL
ERROR: Shader ksPerPixelMultiMap_damage_dirt_sunspot NOT FOUND, RETURNING NULL
ERROR: Shader newStefano_ksTyres NOT FOUND, RETURNING NULL
KGL CREATE FONT Segoe UI
LOADING PP SET:default
Loading PP set from: system/cfg/ppfilters/default.ini
Creating render target 612 424
Creating render target 612 424
Creating render target 612 424
RE-INSTANTIATE g_pPfxContext 00000000
LOADING MODEL content/objects3D/axis.kn5
VERSION=4
Loading 1 textures
LOADING PP SET:b&w
Loading PP set from: system/cfg/ppfilters/b&w.ini

Am I looking at the right log? Nothing else shows anything of value. I would appreciate any help you guys can offer me, I am stumped!


https://drive.google.com/open?id=18u88UwAufbZIBVCafF3cVTstac3jfcQf

This is the track I am working on, maybe someone could try loading it into KSeditor and seeing if it works? It may be a case of too many objects but I am not sure.

the 65k limit also applies to triangles, uvs, etc...

 

[luchian]

the 65k limit also applies to triangles, uvs, etc...

This.

So basically, try to stay under 30k of what Blender tells you and it should work.

 

[TommyDean03]

double post, see below

 

[TommyDean03]

So it actually ended up being .PNG files, I converted them to .dds and it loaded into the editor. The ground texture is black, I know because its 16384x16384, but I am now running into the NULL materials issue. I tried manually replacing them all, but on export it essentially fails because of the lack of textures.

This is currently how ksEditor is treating me. Unfortunately all of the Material names are the same as the textures in my texture folder, but they are mismatched for some reason (i.e. a roof of one building might be Material 4_1 and have a NULL txdiffuse, but the texture in my folder thats called 4_1 might be a billboard)

I would willingly painstakingly do this one by one, but even when i get to background, it would throw an exception. I am not sure what the hang up is. I hate to sound like I am asking you all to give me a tutorial, like I said I made quite a few tracks before, but that was a year ago and a different computer. Every time I turn around now, its 4am and Im still troubleshooting issues :/

 

[Johnr777]

So it actually ended up being .PNG files, I converted them to .dds and it loaded into the editor. The ground texture is black, I know because its 16384x16384, but I am now running into the NULL materials issue. I tried manually replacing them all, but on export it essentially fails because of the lack of textures.

This is currently how ksEditor is treating me. Unfortunately all of the Material names are the same as the textures in my texture folder, but they are mismatched for some reason (i.e. a roof of one building might be Material 4_1 and have a NULL txdiffuse, but the texture in my folder thats called 4_1 might be a billboard)

I would willingly painstakingly do this one by one, but even when i get to background, it would throw an exception. I am not sure what the hang up is. I hate to sound like I am asking you all to give me a tutorial, like I said I made quite a few tracks before, but that was a year ago and a different computer. Every time I turn around now, its 4am and Im still troubleshooting issues :/View attachment 4556

There is a tutorial... right here: https://assettocorsamods.net/threads/build-your-first-track-basic-guide.12/

NULL means the editor cant find textures...

When you export the FBX, make sure the textures are in a folder named >> texture << singular. Then the editor will load them up correctly.

 

[TommyDean03]

There is a tutorial... right here: https://assettocorsamods.net/threads/build-your-first-track-basic-guide.12/

NULL means the editor cant find textures...

When you export the FBX, make sure the textures are in a folder named >> texture << singular. Then the editor will load them up correctly.

I realize what NULL means. I have a texture folder, singular. I have exported the fbx the same as I have in the past, even over the weekend I was able to load this same track, textures and all, into assetto corsa minus my string objects. Its like kseditor forgot how to load material textures only, as normal textures load fine.
The basic track building tutorial doesnt exactly cover the issue I am referring to.

 

[Johnr777]

I realize what NULL means. I have a texture folder, singular. I have exported the fbx the same as I have in the past, even over the weekend I was able to load this same track, textures and all, into assetto corsa minus my string objects. Its like kseditor forgot how to load material textures only, as normal textures load fine.
The basic track building tutorial doesnt exactly cover the issue I am referring to.

Did you save a persistance ini file? The editor uses that every time it loads a fbx. Material/shader info is stored in that ini

 

[GRLap]

I'm having an issue with KsEditor failing to import an fbx (track). It's a fully-functioning track that is in the public domain (Race Department), to which I was going to make a variant for my own use (and offer the owner for permission to upload). Anyways, I converted the kn5 to fbx using AC CM. I opened with Blender (0.01 scale); rescaled everything to 1.0; saved the fbx. I made no changes to the fbx other than the scaling. When I import the fbx to KsEditor I get the error below.

When I press Continue, KsEditor attempts to load but makes no progress. The debug Details are pasted below.
Does anyone have any guidance?

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
at Model.load(Model* , basic_string<wchar_t\,std::char_traits<wchar_t>\,std::allocator<wchar_t> >* , GraphicsManager* , IModelImporter* )
at ksNet.ksGraphics.loadFBX(String filename, UInt32& key) in i:\manu\documents\ac-source-pc\ksnet\ksnet.cpp:line 743
at ksEditor.Form1.loadFBXFile(String file, Boolean saveRecent) in i:\Manu\Documents\ac-source-pc\ksEditor\Form1.cs:line 840
at ksEditor.Form1.openFBXToolStripMenuItem_Click(Object sender, EventArgs e) in i:\Manu\Documents\ac-source-pc\ksEditor\Form1.cs:line 826
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4515.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
ksEditor
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/Steam/steamapps/common/assettocorsa/sdk/editor/ksEditor.exe
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4536.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4515.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4536.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
ksNet
Assembly Version: 1.0.5884.33843
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/Steam/steamapps/common/assettocorsa/sdk/editor/ksNet.DLL
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
ksMathCore
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/Steam/steamapps/common/assettocorsa/sdk/editor/ksMathCore.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.