Assertion fail whenever I try to load a scene (Beta 1.8.0)

Users who are viewing this thread

Total: 2 (members: 0, guests: 2)
bbelasto

bbelasto

Recruit
Steam
When I am trying to load into a scene the same error appears everytime ("Assertion failed" and or contact Abdulltalif.. followed by a crash)
I tried reinstalling both the base game and the modding kit multiple times on different drives, nothing ever changes. I also tried to delete all other game related folders other then the main directory.

Heres the error log

[01:13:22.241]
Assertion Failed!

C:\Develop\mb3\Source\Engine\Rgl\rglTerrain.cpp:781
Expression: vista_record_.tileset_ != nullptr

[01:13:22.241] #TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:13034621
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:1367283
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:746330
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:6279401
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:6283231
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:2844163
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:2984614
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:3797079
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:3796776
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:3801431
#ucrtbase.pdb@{152B3C4F5E1CE0FE6BC36E9F0F2B10E6} (1): 0:138162
#kernel32.pdb@{9CF2BCBC4D0E03503C68E569FAA6DC93} (1): 0:94260
#ntdll.pdb@{CDE75D039306834203EBD8D4E7D50369} (1): 0:337489
-----------------------------------------------
#TaleWorlds.DotNet.AutoGenerated.pdb@{776ACEC2D6B94B529BBD45161746B40C} (1): 100663315:0

[01:13:41.213]
<##########################################################################################>
 
belasto said:
When I am trying to load into a scene the same error appears everytime ("Assertion failed" and or contact Abdulltalif.. followed by a crash)
I tried reinstalling both the base game and the modding kit multiple times on different drives, nothing ever changes. I also tried to delete all other game related folders other then the main directory.

Heres the error log

[01:13:22.241]
Assertion Failed!

C:\Develop\mb3\Source\Engine\Rgl\rglTerrain.cpp:781
Expression: vista_record_.tileset_ != nullptr

[01:13:22.241] #TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:13034621
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:1367283
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:746330
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:6279401
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:6283231
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:2844163
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:2984614
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:3797079
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:3796776
#TaleWorlds.Native.pdb@{30C0885592104AD1A79DA2579BF0DF01} (1): 0:3801431
#ucrtbase.pdb@{152B3C4F5E1CE0FE6BC36E9F0F2B10E6} (1): 0:138162
#kernel32.pdb@{9CF2BCBC4D0E03503C68E569FAA6DC93} (1): 0:94260
#ntdll.pdb@{CDE75D039306834203EBD8D4E7D50369} (1): 0:337489
-----------------------------------------------
#TaleWorlds.DotNet.AutoGenerated.pdb@{776ACEC2D6B94B529BBD45161746B40C} (1): 100663315:0

[01:13:41.213]
<##########################################################################################>
Click to expand...
AFAIK the 1.8.0 tools are riddled with debug asserts which refer to files on C:\Development\ that have not been packaged with the download. Inside the editor, you can bypass these assert warnings with ignore, no, always ignore. In my experience these asserts/bugs never appear in game provided you load the game from the game files menu as opposed to loading the game from the tools menu. This is a pain/inconvenience as I also prefer to jump out of the editor and into the game for quick testing without closing the tools and loading the game from scratch. Hopefully TW will fix it soon, they are well aware of the issue.
 
NPC99 said:
AFAIK the 1.8.0 tools are riddled with debug asserts which refer to files on C:\Development\ that have not been packaged with the download. Inside the editor, you can bypass these assert warnings with ignore, no, always ignore. In my experience these asserts/bugs never appear in game provided you load the game from the game files menu as opposed to loading the game from the tools menu. This is a pain/inconvenience as I also prefer to jump out of the editor and into the game for quick testing without closing the tools and loading the game from scratch. Hopefully TW will fix it soon, they are well aware of the issue.
Click to expand...
I tried that already, either the game instantly crashes after pressing ignore or the scene will load but is bugged to high hell
 
belasto said:
What do you mean by that exactly? I fear I didn't get that, sorry
Click to expand...
You should have two launch icons, one for the Tools (where all the assert bugs live) and one for the base game (the non-modders download). Instead of launching the sandbox game from the Tools menu (with editor as the top menu option) you run/test whatever you modded and saved from the non-modding icon (without editor in the menu).
 
NPC99 said:
You should have two launch icons, one for the Tools (where all the assert bugs live) and one for the base game (the non-modders download). Instead of launching the sandbox game from the Tools menu (with editor as the top menu option) you run/test whatever you modded and saved from the non-modding icon (without editor in the menu).
Click to expand...
The test-run isn't the problem, it is loading a scene inside the scene editor/tool. I literally can't even open the scenes I am trying to edit
 
belasto said:
The test-run isn't the problem, it is loading a scene inside the scene editor/tool. I literally can't even open the scenes I am trying to edit
Click to expand...
That only happens to me, if I make the wrong sequence of responses. As I said originally, the correct sequence to bypass an assert warning is ignore (to the first pop-up), no (to the second pop-up) and always ignore (to the third pop-up). Always works for me.
 
NPC99 said:
That only happens to me, if I make the wrong sequence of responses. As I said originally, the correct sequence to bypass an assert warning is ignore (to the first pop-up), no (to the second pop-up) and always ignore (to the third pop-up). Always works for me.
Click to expand...
Lucky you,
as I said, when I do that the scene is bugged (terrain doesn't load or has the wrong texture)
 
NPC99 said:
Terrain for TW scenes will only load in the editor for those few examples where they included \SceneEditData\terrain_ed.bin files in the download. In 1.8.0 the vista texture for \Sandbox\Main_map is white in the editor (ok in game). I thought you were loading your own scenes.
Click to expand...
Oh I see,
No no I was loading my own scenes too. In my own scenes the game wouldn't let me do anything (Error spam no matter what and bugged terrain) But thanks for the clarification on the sandbox/main map
 
belasto said:
Oh I see,
No no I was loading my own scenes too. In my own scenes the game wouldn't let me do anything (Error spam no matter what and bugged terrain) But thanks for the clarification on the sandbox/main map
Click to expand...
The error spam in your own scenes is probably re the decal atlas bug in 1.8.0. Every decal throws these warnings but only for those close to the camera. I tend to sweep the camera around the scene and always ignore the warnings until eventually, I've got them all and no more spawn. Hopefully, Taleworlds next patch will resolve these problems.
 
NPC99 said:
The error spam in your own scenes is probably re the decal atlas bug in 1.8.0. Every decal throws these warnings but only for those close to the camera. I tend to sweep the camera around the scene and always ignore the warnings until eventually, I've got them all and no more spawn. Hopefully, Taleworlds next patch will resolve these problems.
Click to expand...
The patch came, no fix in sight :/
 
You must log in or register to reply here.
Back
Top Bottom