Problem with -show_err

[Encaitar]

The error-checking in BI seems to be a lot less effective (leading to more message-less CTDs) than previously. Don't know if that's relevant to your issue.

[Monkwarrior]

The error-checking in BI seems to be a lot less effective (leading to more message-less CTDs) than previously. Don't know if that's relevant to your issue.

No, it is with RTW 1.5, and it was working perfectly up to one moment, some weeks ago.

Messages about "texture not found" (mistake in the file name or extension) or "hidden resource not found" (mistake in the name: taraS instead of taras), were usual. But now I don't receive any error message, so I must look for them without any help.

[Makanyane]

Not sure about this, but if you're not getting any error messages at all (even with putting deliberate mistake into say a settlement name in descr_strat)

it could be variation on this sort of thing, see here
https://forums.totalwar.org/vb/showthread.php?t=68736

Originally posted by PatWest:
It turns out you were partially correct and thats all I needed to fix the problem. When I removed the Carthaginian faction and fired it up it crashed but this time I got an error message. I forgot to put the building before the level 'and building_present_min_level barracks militia_barracks'. After fixing that it fired up fine. I then added first Carthage and then Carthaginian back in and it worked fine.

for some reason having Carthaginian in was apparently masking the error message.

If you had, some weeks ago, a non CTD'ing error (ie one of that would have given error message when you exited program - despite the fact that it appeared to be working) and that error was somehow masked from appearing on -show_err by another change, it could be that its always still trying to give you that error message first - so you're not getting others ???!

Unfortunately thats probably not that helpful unless you remember very clearly what you were changing when messages stopped appearing.

[Dol Guldur]

Yep, as Makanyane says the errors can sometimes be masked. Try using ALT F4 to quit at certain points to see if anything displays rather than quitting using thenoraml meothod. Campaign folder errors should not kick in until you try to start a campaign and you might get to a previously unreported error message by quitting after game start up (for example).

Having said that, most of my masks have been reported and after commenting the problem out I have got to the second error report. Hard CTDs are normally caused by a serious coding error.

[Encaitar]

I find errors with EDB, or errors with regards to lookup of text (such as character or settlement names) are the most common cause of no-msg CTDs for me.