i was finally playing vo after computer problems and it just crashed. After about 15 mins. No messages or nothing. I restarted and got back into the game and it just froze. I switched to windows and it showed a Lua error in another window. I remembered that i had some plugins that were old that i didn't upgrade.

I know this is my fault i should have remembered, but I also think the game shouldn't just crash it should tell me why its crashing.

just a suggestion.

I also think the game shouldn't just crash it should tell me why its crashing

Your understanding of a software crash astounds me.

It crashed. Because of a bug. It can't tell you why it's crashed. Because it IS crashed.

It's like saying "WTF YOU DIED AND DIDN'T TELL ME WHY!?".

I was going to respond to this earlier this morning, but changed my mind when I couldn't think of a polite way to do so. But upper case set the bar, so:

The game DOES tell you why it crashed, or at the very least, where it crashed in the code. That's what the slew of 0xDEADC0DE things in your errors.log file is. That's what the big popup is for lua errors.

It's not that the game isn't telling you where/why it's crashing. It's that you, quite simply, are not trained to understand what it tells you when it crashes. Just like most of the other people in the community, save the devs and the interns.

I take the black box approach to this. It crashed, therefore I restart.

Miharu is right. VO gives fairly descriptive error messages, it's just that you don't understand them. Now it might be possible to make VO recover better after a lua error on startup, but that has nothing to do with the detail of the messages(which is pretty good).

I'd wager, in your errors.log(where errors go), it said something along the lines of Lua error: trying to read a nil value, which is caused by the changes from lua 5 -> 5.1

But more importantly, the error is in your errors.log. That's what the errors.log is for.

I think what JestatisBess meant was that the lua error was not in-game and he didn't see it until he went to window-mode. Obviously that's not the best way of showing an error.

For as long as I can remember, lua errors have printed to the console whether or not they triggered a popup window. And as Scuba said, they're in your errors.log either way.

It was not in the game at all. Ray is right i only saw it after i went to the desktop. Yes it was my fault for forgetting to update my plugins.

all I'm suggesting is an error message in the game. Or when it goes to crash reporter it tells me why i crashed.

Not everyone goes to the errors log to see what the error is. Especially a noob. And restarting a dozen times wouldn't have fixed my error.

Like i said just a suggestion. I didn't expect or need all the hostility. Maybe i should post under a new name for now on.

Given it was your fault, consider yourself lucky. Had it been my bug, I would have used the crash to rot13 half your files.

Why settle for rot13 when you can use over rot9000?

That aside, VO doesn't handle lua errors during startup well.