I've been observing this behavior for quite some time. It is simply impossible to list all the situations when the game crashes without writing to the log. There were a lot of them. I see the largest number of crashes when the path to the rules file is incorrectly set. Writing big mods wasn't the easiest thing before, but now it's become much more difficult. My accumulated experience helps me so far, but I can only sympathize with the rest of the beginners.
#The debugger stopped catching some of the errors.
23 messages ยท Page 1 of 1 (latest)
Misspelled file paths in weapons for the shot files are one of these reportless crashes
Yes, and this also applies to I/O operations, and it looks like the library with these functions has been excluded from debugging, which leads to a missing log.
As in, the game just closes without producing an error dialog or error in the log file?
Yes.
Now that I'm more awake, the game crashed without the pop-up and the log just ended.
Just add or remove a directory level pointing to the shot file.
If I recall correctly, this happened to a part with a modified manipulator beam
If you have a way to reproduce this, please send it to us.
use this!
all I did was change one line BeamEmitter1 : <./Data/shots/nono/manipulator_beam/manipulator_beam.rules> I just added nono to the file path
here's the log file
I wrote earlier that this failure occurs in different situations, they have only one thing in common - the path is incorrectly set. Just running the game without mods, but with the wrong path to the Part file:
<../base_part_terran_.rules>/Part
will lead to the same result.:- the game crashes at startup without logging in.
I have an other one to add to this
You can create an other debuggerless crash by using the same Mode in toggle components:
ForwardThrustToggle
{
Type = ModeToggle
Mode = ForwardReverseToggle
OnMode = 0
}
ForwardThrustComponents
{
Type = ToggledComponents
Toggle = ForwardThrustToggle
IncludeInBlueprints = dynamic
Components
{
Turret: &~/Part/Turret
{
Rotation = -90d
}
}
}
ReverseThrustToggle
{
Type = ModeToggle
Mode = ForwardReverseToggle
OnMode = 1
}
ReverseThrustComponents
{
Type = ToggledComponents
Toggle = ReverseThrustToggle
IncludeInBlueprints = dynamic
Components
{
Turret: &~/Part/Turret
{
Rotation = 90d
}
}
}
no wait, Mode should be the same. Ok, either way, I caused a debuggerless crash with this and just commenting this out allows stuff to run right
Not sure if this will help figureout why the debugger isn't even opening on crash, but here are the toggle rules
{
Action = AddMany
AddTo = "<./Data/gui/game/parts/part_toggles.rules>/PartToggles"
ManyToAdd
[
// On/Off
{
ToggleID = "fwdrev"
Style = Switch
ShowWithShipCommands = true
Choices
[
// Off
{
ChoiceID = "fwdthrst"
ButtonToolTipKey = "PartToggles/forwardho"
//DefaultHotkey = [P]
ButtonSprite
{
Texture
{
File = "icons/forwardf.png"
MipLevels = 2
SampleMode = Linear
}
}
}
// On
{
ChoiceID = "revthrst"
ButtonToolTipKey = "PartToggles/reverseho"
//DefaultHotkey = [P]
ButtonSprite
{
Texture
{
File = "icons/reverse.png"
MipLevels = 2
SampleMode = Linear
}
}
}
]
}
]
}
Eitherway, no debugger info makes it hard to figure out what I'm doing wrong.
So I hope this also helps figure out why the debugger isn't even opening on crash
ok, I figured out my crash. It was missing Components in the inheritance filepath. So this is an other example of debugger not opening up on a crash where a path is wrong.
Looks like in some cases writing the error message for the missing path can cause another of the same error, ad infinitum. Should be an easy fix. Thanks!
Welcome!
I would like to fix this error as soon as possible, the complete lack of information about the cause of the failure is already beginning to worry. It is especially difficult to find an error when adding large amounts of code.
Didn't Celeste say:
Looks like in some cases writing the error message for the missing path can cause another of the same error, ad infinitum. Should be an easy fix. Thanks!
This was only two days ago (or one day ago, when you sent that message) so I wouldn't think it's time to start demanding an ASAP release for it.
I've already raised this issue, (#1451346641754914816 message ), and this is not even one month, and this message has been hanging for the second week. I am well aware that this message may get lost among others, but this does not prevent me from hoping for a quick solution. ๐
I fixed the issue on the same day I sent my last message. When it will be released is up to Walt, though at the latest it'll be with the next non-hotfix update
yeah wrong inheritance do cause such crashes