Jump to content

Using The Log File To Find Bug Issues

!!!!

6 replies to this topic

#1 FREDtheDEAD

    Member

  • PipPipPipPipPipPip
  • The 1 Percent
  • 406 posts
  • LocationSouth Autstralia

Posted 27 November 2012 - 11:57 PM

When talking about CTDs, glitches and performance problems, it doesn't hurt to have a poke about in your omicron.log file in the root directory of your MWO install. There is a backup folder for previous logs, one being created each time the game starts. CPU, GPU, memory and other info is in there as well as errors.

Most people don't seem to know about this file.

If your games are like mine, you will find lots and lots of missing assets, bad textures and "runaway thread" errors.

eg


Spoiler


#2 Al Bert

    Member

  • PipPipPipPipPipPip
  • 247 posts
  • LocationGermany

Posted 28 November 2012 - 07:47 AM

wow - thats interesting! Thanks for the hint. Is there information we should give to the Dev`s from?

#3 InfiniteChaos

    Member

  • PipPip
  • Knight Errant
  • 44 posts
  • Locationis being obscured by ECM

Posted 28 November 2012 - 09:38 AM

What you should be giving the devs when submitting a low FPS bug, black screen of death, ctd, disconnect, yellow screen, completely frozen, etc. are the following files:
  • Omicron.log
  • the folder of the .pak file of the map you encountered the issue on
  • crashdump.dmp
  • dxdiag.txt (of 32bit processes)
  • dxdiag.txt (of 64bit processes)
Make a folder on your desktop and label it as you want. COPY the above files to that folder. IF you don't know how to get your dxdiag info read the spoiler.

Spoiler

Doing so will give you a copy on your desktop. Put both varieties in the folder. Then Right-Click on that folder and compress it using a .zip file extension so that you can 1, make it one file and 2, make it a smaller upload/download.
Attach that file in your email to support@mwomercs.com. Also, in the email provide a description to what occurred, what you were doing immediately before the issue, and any possible steps to correct it.

THEN, delete your crashdump.dmp file. (So, the next time it crashes, it will record the information in it's very own .dmp file. I have found that if there is one already there, it won't update with the details of the most recent crash.)
I also delete my Shaders\cache for good measure as this is rebuilt by the engine upon successful logging in and hitting the "Play" button when you reach the MechLab.

Edited by InfiniteChaos, 28 November 2012 - 09:40 AM.


#4 Al Bert

    Member

  • PipPipPipPipPipPip
  • 247 posts
  • LocationGermany

Posted 28 November 2012 - 02:21 PM

View PostInfiniteChaos, on 28 November 2012 - 09:38 AM, said:

What you should be giving the devs [...].


thanks a lot! Would have been easier though to get these hints by the Dev's themselves in the beginning, when they asked to beta-test :D ...

#5 TigrisMorte

    Member

  • PipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 125 posts

Posted 28 November 2012 - 03:00 PM

View PostNiko Snow, on 28 November 2012 - 09:56 AM, said:

This is great notes guys!

um,
"this is" singular
"notes" plural
Ain't Grammar NZI for the win! Just 'cause. WooHOOO, y'all!

#6 TigrisMorte

    Member

  • PipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 125 posts

Posted 28 November 2012 - 03:03 PM

Grant me the PPCs to destroy the things I cannot change,
Courage to charge the things I can,
And wisdom to know to dodge if the difference in tonnage isn't in my favor.

#7 sycocys

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Moderate Giver
  • Moderate Giver
  • 7,697 posts

Posted 28 November 2012 - 03:22 PM

This info probably should have a sticky or whatever that passes for on this forum. Might be good to toss up something the devs can post/add to on the top portion of all the game related ones so everyone has a quick link to it.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users