216 replies to this topic

[warp103]

Krist Smith, on 16 April 2013 - 01:27 PM, said:

That's why I gave myself an easy out and said "may fix your problems".

It does at least prove that you have all the correct files with no corruption. A good base to start from.

lol well it a good base and thank you for a least feedback and help. But you see my specs no way should the fps i have. I can post the other 3 computer specs or you can look it up here. http://mwomercs.com/...k/page__st__320 . The long and short is ,you are going to lose a lot of people that would love to play but can not. At this time I could not talk any of my friends to play this game. In fact the group I am in on TS redhand we hardly even play anymore, with all the bugs from the April patches.

Edited by warp103, 16 April 2013 - 01:38 PM.

[Krist Smith]

Mokou, on 16 April 2013 - 01:31 PM, said:

Too bad for me, u'r tool didn't work.

Ugh, that ain't good. Did it say something about not being able to find the Bin32 folder?

[warp103]

Krist Smith, on 16 April 2013 - 01:40 PM, said:

Ugh, that ain't good. Did it say something about not being able to find the Bin32 folder?

found and checked as least for me it did

[Mokou]

Krist Smith, on 16 April 2013 - 01:40 PM, said:

Ugh, that ain't good. Did it say something about not being able to find the Bin32 folder?

As u can see.

[Jacob Roamer]

How does one do the dxdiag thing again? Im still DLing the patch but wanted to know in case I have issues.

[Hisashi No Oni]

Three or four games in ten Mech steps into match crash to desktop everything frozen had to reboot. After return to game about ten Mech steps into game match crash to reboot not desktop this time. Come here with sad face and question mark above head.

[Krist Smith]

Mokou, on 16 April 2013 - 01:51 PM, said:

As u can see.

Thanks. Working on a fix now. This is just because it can't auto-determine the install folder. It's a simple fix, should have something new on the CDN in 20 minutes or so.

[HarmAssassin]

I was crashing to desktop in 4 out of 5 game attempts before this patch.

Since the patch I played 3 games before getting a crash to desktop. Will try more, but even a 25% crash rate is not something I will tolerate. I stopped playing entirely during this past week due to the crash rate, returned today to see if it was fixed. If it hasn't been, I'll go back to playing BF3.

[zaknafein elwin]

I encounterd new glitch,
after start the game, Blinking off my mech's HUD per about 10 seconds,
this Problems frequently arise again and again,until end of game.

[Alexandr Britten]

I've played 4 games so far, and crashed to mechlab 3 times... 2 of them were before the animated startup sequence started. Needless to say, I think I'm done with MWO for awhile. This needs to be your PRIORITY over anything else that will make you money, etc. If I can't play the game at all, I'm not putting ANY money into it.

I've tried working with your customer support and it went nowhere. I've already tried re-installing for each of the past 3 patches, and except for 2 weeks ago, it's been consistently crashing. Today has been the worst, I used to be about 33-50% crash rate... now I'm at a 75-100% crash rate.

Make that 4 out of 5, with the last drop being a CTD and not CTM.

Where do I find this 'tool' that everyone is referring to?

EDIT: update and question.

Edited by Alexandr Britten, 16 April 2013 - 02:49 PM.

[PraetorRUS]

Just experienced a new map bug. It was visible all match long and the only way to get rid of it was to disable the hud completely.

Edited by PraetorRUS, 16 April 2013 - 02:53 PM.

[AdmiralBeran]

=========================== PrepareLevel frozencity_night ============================
Initializing default materials...
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/forestcolony_clouddome_a.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/forestcolony_clouddome_a.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/frozencity_night_clouddome_a.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/frozencity_night_clouddome_a.dds]
[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]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop1.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/laser_beam_1x4_lop1.dds]
[Error] locomotion-group not found: animations/mechs/jagermech/lmg_files/flight_fs_1.lmg
[Error] locomotion-group not found: animations/mechs/jagermech/lmg_files/flight_take_off_ltf.lmg
[Error] locomotion-group not found: animations/mechs/jagermech/lmg_files/flight_fs_1_fp.lmg
[Error] locomotion-group not found: animations/mechs/jagermech/lmg_files/flight_take_off_ltf_fp.lmg
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
======== frozencity_night is loaded in 15.7 sec ========
CHAT LANCE- AdmiralBeran to LANCE:
wow, lotta firepower for this lance
CHAT LANCE- AdmiralBeran to LANCE:
moving kappa
CHAT TEAM- AdmiralBeran to TEAM:
two stalkers
*** CSequencedStateHistory<struct SMoveInput>::Update: Warning: Discarding 427 states due to excessive queue size: maxSize=240 ***

