229 replies to this topic

[RedEagle86]

Other than what seems like an exceedingly long amount of time to save a loadout, there seems to be a very consistent bug where you get out of a match and the 'Connecting' circle appears indefinitely.

[Flushot]

Summary: Weapons disappeared when attempting to save loadout
Description: I was just dropping a ton of lrm ammo for a ton of uac 10 ammo. I got an error when I tried to check out and it went back to before I changed anything. I tried again and this time after getting the same error my weapons had all been deleted. Not just unequiped, they were just gone altogether.
Location: Mechlab
Reproduction Rate:
Steps to Reproduce:[color=#00FFFF] [/color]

[color="#00ffff"]Correction, after more playing around, all my clan mechs lost their weapons.[/color]

[MuonNeutrino]

Found a bug with the Timber Wolf hitboxes:

Summary:
The Timber Wolf has a hole in its torso hitboxes that results in no damage being taken when shot in a particular location.

Description:
On the Timber Wolf's right torso, at approximately the location where the second missile launcher would be found on the S variant, shooting the mech with a laser results in no damage being taken. Picture evidence of location here: http://i.imgur.com/r4jEtQg.jpg (notice the damage display is not flashing, despite the mech currently being hit with a laser).

Location:
Timber Wolf right torso hitbox.

Reproduction Rate:
100% over three medium laser shots. My team mates killed the last piloted enemy mech before I could attempt reproduction on the left torso. (I was experimenting by shooting disconnected mechs while my team mates chased the last firestarter.)

Steps to Reproduce:
Find Timber Wolf (prime, in this case). Shoot laser at indicated location on right torso. Observe no damage taken.

Edited by MuonNeutrino, 12 June 2014 - 07:10 PM.

[Ranger Aodhan]

Summary: Sliding Clan mechs
Description: The clan mechs (all of them) seem to move just lightly faster than the legs animate this causes a weird sliding effect. Also, the feet don't conform to the tarrain as well as IS 'mechs.
Location: Everywhere
Reproduction Rate:100%
Steps to Reproduce: Look at a clan 'mech walking from the side

P.S. I did not mean to come off as rude in this critical feedback.

[NEWater]

Can't save any new configurations in the mechlab. There's no point to a "test" when you fail to let your "testers" change the configs of their mechs.

Well done.

[Shepherd]

Summary: crash on "quit match" button
Description: If I die before the end of the match and opt not to watch the end of the match, when I click "quit match" the game crashes and gives a "pure function call error" message.
Location: In my computer?
Reproduction Rate: 100%
Steps to Reproduce: Die in a match, hit escape, click "quit match."

[SolCrusher]

I bugged my Dire Wolf Prime. I had 6 UAC2s on it and full ammo using the B omni pods. I decide to run two LBX20's and 2 SRM6s so I had to change the right torso omni pod to A variant. I configured the mech and put ammo on it. When it saved it failed to save and every attempt after that it will not allow me to save the configuration of the mech.

I had to put all 6 UAC2 back on it, attempt to save it and it loaded my LBX20 config + 2 SRM6s + 6 UAC2s. I removed the UAC2s and then it would save correctly.

I rebugged my dire wolf prime by swapping out omni pods again. Now I can't get it to fix. So DWP is locked. It also stole CBills from me by not crediting me the purchase of LBX20s. The modules are stuck on my DWP as well.

Mech lab stole weapons from me again. Lost another LBX20 and 4 ERML.

Edited by SolCrusher, 12 June 2014 - 07:54 PM.

[Chimerahawk]

SolCrusher, on 12 June 2014 - 07:26 PM, said:

I bugged my Dire Wolf Prime. I had 6 UAC2s on it and full ammo using the B omni pods. I decide to run two LBX20's and 2 SRM6s so I had to change the right torso omni pod to A variant. I configured the mech and put ammo on it. When it saved it failed to save and every attempt after that it will not allow me to save the configuration of the mech.

I had to put all 6 UAC2 back on it, attempt to save it and it loaded my LBX20 config + 2 SRM6s + 6 UAC2s. I removed the UAC2s and then it would save correctly.

Same thing happened to me with regular clan AC/2s on the direwolf-B varient. I put 6 of them on, ammo and all. I switched an omni pod and then stripped the ac/2s, put on other stuff, saved at first, but failed to save again. I took everyone off the mech, saved, and it worked again.

[Docta Pain]

IS LRMs seem to hit the ground 10% of the time on the first firing right after the reticle goes red for a lock... maybe something to do with the lock-on denial module, even though I could see the target???

[Thalynos]

Issue changing loadout on a Timberwolf C after having saved the load out with one half ton of S-SRM ammo. Attempting to remove the ammo results in those changes being reverted after attempting to save.

[Sheridan Mackison]

Summary: Kitfox-S errors when saving OmniPod changes
Description:
Location: Mechlab
Reproduction Rate: 3 times in a row
Steps to Reproduce:[color=#00FFFF] select arm OmniPod that allows ECM, add 3 pieces of equipment including ECM then try to checkout[/color]

Summary: Error saving changes to Nova-S
Description:
Location: Mechlab
Reproduction Rate:
Steps to Reproduce:[color=#00FFFF] [/color]

[Mc JR]

Hello,

Though out the play test I've been testing all of the weapons with the Timber Wolf and the Dire Wolf,

Lasers:
I love the lasers and can't find anything wrong with them, and really love the path that was taken with them. I don't normally say this but good job PGI .

LRMs: I like the lrms but they have a arc problem I can be locked on a target and at times every other set will drop right in front of me. If this is fixed then boom another goo job PGI.

SRMs: Other than HRP problems great job.

and this leaves AC:
I like the rate of fire and all the options for UAC but here's the thing. A IS UAC5 shoots 2 shells that both deal 5 dmg. witch is great.

Clan UAC 5 is a different story. Shooting 3 shells for a total of 5 dmg. this is a huge disadvantage for anyone dropping with clan UAC5 or UAC anything take. Take the UAC's to 2 shells at UAC#, so UAC5 = 2 shells at 5 dmg each, and so on for each UAC.

Other than that good job and can't wait for the drop.

[Sheridan Mackison]

Summary: Unknown Error when exiting Mechlab
Description: Mech = Nova-S
Location: Leaving Mechlab
Reproduction Rate:
Steps to Reproduce:[color=#00FFFF] [/color]

[Solahma]

Summary: Dire Wolf not taking any damage on the back. Possible transfer to front of mech.
Description: I turned my back to an Adder with PPCs and a Timber Wolf with SRMs, Pulse lasers, and other. All of the damage I took transferred to my front even though they were directly behind me. Did not notice a single flashing section on my rear components. Meanwhile my front component took a lot of damage. There were no mechs in-front of me to cause the damage.
Reproduction: none

[monk]

Summary: Game started, but hud failed to load and I was in some sort of free look mode. Couldn't figure out much to do but open the console and then quit out. Quitting the match resulted in a crash to desktop (Cry error pure function call or something - sorry I'm tired)
Description: Started my second match using the TDR-5S for the second time. Game didn't load how it normally does. I was presented with this screen instead of the ready up page:

Image 1

Game eventually started and I was able to fly around using wasd a bit but could not manage to get things to load. Eventually hit the traditional console button and it popped down and saw this:
Image 2

After hitting quit match the game crashed to desktop.

Location: Ready up screen and during match.
Reproduction Rate: Haven't attempted to reproduce. Unsure what caused it.
Steps to Reproduce: Haven't attempted to reproduce.

Edited by monk, 12 June 2014 - 07:54 PM.

[Thorn0616]

Quitting a match after you die crashes the client is happening to me as well. Also having a lot of issues saving mech changes.

Edited by Thorn0616, 12 June 2014 - 07:53 PM.

[JHackworth]

tried to save a loadout for the Dire Wolf Prime. It gave me an error, and refused to save, then it showed me a layout of the DW with most weapons unmounted, and I found the other variants and other mech loadouts were also all equally fubared. Had to relog in

[Docta Pain]

I think the Daishi has a damage multiplier problem in the CT front. I had just killed 2 Daishis in my 3AC5 Jag, when I ran out of ammo and another one attacked me. It's CT armor was not quite dark orange and I fired 2 MedLas squarely into it's CT and it removed the rest of its armor and went yellow internals. It took waaaaay too much damage for a pair of MedLas. Anyway, 3 Daishi kills and another clan mech in a single match with a JAG... I fear no clanner... unless they have the screen-shake-of-death-lrms that is.

[dak irakoz]

Summary:Kit Fox Foot Animation
Description:, spahsUnlike other mechs like the Nova, the feet of the kit fox seem to be rigid, phasing slightly into the ground in the front and kicking up in the back, rather than curling.
Location: In matches
Reproduction Rate: 100%
Steps to Reproduce:Be in a match and look at a kit fox's feet.

Edited by dak irakoz, 12 June 2014 - 08:10 PM.

[RegalR3]

Here's a list of stuff that went wrong with me
1:Every time I quit a match, i would get a error called "pure function call" and the game clinet closes
2:Sometimes when I try to login it fails with a "unknown error"
2.5:After a few games the client would get an unknown error and jump back to the login screen
3:I launched with one mech but dropped with another.
4:My pilot will look at a random part of the cockpit (this may be from some new impact subroutine you added in but I thought i would let you know just incase)
5:The green smoke is back.
Other than that it was great, Keep up the good work and I look forward to monday