Jump to content

Mwo Crashlog


3 replies to this topic

#1 G4LV4TR0N

    Member

  • PipPipPipPipPipPipPip
  • The Solitary
  • The Solitary
  • 911 posts

Posted 28 October 2017 - 07:50 AM

I have been checking omicron.log files after each crash and came to conclusion that few lines are very common. I do wonder is it only me getting those lines. Here are examples:

This one is most common, almost always there. But it could also be very generic error.

Quote

[Error] <Flash> Missing font "Times New Roman" in "_level0.mcMain.mcCurrentLayout.mcLayout.mcInGameChat.translate".


This one comes in pair with previous one, although not always.

Quote

[Error] <Flash> Import error: GFxResource 'mcCloseBtn' is not exported from movie '..\UIButton.swf'


This one is somehow specific, not sure the reason. It's almost always 'jenner', albeit I've seen 'archer' and 'vindicator' show up there too. But they are always paired with 'jenner', that is in every log I got.

Quote

[Error] CryAnimation: no character created: objects/mechs/jenner/cockpit_standard/jenner_a_cockpit_standard.cdf


#2 Tarl Cabot

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Tai-sho
  • Tai-sho
  • 7,828 posts
  • LocationImperial City, Luthien - Draconis Combine

Posted 28 October 2017 - 11:45 AM

Check the logs after logging out where you do not crash so you can have a reference point because those are normally generated..

Logs are always being generated. All of my logs have those lines except for the cockpit_standard there is one for the jenner and for the archer, two mechs I have not piloted in a long time. Those lines only show up when I have dropped into combat. They could be generated when I am spectating in a jenner or archer.

Edit.

With that said, driver conflict or system files corrupted/missing. Memory that is not stable. Most bios today are setup for auto on everything. That works til it doesn't which makes troubleshooting a royal pain. Unfortunately there is no Easy Fix button.

Example on system file issue. One player was constantly getting a GPU driver reset while playing MWO, of course directx11. What allegedly fixed his problem is running the directx 9c June 2010 redistribution package to install/reinstall direct9c, since there are calls made to those modules.

https://mwomercs.com...device-removed/

And it is stuff like this that prevents PGI from replicating some issues that crop up. And since PGI does most of their troubleshooting via email, we barely get a glimpse of the issues they see then feedback from the users when resolved.

Edited by Tarl Cabot, 28 October 2017 - 05:28 PM.


#3 G4LV4TR0N

    Member

  • PipPipPipPipPipPipPip
  • The Solitary
  • The Solitary
  • 911 posts

Posted 28 October 2017 - 07:43 PM

Indeed

Quote

[Error] <Flash> Missing font "Times New Roman" in "_level0.mcMain.mcCurrentLayout.mcLayout.mcInGameChat.translate".
shows all the time, even when I don't crash. Others don't.

#4 NARC BAIT

    Member

  • PipPipPipPipPipPipPip
  • Ace Of Spades
  • 518 posts
  • Twitch: Link
  • LocationAustralia

Posted 28 October 2017 - 11:20 PM

those are more like 'developer warnings', than actual info about what crashed, if you really want to have any hope of seeing whats going on, at the point of crash, you need to increase the logging verbosity, and if that doesn't reveal anything, you might have to log the UI actions to 'catch' the error, the key you need to add is
log_WriteToFileVerbosity = 4
or over the top ui logging is
gfx_uiaction_log = 1
... log files will grow *VERY* quickly, so the quicker you can make it crash, the less megabytes you need to skip past before getting to the error .... oh and normally' if you set the verbosity to 0, it wont give you those 'additional warnings' ....





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users