Game crashed while viewing other team members after death.

Video setting remain unchanged from any patches, and left on default settings from original install.

Spoiler

Radeon HD 5830, Intel i7 950 @3.07Ghz, 8GB RAM, Windows 7 64bit ult

[AntharPrime]

I regularly play 10-15 rounds plus mechlab tweaking per evening with no heat issues with my laptop. After downloading the new patch and playing 2 rounds my laptop was so hot that I could no longer touch my keyboard. This is no exageration, I was in my 3rd round and had to type a quick "I'm out" warning before leaving as I noticed the heat through my keys. I shut down the game and tested som other games like BF3 an Planetside 2 and didn't have an issue.

With how fast and how hot my PC got in such a short time, I don't feel comfortable even turning on the game for risk of damaging my PC.

Edit: I did send in a support ticket for this as well.

[Alexandr Britten]

I ran the tool and it seems to have fixed my issue. Must give a big thanks to PGI in this case. I can play MWO again! My teammates must beware!

[HarmAssassin]

I give up.

Start game, select mech, click Launch - crash to desktop.
Restart game, first mech is unavailable "in-game", select a second mech, click launch - crash to desktop.
Restart game, first and second mechs are unavailable "in-game", select third mech, click launch - game actually starts. Play 4 minutes, game locks up have to use ALT+CTL+DEL to close process. Restart game, now 3 mechs are tied up unavailable. Select a fourth mech, click launch - crash to desktop.

I'm done.

I'll be back in 2 weeks to see if the next patch has fixed the issue... maybe.

i5-2500K CPU @ 3.30 GHZ (but overclocked higher)
8GB RAM
Windows 7 - 64 bit
GeForce GTX 570 Driver 314.22 (over clocked)

Ran the game fine until 2 patches ago, I can play all other games out there on high or ultra high - but apparently I can't play MWO anymore.

Edited by HarmAssassin, 16 April 2013 - 03:41 PM.

[Wraithlord77]

im crashing mid battle and if i stay any longer than 30 sec in mech bay, ive had 1 full battle since patch only to crash in the mech bay , its gone from crashing once every 5-8 matches to every bloody match, Oh and 3 of the crashes today were complete PC shutdown, blue screen of death....which is new , and no error report , if it was there before the blue screen its not there now.

Realy thinking of putting this game down now ,stability should be OK but getting better at this stage (IMO) but its seems to be stuck and i dont see it being fixed any time soon , i hope im wrong.

What and where is this "TOOL" i keep hearing about ?



Somewhere in deep space aboard the Jumpship "Direwolf"
"Jump the ship , take us to the inner Sphear , let the Return begin"
"Ummm....sorry my Kann , i am unable"
"WHAT!!!!"
"Every time i try i get the same message my Kann"
" We are sorry ,due to unforseen Technical Difficulties the Inner Sphear is un reachable at this time , please try again later or contact our support services."
"Hmmmmm...."

Edited by Wraithlord77, 16 April 2013 - 03:44 PM.

[AntharPrime]

Where can we find this repair tool I keep hearing about.

[Black Templar]

crashes everywhere. every few matches. no error message just a plain freeze and i have to use the task manager to close the game.

[warp103]

Ninjai, on 16 April 2013 - 02:11 PM, said:

They also add your ticket in the QA queue with your DXdiag so the Dev have all the, ticket descriptions, dxdiag, logs and whatnot under one singular bug so it's easy for them to look into. They basically gather as much info from as many different players in on place so the dev don't have to crawl in the forums and ask the questions support would usually do for them.

and yet we have bug that have been around since the closed beta. Mini map.FPS{though it did go up never a min spec getting 30fps},lag shield/teleporting with low ping(under 450),CTD, need I go on.Oh for got weapons damage tranferr{ to the front if firing from behind}

Edited by warp103, 16 April 2013 - 05:09 PM.

[Nidhogg LeFabre]

Ping reads 76-85 in game. No damage given, no damage taken, no zoom capability. Next time it happens, I will try to see my frame rate. Sending DxDiag to support. My ping spiked to 146 for 10 seconds or so, then went back to 86. I can not zoom in, so that tells me I will not give nor take damage. It is NOT my service provider as I am able to play other games without this issue. It is only MWO. I Just died out of bounds without going out of bounds. A fellow mechwarrior suggested I am desinking from the server.