Jump to content

Mechlab Does Not Load

Bug Report

10 replies to this topic

#1 zudukai

    Member

  • PipPipPipPipPipPipPipPip
  • Trinary Star Captain
  • Trinary Star Captain
  • 1,707 posts

Posted 10 May 2014 - 07:09 PM

i was getting BSOD's only while playing MWO, they told me my IGFX driver was not cooperating with direct x 9, and 10.

i re-installed mechwarrior 6-8 times now in two different hard drives and both running the repair tool and disabling my anti-virus during install nor running everything possible as admin has made any observable difference.

the omicron log says; "
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop0.dds' compressed texture is dangerous (only single mip)
[File=textures/particles/weapons/laser_beam_1x4_lop0.dds]

[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/ppc_beam_b.dds' compressed texture is dangerous (only single mip)
[File=textures/particles/weapons/ppc_beam_b.dds] "

and no amount of repair tooling or re-installing seems to be repairing this, also, i have deleted both texture.pak's and re-downloaded them with no difference.

dxdiag does not identify any issues.

re-re-reinstalling multiple graphics driver versions seem to not be making any difference either.

Spoiler


this is as far as my game will load.
http://imgur.com/dsvnOJw

Edited by Marvyn Dodgers, 13 May 2014 - 03:25 PM.


#2 Deathlike

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • Littlest Helper
  • Littlest Helper
  • 29,240 posts
  • Location#NOToTaterBalance #BadBalanceOverlordIsBad

Posted 11 May 2014 - 10:00 AM

Some of those omicron errors are normal (it's up to PGI to fix or suppress the errors).

With that said.... if you're using the onboard Intel graphics to play the game, you really need a gaming video card...

#3 zudukai

    Member

  • PipPipPipPipPipPipPipPip
  • Trinary Star Captain
  • Trinary Star Captain
  • 1,707 posts

Posted 11 May 2014 - 10:56 AM

View PostDeathlike, on 11 May 2014 - 10:00 AM, said:

Some of those omicron errors are normal (it's up to PGI to fix or suppress the errors).

With that said.... if you're using the onboard Intel graphics to play the game, you really need a gaming video card...

my gtx460 died about a month ago, and i cannot afford a replacement... i ended up reinstalling my OS because i was out of ideas..

#4 zudukai

    Member

  • PipPipPipPipPipPipPipPip
  • Trinary Star Captain
  • Trinary Star Captain
  • 1,707 posts

Posted 11 May 2014 - 01:13 PM

after reinstall it still does not load, still same one mip texture problem, :D (though i cannot read the crashdump.dmp) i am totally lost now. what even COULD be causing this issue ??? :ph34r: :D

#5 zudukai

    Member

  • PipPipPipPipPipPipPipPip
  • Trinary Star Captain
  • Trinary Star Captain
  • 1,707 posts

Posted 13 May 2014 - 01:28 PM

still unable to run MWO, other games play fine; hawken, loadout, dead space, C&C 3... etc...

repair tool "completed" with no change many times, sometimes finding issues in the shader.pak's, but the game crashes without an error though there is a crash dump, i cannot read it (and thusly has sent it to support) i have deleted the entire user file along with system.cfg and override, again with no change.

Change of DNS yields no results.

i have Cogeco cable with 2mbps down 1mbps up
a Dlink Dir632, corded LAN, 2 PC's.
there is no error message/pop up, the program just self terminates all threads.
i am unable to get farther then a successful login, the game does not proceed farther then here
Spoiler

but after 6 re-installs and an OS re-install along side another 2 installs no change yet...

all my drivers are up-to-date and current, and i tried older drivers to try compatibility.

all MWO related executables are forced admin, disabled desktop themes, i also tried to use XP sp3 compatibility mode with no change in behavior.

awaiting support replies...

#6 Marvyn Dodgers

    Member

  • PipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 1,859 posts
  • LocationCanuck transplanted in the US

Posted 13 May 2014 - 02:45 PM

Sorry, you referenced awaiting support replies but I don't seem to see you saying you have submitted a support ticket with related files attached - have you?

#7 zudukai

    Member

  • PipPipPipPipPipPipPipPip
  • Trinary Star Captain
  • Trinary Star Captain
  • 1,707 posts

Posted 13 May 2014 - 03:10 PM

View PostMarvyn Dodgers, on 13 May 2014 - 02:45 PM, said:

Sorry, you referenced awaiting support replies but I don't seem to see you saying you have submitted a support ticket with related files attached - have you?

yes i have, i am simply following up with my earlier post, hoping that perhaps someone may have some ideas, or if i find a solution, people with a similar issue may also find a resolution through my success, or failure.

#8 Grendel408

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 2,611 posts
  • LocationBay Area, California

Posted 13 May 2014 - 03:15 PM

Yeah dude... submit a ticket with Support, send them your dxdiag file, any crashdumps, your system specs, etc as they request... but I seriously think it's your on-board GPU built onto your motherboard... always a bad thing to use for graphical/memory intense games like MWO or BF4, etc... I've got the same processor as your i7, half the RAM (8g total), and a Radeon HD 6850 GPU... on-board GPUs are evil... pointless, should be disabled... oh snap... check your system bios too lol BSOD's are usually due to instability in system resources and hardware, or conflicting hardware confusing the hell out of your operating system.

Edited by Grendel408, 13 May 2014 - 03:17 PM.


#9 Grendel408

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 2,611 posts
  • LocationBay Area, California

Posted 13 May 2014 - 03:23 PM

Also... is your old GPU still installed inside your PC, while you are using the on-board GPU?

#10 zudukai

    Member

  • PipPipPipPipPipPipPipPip
  • Trinary Star Captain
  • Trinary Star Captain
  • 1,707 posts

Posted 14 May 2014 - 05:43 AM

View PostGrendel408, on 13 May 2014 - 03:15 PM, said:

oh snap... check your system bios too lol BSOD's are usually due to instability in system resources and hardware, or conflicting hardware confusing the hell out of your operating system.

View PostGrendel408, on 13 May 2014 - 03:23 PM, said:

Also... is your old GPU still installed inside your PC, while you are using the on-board GPU?
is there something specific i can (or need to) look for?

no i pulled it out and chucked it out of my window. :) (not really)

#11 Grendel408

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 2,611 posts
  • LocationBay Area, California

Posted 14 May 2014 - 10:29 AM

I was just thinking that if you had your old GPU still installed but not being used while the on-board was in use could have caused your BSOD's due to driver/resource conflicts, disabling from the bios and system manager in windows would prevent that... but since you've got it removed it makes me wonder what else is happening to cause your BSOD's.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users